I generated a datfile with the latest mame2003-plus core and can’t rebuild set ktiger2p using clrmamepro. The CRC’s match the datfile, but not the sha1 hashes.
Can you check with this dat file, if it is a problem with your datfile or with the rom itself:
I have the same problem with your dat file. It’s these two files giving me problems.
b30_02_2p.8j [CRC32: 321e2be6] [SHA1: 56c97523d243927c09f02979d2a208a281eed4b5]
b30_04_2p.8h [CRC32: c3f960ff] [SHA1: f93d0b72bedee65268e3aa4b20fa59da82e29ccf]
I verified the files with a program and got different hashes.
b30_02_2p.8j [CRC32:321e2be6] [SHA1: 03b2c530326d1859b66829b49555d862be235643]
b30_04_2p.8h [CRC32:c3f960ff] [SHA1: cbebf576d677cc02f4d0f22dcc226e898d4832c6]
I could be wrong, but this is a patched rom that was added to FBNeo and mame2003-plus a couple of weeks ago.
Maybe different patch programs generate different hashes?
I found nothing on the FBNeo side, since they are using only crc32 hashes.
Best advice is to open an issue on https://github.com/libretro/mame2003-plus-libretro
Should be fixed now. Thanks for opening the issue.