Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: Farmboy90 on January 18, 2006, 12:31:12 am
-
Hey Minwah,
Frequently while scrolling through my list of games mamewah will craash and exit. Here is the log (it is always the same error):
1/17/2006 10:25:23 PM MAMEWAH launched
1/17/2006 10:25:23 PM Cursor scheme: Windows default, Arrow: (None), Wait: (None), AppStarting: (None)
1/17/2006 10:25:23 PM Desktop colour: 9981440
1/17/2006 10:25:23 PM Wallpaper filename:
1/17/2006 10:25:23 PM Display mode: 800x600 @ 75Hz, 32 bit colour
1/17/2006 10:25:23 PM Decimal symbol: '.'
1/17/2006 10:25:23 PM Games list read: 0000-1.lst
1/17/2006 10:25:23 PM Layout selected: C:\mame\mamewah\layouts\_installed layouts\0000.lay
1/17/2006 10:25:24 PM Ctrlr file selected: C:\mame\mamewah\ctrlr\default.ini
1/17/2006 10:26:11 PM Games list read: 0000-1.lst
1/17/2006 10:26:33 PM Commandline run: c:\mame\mame.exe "c:\mame\roms\NEWFANT.zip" {flags=9}
1/17/2006 10:28:26 PM Error: 91 Object variable or With block variable not set in Music_Play1/17/2006 10:28:33 PM MAMEWAH quit
Any ideas why it does this?
By the way, is the source code available? Maybe I could debug it...
-
Frequently while scrolling through my list of games mamewah will craash and exit. Here is the log (it is always the same error):
Which version of Mamewah? I thought this was an old bug which has been fixed...
Any ideas why it does this?
Not yet, but it has something to do with the music playback.
By the way, is the source code available? Maybe I could debug it...
Not currently, sorry.
-
- Version 1.61
- The music plays fine, so do the sound effects (I have a navigate sound). They seem to play even when the program crashes.
- Shoot. No source code? Why not open source it? Or at least give it to your good buddy over here. :) I would love to help debug at the very least.
So what bug was supposed to have been fixed? I mean what was the issue? Maybe that can shed more light on what I am seeing.
-
Hey Farmboy,
Are you sure you don't have a stuck key? I read your posts on the other forum. I had a stuck key once and it made a lot of things crash. I don't use mamewah but a lot of weird things happened to Mame32.
My I-pac is older and doesn't have the led but I would test it by plugging a keyboard into the pass through and pressing Ctr Alt P or something like that. Testing for a stuck key should be listed on Andy's site.
As you said on the other forum, you'd think a stuck keywould effect whatever switch was stuck consistantly but that didn't happen in my case. Anyway, it's worth a shot and may explain your second player dying all the time.
-
Hey Farmboy,
Are you sure you don't have a stuck key? I read your posts on the other forum. I had a stuck key once and it made a lot of things crash. I don't use mamewah but a lot of weird things happened to Mame32.
My I-pac is older and doesn't have the led but I would test it by plugging a keyboard into the pass through and pressing Ctr Alt P or something like that. Testing for a stuck key should be listed on Andy's site.
As you said on the other forum, you'd think a stuck keywould effect whatever switch was stuck consistantly but that didn't happen in my case. Anyway, it's worth a shot and may explain your second player dying all the time.
Thanks for the tip. The MameWAH crash doesn't happen all the time. Seems to only crash when I scroll one by one through the list (which is rare). I only happened to be doing it last night as I was trying to weed out games. Normally I pageup/pagedown and then scroll to the game I want.
At any rate, yes I have a keyboard plugged into the IPAC passthrough. When I hit ctrl-alt-p the IPAC tool comes up and reports nothing unusual.
Although you just reminded me of something. This probably has something to do with DOS and whether echo is on of off or something, but here is what I do to get to the IPAC tool.
- Launch a dos prompt
- Type 'copy con' at the prompt and hit return
- Then hit ctrl-alt-p
The IPAC tools comes up but prints everything twice. Is that normal? I don't remember all the options the tools lists, but my window will look something like this when I enter the IPAC tool mode:
Welcome to IPAC blah blah blah
Welcome to IPAC blah blah blah
Press t for test mode
Press t for test mode
Press e to save and exit
Press e to save and exit
Press a to abort
Press a to abort
Weird or normal? :)
-
Frequently while scrolling through my list of games mamewah will craash and exit. Here is the log (it is always the same error):
Which version of Mamewah? I thought this was an old bug which has been fixed...
Any ideas why it does this?
Not yet, but it has something to do with the music playback.
By the way, is the source code available? Maybe I could debug it...
Not currently, sorry.
By the way Minwah, is there a plan to support animated backgrounds in mamewah?
-
I had an issue with the ipac not long after I installed it when it would you random weird stuff. After a bit of hair pulling, it turned out to be a connection that kept crossing due to my shoddy positioning and wiring.
Just a suggestion.
Cheers,
Brad
-
Hmmm.....I don't remember the ipac printing things twice but it has been a while since I've triend it. I will give it a shot either tonight or tomorrow morning when I'm near my cab. I'm sure you did this but did you hit t during test mode?
-
I just ran into a very similar Mamewah crash:
Running 1.62b9
1/18/2006 11:33:03 PM Error: 91 object variable or with block variable not set in movie_play
1/18/2006 11:33:09 PM MAMEWAH quit
It was the same scenario as listed above, scrolling through games one at a time (looking at all of the game videos I installed yesterday).
-
I just ran into a very similar Mamewah crash:
Running 1.62b9
1/18/2006 11:33:03 PM Error: 91 object variable or with block variable not set in movie_play
1/18/2006 11:33:09 PM MAMEWAH quit
It was the same scenario as listed above, scrolling through games one at a time (looking at all of the game videos I installed yesterday).
I get these errors as well.
-
- Version 1.61
Give the latest beta a shot - I've done quite a lot to the sound stuff since v1.61.
- Shoot. No source code? Why not open source it? Or at least give it to your good buddy over here. :) I would love to help debug at the very least.
Good try ;)
So what bug was supposed to have been fixed? I mean what was the issue? Maybe that can shed more light on what I am seeing.
Just the same error message occurring...I might well have fixed it between 1.61 and 1.62b9 (hopefully).
PS install the beta to a new directory so not to mess up your current Mamewah setup.
-
By the way Minwah, is there a plan to support animated backgrounds in mamewah?
Probably one day, but I will be re-writing the layout system and moving to DirectDraw first.
-
1/18/2006 11:33:03 PM Error: 91 object variable or with block variable not set in movie_play
See if this happens on any specific game(s)/movie(s). If so check the movies are OK (in Media Player or whatever)...
-
Probably one day, but I will be re-writing the layout system and moving to DirectDraw first.
Just curious what you're using now, straight VB6?
-
PS install the beta to a new directory so not to mess up your current Mamewah setup.
The only place I found the zip of the beta was on the mame forum and I don't have an account there (and didn't bother to create one since I am lazy ;D).
So I will just wait until you post the final release and then let you know if I still have problems.
Thanks Minwah
-
Just curious what you're using now, straight VB6?
Yep, with DirectX for input, sound, movie playback etc...
-
1/18/2006 11:33:03 PM Error: 91 object variable or with block variable not set in movie_play
See if this happens on any specific game(s)/movie(s). If so check the movies are OK (in Media Player or whatever)...
It isn't movie specific. It will just crash. Relaunch mamewah and try the same movie again and it works.
-
I just ran into a very similar Mamewah crash:
Running 1.62b9
1/18/2006 11:33:03 PM Error: 91 object variable or with block variable not set in movie_play
1/18/2006 11:33:09 PM MAMEWAH quit
OK I can't see why this is occurring, so I have made a change to basically ignore this error when it occurs. Since I cannot replicate the bug, I do not know what effect this will have (movie might stop playing etc.). Please give the next beta release a try when available, and see what happens. If anything adverse does occur at least it might give a better indication of what is actually wrong.
-
The only place I found the zip of the beta was on the mame forum and I don't have an account there (and didn't bother to create one since I am lazy ;D).
So I will just wait until you post the final release and then let you know if I still have problems.
As per this thread: http://forum.arcadecontrols.com/index.php?topic=48998.0
...just so you are aware the MusicPlay problem shouldn't be present with the latest beta. From what Extreme8 has said it seems the MoviePlay problem is still there tho - check the next release when available.
-
Hey,
I've installed Mamewah onto my pc but it doesn't load & I keep getting the same error,
Error: -2005401480 Automation error in SFX_InitialiseDS
I've also installed the system files and Direct-X.
I've looked around but couldn't find any info on this, if anyone knows what the problem might be it would be a great help if you could let me know.
-
Error: -2005401480 Automation error in SFX_InitialiseDS
It could be that either your sound drivers are bad, or not DirectX compatible - try reinstalling them.