MAME Crash when launched from Mamewah...only sometimes

[electricd]

Hello,

I recently upgraded to Mamewah 1.6 from Mamewah .97.  Since doing so I have noticed some weirdness with my cabinet.  For example:  Last night I tried to launch world class bowling from the Mamewah menu.  It acted like it launched fine, except the screen went black.  I could hear the WCB music playing but the game would not respond to buttons (tried credit, and escape, but nothing.)  I hit Ctrl-Alt-Del and saw both mame and mamewah running (neither said not responding.)  I had to physically shut the machine off to get it to stop.  This has happened a few times now (sometimes 3 times in a row even.)  I am not sure what to think.  I have looked through my log and found a few wierd things such as:


1/19/2006 2:54:19 PM MAMEWAH launched
1/19/2006 2:54:19 PM Cursor scheme: Windows default, Arrow: (None), Wait: (None), AppStarting: (None)
1/19/2006 2:54:19 PM Desktop colour: 8421376
1/19/2006 2:54:19 PM Wallpaper filename:
1/19/2006 2:54:19 PM Display mode: 0x0 @ 0Hz, 0 bit colour
1/19/2006 2:54:19 PM Decimal symbol: '.'
1/19/2006 2:54:20 PM Games list read: mame-1.lst
1/19/2006 2:54:20 PM Games list read: mame-0.lst
1/19/2006 2:54:21 PM Games list read: mame-1.lst
1/19/2006 2:54:21 PM Mode 800 x 600 @ 60, 32bit colour not available
1/19/2006 2:54:37 PM Mode 0 x 0 @ 0, 0bit colour not available
1/19/2006 2:54:55 PM Mode 0 x 0 @ 0, 0bit colour not available
1/19/2006 2:55:12 PM Mode 0 x 0 @ 0, 0bit colour not available
1/19/2006 2:55:29 PM Mode 0 x 0 @ 0, 0bit colour not available
1/19/2006 2:55:45 PM Mode 0 x 0 @ 0, 0bit colour not available
1/19/2006 2:56:04 PM Mode 0 x 0 @ 0, 0bit colour not available
1/19/2006 3:06:29 PM MAMEWAH launched
1/19/2006 3:06:29 PM Cursor scheme: Windows default, Arrow: (None), Wait: (None), AppStarting: (None)
1/19/2006 3:06:29 PM Desktop colour: 10841658
1/19/2006 3:06:29 PM Wallpaper filename:
1/19/2006 3:06:29 PM Display mode: 800x600 @ 60Hz, 32 bit colour
1/19/2006 3:06:29 PM Decimal symbol: '.'
1/19/2006 3:06:29 PM Games list read: mame-1.lst
1/19/2006 3:06:29 PM Games list read: mame-0.lst
1/19/2006 3:06:30 PM Games list read: mame-1.lst
1/19/2006 3:06:30 PM Layout selected: C:\mamewah\layouts\MyLayout\layout.lay
1/19/2006 3:07:13 PM Ctrlr file selected: C:\mamewah\ctrlr\default.ini
1/19/2006 3:12:54 PM MAMEWAH quit

Not sure what is going on with the resolution lines??  Also, what is this "verify roms" option that runs before the launch of each game:

1/19/2006 9:14:51 PM Commandline run: CMD.EXE /c c:\mame\mame.exe WCBOWL -verifyroms > C:\Mamewah\files\verify {flags=17}
1/19/2006 9:14:52 PM Commandline run: c:\mame\mame.exe WCBOWL {flags=12}


Thanks in advance!

[Minwah]

Last night I tried to launch world class bowling from the Mamewah menu.  It acted like it launched fine, except the screen went black.  I could hear the WCB music playing but the game would not respond to buttons

Not using 'frames_to_run 1' in \mame\mame.ini are you?  If not, try using the {safelaunch} flag in your (mamewah) mame.ini file - that should do it.

Not sure what is going on with the resolution lines??

Not sure either (tho I've seen this before).  What resolution is your desktop at?

Also, what is this "verify roms" option that runs before the launch of each game:

That is for the {autodosbox} feature (to determine if the roms are bad/no dumps).  This may not be required (just use {nodosbox}) for latest Mame versions as I think they moved the bad dump warning screen to the main UI.

[electricd]

Im running at 800X600 and I dont see any "frames_to_run" setting in my mame.ini either.

[Minwah]

Im running at 800X600 and I dont see any "frames_to_run" setting in my mame.ini either.

Not sure that this would affect anything but in that case refresh your mame.ini with a 'mame -cc' - to my knowledge MAMEdev haven't removed 'frames_to_run_ so it should be in there.

I don't fully understand the problem with the video mode, but are your video drivers OK?

[KenToad]

I've been having the exact same problem, most commonly with Puzz Loop (probably because that's the most played game right now).  I've set the mame Mamewah setting to "nodosbox."  I've only minimally tested, but that seems to fix the problem.  Also, I do have frames to run set to "1" using mame.87 and this just started happening recently, so I don't know what's going on.

I'll post once more if this does indeed prove to be the fix for this mystifying problem.

Cheers,
KenToad

[electricd]

I no longer have this problem with the new beta version of Mamewah.

[KenToad]

I really really don't want to update all my configs for the new version of Mamewah. 

The problem has not gone away.  I now will try Safelaunch and see if that helps.

Cheers,
KenToad

[Minwah]

The problem has not gone away.  I now will try Safelaunch and see if that helps.

Yes, I'm certain that will work.

[KenToad]

So far so good.  Will post again if it happens again.

Cheers,
KenToad