I saw this in another thread, and I think it deserves more attention. Maybe if it proves useful, this can become a sticky thread...
This is the main reason I disabled -mt by default in GroovyMAME: HyperSpin users massively complaining about stability issues that do not occur with other frontends. On the other hand, now that we have -mt disabled by default all users are massively complaining about vertical games running slow. The dilemma is, if I want to release GroovyMAME with all the options set by default to provide the experience as it is intended to be, then I kill HyperSpin users. Then I think about it and since the release of CRT Emudriver several years ago I've been fighting with issues directly related to this frontend, and I'm a bit tired of it. I'll end up advising specifically against HyperSpin if using GroovyMAME. Emulation quality must be the priority IMHO, not frontend cuteness.
...
In other words, in order to have vertical games like Galaga running at 100% you'd need -triplebuffer which also requires -mt enabled, but because you can't enable it due to HyperSpin then the suboptimal solution is to force everything to be synchronized regardless of the speed variations.
So, given the limitations and annoyances of HyperSpin (and there have been more than the particular issue above), what should we be using instead?
Back in the day, when I was running Windows 98, I used MameWah as my frontend, but I understand that development on it stopped a long time ago.
I'm currently running GroovyMAME on a 15KHz arcade monitor with a Radeon x600 (I also have a Radeon HD 4550 available). My OS is Windows XP x64 Edition. I believe that the highest windows desktop resolutions I can use are 640x288 (non-interlaced) and 640x480 (interlaced). I think that back when I was using an ArcadeVGA, I was able to run 512x512 (interlaced) on my monitor and it actually looked better than 640x480 (interlaced) but it's not a 4:3 aspect ratio, so if the frontend displays artwork, it may look weird. Personally, I'd be happy with a text-only frontend at 512x512.