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)