> Topic. Google fails me, even though it's now been days since 146u3 was released. The > chdman from 146u2 generated 300GB of CHDs that ClrMamePro and MAME both did not like > (bad SHA1, almost universally, and I tested three copies of the 146u2 chdman from > three separate sources including a forum post from supposedly a dev) so I went back > to my v4's. I'm keen to test whether this apparent bug was fixed. Would be nice to > have a 100% clean CMP scan for the first time ever.
Rather than explain it again to yet someone else, I'll attempt to lay it out as simple as possible for you...
It is advised to keep everything in your collection v4 unless MAME puts out a new or redumped CHD (anything since 0.145) as all those new CHD's will come across as v5. For now, that's as simple as it needs to be.
CMP has the option to shut off version checking in the latest versions, so I'd suggest you do that, follow the advise above, and CMP will come up 'clean' for you.
|