Trouble mamewah 1.61 and Duke Nukem - MP (Now with more info)

[SpamMe]

I updated mamewah to 1.61 (from 1.5) recently, and I'm having trouble with Duke Nukem Manhattan Project now.
It opens correctly, it plays alright, but it seems that mamewah retains simultaneous focus while playing (I'll cycle through gamelists, open other games, or multiple instances of DN etc). This doesn't happen with any other games, PC or otherwise, and seems to be new to this version of mamewah (or maybe one in between 1.5 and 1.61). I assume I'm doing something wrong, any pointers?


[Edit]: More info in bottom-most post.

[DreamWeb]

I use windows shortcuts for all of my PC games..  So, I setup Mamewah to look for .LNK (s) in a particular folder, and then I direct each LNK to the PC game.  They all play perfectly (including Duke Nukem MP).

d.

[SpamMe]

Ayuh, same here (frankly I'm not aware of any other way of doing it, really), and that's the only one giving me any trouble.

[DreamWeb]

Not sure if this will help.. but.. here is my .ini for PC games.

----------

### 0021.ini (mamewah v1.61) ###

emulator_title                            PC Games

### List Generation Settings ###
rom_path                                  c:\systems\pc
rom_extension                             lnk
dat_file                                 
nms_file                                 
catver_ini_file                           
list_generation_method                    rom_folder

### Execution Settings ###
emulator_executable                       PC
commandline_format                        "[name].[romext]"{nodosbox}{nosafelaunch}{cursor}
alt_commandline_format_1                  [name]
alt_commandline_format_2                  [name]
game_specific_config_path                 

[SpamMe]

Thanks. My commandline format was slightly different but I'm having the same effect with both (and again, only with that one pc game and no others).

[Minwah]

All I can suggest is to try {safelaunch}, and {dosbox} - the former should have most effect (hopefully) 

[DreamWeb]

Like I already said.. my Duke works fine.  But, I know how it feels.  I have about 3 PC games that SHOULD work... that don't, from Mamewah.

d.

[SpamMe]

Had a few minutes to play around with this again today. Some things I've learned:

• It seems that the actual duke nukem executable (which runs a dialog once, allowing you to set 3d devices and so forth) spawns an exe called prism3d.exe and then closes. It's at this point that mamewah decides the original application has closed, and begins accepting key input again (even though there's a fullscreen application covering it up). After the first run, the first dialog isn't shown.
• The game can be run from explorer via the prism3d.exe directly with no obvious difficulties, but
• Prism3d.exe, if run from mamewah via shortcut does the following:
• Won't play audio or music
• Won't accept keyboard or joystick input
• Will prevent mamewah from deciding that the application's closed before it has. Mamewah will not accept keyboard input until prism3d actual exits.
• Above seem to happen with all configurations of {dosbox}/{nodosbox} and {safelaunch}{nosafelaunch}, and regardless of whether mamewah is running as a shell or not.

Follow up to follow up. When launching the Prism3d.exe directly from mamewah, it's just not getting focus. If, through a combination of alt-tabbing, and ctrl-alt-deleting, I can get Prism3d.exe to gain focus, sound as well as keyboard input return.

So a run down: Running the dukenukem.exe causes mamewah to think the game's closed before it has, and allows input to both the game and mamewah at the same time. Running the prism3d app from mamewah will not focus the game and neither mamewah nor the game will accept key input.

[edit number god-knows-how-many]The focus issues I'm now having are too numerous to address in this thread (for instance, setting {nodosbox} in a pc game causes any game afterwards (eg in mame) to start minimized.