Re: Why does ClrMamePro not say that my 929jbb02.chd is corrupt?

Hmmmm...let's see...2 seconds to look at the summary or 5 minutes to go through the scan window...which is easier?

The tree got much more details and is the prefered one. No tree entry -> you're done.


Also, if a CHD is corrupt, then the checksums will be wrong as well and should show up as such.

Erm...no. A corrupt CHD is a corrupt chd. CHD (= compressed hunks of data) is a container for an image (disc, hd, whatever) which is header + sector maps + compressed data. You can even have a corrupt chd, while the included compressed data is 100% ok and does match the checksum which is given by the database.
The checksums given by the database are for the decompressed image and not the chd itself.



I really don't understand the logic you're applying to this and the invaders sample thing. Not making a lot of sense.


It does make sense:

- a set got a "sampleof" entry which points to a non-existing sampleset (in this case invaders). Cmpro asks you if you want to remove it. If you say yes, the "sampleof" entry is removed.
- then cmpro detects that the parent romset (kamikaze in the example) got a similiar sample file structure as the set (astinvad). So cmpro asks you again if you want to adjust the setting to have a "sampleof" which points to kamikaze.
In either way, you as end user decide what to do with the bad structured database which comes from mame.
.