Home Page Forums MAME QMC2 Patched Version of QMC2 not working on MAME 0.228

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 ?!

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.

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"

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

Sorry, I don´t know. Maybe I should try with older MAME 0.227.

Sorry, I don´t know this too.

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.

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

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

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

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.

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