Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: peanut on April 17, 2006, 02:59:06 pm
-
Is anyone else using the beta version of mamewah getting this error on startup?
Runtime Error 91 may occasionally occur in MoviePlay (fixed?),
>
> 3/30/2006 1206 AM Error: 9 Subscript out of range in Movie_Stop
No one has posted a reply on the mamewah message board, which is why im asking here.
-
Ya I was getting that error too.
I had to reformat and put Windows on to get it working, after that everything perfect.
Hope that helps you.
-
thats not the answer i was looking for ???
-
thats not the answer i was looking for ???
Don't do it...reinstalling windows should have no direct effect on Mamewah's behaviour.
I can't get this error to occur on my system, but a handful of people have mentioned it so I'll be taking a look into it at some point...
If anyone could give me any more info it would be useful...such as when this occurs, is it with a startup/preview/exit movie etc.
-
My error happens within the first seconds of booting the new copy of mamewah. I havent set anything up, i just ran the EXE to generate my list, but cant get that far.
-
My error happens within the first seconds of booting the new copy of mamewah. I havent set anything up, i just ran the EXE to generate my list, but cant get that far.
Do you have an intro movie set in mamewah.ini? If so, try removing it...
-
Maybe you don't have the right video codec installed to read your movie. Try playing the same movie in Windows Media Player.
-
The videos work fine in the normal version of mamewah and in WMP. I wanted to use the beta to fix the random errors that sometimes make it crash.
-
That what was happening to me, start it up then about 5 seconds later went back to Windows.
I did have to redo Windows so I didn't do it just to get mamewah working but I insalled the same software I had on before, but this time it worked fine.
I never had any intro movies playing.
But a great release Minwah, a lot more easy to get the layouts set up now.
-
FWIW I have the same error.
I also have a fresh install of mamewah 1.62.
Mamewah log:
4/23/2006 11:34:13 AM MAMEWAH v1.62 launched
4/23/2006 11:34:13 AM Cursor scheme: Windows default, Arrow: (None), Wait: (None), AppStarting: (None)
4/23/2006 11:34:13 AM Desktop colour: 0
4/23/2006 11:34:13 AM Wallpaper filename:
4/23/2006 11:34:13 AM Display mode: 1400x1050 @ 60Hz, 32 bit colour
4/23/2006 11:34:13 AM Decimal symbol: '.'
4/23/2006 11:34:13 AM Error: 9 Subscript out of range in Movie_Stop
4/23/2006 11:34:13 AM Games list read: -0.lst
4/23/2006 11:34:13 AM Error: 9 Subscript out of range in Movie_Stop
4/23/2006 11:34:14 AM Mode 640 x 480 @ 60Hz, 16bit colour selected after 2 attempt(s) at 1/2 second intervals.
4/23/2006 11:34:14 AM Layout selected: C:\mamewah\config\\\layout.lay
4/23/2006 11:34:15 AM No. joystick devices attached: 0
4/23/2006 11:34:15 AM Ctrlr file selected: C:\mamewah\config\mamewah.cfg
4/23/2006 11:34:15 AM Keyboard enabled
4/23/2006 11:34:15 AM Mouse enabled
4/23/2006 11:34:19 AM Error: 9 Subscript out of range in Movie_Stop
4/23/2006 11:34:20 AM Mode 1400 x 1050 @ 60Hz, 32bit colour selected after 1 attempt(s) at 1/2 second intervals.
4/23/2006 11:34:21 AM MAMEWAH quit
More info:
-I do not have any movies
-my copy of mamewah 1.61 works fine
-when i launch 1.62 I only get a quick flash of ...an internal error has occurred... before it shuts down
-the layout doesn't seem to load either.
-Also, with mamewah 1.61, the default layout never worked either. I had setup one using mamewah config. Before I set up a layout, mamewah would flash a message ...an internal error has occurred... and then shut itself down. Probably not related but thought i might as well mention it.
-Joe
-
same thing with me, except never had a prob with 1.61
-
More info:
-I do not have any movies
Well, that's just not right! :angry:
-
This is interesting...thanks for the additional info people. Seems to be affecting more and more people (although still not me!) so I'll have another look around...
-
For those affected I *think* I have made a revision which should prevent this problem in future - please try the next beta when available* and let me know if the problem remains...
* Sorry I cannot give any ETA for this as I am very busy at work and in free time with other things for the near future. I am working on it, just in a gradual bit by bit kind of way :-\
-
Any news on b11 Minwah ?
Thanks
Bulla
-
Any solution for this? I have the same error. It's a stripped version of XP and I dont want to use any movies. v1.61 has been working great.
Thanks,
Steve
-
Any news on b11 Minwah ?
Not yet...I got quite a lot done a few weeks ago but haven't had time to touch it since then :( AFAIK I only have 2 bugs left to fix so it shouldn't take me too long when I get chance to look at it. I was going to add a few features but might knock that on the head until b12...
-
Darn, I just started getting this error too on a fresh install of 1.62b10 with no modifications to anything, just running mamewah for the first time (ie no movie specified). I'm running Win98SE if that matters...
Sucks because all the example ini files I am finding are for 1.62. :(
-
*SOLVED SINCE I POSTED THIS EARLIER*
But I'm leaving everything I typed, just in case it helps someone somehow.
Scroll below this block to see what I found out.
-----------------------------------------------------------------
OK Minwah, I'm not sure if this will make things better or worse for you, but I've now gotten this error on two systems, and the following things have been in common both times:
1) an external USB hard drive was involved.
2) Mamewah first ceases to scan the config folders for available platforms. At first, it simply runs the one platform listed in mamewah.ini (NEXT_PLATFORM and PREV_PLATFORM do nothing, and SELECT_PLATFORM shows a list containing only the current platform)
3) Eventually, somehow, mamewah.ini loses the setting for CURRENT_EMULATOR, and I start getting "Error: 9 Subscript out of range in Movie_Stop" and Mamewah refuses to run.
4) Manually setting CURRENT_EMULATOR to any valid folder name (i.e. 01MAME) allows that one platform to run. SELECT_PLATFORM shows that one platform only, no others. NEXT_PLATFORM and PREV_PLATFORM still do nothing.
Now, for the odd bits...
1) My Mamewah 1.62b10 setup has been running flawlessly since about March 2006. I first noticed this problem when I copied all files to an external USB drive and took it to a friend's house. Immediately, all of the above problems were evident. I blamed it on everything, from him running XP (I run 2K) to his crappy external hard drive, but thaty didn't make it work. I don't think he ever got it working for more than one platform.
And most odd of all....
2) My perfect, flawless, can't be messed up configuration.... DIED LAST NIGHT and began exhibiting all symptoms. Guess what I did? I had begun copying all the files to an external USB hard drive for a friend, and the copy was interrupted, and upon rerunning the copy, I accidentally went FROM his drive to MINE. I can absolutely guaran-dang-tee you that the files were I-DENTICAL. And yet, immediately afterward, Mamewah began exhibiting all symptoms on what had been a stable setup for almost 9 months.
I run no movies, nothing of the sort. Just a basic get in, play, get out setup. And yet, even with no movie info, that's the error I get. Error 9, MOVIE_STOP.
I don't suppose my config files or log files or anything would help you?
Chemame
*EDIT* OK Minwah, your head will spin with this one. After fighting and fighting and fighting with it, I came to the conclusion that it simply HAD to be some sort of permissions problem making mamewah think it couldn't read those folders. I tried EVERYTHING, man... I copied all the folders to a new location, reset all permissions on them, even tried archiving them all up with winrar then extracting to a new location. Nothing. No change... and THEN... copied just the EXE and related files to a new location, ran it, got a brand new CONFIG folder... went into there, created 01MAME and 02ATARI2600 in there, and copied all the files into there... now, just to be crazy, I didn't copy the INI files. I opened them in textpad and saved them in the new folders.
Anyway... IT WORKED. Mamewah now reads two platforms: 01MAME and 02ATARI2600. Go figure. I haven't extrapolated out yet to restore my other 10 platforms, but I see no reason why it won't work.
Also, I don't know what made me open/save the ini files via textpad, except that I was trying to avoid filesystem copies whenever it was easy to do so. I don't know that that is part of what got it working again.
I've got to head out for the evening, but I'll try some more when I get home, see exactly which piece restored it. It was EITHER the "mamewah created a fresh config folder", or "textpad saved out new INI files". I don't think my new 01MAME and 02ATARI2600 folders are part of the solution, because I had already tried creating new folders under my existing setup, and it didn't help.
Somehow right now my money is on the newly created config folder. Not sure why I suspect that though.
I'll post more when I know more.
Chemame
----------------------------------------------------------------
Okay, I know more. It is not related to EITHER the config folder OR the ini files. Contrary to everything I suspected, it WAS the platform subfolders underneath config.
The error 9 is somehow related to Mamewah THINKING it has config files to read, and then for whatever reason not finding them when it actually goes to read them. I can reproduce this error 9 every time (a phantom error IMO, because I don't use movies), by simulating what happened to me, as follows:
1) edit mamewah.ini, wipe out setting for current_emulator (just leave it blank)
2) tag all platform config folders (01mame, etc) and mark them as "this folder is ready for archiving". You don't need to have it do all subfolders & files, just the selected items will recreate the problem.
That's it. Run mamewah, you'll get an internal error, no games listed, and when you view the logfile, you should see error 9/movie_stop
My rough guess is, for a new install, mamewah.ini has no setting for current_emulator, and maybe somehow people are getting copies of existing config folders with the archive glag set, thus satisfying #1 and #2 above? Not real sure. In my case, the archive bit was somehow set by transfer to/from the usb drive (through linux, even!), and current_emulator was wiped out while I was bumbling around trying to solve the immediate problem of NEXT_ and PREV_ not working.
Anyway. Like I said I can now force (or fix) this particular problem every time on my setup. Hopefully it helps someone.
Chemame
-
okay, so one last thought.
I figured I might as well cron a job of attrib -a config/*, so if things got out of whack they would get rewhacked without me having to go do anything.
Would you believe the attrib command won't work on directories by default? You need to add the /d switch. Which, you know, whatever... but would you believe /d throws an error telling you you must also use /s? And /s is recursive. I don't WANT recursive. I mean, yeah, it doesn't hurt anything, but why do more than you have to? Thank you, Microsoft!
Chemame
-
Thanks for your testing Chemame...that sounds pretty comprehensive. I have not yet investigated this but from what you say it sounds like you have found the problem, and it shouldn't be too hard to fix. At the same time I am not sure why the archive attribute affects things but there we are...
Cheers!
-
I hate to say it....but following chemame's instructions do not make the slightest bit of difference to my Mamewah meaning I still don't know how to reproduce this damn problem! >:(