Previous Thread
Next Thread
Print Thread
Page 1 of 2 1 2
#107935 - 11/18/16 01:40 PM Problem Full ROM Audit showing not available ROMs  
Joined: Nov 2015
Posts: 14
Luzie Offline
Member
Luzie  Offline
Member

Joined: Nov 2015
Posts: 14
Germany
I use the latest QMC2 v0.69 on Windows.

I think I have a complete MAME 0.169 Set, but QMC reports 2031 as not found.

When I single-audit the reported not found game, ROM-audit is OK.

After I start a new Full ROM Check, the progress bar goes up to about 9X percent and than directly the ROM Check is finished.

I´ve tried to find a bad ROM which causes QMC2 to not right audit the "last 2013 ROMs", but not yet managed to find out, if a faulty ROM-File maybe the cause.

Can I enable a log to find out where ROM-Auditing maybe has problems ?


Running MAME and QMC2 on Windows 10 32-Bit (German)
#107936 - 11/18/16 02:14 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
The last few thousand sets are device sets which are handled specifically, and the ROM audit is definitely correct. Give me a concrete example, and I can check what might be missing on your end (or may be confusing you).

In case you've hidden device sets you won't see their individual states since they aren't listed (but they are still counted in the overall stats).


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!
#107937 - 11/18/16 03:54 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
I´ve tried to find the ROM/ROMs which maybe causing the problem, but not yet can find it.

I move some hundred out of the ROM-Directory, did a full ROM Audit, and than e.g. get only 553 listed as non available. When I move them back, I get N: 2032.

Also, with older QMC2/MAME-combinations I was able to get N:0 in the past, so I think no hidden things should be my problem.

Last edited by Luzie; 11/18/16 03:55 PM.

Running MAME and QMC2 on Windows 10 32-Bit (German)
#107938 - 11/18/16 04:10 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
Well, there's no 1:1 relationship between the number of files in the ROM path and the number of correct (, ...) or not found sets the audit may find.

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

Anyway, without a concrete / simple example I'm unable to help you. Pick a set which you think should be correct (but is shown as "not found"), then check the corresponding files... also check what the ROMAlyzer has to say about it... and then post your results here.

Oh, and excerpts from the front-end log would help, too:

Code:
17:48:10.384: verifying ROM status for all sets
17:49:14.293: checking real status of 2830 sets not mentioned during full audit
17:49:14.508: done (checking real status of 2830 sets not mentioned during full audit)
17:49:14.510: done (verifying ROM status for all sets, elapsed time = 01:04.126)

Last edited by qmc2; 11/18/16 04:50 PM.

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!
#107939 - 11/18/16 04:35 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
Also, I suggest you read this thread from our mailing list (I still think you're confused because you've hidden the device sets, just like the OP in this mail thread): https://sourceforge.net/p/qmc2/mailman/message/35340635/


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!
#107940 - 11/18/16 05:25 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
Thanks for the suggestions.
I´ll read it on the weekend an mail back than.

When I issue:
K:\MAME>mame.exe -verifyroms *

the last lines are:
...
romset m50458 is best available
romset microdisc is good
romset jasmin is good
Caught unhandled St9bad_alloc exception: std::bad_alloc

K:\MAME>

Will try to post excerpts from the front-end log here next time.


Running MAME and QMC2 on Windows 10 32-Bit (German)
#107941 - 11/18/16 06:57 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
The exception is the likely reason for what you see.


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!
#107951 - 11/20/16 07:32 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
Tested something more...

Did a "clean install" of MAME 0.169 and QMC2 v0.69: Here MAMEs -VERIFYROMS * runs OK and QMC2 too.

Found a thread on the error on this MAME board:
http://www.mameworld.info/ubbthreads/sho...amp;o=&vc=1
here the fault for MAMEs VERIFYROMS was one an incomplete ROMFILE.ZIP

However, I not found one single ROM-File rises this error, but MAME.EXE rises this error while comparing different ROMs in sequence. If I delete the maybe faulty ROMs, the error arrise later.

Now I´ll check all my ROM-ZIPs with 7-ZIPs File-Manager but as -VERIFYROMS * runs without errors on a clean installed MAME, it should be something within my complete MAME-Directory.

#107952 - 11/20/16 07:50 PM Re: Problem Full ROM Audit showing not available ROMs [Re: Luzie]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
Note that you could also use QMC2's built-in ROM manager to rebuild your ROM collection. There's a video tutorial for it as well (linked to from the wiki).


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!
#107970 - 11/22/16 06:38 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
Thanks for your reply and suggestions.

In the meantime I found on:
http://stackoverflow.com/questions/9456728/how-to-deal-with-bad-alloc-in-c

that this error "Caught unhandled St9bad_alloc exception: std::bad_alloc" shouldn´t ever appear.
So no faulty ROM or MAME should be causing my problem...

I installed a fresh Win10 and the error has gone: MAME -verifyroms * and QMC2 reporting all ROMs OK.

Will try QMC2's built-in ROM manager when I found some spare time !

Last edited by Luzie; 11/22/16 06:39 PM.

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

Moderated by  qmc2 

Who's Online Now
3 registered members (Duke, shattered, Tauwasser), 19 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,411
Posts108,925
Members4,757
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.028s Queries: 15 (0.007s) Memory: 5.0177 MB (Peak: 5.2451 MB) Zlib enabled. Server Time: 2017-09-24 14:01:17 UTC