Mame core freeze

Libretro Cores
#21

thanks guys, I will try your advice. You are really kind, thanks

1 Like
#22

I tried your advice but the microblocks continue. The roms are on an external hard disk and when the hard disk microblocks occur the light starts flashing as if it can no longer read them. I changed the hdd by moving the roms to a new one I just bought and connected to another USB socket on the PC. Is it possible that only the mame roms have problems being read from an external hdd? I’ve been using Retroarch for many years and this problem only with the roms mame, does it seem impossible to me?

#23

It might happen if MAME needs to read something at runtime, like maybe a game with chd. It shouldn’t happen on crime city.

#24

No. If the game works fine with MAME standalone, it should work fine with core. MAME core on RetroArch works fine, I have tested it on several devices.

The problem lies in the configuration.
I trust you reset the configuration. If you are not sure, the best thing to do is to delete the “retroarch.cfg” files and the “config/MAME” folder.
You’re going to be starting from scratch, but it’s the fastest way to unload a bad configuration.

If the problem continues, the frontend configuration may be affecting it. Try using RetroArch directly to see if the error happens.

+info: The game was included in 0.37b3 (0.39) ,since 0.100u4 it has good emulation and the last change was in “0.262”, minor changes.
Version 0.246 was the last modification of the game set, since then it has remained unchanged.

This is what you will find inside the zip, it would not hurt to check the crc or sha1, to be absolutely sure that the game is not corrupted.

Crime City (World) » crc & sha1 
<machine name="crimec" sourcefile="taito/taito_b.cpp">
     <description>Crime City (World)</description>
     <year>1989</year>
     <manufacturer>Taito Corporation Japan</manufacturer>
     <rom name="b99-07.40" size="131072" crc="26e886e6" sha1="b7d0024a084216c1139eb6705f1b8143902cbed3" region="maincpu" offset="0"/>
     <rom name="b99-05.29" size="131072" crc="ff7f9a9d" sha1="c1897a141eea423879d2792640a9ee85636ed5be" region="maincpu" offset="1"/>
     <rom name="b99-06.39" size="131072" crc="1f26aa92" sha1="10ab253812db83204c136d01d865063a2210cb92" region="maincpu" offset="40000"/>
     <rom name="b99-14.28" size="131072" crc="71c8b4d7" sha1="55068c9cac75200f564b10f98f322e30aaa6849e" region="maincpu" offset="40001"/>
     <rom name="b99-08.45" size="65536" crc="26135451" sha1="651c77285eb12a13a2fe4069031c6f01150ecba4" region="audiocpu" offset="0"/>
     <rom name="b99-02.18" size="524288" crc="2a5d4a26" sha1="94bdfca9365970a80a639027b195b71cebc5ab9c" region="tc0180vcu" offset="0"/>
     <rom name="b99-01.19" size="524288" crc="a19e373a" sha1="2208c9142473dc2218fd8b97fd6d0c861aeba011" region="tc0180vcu" offset="80000"/>
     <rom name="b99-03.37" size="524288" crc="dda10df7" sha1="ffbe1423794035e6f049fddb096b7282610b7cee" region="ymsnd:adpcma" offset="0"/>

The ideal is to use a rom manager, but that’s a bit more advanced, although… :thinking:

#25

updated the core to 0.262 and maybe it’s a coincidence but I played again from start to finish without any problems. I’m not sure I’ve solved the problem, maybe it’s a coincidence, I’ll do more tests

1 Like