JessicaJones wrote: ↑
Sat Feb 08, 2020 5:07 pm
I'm manually (using a tool) calculating CRC32 values of ROM files inside the zip files of game & watch games.
I'm using a working ROM zip file for mame 0.218 so my file is correct and plays in MAME.
I found CRC32 errors in -listxml .
for example: gnw_helmet.zip
This file has 2 files inside: "cn-17" and "gnw_helmet.svg"
The CRC32 of "cn-17" is 6d251e2e and correct.
The CRC32 of "gnw_helmet.svg" is 0dce1694 but is WRONG!
My result is fa8294a3
(you can confirm this by calculating CRC32 of file "gnw_helmet.svg")
Why is there a wrong CRC32 value for this file in -listxml? Is this a bug?
Many other game & watch games have wrong CRC32 for *.svg files inside the zip file. (it are always the *.svg files that have wrong CRC32, all other files inside the zip file are having correct CRC32).
examples with wrong CRC32 values for *.svg files:
Simply put, as has been stated by another, you are using parts of a romset which have since been updated from what you have locally and you'll need to obtain a copy matching what MAME expects. Great lengths are made to assure that everything that has any type of hash value in MAME has been verified to exist. MAME is 100% correct.
you mentioned and other handhelds there was an issue with the .svg files and display problems which was fixed in the latter commit shown below:
Initial commit - https://github.com/mamedev/mame/commit/ ... ae30bd1f3
- for 0.214
Romset changed - https://github.com/mamedev/mame/commit/ ... 2cbc4b0a7f
- for 0.215
As far as your issue with auditing, MAMEDEV produced MAME will tell you that the romset is incorrect. In fact, if running through the internal MAME user interface, it will not let you attempt to emulate until the issue is resolved. If you run via command-line, you get an error as detailed before, but you can run it after acknowledging the mismatch issue - as well as attempting -verifyroms
gnw_helmet.svg WRONG LENGTH (expected: 0001ab5c found: 0001aab9)
gnw_helmet.svg WRONG CHECKSUMS:
EXPECTED: CRC(0dce1694) SHA1(412e69054b95f17fe08545f3c303c11abbe26304)
FOUND: CRC(fa8294a3) SHA1(05b734ac0126d3bffe160a23753a0a7e6f82996e)
WARNING: the machine might not run correctly.
c:\mamegit\mame>mame64 -verifyroms gnw_helmet
gnw_helmet : gnw_helmet.svg (109404 bytes) - INCORRECT LENGTH: 109241 bytes
romset gnw_helmet is bad
1 romsets found, 0 were OK.
In summary, update your romsets and know that MAME is 100% right when it comes to its hash data.