Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All Threads*Show in Threaded Mode


Subjecttrally question new Reply to this message
Posted byMrPib
Posted on04/30/04 09:58 PM



Hi. I first want to thank Roman for ClrMame. It's a fantastic proggie. Now onto my question. I have Mame32 .81u9 and ClrMame 3.31 installed, and I had ClrMame create the .dat file from Mame32. ClrMame showed that I had all u9 roms (and chds), but a Mame32 audit showed that Thrash Rally was missing two roms (038-c3.bin and 038-c4.bin). [Mame also complains about are51, but I understand that that's being corrected in Mame]. I downloaded a fresh trally.zip, which has those two roms. Mame32 now OKs trally, but ClrMame flags them as unneeded. My question is, how can Mame32 and ClrMame have different ideas about trally, when ClrMame's data file is *from* Mame?

Thanks,
Pib





SubjectRe: trally question Reply to this message
Posted byRoman
Posted on05/03/04 03:44 AM



> Hi. I first want to thank Roman for ClrMame. It's a fantastic proggie. Now
> onto my question. I have Mame32 .81u9 and ClrMame 3.31 installed, and I had
> ClrMame create the .dat file from Mame32. ClrMame showed that I had all u9 roms
> (and chds), but a Mame32 audit showed that Thrash Rally was missing two roms
> (038-c3.bin and 038-c4.bin). [Mame also complains about are51, but I understand
> that that's being corrected in Mame]. I downloaded a fresh trally.zip, which
> has those two roms. Mame32 now OKs trally, but ClrMame flags them as unneeded.
> My question is, how can Mame32 and ClrMame have different ideas about trally,
> when ClrMame's data file is *from* Mame?
>
> Thanks,
> Pib
>



1) area51 -> this is a mame bug, wait for u10/.82
2) trally -> Clrmamepro uses all data which the mame.exe exports or you got in a datfile. If trally is marked as unneeded, it's unneeded. Always trust clrmame over any mame audit. The mentioned files are needed though, so either you're using a wrong datfile or the files you've downloaded are the wrong ones (don't match crc32). There were a lot neogeo c-file changes lately. Be sure you always scan with all check options enabled and be sure at least checksum->crc32 is enabled.

Roman Scherzer
ClrMamePro


View All Threads*Show in Threaded Mode