|
mame 0.171 -verifyroms does not always work
#351299 - 03/08/16 01:45 AM
|
|
|
I type MAME bbca, and the BBCA machine loads.
But when I type MAME bbca -verifyroms
I get romset "bbca" not found!
What am I doing wrong in MAME 0.171, or does this MAME have bugs with the verify?
Thanks,
Kranser.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351300 - 03/08/16 02:06 AM
|
|
|
Make sure your rompath is set correctly in mame.ini
Quote:
J:\MAME>mame64 -verifyroms bbca
bbca : saa5050 (960 bytes) - NEEDS REDUMP
romset bbca [bbcb] is best available
1 romsets found, 1 were OK.
J:\MAME>
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: B2K24]
#351315 - 03/08/16 11:06 AM
|
|
|
In mame.ini my rompath is set as default: rompath roms
And I have a bbca.zip file in the roms\ folder - but still have issues with -verifyroms.
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3135
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351317 - 03/08/16 11:18 AM
|
|
|
> In mame.ini my rompath is set as default: rompath roms
>
> And I have a bbca.zip file in the roms\ folder - but still have issues with
> -verifyroms.
saa5050.zip (notice that it shows it needs to be redumped) is expected either in that .zip or within the bbca.zip romset.
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Tafoid]
#351318 - 03/08/16 11:35 AM
|
|
|
Hi thanks for your reply, but it's not that either!
verifyroms for saa5050 works:
C:\mame>mame -verifyroms saa5050
saa5050 : saa5050 (960 bytes) - NEEDS REDUMP
romset saa5050 is best available
C:\mame>mame -verifyroms bbca
romset "bbca" not found!
C:\mame>mame -verifyroms bbcb
romset "bbcb" not found!
C:\mame>mame -verifyroms bbcm
bbcm : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcm is best available
1 romsets found, 1 were OK.
so saa5050 and bbcm are found with -verifyroms, but bbca.zip and bbcb.zip are not.
My bbca.zip is correct and contains these files:
Testing files from .ZIP: C:\c\roms\bbca.zip
Testing: basic2.rom OK
Testing: os12.rom OK
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351319 - 03/08/16 11:44 AM
|
|
|
Also when I verifyroms for all roms I get the following error:
romset nsmdsa is best available
m50458 : m50458-001sp (4608 bytes) - NEEDS REDUMP
m50458 : m50458_char.bin (4608 bytes) - NEEDS REDUMP
romset m50458 is best available
Caught unhandled St9bad_alloc exception: std::bad_alloc
So maybe that is part of the issue?
Also bbca and bbcb are skipped when -verifyroms is used for all romsets:
romset batmantv [vii] is good
bbcb1770 : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcb1770 [bbcb] is best available
bbcb_de : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcb_de [bbcb] is best available
romset bbcbc is good
bbcm : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcm is best available
bbcm512 : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcm512 [bbcm] is best available
bbcmaiv : mos320aiv.cmos (50 bytes) - NEEDS REDUMP
bbcmaiv : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcmaiv [bbcm] is best available
bbcmarm : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcmarm [bbcm] is best available
bbcmc : mos510.ic49 (65536 bytes) - NEEDS REDUMP
bbcmc : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcmc is best available
bbcmc_ar : mos511.ic49 (65536 bytes) - NEEDS REDUMP
bbcmc_ar : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcmc_ar [bbcmc] is best available
bbcmet : mos400.cmos (50 bytes) - NEEDS REDUMP
bbcmet : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcmet [bbcm] is best available
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351322 - 03/08/16 12:43 PM
|
|
|
> Hi thanks for your reply, but it's not that either!
>
> verifyroms for saa5050 works:
>
> C:\mame>mame -verifyroms saa5050
> saa5050 : saa5050 (960 bytes) - NEEDS REDUMP
> romset saa5050 is best available
>
> C:\mame>mame -verifyroms bbca
> romset "bbca" not found!
>
> C:\mame>mame -verifyroms bbcb
> romset "bbcb" not found!
>
> C:\mame>mame -verifyroms bbcm
> bbcm : saa5050 (960 bytes) - NEEDS REDUMP
> romset bbcm is best available
> 1 romsets found, 1 were OK.
>
> so saa5050 and bbcm are found with -verifyroms, but bbca.zip and bbcb.zip are not.
> My bbca.zip is correct and contains these files:
> Testing files from .ZIP: C:\c\roms\bbca.zip
> Testing: basic2.rom OK
> Testing: os12.rom OK
I cannot duplicate your issue with 171 binary and a merged romset:
Code:
E:\Emulators\MAME>mame64 -verifyroms saa5050
saa5050 : saa5050 (960 bytes) - NEEDS REDUMP
romset saa5050 is best available
1 romsets found, 1 were OK.
E:\Emulators\MAME>mame64 -verifyroms bbca
bbca : saa5050 (960 bytes) - NEEDS REDUMP
romset bbca [bbcb] is best available
1 romsets found, 1 were OK.
E:\Emulators\MAME>mame64 -verifyroms bbcb
bbcb : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcb is best available
1 romsets found, 1 were OK.
E:\Emulators\MAME>mame64 -verifyroms bbcm
bbcm : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcm is best available
1 romsets found, 1 were OK.
E:\Emulators\MAME>mame64 -verifyroms bbcmet
bbcmet : mos400.cmos (50 bytes) - NEEDS REDUMP
bbcmet : saa5050 (960 bytes) - NEEDS REDUMP
romset bbcmet [bbcm] is best available
1 romsets found, 1 were OK.
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Pernod]
#351323 - 03/08/16 12:53 PM
|
|
|
Thanks for checking. Just wondering whether the issue is that I do not have the torch roms (torchf, torchh10, torchh21) - I wonder if these are necessary for -verifyroms?
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351324 - 03/08/16 01:03 PM
|
|
|
No, that didn't work!
Does anyone know how to find the files that -verifyroms requires? They are certainly different to the requirements when a machine/game is loaded by mame?
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351325 - 03/08/16 01:25 PM
|
|
|
bbca actually requires 5 roms:
basic1.rom
basic2.rom
os01.rom
os10.rom
os12.rom
Also check your bbca.zip to ensure it doesn't contain any folders, the files should be at the root level of the archive.
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Pernod]
#351329 - 03/08/16 05:05 PM
|
|
|
My bbca.zip file only contained the following:
basic2.rom
os12.rom
which was enough for the machine to load in MAME.
But adding the missing files causes -verifyroms to work - thanks Pernod.
But why did -verifyroms report 'ROM not found error' rather than ROM is found but contained missing files? It is because bbca is a clone of bbcb?
Thanks,
Kranser
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351331 - 03/08/16 07:12 PM
|
|
|
> My bbca.zip file only contained the following:
> basic2.rom
> os12.rom
>
> which was enough for the machine to load in MAME.
>
> But adding the missing files causes -verifyroms to work - thanks Pernod.
>
> But why did -verifyroms report 'ROM not found error' rather than ROM is found but
> contained missing files? It is because bbca is a clone of bbcb?
>
> Thanks,
> Kranser
The ZIP is not the Rom. The ROM file is the rom. Your Zip was missing Roms, hence the message.
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#351332 - 03/08/16 07:19 PM
|
|
|
IIRC the behaviour was changed (inadvertently?) some time ago. I think the previous behaviour was better and, in your case, would have resulted in MAME telling you which ROMs were missing in you bbca romset.
|
.
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: lamprey]
#351334 - 03/08/16 08:22 PM
|
|
|
Thanks lamprey, but I went back and checked, and the actual message was romset bbca not found, which seems to indicate the whole zip was missing - which was not the case!
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Osso1]
#351335 - 03/08/16 08:23 PM
|
|
|
Thanks Osso1, that makes sense - but I would much prefer the old method too!
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#361086 - 12/08/16 05:10 PM
|
|
|
Edit: Posted this at the end of the thread ...
Edited by Luzie (12/08/16 05:13 PM)
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Kranser]
#361087 - 12/08/16 05:12 PM
|
|
|
I encounter the same error with 32-Bit MAME.EXE v0.179 or v0.180 under Windows 10:
romset goindolu [goindol] is good
romset goinnuts is good
Caught unhandled St9bad_alloc exception: std::bad_alloc
Those ROMs are OK, this must be an issue with MAME or Windows.
Interesting fact: While doing a little research I found a problem I have with old MAME v0.53:
This rises error while doing single ROM audit:
X:\MAME>mame -verifyroms vsavh
-----------------------------------------------------
Exception at EIP=007BACB5: ACCESS VIOLATION
While attempting to read memory at FFFFFFFF
-----------------------------------------------------
-> Problem was a Carriage Return in MAME.INIs rompath-line
where my rompath was really on the next line in MAME.INI.
So now I deleted MAME.INI on my actual MAME 0.180
and when I now run a complete ROM audit with -verifyroms *
I get the error later with:
romset travrusa is good
romset travrusab [travrusa] is good
Caught unhandled St9bad_alloc exception: std::bad_alloc
Edited by Luzie (12/08/16 05:55 PM)
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Luzie]
#364731 - 03/29/17 09:57 PM
|
|
|
I just want to inform you, that with new MAME 0.184 the error "Caught unhandled St9bad_alloc exception: std::bad_alloc" on MAME -verifyroms is gone.
I think this has to do with News on MAME 0.184 told on www.mame.net:
==== SNIP ====
We’ve made substantial improvements to some of MAME’s non-emulation features. The -romident verb is now much faster when used on a folder or archive containing multiple files, and will identify ROMs for emulated slot devices that aren’t inserted by default. The -listxml output now includes all linked devices, and is produced at least 30% faster. We’ve also improved -verifyroms so it covers more devices and is faster when verifying ROMs for a subset of drivers/devices.
==== SNAP ====
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Luzie]
#364746 - 03/30/17 08:58 AM
|
|
|
> I just want to inform you, that with new MAME 0.184 the error "Caught unhandled
> St9bad_alloc exception: std::bad_alloc" on MAME -verifyroms is gone.
Yeah, but it still can't verify that ROM properly on a 32-bit system, it just doesn't crash any more. The happyfish set has a 4GB Flash ROM image that can't be loaded into memory in a normal 32-bit application.
|
|
|
| smf |
|
I've been here before
|
|
|
|
|
|
Reged: 01/16/15
|
|
Posts: 130
|
|
|
|
|
|
Send PM
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Vas Crabb]
#364750 - 03/30/17 12:26 PM
|
|
|
> Yeah, but it still can't verify that ROM properly on a 32-bit system, it just doesn't
> crash any more. The happyfish set has a 4GB Flash ROM image that can't be loaded into
> memory in a normal 32-bit application.
I thought -verifyroms in a zip file just checked the crc and didn't actually load the file. The SHA1 were checked at some point, but it's so slow that it got backed out quickly.
out of memory when doing -verifyroms * on 32 bit builds was due to memory leaks that nobody cared about because it worked on 64 bit builds. If you monitored it's memory usage it just kept getting bigger and bigger.
Edited by John Doe (03/30/17 12:35 PM)
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: smf]
#364754 - 03/30/17 04:07 PM
|
|
|
|
|
|
Re: mame 0.171 -verifyroms does not always work
[Re: Vas Crabb]
#364765 - 03/30/17 10:54 PM
|
|
|
> > I just want to inform you, that with new MAME 0.184 the error "Caught unhandled
> > St9bad_alloc exception: std::bad_alloc" on MAME -verifyroms is gone.
>
> Yeah, but it still can't verify that ROM properly on a 32-bit system, it just doesn't
> crash any more. The happyfish set has a 4GB Flash ROM image that can't be loaded into
> memory in a normal 32-bit application.
Shit. Too early happy. Today the error is back:
...
romset goinnuts is good
Caught unhandled St9bad_alloc exception: std::bad_alloc
I think I have to use 64-Bit OS/64-Bit MAME...
Update: Now I tested with moving "hapyfsh2.zip" (4GB Flash-ROM) out of ROMS-Directory and verifyroms finished correctly without errors on my Win10 32-Bit.
Thanks for you information!
|
|
|
Index 
Threaded 
mame 0.171 -verifyroms does not always work
Reply
[Re: 
