Fixed [BUG 3.31] CHD bad sha1
Posted: Thu May 07, 2009 8:51 am
As we know, MAME 130u1 had changed a lot of chds, so we need to use the new version of chdman.exe to update chds. But if I use MAME 131 data file, romcenter reported my chds are bad, and the SHA1 data of my chd files looks strange. For example, area51.chd, scaned by romcenter 3.31, the SHA1 of original file is 9ea749404c9a5d44f407cdb8803293ec0d61410d, that is correct according to MAME 130 data, but the SHA1 of updated file is 00000000000000009ea749404c9a5d44f407cdb8, its not correct in MAME 131 data, its supposed to be 3b303bc37e206a6d7339352c869f050d04186f11.
But when I use ClrMame scan my updated chds, its ok(using the same MAME 131 data file). Why? Is this a bug of romcenter? Or I can do something to avoid that? Did it happened to anybodyelse?
But when I use ClrMame scan my updated chds, its ok(using the same MAME 131 data file). Why? Is this a bug of romcenter? Or I can do something to avoid that? Did it happened to anybodyelse?