Hi Roman,

I was just having a look at the Testdrivers, and compiled a version of Mame32 with all of them activated. There are 3 roms that are NOT reported in ClrMamePro as being incorrect, but they ARE being reported in my Mame32. The results of the audit in Mame32 is as follows :

shootgal: sg-01-0 2048 bytes NOT FOUND
CRC(f055a624) SHA1(5dfe89d7271092e665cdd5cd59d15a2b70f92f43)
secretab: sa_05.bin 65536 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(d7978eeb)
secretab: sa_03.bin 65536 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(d7978eeb)
secretab: sa_06.bin 65536 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(d7978eeb)
secretab: sa_04.bin 65536 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(d7978eeb)
jsk : jsk-u4.bin 131072 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(6c5050cb)
jsk : jsk-u24.bin 131072 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(6c5050cb)
jsk : jsk-u38.bin 131072 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(6c5050cb)
jsk : jsk-u52.bin 131072 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(6c5050cb)
jsk : jsk-u72.bin 131072 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(6c5050cb)
jsk : jsk-u71.bin 131072 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(6c5050cb)
jsk : jsk-a0.bin 4194304 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(88f591db)
jsk : jsk-b0.bin 4194304 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(88f591db)
jsk : jsk-c0.bin 4194304 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(88f591db)
jsk : jsk-d0.bin 4194304 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(88f591db)
jsk : jsk-s0.u65 2097152 bytes INCORRECT CHECKSUM:
EXPECTED: CRC(00000001)
FOUND: CRC(3767e925)

I was just wondering why ClrMamePro is not reporting the incorrect CRC's (does it ignore 00000001's?) and why the 'shootgal' missing rom is not being reported. There are no SHA1 values set in the source for 'secretab' and 'jsk', just CRC's of 00000001, so how does it miss them?

No big deal or anything, just interested.

Just furthur to this, I grabbed your datfile for the testdrivers (0.72u2) from your site.

The missing rom from 'shootgal' was detected, so it must just be something to do with the processing of the -listinfo / -listxml output, I guess.

Also, it came up with 12 roms that are no longer testdrivers :

bombrman
defender
gokuparo
goldmedl
kof2001
kov
liberatr
rranger
slyspy
smgolf
vsbball
xmen

> bombrman
> defender
> gokuparo
> goldmedl
> kof2001
> kov
> liberatr
> rranger
> slyspy
> smgolf
> vsbball
> xmen


They are included because they are needed parent sets for some testdriver sets.

Roman Scherzer
ClrMamePro

> secretab: sa_05.bin 65536 bytes INCORRECT CHECKSUM:
> EXPECTED: CRC(00000001)

As you can see your datfile has some wrong entries. The crc = 1 has to be converted to "crc 0" or "flags nodump".

Roman Scherzer
ClrMamePro

> > bombrman
> > defender
> > gokuparo
> > goldmedl
> > kof2001
> > kov
> > liberatr
> > rranger
> > slyspy
> > smgolf
> > vsbball
> > xmen
>
>
> They are included because they are needed parent sets for some testdriver sets.
>
> Roman Scherzer
> ClrMamePro
>
Ahhh....no probs! That makes sense!

Thanks.