Previous Thread
Next Thread
Print Thread
Page 1 of 2 1 2
Joined: Nov 2015
Posts: 18
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 18
Hi,

the patched Version of QMC2 (which was patched to work with MAME 0.217 and later)
from HBMAME-Website ( Download: https://messui.1emulation.com/ )
seem to doesn´t work with actual MAME64.EXE v0.228 ?!

Last edited by Luzie; 01/29/21 05:25 PM.

Running MAME and QMC2 on Windows 10 32-Bit and 64-Bit Versions (German)
Joined: Aug 2004
Posts: 1,442
Likes: 2
Very Senior Member
Offline
Very Senior Member
Joined: Aug 2004
Posts: 1,442
Likes: 2
That patched version came from here: https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=116746#Post116746

I've added a note to my site (the one you linked to), and await someone to develop a new version.

Sadly, QMC2 development is pretty much abandoned at this time.

1 member likes this: Luzie
Joined: Jun 2017
Posts: 50
Member
Offline
Member
Joined: Jun 2017
Posts: 50
What is the error? It is still working, for me (Win 10, 64 bit), with the binary I posted, here:
https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=116746#Post116746

Please remember that only 64 bit Mame is supported. 32 bit no longer works:
https://drive.google.com/open?id=1B4WnXdYzF7mTmY_j-RSKTTjhiVLgU7By

Joined: Nov 2015
Posts: 18
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 18
Originally Posted by MusicLovr
What is the error? It is still working, for me (Win 10, 64 bit), with the binary I posted, here:
https://forums.bannister.org/ubbthreads.php?ubb=showflat&Number=116746#Post116746

Please remember that only 64 bit Mame is supported. 32 bit no longer works:
https://drive.google.com/open?id=1B4WnXdYzF7mTmY_j-RSKTTjhiVLgU7By

I tried the 64-Bit-Version you linked, it´s the same I tried originally here.

Yesterday it seem to me it doesn´t do anything while starting "Tools / Check ROMs..."

Today this "Tools / Check ROMs..." runs some minutes and reports some ROMs as Incomplete,
even if mame64.exe reports "romset indytempc [indytemp] is good" while auditing "indytempc"

Last edited by Luzie; 01/30/21 06:42 PM.

Running MAME and QMC2 on Windows 10 32-Bit and 64-Bit Versions (German)
Joined: Jun 2017
Posts: 50
Member
Offline
Member
Joined: Jun 2017
Posts: 50
With QMC2, i get:
L:43152 C:37906 M:4387 I:614 N:425 U:0 S:0 T:0

This seems consistent with what I'm used to seeing. Maybe QMC2 has always reported rom check incorrectly?

Does indytempc work? Does it now fail, when previously it worked?

Perhaps MAME and QMC2 are reporting something different, which I do not understand?

btw: My indytempc is shown as C (green), though 'driver status' is 'imperfect'.

Are you stopping 'check roms'? Or is it aborting? Try checking, again, and watch the progress, to make sure it is completing (watch the status bar)...

Last edited by MusicLovr; 01/30/21 08:30 PM.
Joined: Nov 2015
Posts: 18
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 18
Originally Posted by MusicLovr
This seems consistent with what I'm used to seeing. Maybe QMC2 has always reported rom check incorrectly?
Sorry, I don´t know. Maybe I should try with older MAME 0.227.

Originally Posted by MusicLovr
Does indytempc work? Does it now fail, when previously it worked?
Sorry, I don´t know this too.

Originally Posted by MusicLovr
btw: My indytempc is shown as C (green), though 'driver status' is 'imperfect'.
Mine is showed red with MAME 0.228. When trying to start it by Double Click from QMC2, it doesn´t start.
With manual start on commandline "MAME64.EXE indytempc" the game starts.

Originally Posted by MusicLovr
Are you stopping 'check roms'? Or is it aborting? Try checking, again, and watch the progress, to make sure it is completing (watch the status bar)...
Now that you write this, I remember there was some problems in older QMC2-versions with "Check roms" where the Audit-Run just quits without any error. Progess bar still shows 0%.
I haven´t stopped "Check roms" (Auditing) manually.
It´s hard to find out. Seems I have to do more checks even with a freshly created MAME-Dir and just QMC2x64 and some ROMs like indytempc

Last edited by Luzie; 01/31/21 11:11 AM.

Running MAME and QMC2 on Windows 10 32-Bit and 64-Bit Versions (German)
Joined: Jun 2017
Posts: 50
Member
Offline
Member
Joined: Jun 2017
Posts: 50
WOW! Don't start over! But I also suspect a corrupted database.

So, simply exit QMC2, then delete all the .db (file type 'database') from your profile (.QMC2). Be careful not to delete the .ini files. Then restart. Then 'check roms'.

I do believe this will fix your problem.

Using the 'exit - stop all active processing' button often corrupts the database. NEVER use it! If it were my product, I would remove it! If it is pressed during startup, it will result in truncated or mismatched db files.

I call it 'the corrupt the database button'.

Last edited by MusicLovr; 01/31/21 06:37 PM.
Joined: Jun 2017
Posts: 50
Member
Offline
Member
Joined: Jun 2017
Posts: 50
This is a late edit of my previous post:

WOW! Don't start over! But I also suspect a corrupted database.

So, simply exit QMC2, then delete all the .db (file type 'database') files from your profile (.QMC2). Be careful not to delete the .ini files. Then rerun Qmc2 and wait while the db files are recreated. Then 'check roms'.

I do believe this will fix your problem.

Using the 'exit - stop all active processing' button often corrupts the database. NEVER use it! If it were my product, I would remove it! If it is pressed during startup, it will result in truncated or mismatched db files.

I call it 'the corrupt the database button'.

Joined: Nov 2015
Posts: 18
L
Luzie Offline OP
Member
OP Offline
Member
L
Joined: Nov 2015
Posts: 18
Originally Posted by MusicLovr
WOW! Don't start over! But I also suspect a corrupted database.

So, simply exit QMC2, then delete all the .db (file type 'database') files from your profile (.QMC2). Be careful not to delete the .ini files. Then rerun Qmc2 and wait while the db files are recreated. Then 'check roms'.

I do believe this will fix your problem.
Hi @MusicLovr, thank you very much. It was indeed problem with corrupt database-Files from QMC2.After delete all those *.db-Files and start ROM-Auditing from scratch, ROM-Auditing runs completely OK.

Sorry @Robbbert for this false alarm. Looks really to me that QMC2 with MAME 0.228 doesn´t work, even on smallest Audit-Tests.

Last edited by Luzie; 02/04/21 08:40 PM.

Running MAME and QMC2 on Windows 10 32-Bit and 64-Bit Versions (German)
Joined: Jun 2017
Posts: 50
Member
Offline
Member
Joined: Jun 2017
Posts: 50
Glad I was able to be of some help.

Remember that errors are in the .log file, on .qmc2. Any errors, during qmc2 startup are likely an indication of some .db problem...

Page 1 of 2 1 2

Moderated by  qmc2 

Link Copied to Clipboard
Who's Online Now
2 members (MAMEBase, AJR), 46 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
Topics8,933
Posts117,404
Members4,994
Most Online890
Jan 17th, 2020
Forum Host
These forums are hosted by www.retrogamesformac.com
Forum hosted by www.retrogamesformac.com