GameEx 4.55 - Out

[Tom Speirs]

13th July 2005
- GameEx 4.55

• Should fix issues on some
  systems, that when returning to MCE or pressing
  Green Button MCE did not have focus.
• Focus will now return to
  GameEx if Emulator exits immediately after
  launching.
• Maximum number of emulators
  and external applications increased from 100 to
  300.
  

---

[djrobx]

The hanging when immediately returning bug is fixed.

Still have that focus issue though. MCE comes up and focuses itself, but then seems to go into the background once GameEx finishes closing.

The problem has something to do with HideOS. If I copy notepad.exe to hideos.exe, MCE comes back and stays focused without a problem.

[djrobx]

Oops, problem with the fix

Now one of my working configs (cmd.exe /c [Romfile]) starts the app, but GameEx comes back without waiting for it to finish.

[Tom Speirs]

Oops, problem with the fix

Now one of my working configs (cmd.exe /c [Romfile]) starts the app, but GameEx comes back without waiting for it to finish.

Changing 'cmd.exe /c [ROMFILE]' to just '[ROMFILE]' I think will do the trick.

Does that work?

[Tom Speirs]

Changing 'cmd.exe /c [ROMFILE]' to just '[ROMFILE]' I think will do the trick.

Does that work?

Or

start /wait [romfile]

This functionality was a bug, so its staying.

[djrobx]

I'm not sure I understand why the old behavior was a bug, cmd is a running process, and stays there until the application exits, so why doesn't GameEx "see" it?

The ROMFile in this case is a .BAT file. It took me a bit to figure out how to get START to work right for program names with spaces. If you try and START a program with quotes, e.g.

start /WAIT "Test me.bat"

it would just open a command prompt. If you tried it without the quotes:

start /WAIT test me.bat

You got an error because it couldn't fnd the "test" file. Apparently if you have quotes it thinks you're titling the window, so you have to do:

start "Blah" /WAIT "[RomFile]"

Of course, the end result was it didn't matter, it behaves exactly like cmd dot exe slash c [RomFile]. It won't even work if I launch a bat file in my custom executable. My executable continues to run but GameEx comes back to the menu.

I just did a test. It seems that GameEx returns to the menu if cmd exe is loaded *anywhere*. For instance, I set my command line to notepad.exe. Notepad opens up as expected. All is good. Now I start->run and type "cmd" ... BAM! I'm back in GameEx, and Notepad is still running.

The good news is the focus is returned to MCE beautifully in 4.56!! Thanks for the great work.

- Rob

[Tom Speirs]

I'm not sure I understand why the old behavior was a bug, cmd is a running process, and stays there until the application exits,  so why doesn't GameEx "see" it?

The ROMFile in this case is a .BAT file.  It took me a bit to figure out how to get START to work right for program names with spaces.  If you try and START a program with quotes, e.g.

start /WAIT "Test me.bat"

it would just open a command prompt.    If you tried it without the quotes:

start /WAIT test me.bat

You got an error because it couldn't fnd the "test" file.  Apparently if you have quotes it thinks you're titling the window, so you have to do:

start "Blah" /WAIT "[RomFile]" 

Of course, the end result was it didn't matter, it behaves exactly like cmd dot exe slash c [RomFile].  It won't even work if I launch a bat file in my custom executable.  My executable continues to run but GameEx comes back to the menu.

I just did a test.  It seems that GameEx returns to the menu if cmd exe is loaded *anywhere*.    For instance, I set my command line to notepad.exe.  Notepad opens up as expected.  All is good.  Now I start->run and type "cmd" ... BAM!  I'm back in GameEx, and Notepad is still running. 

The good news is the focus is returned to MCE beautifully in 4.56!!    Thanks for the great work.

- Rob

Yes, quite right, my bad, that was exactly the problem. Another bug, but fixed now.

It was checking for any difference in no. of instances of the process called, and not just less instances of the process called.

[Tom Speirs]

Yes, quite right, my bad, that was exactly the problem. Another bug, but fixed now.

It was checking for any difference in no. of instances of the process called, and not just less instances of the process called.

By the way Rob, thanks for all your help. I think your my MVP right now