> Ok, I've gotten two of the "new" CHD's, Carnevil and Wayne Gretzky. I have m32
> 0.77, no bloody u1 or u2 suffix. I've run the CMP SCAN option, and both CHD's
> verify with no errors. How is this possible?


Why should it show new chds as bad? The md5 of the belonging file doesn't change, so all checksum/fullintegrity checks verify fine.

ClrMamePro will warn you if MAME needs a 'new' chd file and you still got a not converted one. So with MAME 78 you'll get messages for your old ones.

Hmm....the other way around is not 100% correct, since from a datfile you can't really say that a chdfile has to be in an old or new format. Currently I only use the sha1 information for it. So it'll complain if the datfile requires a sha1 for a chd while the chd header doesn't have one. Well...I could add that the other way around to say that you have a new chd while you need an old one. But since the old chd format becomes obsolete I doubt I will add that.

All mame versions below 77u1 can't run them because they don't understand the new format. That's why mame shows errors.

ClrMamePro's name, checksum and integrity check work with old and the new format...so it won't show any message

Roman Scherzer
ClrMamePro