Previous Thread
Next Thread
Print Thread
Page 2 of 2 1 2
#108641 - 01/26/17 07:31 PM Re: Problem Full ROM Audit showing not available ROMs [Re: qmc2]  
Joined: Nov 2015
Posts: 14
Luzie Offline
Member
Luzie  Offline
Member

Joined: Nov 2015
Posts: 14
Germany
Originally Posted By qmc2
If you don't trust QMC2, run "mame -verifyroms" over your ROM path - the information will basically be the same, except that it's textual (QMC2 parses this text).

One question from me: Does QMC2 make a MAME.EXE -VERFIYROMS *
or does it do a "single Audit" one after one by sending MAME.EXE -VERIFYROMS romname1 then MAME.EXE -VERIFYROMS romname2 and so on?


Running MAME and QMC2 on Windows 10 32-Bit (German)
#108642 - 01/26/17 07:34 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: May 2008
Posts: 4,793
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,793
Germany
It does a full audit ("mame -verifyroms") for a typical ROM check, but you can also check one or more sets individually.

Also, there's this section in the QMC2 guide which explains it in more detail.


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
#109280 - 03/29/17 07:54 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: Nov 2015
Posts: 14
Luzie Offline
Member
Luzie  Offline
Member

Joined: Nov 2015
Posts: 14
Germany
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 ====

Last edited by Luzie; 03/29/17 07:54 PM.

Running MAME and QMC2 on Windows 10 32-Bit (German)
#109284 - 03/30/17 08:26 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: Nov 2015
Posts: 14
Luzie Offline
Member
Luzie  Offline
Member

Joined: Nov 2015
Posts: 14
Germany
Originally Posted by Luzie
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 ...

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...

Well, I´m informed (from: http://www.mameworld.info/ubbthread...ded&sb=5&o=&fpart=1&vc=1 )
that the problem is caused by the 4 GByte Happy Fish Flash-Card. I moved "hapyfsh2.zip" out of my ROMS Directory and now verifyroms finished correctly without errors on my Win10 32-Bit.

Last edited by Luzie; 03/30/17 09:13 PM.

Running MAME and QMC2 on Windows 10 32-Bit (German)
Page 2 of 2 1 2

Moderated by  qmc2 

Who's Online Now
2 registered members (Olivier Galibert, Praxis), 23 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,319
Posts107,561
Members4,734
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.030s Queries: 15 (0.013s) Memory: 4.9580 MB (Peak: 5.1374 MB) Zlib enabled. Server Time: 2017-04-28 11:58:08 UTC