[RESOLVED] Gameex Arcade Edition, global exit does not stop MAME game

[BUR]

A few years ago, I build an Arcade machine. Inside is a Windows 10 build 20H2, it’s configured with 2 joysticks and 2x12 buttons. I choose Gameex Arcade Edition as frontend. Now, during corona lockdown, I felt it was time for a bit of tiding up. So, I started all over.

GameEx Arcade Edition 16.74. MAME 0.229b 64b bit. Nothing else.

Everything worked – I thought. I can play every game and the controls seems to work as they should.

When I hit the Joystick Exit buttons as defined in “Global Exit” there is a problem.

First of all, they seem to react much slower than in my previous installation. But the real problem is that it does NOT shut down the MAME game I was playing.

Global Exit does return me to Gameex Arcade, and I can start a new game. But the one I started with, is still running in the background. When I exit Gameex Arcade I find to programs running. One black cmd-windows with the text: “Active code page: 65001”, and secondly the MAME game itself. When I kill the cmd-windows the MAME game disappears. If I kill the MAME game, the cmd-windows disappears.  

So, I guess I’ve made some kind of faulty setup. Any idea on how to make a correct Global Exit that kills the MAME game.

Included log of latest attempt to play and exit asteroid. Afterwards I stopped asteroid as described.

BUR, Denmark

log.txt GameEx.ini

[Tom Speirs]

im not too sure, but perhaps a permission issue. is mame.exe flagged to run as admin or does gameex.exe have enough rights to kill a process?

[BUR]

I am local administrator. Neither Gameex Arcade not MAME is set to run as Administrator. I am starting to wonder if the problem is in MAME configuration, not in Gameex configuration. When a game is running, and I hit the Global Exit, what does Gameex actually do? Send some kind of a keypress or perhaps the TASKKILL command?

 

[BUR]

Experiment: I ran Gameex as administrator, it didn't  help. 

[Tom Speirs]

Maybe an unusual version of MAME?

 

Could be something changed in an update of MAME or windows and you are first to report it.

 

I will test myself shortly.

[BUR]

Experiment: Downloaded 0.228b 64bit.  Extracted only mame64.exe and mame64.sym to the MAME folder. Not quite sure if this approach is OK, maybe other files are needed. Redirected Gameex to use the MAME64.exe file.  It didn't help. 

[Tom Speirs]

Im able to duplicate it. Should be fixed shortly.

Its due to changes in MAME. Maybe it started in 0.228.

[Tom Speirs]

Fixed in 16.82. Now available.

Thank you for reporting the issue.

[BUR]

Thanks a lot. Downloaded, installed an tested. All OK :-)