Recent Posts

Looks like a fantastic solution.. Enjoy!!

Great story, fantastic looking setup, hope you enjoy it for years to come.

Zeosstud

Good spot, exactly, this is where they are fitted. All reused from the original panel, no brainwork involved on my end 

Ok. Thank you for the detailed responses. I'll tinker a bit more and report back. I'll attach a log file if I can't sort it out. It might take some days. Probably next weekend.
One thing I do see is that my system never generates 2560x... modes. It is always much lower though 2560 is in mame.ini super_resolution it's called if I'm not mistaking.
I do not understand why it behaves that way but I'll document it and report back.
I also started from a fresh ini created with ./groovymame -cc.
The dotclock 6.0 is what made Cabal work.
I'm not using RetroArch. It's a bash shell with groovymame 0.280 and some scripts around it.

another video showing the problem


https://youtube.com/shorts/PJ_gMrO0Ang?si=qH5jVV3A6qE2WKwM

Hi Alex,

I wouldn't touch that PC. Even in 2025.

If you really want to upgrade, specially with that Ryzen 5700G, then you should definitely leave Windows behind and move to Linux (Groovy Arcade). That means no Hyperspin (which honestly I'm surprised it's still around). The thing with the 5700G is that it's an APU that is directly supported for 15 kHz through DP->VGA adapter. You could still use your 7850 although I doubt the new motherboard uefi will show through the modded bios.

Yes, the method explained by Zebidee is how this is supposed to be handled.

Give that a game has a 'Working' status in MAME is it correct to expect GroovyMAME to show at least some output on screen when launched with a preset.

Yes, GroovyMAME will always show some output on the screen. If you have a certain game that goes out of sync, try to find the reason. If you have dotclock issues, 8.0 is a reasonable minimum (rather than 6.0). Note that the lower end of admitted dotclocks may have gaps (i.e. 5.5 may work, 5.6 not, etc.) until you find a number that works fine from there on.

Hi go2ldook!

Some good advice from Neil in the last post. Just thought I'd add:

>> Even tried running as admin. When I click START I get a brief screen pop-up then nothing.

Unfortunately, WIndows 11 is very strict on what executables it allows you to run these days. When you click the GUI Launcher's START button, the GUI Launcher will attempt to run mgpr.exe with various command line arguments. Even though you may have run gui_launcher.exe as admin, those privileges don't automatically get assumed by mgpr.exe.

Thus, can you make sure you have given administrator privileges to both gui_launcher.exe and mgpr.exe. I.e. For both files, right-click and select 'Properties', go to the 'Compatibility' tab, check the box for 'Run this program as an administrator', click Apply, and then OK.

Hope this helps

GroovyMAME 0.283 is out!

Installed on Windows 11 and will not run from cmd line or using the application. Even tried running as admin. When I click START I get a brief screen pop-up then nothing.

Runs fine on Win11 24H2 for me. A couple of things to be aware of:

• You have to fully extract the archive. Don't try to run the exe from the Windows explorer view of the archive folder without extracting
• When launching from command line the terminal has to have the current working dir as the dir with the mgpr.exe in. i.e. cd to this dir first and run only with command mgpr.exe - do not provide a path to the exe from another dir