Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|07410||Interface||Minor||Always||Sep 8, 2019, 11:49||Oct 4, 2020, 08:55|
|Tester||hap||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||cuavas||Resolution||Fixed||OS||Windows 10 (64-bit)|
|Version||0.213||Fixed in Version||0.226||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||07410: verifyroms: romset may report as bad if checksums are same as parent|
If a clone romset has the same checksums as the parent romset, and at least one used rom is available, -verifyroms will report it as bad when the user doesn't have the romset at all. It's a weird combination and verifyroms somehow gets confused.
For example, mu100r in ymmu100.cpp
|Steps To Reproduce||
- make a fresh MAME install (either compile, or download newest version)
- put hd44780_a00.zip in the roms folder, this is a common LCD device.
mame -verifyroms mu100
romset "mu100" not found!
mame -verifyroms mu100b
romset "mu100b" not found!
mame -verifyroms mu100r
mu100r : xu50720.ic11 (2097152 bytes) - NOT FOUND (mu100)
mu100r : xt71420.ic11 (2097152 bytes) - NOT FOUND (mu100)
mu100r : xt714e0.ic11 (2097152 bytes) - NOT FOUND (mu100)
mu100r : sx518b0.ic34 (4194304 bytes) - NOT FOUND (mu100)
mu100r : sx743b0.ic35 (4194304 bytes) - NOT FOUND (mu100)
mu100r : xt445a0-828.ic36 (2097152 bytes) - NOT FOUND (mu100)
mu100r : xt461a0-829.ic37 (2097152 bytes) - NOT FOUND (mu100)
mu100r : xt462a0.ic39 (4194304 bytes) - NOT FOUND (mu100)
mu100r : xt463a0.ic38 (4194304 bytes) - NOT FOUND (mu100)
mu100r : mu100-font.bin (4096 bytes) - NOT FOUND (mulcd)
mu100r : hd44780_a00.bin (4096 bytes) - NEEDS REDUMP
romset mu100r [mu100] is bad
1 romsets found, 0 were OK.
Bug reported by Berger (MAME Linux build)
Bug does not happen in for example fidel_excel.cpp where fexceld is the same romset as fexcel. In this case there's no rom available at all (like the LCD rom in mu100r)
|Affected Sets / Systems|
|There are no relationship linked to this issue.|
Oct 4, 2020, 01:59
edited on: Oct 4, 2020, 02:00
|I’ve addressed at least some of these kinds of issues in https://github.com/mamedev/mame/commit/aca0aaaa3d6870f0372316912031794329a5ca41 – please re-test this with the systems that this was reported for here.|
Oct 4, 2020, 08:54
|works as expected with mu100r now|