Romcenter

This is a bug. It is fixed for the next telease. I was comparing the wrong sha1 on chd v5...

A couple of things you could check, if you feel like it.

You have a mame XXX version database, in which the CHDs appear as correct in RC 3.71. Create the same mame version database in RC4 and check if indeed the CHDs appear as red in RC4. If they do, then check the CRC of a CHD in both RC versions to see if a different CRC is reported or if it is the same CRC but falsely reported as red in RC4. This could help Eric pinpoint the error.

Have fun.

[b]MAMEUI 0.164 (mameui.exe):[/b] http://www.progettosnaps.net/UI_Museum/MAMEUI32_0.164a_03-08-2015.7z

previously in RC 3.7.1 I had all my CHD files ok, but now with RC 4.0b2.1 I noticed that my CHD files are identified as incorrect.

here few pictures from RC 4.0b2.1 and kinst.chd file...

[img]http://i.imgur.com/rERTBiS.png[/img]
[img]http://i.imgur.com/BPN0wKY.png[/img]
[img]http://i.imgur.com/qCqwsfp.png[/img]

but if I check kinst.chd file with chdman.exe tool from mame, the file is ok...

[img]http://i.imgur.com/AfKwF54.png[/img]

then it is a bug ?