*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
Home
Help
Search
Login
Register
Send this topic
Print
Topic: Mamewah beta error? (Read 3697 times)
