Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05556 Interface Minor Always Apr 27, 2014, 12:42 Jun 8, 2021, 07:02
Tester Klez View Status Public Platform MAME (Official Binary)
Assigned To Resolution Fixed OS Windows Vista/7/8 (64-bit)
Status [?] Resolved Driver
Version 0.153 Fixed in Version 0.231 Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 05556: mame -verifyroms lists nonexistent roms / clones as bad
Description Somewhat similar to bug: 04267: -verifyroms lists nonexistent roms / clones as bad
Hapening since a few major versions ago. Not new from v 0.153

The following roms are listed as bad but NONE of these are installed.
aliensyn2, aliensyn5, aliensynjo, sdib, sdibl, defense, kizuna4p, mac2bios, rdft2us, rfjets, rfjetsa, shinobi2, shinobi3, shinobld, h63484, mb90082

Original parent roms are OK and do not contain any extra unedded files:

# mame64 -verifyroms aliensyn
romset aliensyn is good

# mame64 -verifyroms sdi
sdi : 317-0027.key (8192 bytes) - NEEDS REDUMP
romset sdi is best available

# mame64 -verifyroms rdft2
romset rdft2 is good

# mame64 -verifyroms rfjet
romset rfjet is good

# mame64 -verifyroms shinobi
romset shinobi is good

Now, if i execute "mame64 -verifyroms" to do a full rom audit the following nonexistent roms are listed:
(i never installed any of these i promise!)

h63484 : h63484.bin (256 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset h63484 is best available

mb90082 : mb90082_char.bin (2048 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset mb90082 is best available

mac2bios : macs2os_l.bin (524288 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
[...] romset mac2bios is best available

kizuna4p : 216-p1.p1 (2097152 bytes) - NOT FOUND (kizuna)
[...] romset kizuna4p [kizuna] is bad

aliensyn2 : epr-10808 (32768 bytes) - NOT FOUND
[...] romset aliensyn2 [aliensyn] is bad

aliensyn5 : epr-10804.43 (32768 bytes) - NOT FOUND
[...] romset aliensyn5 [aliensyn] is bad

aliensynjo : epr-10699.43 (32768 bytes) - NOT FOUND
[...] romset aliensynjo [aliensyn] is bad

sdib : epr-10986a.a4 (32768 bytes) - NOT FOUND
[...] romset sdib [sdi] is bad

sdibl : a4.rom (32768 bytes) - NOT FOUND
[...] romset sdibl [sdi] is bad

defense : epr-10917a.a4 (32768 bytes) - NOT FOUND
[...] romset defense [sdi] is bad

rdft2us : prg0.u0259 (524288 bytes) - NOT FOUND
[...] romset rdft2us [rdft2] is bad

rfjets : rfj-06.u0259 (524288 bytes) - NOT FOUND
[...] romset rfjets [rfjet] is bad

rfjetsa : rfj-06(__rfjetsa).u0259 (524288 bytes) - NOT FOUND
[...] romset rfjetsa [rfjet] is bad

shinobi2 : epr-11282.a4 (65536 bytes) - NOT FOUND
[...] romset shinobi2 [shinobi] is bad

shinobi3 : epr-11299.a4 (65536 bytes) - NOT FOUND
[...] romset shinobi3 [shinobi] is bad

shinobld : 12.bin (65536 bytes) - NOT FOUND
[...] romset shinobld [shinobi] is bad

These sets should not be listed because they are not installed and not needed.
Steps To Reproduce 1) Start with a empty ROMS folder.
2) Install the following roms: sdi, aliensyn, shinobi, rdft2, rfjet.
3) execute this in the terminal: "mame -verifyroms"
4) Now you will see some non existent roms being audited and giving an error.
Additional Information I used the official command line MAME binary from
Github Commit
Regression Version
Affected Sets / Systems
Attached Files
There are no relationship linked to this issue.
User avatar
Apr 27, 2014, 23:57
In most of the cases, it seems, parents are in a driver and it is assumed the clones are in the same driver and they are not
EG: shinobi

C:\Users\ThenGames\Desktop\153>mame shinob* -ls
shinobi segas16a.c
shinobi1 segas16a.c
shinobi2 segas16b.c
shinobi3 segas16b.c
shinobi4 segas16b.c
shinobi5 segas16b.c
shinoblb segas16a.c
shinobld system16.c
shinobls segas16a.c
User avatar
Senior Tester
Apr 10, 2018, 08:57
Is this still an issue?
User avatar
Apr 12, 2018, 14:45
Yes, mame binary (mame0196-307-gef77d3f1aa-dirty) is isolated, no roms folder or any *.ini
romset 1292apvs is best available
romset 1392apvs [1292apvs] is best available
romset a2600 is best available
romset a2600p [a2600] is best available
romset advsnha [arcadia] is best available
romset apexc is best available
romset arcadia is best available
romset bndarc [arcadia] is best available
romset breakout is best available
romset copera is best available
romset cpc464p is best available
romset cpc6128p is best available
romset cx3000tc [vc4000] is best available
romset database is best available
romset dendy [iq501] is best available
romset dendy2 [iq502] is best available
romset dynavisn [intmpt03] is best available
romset ekusera [intmpt03] is best available
romset elf2 is best available
romset f1392 [1292apvs] is best available
romset famicom is best available
fccpu30lite4: rom.bin (65536 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset fccpu30lite4 [fccpu30] is best available
fccpu30lite8: rom.bin (65536 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset fccpu30lite8 [fccpu30] is best available
fccpu30senr : rom.bin (65536 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset fccpu30senr is best available
fccpu30senr501: rom.bin (65536 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset fccpu30senr501 is best available
romset fforce2 [1292apvs] is best available
romset gchinatv is best available
romset genesis is best available
grid1101 : 1101even.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1101 : 1101odd.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1101 : 80130 (16384 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset grid1101 is best available
grid1109 : 1109even.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1109 : 1109odd.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1109 : 80130 (16384 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset grid1109 [grid1101] is best available
grid1121 : 1121even.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1121 : 1121odd.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1121 : 80130 (16384 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset grid1121 is best available
grid1131 : 1131even.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1131 : 1131odd.bin (8192 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
grid1131 : 80130 (16384 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset grid1131 [grid1121] is best available
romset gx4000 is best available
romset h21 is best available
romset hanihac [arcadia] is best available
romset hmg1292 [1292apvs] is best available
romset hmg1392 [1292apvs] is best available
romset hmg2650 [arcadia] is best available
User avatar
Senior Tester
Apr 18, 2018, 04:36
All appears normal.

The sets listed either do not need roms, or their only roms are undumped.

User avatar
Apr 18, 2018, 19:42
Yes, this is still an issue. I still have clones of pull parent sets being expected when they shouldn't be even attempted to audit.
Please follow the instructions above and note the numerous 'missing' from clones of those parents, not including NO_DUMP/BAD_DUMP or other sets not requiring ANY roms at all.
User avatar
Apr 19, 2018, 09:52
This function should also consider the rom file availability, if there's no file to be audited, nothing should be done or reported to avoid a flood of "xxx file not found".
User avatar
Apr 19, 2018, 13:16
If anything, perhaps the list of never validating roms could be controlled by linking into the "Hide romless machines" UI Miscellaneous option.
I agree that by design it is only supposed to show those which you already a folder/compressed folder.
User avatar
Dec 30, 2018, 13:32
I am seeing this too with the following roms:
- vgmplay
- mbaao
- mushi2eo
- ffrevng10
- mu100r
User avatar
Oct 29, 2020, 01:25
Has some further examples. Since it is closed, I'm unsure how we will go to fix individual scanning of machines.
User avatar
Jun 4, 2021, 07:09
edited on: Jun 4, 2021, 07:13
Update -

Situation improved a lot in recent MAME releases.

Now repeating these tests in MAME version 0.231, for me the only non existent rom being reported as bad is "vgmplay".
All other entries listed in the original report do not show anymore as missing or bad and also work well.

I think this bug can be closed as FIXED, because the only remaining problem, the "vgmplay" set might be something different specific to that driver.
Thank you all for your input.
User avatar
Jun 4, 2021, 18:48
vgmplay requires "new" roms for the new FM cores, so anything missing is likely expected if you haven't updated your romsets correctly.
User avatar
Jun 7, 2021, 10:10
I do not have the rom "vgmplay", hence it should't be reported as bad.

However, with an empty roms folder this "vgmplay" is not reported, so might be required for something i cant guess(?¿)

Anyway I propose this MT to fixed, since none of the previously reported errors appear anymore.