Firstly, I am sorry if this is the worng place to post this.

I have a complete 0.115u1 ROM and CHD collection acording to clrmame using both the logiqx DAT and a DAT generated by clrmame from the Mame32.exe. Everything is totally up to date a 100%. The problem I have is that Mame32 fails the Audit of two CHD based games, San Francisco Rush 2049 and Guitar Freaks 2nd Mix Ver 1.01 (GQ883 VER. JAD).

Here is the Audit report from Mame32:

San Francisco Rush 2049
sf2049 : sf2049 - NOT FOUND

Guitar Freaks 2nd Mix Ver 1.01 (GQ883 VER. JAD)
gtrfrk2m: gq883jad.u1 (132 bytes) - NEEDS REDUMP
gtrfrk2m: gq883jad.u6 (8 bytes) - NEEDS REDUMP
gtrfrk2m: 929jbb02 - NOT FOUND

Do you have any idea why Mame32 can't find the files, but clrmame checks out okay? I have checked all files and they are definitely there.

Any ideas?

I wouldn't trust MAME's audit functions. They were way too buggy in the last years.

'needs redump' simply means that the file is flagged (in the MAME database) as bad_dump, so nothing to worry about. Cmpro can optionally show bad_dumps as well.

So it looks like MAME32 doesn't find two chds on your system (929jbb02.chd and sf2049.chd) but I can't tell you why. You can still do a chdman -verify on them (or enable cmpro's checksum->chd unpack option) to verify the chds.



Roman Scherzer

> I wouldn't trust MAME's audit functions. They were way too buggy in the last
> years.
>
> 'needs redump' simply means that the file is flagged (in the MAME database) as
> bad_dump, so nothing to worry about. Cmpro can optionally show bad_dumps as
> well.
>
> So it looks like MAME32 doesn't find two chds on your system (929jbb02.chd and
> sf2049.chd) but I can't tell you why. You can still do a chdman -verify on them
> (or enable cmpro's checksum->chd unpack option) to verify the chds.
>
>
>
> Roman Scherzer
>
Thanks Roman. I managed to get Mame32 to see both games by re-downloading the two CHD's. Even though they were exactly the same file size and had exactly the same files as the ones I already had, Mame32 now audits them without error.

> same files as the ones I already had, Mame32 now audits them without error.

Most likely an internal datastructure error in the chds.

Using clrmamepro's checksum->chd unpack and check sha1/md5 option should have listed the chd as bad too.


Roman Scherzer

> > same files as the ones I already had, Mame32 now audits them without error.
>
> Most likely an internal datastructure error in the chds.
>
> Using clrmamepro's checksum->chd unpack and check sha1/md5 option should have
> listed the chd as bad too.
>
>
> Roman Scherzer
>
I'm doing this as I type this reply. Will let you know how I get on.