> > ...more on monday...when I'm at home and can look in the source ;)
>
>
> ok...I checked the values with 78u3 now...
> a pure, not modified -listinfo of 78u3 gives 175 nodumps and 127 baddumps.
> ClrMamePro reports 146 nodumps and 156 baddumps.
>
> The reason for the less nodumps are:
> - double entries in -listinfo were removed
> - several 0-crc32s were corrected to gooddumps to avoid overwriting
>
> The reason for the more baddumps are:
> - several nodump were converted to baddump to avoid overwriting
> - cmpro counts the baddump flag and inverted crc32s as baddumps (since they were
> marked that way in older mame versions). I guess I change it to flags baddump
> only when a baddump flag is available in the datfile.
>
> The values were counted on all roms, including biossets.

Thanks for the explanation Roman. I appreciate the need to convert a nodump so ClrMamePro can do it's job - that's a processing issue. However, I'd ultimately mark those roms with their original listinfo status to correctly report the roms status at the end. I'm not sure why it only happens with some nodumps and not all of them. No matter, my program matches yours for total of nodumps + baddumps and each reports the exact same set of roms, just classifies some differently. After after, none of these incorrect/fake roms will make the emulation run more accurately so it's a moot point.

Cheers,
Tim