So it looks like there will be some major chd changes coming soon to MAME. Basically the idea is to include metadata into the hashcalculation plus some more additional data. And the Viper System chds are bad anyway and will be replaced.

Since the inclusion of metadata into the hash will alter the checksum, all your chds need to get updated. Most likely chdman will offer a possibility to do so.

Currently I don't know and I cannot forsee how cmpro will react on the changes. I assume that the old chds are being read correctly, the hashes mismatch and cmpro will mark them as unneeded (and moves them to backup). I also assume that the deep verification which decompresses the chd and recalcs sha1/md5 will lead to the wrong hash, too.

As soon I got more information I will recode the chd routines...

So...don't wonder if next MAME's scan result looks odd ;)


Roman Scherzer

Hi there,

it seems that MAME 0.130 also changed most of the rom-checksums, because I get a lot of unneeded roms. With version 0.129u6 all was fine.

Bye,
K.

No. You're wrong. .130 compared to .129u6 only had a minimum set of changes...mainly new sets. You most likely scanned with a wrong database.

> Hi there,
>
> it seems that MAME 0.130 also changed most of the rom-checksums, because I get a
> lot of unneeded roms. With version 0.129u6 all was fine.
>
> Bye,
> K.
>



Roman Scherzer

I don't think so because I got my dat-file right from mame/mame32UI into cmpro (same procedure as every time) and in both cases (mame/mame32UI) most (not all) of the checksums were wrong. Same with rebuild where only few of the roms are recognized. I also updated to 3.123 in hope of a problem between the last version of cmpro and 0.130 but it stays the same. Anyway, you say there is no prob so I go on searching my configurations and maybe delete all the programs to make a fresh start.

Many thanks for your quick answer and many many thanks for this great piece of software.

Bye,
K.
> No. You're wrong. .130 compared to .129u6 only had a minimum set of
> changes...mainly new sets. You most likely scanned with a wrong database.

Hi again,

it was a classic pebmac(problem exist between monitor and chair)-error. All I need to to was to delete the cache, dat-files, cmpro-settings and import it fresh from mame. The update of the older database just went wrong in some strange way. Now it's fine, I can scan my collection again and I'm happy again. ;)

Have a nice day,
K.