Previous Thread
Next Thread
Print Thread
Page 2 of 2 1 2
Joined: Nov 2015
Posts: 22
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 22
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 and 64-Bit Versions (German)
Joined: May 2008
Posts: 4,899
Q
Very Senior Member
Offline
Very Senior Member
Q
Joined: May 2008
Posts: 4,899
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!
Joined: Nov 2015
Posts: 22
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 22
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 and 64-Bit Versions (German)
Joined: Nov 2015
Posts: 22
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 22
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 and 64-Bit Versions (German)
Page 2 of 2 1 2

Moderated by  qmc2 

Link Copied to Clipboard
Who's Online Now
3 members (ksherlock, 2 invisible), 26 guests, and 3 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics9,019
Posts118,453
Members5,010
Most Online890
Jan 17th, 2020
Forum Host
These forums are hosted by www.retrogamesformac.com
Forum hosted by www.retrogamesformac.com