MAMEWAH Bug list.. POST HERE.

[JoeB]

Moderators.. please make this thread sticky..

I think it's only fair to have all the bug reports in one place.  Makes it easier for everyone, especially the author.

In my opinion, Mamewah is the best windows based front-end for a true arcade machine, and getting the bugs out of it will make it only better.

Please post all your bug reports here.  Include version number, and how to reproduce it.

[JoeB]

MAMEWAH 0.96

MAMEWAH looses focus very easily.

What happens is MAMEWAH sometimes looses focus, and I have no way to bring it to the forground (this is especially true if I have a keyboard plugged into the J-PAC when windows XP boots).

The only fix is to restart mamewah, exit it.. the 1st MAMEWAH suddently has focus again, but running at 640x480 rather than 368x240, I select exit, and restart MAMEWAH again..

BANG: MAMEWAH.CFG is corrupt.  Only a few of the top lines are there.

POSSIBLE FIX: let MAMEWAH parse a command line parameter where it does not touch any config files (useful if running for CD or DVD?)

[JoeB]

MAMEWAH 0.96:

Every time I try to switch emulators in MAMEWAH, it crashes on me with the following error:


Run-time error '384':

A form can't be moved or sized
while minimized or maximized.


I'm using custom layout files with backgrounds set.  If I try to use the layout files that came with MAMEWAH, no problem.

I have just manged to narrow it down to something in the layout file that Mamewah doesn't like.. (even the older version).  The wierd thing though, if I tell MAMEWAH to use a specific default (current) emulator, it loads it fine!

If I use MAMEWAH to switch to another, it crashes.. if I manually switch it in the MAMEWAH.CFG file, it loads it fine.

further more, the layout editor created this file.

[JoeB]

MAMEWAH 0.96:

MAMEWAH writes out to emulator config files every time it switches to another causing data loss.

E.G:

Select Emulator #3 as the current one.  Use another PC to connect to your arcade machine via windows filesharing for maintenance.  Modify the settings inside EMU3.CFG remotly and save it.

MAMEWAH doesn't pickup nor use these settings.  You have to be in another emulator in order to modify the config file.

PROBABLE FIX: Allow command prompt command line disable of config rewrite.

[Minwah]

MAMEWAH 0.96

MAMEWAH looses focus very easily.

What happens is MAMEWAH sometimes looses focus, and I have no way to bring it to the forground (this is especially true if I have a keyboard plugged into the J-PAC when windows XP boots).

The only fix is to restart mamewah, exit it.. the 1st MAMEWAH suddently has focus again, but running at 640x480 rather than 368x240, I select exit, and restart MAMEWAH again..

BANG: MAMEWAH.CFG is corrupt.  Only a few of the top lines are there.

POSSIBLE FIX: let MAMEWAH parse a command line parameter where it does not touch any config files (useful if running for CD or DVD?)

I never seem to have this problem.  Is it set as your shell?

[Minwah]

MAMEWAH 0.96:

Every time I try to switch emulators in MAMEWAH, it crashes on me with the following error:


Run-time error '384':

A form can't be moved or sized
while minimized or maximized.


I'm using custom layout files with backgrounds set.  If I try to use the layout files that came with MAMEWAH, no problem.

I have just manged to narrow it down to something in the layout file that Mamewah doesn't like.. (even the older version).  The wierd thing though, if I tell MAMEWAH to use a specific default (current) emulator, it loads it fine!

If I use MAMEWAH to switch to another, it crashes.. if I manually switch it in the MAMEWAH.CFG file, it loads it fine.

further more, the layout editor created this file.

Could you email me the layouts you are using?  I just tried a few of Cave's multi emulator layouts and they seemed to work OK for me...

[Minwah]

MAMEWAH 0.96:

MAMEWAH writes out to emulator config files every time it switches to another causing data loss.

E.G:

Select Emulator #3 as the current one.  Use another PC to connect to your arcade machine via windows filesharing for maintenance.  Modify the settings inside EMU3.CFG remotly and save it.

MAMEWAH doesn't pickup nor use these settings.  You have to be in another emulator in order to modify the config file.

PROBABLE FIX: Allow command prompt command line disable of config rewrite.

I don't really consider this a bug...I did not intend for the CFG files to be altered while MAMEWAH is running.  The reason this happens is that the EMU?.CFG stuff is held in memory, and then written to file whenever you switch emulator, or change some options.  You are changing the file which is going to be written over anyway.

If you must alter things why MW is running, why not just select a different emulator while you make the changes?

BTW Thanks for making this thread, I probably should have done so myself  

[papaschtroumpf]

MinWah, I have more details about the "access denied" crash I was getting. It seems that when I crash the first time there is a new file called VERIFY in my mamewah directory, and mamewah won't start again (run time error 70, access denied) until I delete that file.

I emailed you the details.

Does this help?

I suppose I could run a batch file before mamewah to delte the file if it exists but that seems kludgy and we still don't know wht caused it to crash in the first place.

[JoeB]

MAMEWAH 0.96

MAMEWAH looses focus very easily.

What happens is MAMEWAH sometimes looses focus, and I have no way to bring it to the forground (this is especially true if I have a keyboard plugged into the J-PAC when windows XP boots).

The only fix is to restart mamewah, exit it.. the 1st MAMEWAH suddently has focus again, but running at 640x480 rather than 368x240, I select exit, and restart MAMEWAH again..

BANG: MAMEWAH.CFG is corrupt.  Only a few of the top lines are there.

POSSIBLE FIX: let MAMEWAH parse a command line parameter where it does not touch any config files (useful if running for CD or DVD?)

I never seem to have this problem.  Is it set as your shell?

No its not.  It's set to autostart in Windows XP star folder.  The administrator ID is set to autologin, and MAMEWAH auto starts.

When the keyboard is not plugged in, all is well, when the keyboard is plugged into port 2 of the J-PAC, the start menu is on the bottom (in really huge size, because the screen is at 368x240) and I have no clue how to switch focus (alt-tab doesn't do it).

The only fix I found was to start a 2nd instance of MAMEWAH, exit, 1st instance regainst focus (but now showing at 640x480 desktop resolution), exit, and restart MAMEWAH..

[JoeB]

MAMEWAH 0.96:

Every time I try to switch emulators in MAMEWAH, it crashes on me with the following error:


Run-time error '384':

A form can't be moved or sized
while minimized or maximized.


I'm using custom layout files with backgrounds set.  If I try to use the layout files that came with MAMEWAH, no problem.

I have just manged to narrow it down to something in the layout file that Mamewah doesn't like.. (even the older version).  The wierd thing though, if I tell MAMEWAH to use a specific default (current) emulator, it loads it fine!

If I use MAMEWAH to switch to another, it crashes.. if I manually switch it in the MAMEWAH.CFG file, it loads it fine.

further more, the layout editor created this file.

Could you email me the layouts you are using?  I just tried a few of Cave's multi emulator layouts and they seemed to work OK for me...

I sure will next time I'm at the machine.  Maybe you can re-create the problem.

- Take your 368x240 layout
- Create a 368x240 JPG background
- Drop it into the same directory as layout.lay
- Select the background to be this file
- Save layout as layout.lay, emu1.lay, emu2.lay, emu3.lay
- Copy your EMU1.CFG to EMU2.CFG and EMU3.CFG
- Start MAMEWAH, and try to switch layouts.

If it doesn't crash, tell the layout editor to only display Artwork image, Game List, and Year + Manufacturer.  (very easy to modify your 368x240 layout to above settings).

[Minwah]

MinWah, I have more details about the "access denied" crash I was getting. It seems that when I crash the first time there is a new file called VERIFY in my mamewah directory, and mamewah won't start again (run time error 70, access denied) until I delete that file.

I emailed you the details.

Does this help?

Great, that helps alot

Does everything work OK if you set the 'Show DOS Box' options to Yes or No?  The 'VERIFY' part should only happen with this set to 'Auto Show' - let me know what happens...

[Minwah]

No its not.  It's set to autostart in Windows XP star folder.  The administrator ID is set to autologin, and MAMEWAH auto starts.

When the keyboard is not plugged in, all is well, when the keyboard is plugged into port 2 of the J-PAC, the start menu is on the bottom (in really huge size, because the screen is at 368x240) and I have no clue how to switch focus (alt-tab doesn't do it).

The only fix I found was to start a 2nd instance of MAMEWAH, exit, 1st instance regainst focus (but now showing at 640x480 desktop resolution), exit, and restart MAMEWAH..

OK, can I ask that you wait until the next release to try this again...I have altered some code which *may* fix/improve this, but since I do not have the problem myself it is difficult to say for sure...

[Minwah]

I sure will next time I'm at the machine.  Maybe you can re-create the problem.

- Take your 368x240 layout
- Create a 368x240 JPG background
- Drop it into the same directory as layout.lay
- Select the background to be this file
- Save layout as layout.lay, emu1.lay, emu2.lay, emu3.lay
- Copy your EMU1.CFG to EMU2.CFG and EMU3.CFG
- Start MAMEWAH, and try to switch layouts.

If it doesn't crash, tell the layout editor to only display Artwork image, Game List, and Year + Manufacturer.  (very easy to modify your 368x240 layout to above settings).

JoeB:  I just gave this a go with my WIP version, and it seemed OK.  This may be due to something I have changed (possibly related to the other problem you are having).

I cannot run at 368x240 since I don't have an arcade monitor setup atm, so hold fire with your layouts.

Again could you wait for the next version to see if it's OK - I have a couple of things to do but it should be ready by the end of the week...

[papaschtroumpf]

I changed the DOS box setting to YES/1 as you suggested and started a game: it caused a run-time error 75 File/Path error.
I rebooted the machine, deleted the VERIFY file, started mameah, attempted to start a game and got the same error.

Both times mamewah did generate a verify file in the FILES folder.

Here's the contents of the verify file. Note that I was able to play the game before, so I'm not sure what the "NOT FOUND" messages are all about:

GetModuleHandleA succeed

LoadLibrary returns baaa0000
viewpoin: sp-s.sp1      131072 bytes NOT FOUND
   CRC(c7f2fa45) SHA1(09576ff20b4d6b365e78e6a5698ea450262697cd)
viewpoin: usa_2slt.bin  131072 bytes NOT FOUND
   CRC(e72943de) SHA1(5c6bba07d2ec8ac95776aa3511109f5e1e2e92eb)
viewpoin: sp-e.sp1      131072 bytes NOT FOUND
   CRC(2723a5b5) SHA1(5dbff7531cf04886cde3ef022fb5ca687573dcb8)
viewpoin: asia-s3.rom   131072 bytes NOT FOUND
   CRC(91b64be3) SHA1(720a3e20d26818632aedf2c2fd16c54f213543e1)
viewpoin: vs-bios.rom   131072 bytes NOT FOUND
   CRC(f0e8f27d) SHA1(ecf01eda815909f1facec62abf3594eaa8d11075)
viewpoin: sp-j2.rom     131072 bytes NOT FOUND
   CRC(acede59c) SHA1(b6f97acd282fd7e94d9426078a90f059b5e9dd91)
romset viewpoin is bad
1 romsets found, 0 were OK.

I haven't tried setting the DOS box to NO yet. I'll try ot tomorrow. I did try settiing it to know without deleting the verify file (since I would have had to reboot) and I got run-time error 70 access denied, so it looks like something is still trying to touch the file.

Hope this helps. let me know what else I can do to help.

[Minwah]

I remember this problem from when I started writing the FE...I can't remember the specifics but it's something like when you output something to a file (eg mame -whatever > filename) for the first time, it adds the 'GetModuleHandleA succeed' etc. stuff to the top of the file.  Also, as you have found, the file seems to remain open, with access denied.

I am not surprised this problem has popped up again, but I have been doing some testing on a '98 machine and I can't get the problem to occurr  

I'll have to do some guess-work in trying to fix it, you'll have to let me know if it doesn't work next release...

Edit: don't bother trying it with Show DOS Box set to No - it will not make any difference.  I have now altered this so next release it should at least work when set to Yes or No, if my 'guess-work' doesn't succeed

[papaschtroumpf]

Great, let me know if there is anything I can do to help.
Any ETA on the next realease?

[Minwah]

Great, let me know if there is anything I can do to help.
Any ETA on the next realease?

I was hoping this week but it's looking like maybe next week atm

[kujina]

Hi Minwah

This is an update concerning that problem I was talking about when running mamewah as a shell.

Hopefully this will clear things up, after some testing it appears that mamewah (0.96) only has a problem running as a shell if you do not disable the welcome screen in xp.

[Minwah]

Hi Minwah

This is an update concerning that problem I was talking about when running mamewah as a shell.

Hopefully this will clear things up, after some testing it appears that mamewah (0.96) only has a problem running as a shell if you do not disable the welcome screen in xp.

Great, thanks for letting me know.  I still don't really understand why it has a problem at all, one of those things I suppose...

So do you have your PC auto-logging in?

[kujina]

Yeah I had it automaticlly logging in. I also manually logged in too after being automaticlly looged out when testing remote desktop.

[Minwah]

Yeah I had it automaticlly logging in. I also manually logged in too after being automaticlly looged out when testing remote desktop.

Well I have now removed the auto-deletion of old .CFG files, in case this is the cause of the problem you are having.  I don't think it should be, but I don't recall changing anything else relating to the .CFG files.

Let me know how it goes, hopefully I may have a new version ready tonight  

[Fuzzguitar]

Has anyone else had this happen in version 0962?

I can't load mame roms from a folder other than the standard directory of C:\mame\roms\. It's like there's something wrong with the path (but there can't be because the rom list generates no worries) and I don't think I'm doing anything different than what worked in the last version.

The only reason I wanted to do this is beacuse I don't yet have a cabinet-only PC and I still use mame32 in the meantime while sitting at my desk, so I'd like to be able to have them both reading roms from the same location.

I just extracted the new version over the previous installtion which was 100% and it's never worked, I've tried deleting cfg's etc but no go.

Maybe I'm just tired and inexperienced but it sure feels like a bug atm.

[JoeB]

One thing I noticed about MAMEWAH (didn't get a chance to try the newest version yet) is that when you install a new version over an older, the first time it runs, it deletes the config files and creates new ones.

MAME does not follow the mame.ini file for ROM locations, MAMEWAH overwrites this with information you give it under the C:\PROGRA~1\MAMEWAH\FILES\EMU1.CFG file.

Read the supplied documentation, or look at the links on MAMEWAH's web site for details on how to configure it.

[Minwah]

Has anyone else had this happen in version 0962?

I can't load mame roms from a folder other than the standard directory of C:\mame\roms\. It's like there's something wrong with the path (but there can't be because the rom list generates no worries) and I don't think I'm doing anything different than what worked in the last version.

The only reason I wanted to do this is beacuse I don't yet have a cabinet-only PC and I still use mame32 in the meantime while sitting at my desk, so I'd like to be able to have them both reading roms from the same location.

I just extracted the new version over the previous installtion which was 100% and it's never worked, I've tried deleting cfg's etc but no go.

Maybe I'm just tired and inexperienced but it sure feels like a bug atm.

MAMEWAH only requires the ROM Location for list generation (unless the emulator requires 'Send ROM Path').  It sounds like your list is generating OK...

I think you need to setup your ROM path within your MAME.INI file, so that MAME itself knows where your roms are.  By default, MAME will only look in \MAME\ROMS, which is why yours works if you use this folder.

JoeB:  Note that I took out the auto-deletion of .CFG files this version, to try and prevent the 'chopped' CFG files that a few people were having.  I can't see why this would be the problem, but I thought I'd try it...

[creatine28]

Minwah,  is there anyway to adjust the delay time for the MP3 background sounds file to start?

My sounds file plays, but for some reason it take a few minutes to start working?

Thanks,

Steve

[Minwah]

Minwah,  is there anyway to adjust the delay time for the MP3 background sounds file to start?

My sounds file plays, but for some reason it take a few minutes to start working?

Um, no.  The MP3 should start as soon as your intro sound has finished (if you have one).  If you do have an intro sound, try disabling it and let me know if the MP3 plays straight away...

[Fuzzguitar]

I should of known - it's a mame issue. I tried launching games from the command line and it's not working. I'm getting a message saying:

 "error:trailing garbage: "Documents\Emulators\Arcade" on line: 7 of file: mame.ini

  ignoring line ....

-Then it has the standard files not found message like if you try to run a rom you don't have.

How should I fix this problem?

[Isometric Bacon]

The screen bug from 96 that I described here http://www.arcadecontrols.org/yabbse/index.php?board=3;action=display;threadid=12313

is still around in 962. Granted it doesn't happen nearly as much as before, but it still seems to happen.

I'm running 640 by 480 in Windows XP with the default layouts if that's any help.

Otherwise, it's been bug free for me Keep up the good work!

[papaschtroumpf]

I remember this problem from when I started writing the FE...I can't remember the specifics but it's something like when you output something to a file (eg mame -whatever > filename) for the first time, it adds the 'GetModuleHandleA succeed' etc. stuff to the top of the file.  Also, as you have found, the file seems to remain open, with access denied.

I am not surprised this problem has popped up again, but I have been doing some testing on a '98 machine and I can't get the problem to occurr  

I'll have to do some guess-work in trying to fix it, you'll have to let me know if it doesn't work next release...

Edit: don't bother trying it with Show DOS Box set to No - it will not make any difference.  I have now altered this so next release it should at least work when set to Yes or No, if my 'guess-work' doesn't succeed

Minwah, I still get this behavior in .962, although I didn't see anything in the changelog that indicated that it was fixed either, so just letting you know.

[Minwah]

I should of known - it's a mame issue. I tried launching games from the command line and it's not working. I'm getting a message saying:

 "error:trailing garbage: "Documents\Emulators\Arcade" on line: 7 of file: mame.ini

  ignoring line ....

-Then it has the standard files not found message like if you try to run a rom you don't have.

How should I fix this problem?

Try putting your path in "quotes".  If that doesn't work, find & use the 'short' path (eg C:\docume~1\emulat~1\arcade).

[Minwah]

The screen bug from 96 that I described here http://www.arcadecontrols.org/yabbse/index.php?board=3;action=display;threadid=12313

is still around in 962. Granted it doesn't happen nearly as much as before, but it still seems to happen.

I'm running 640 by 480 in Windows XP with the default layouts if that's any help.

Otherwise, it's been bug free for me Keep up the good work!

OK, are you just launching MAME?  Is there any pattern to when it happens?  It doesn't seem to do it on my system, tho I have my desktop set to 1024x768...

[Minwah]

Minwah, I still get this behavior in .962, although I didn't see anything in the changelog that indicated that it was fixed either, so just letting you know.

Try setting Show DOS Box to Yes or No.  That should now fix it.  I didn't bother with my 'guess work' yet as I wanted to get the release out to deal with some other problems.  I'll try to sort it for next release...

[JoeB]

I just tried the newest MAMEWAH on my arcade machine (version 0.962) and I'm sorry to say it's the buggiest one yet.

It's actually completly unusable!

Here's the "bad":

- Doesn't want to start. Tells me version mismatch.
- I deleted MAMEWAH.CFG and it started.
- customized MAMEWAH.CFG (told it to use the standard 640x480 layout)
- Every single time I exit the game back to MAMEWAH, MAMEWAH crashes with an error message.

I believe the error message is the same as above.

I restored 0.96 and hope whatever broke can be fixed.

[Minwah]

Sorry to hear about the problems you're having JoeB...

- Doesn't want to start. Tells me version mismatch.

I don't know how this can happen - I never put a version mismatch message in.  Also, I removed the part which deleted the 'old' CFG files which I added for v0.96.  I suspect there was actually a run-time error (type mismatch or similar?)

- I deleted MAMEWAH.CFG and it started.

OK, this makes sense due to the above

- customized MAMEWAH.CFG (told it to use the standard 640x480 layout)

OK

- Every single time I exit the game back to MAMEWAH, MAMEWAH crashes with an error message.

I believe the error message is the same as above.

Could you explain what you mean by 'same as above'?

Edit:  FYI The reason I removed the version check part, was in an effort to stop the CFG 'corruption' that some people were suffering in 0.96.  I'm not sure if it worked yet...

[kujina]

Edit:  FYI The reason I removed the version check part, was in an effort to stop the CFG 'corruption' that some people were suffering in 0.96.  I'm not sure if it worked yet...

Hi Minwah

FWIW I cant comment on corruption other people were experiencing. Its still possible for the .cfg to get corrupted, by running mamewah as a shell while using the welcome screen. But like I said before, its not an issue if you simply disable the welcome screen (you wouldnt want it on a cab anyway).

 

[JoeB]

I get the following error message after MAMEWAH returns from any game:

Run-time error '384':

A form can't be moved or sized
while minimized or maximized.

And it crashes.. (I'm 99.99% sure it's the error message.. can try again later a confirm)

[JoeB]

I was wondering,

could it be that I'm having all these errors because I'm running with the ArcadeVGA and some commands are being issued that don't like it??

Better yet, have you changed anything in the way MAMEWAH runs after it returns from a game?? because what ever you did, makes it crash now.

I also have a suggestion for you..

You can assign an "exit" button in MAMEWAH.. which is great! I installed a special button in my arcade machine that I use to EXIT games, and now exit MAMEWAH.  The problem is now the "exit to windows" is missing, and the machine automatically shuts down when I either press this button, or select exit via the menus.

Is it possible to have the button shutdown (or what ever the default exit option is the user selects via mamewah.cfg) while at the same time still maintain "Exit to windows" via menus?  Or at least have "default menu exit" and "defualt button exit" ??

[vitaflo]

Hey Minwah, just took a bit of time to play w/ the new release.  Very solid.  Fixes all the bugs I told you about from .96.  There is one new(?) bug though.

I recently set up MameWah as my shell in Win2k.  That all works fine, and it starts up, however, when it does the sound in the frontend does not play.  I know its not bad audio on my part since MAME pays game sounds just fine.  This also is not due to the issue I had w/ those big MP3s from 0.96 since I'm using the smaller version.

I did make another user that just has MameWah in the startup folder instead of the shell, and this works as expected, the sound plays in the frontend fine.  So it seems to be some sorta issue w/ setting the frontend to be the Shell.  I can live w/ it the other way, but just wondering if you had any insight?

Thanks for all the hard work!

[Minwah]

I get the following error message after MAMEWAH returns from any game:

Run-time error '384':

A form can't be moved or sized
while minimized or maximized.

And it crashes.. (I'm 99.99% sure it's the error message.. can try again later a confirm)

Better yet, have you changed anything in the way MAMEWAH runs after it returns from a game?? because what ever you did, makes it crash now.

This thing is odd.  In v0.96, the problem appeared whereby MAMEWAH would not fill the screen when returning from a game - strangley, I did not alter any code that should affect that part in this version.

Anyway, I added some code back in to remedy the problem (incidentally I removed this code back in v0.953b).  This code resizes the form after playing a game to make sure it fills the screen.  So this kindof explains the error message you are now getting, although the form is (in theory at least) never minimized or maximized (I checked).  Maybe for some reason it is getting minimized on your system - I will try to remedy this somehow for next time...

[Minwah]

I was wondering,

could it be that I'm having all these errors because I'm running with the ArcadeVGA and some commands are being issued that don't like it??

I also have a suggestion for you..

You can assign an "exit" button in MAMEWAH.. which is great! I installed a special button in my arcade machine that I use to EXIT games, and now exit MAMEWAH.  The problem is now the "exit to windows" is missing, and the machine automatically shuts down when I either press this button, or select exit via the menus.

Is it possible to have the button shutdown (or what ever the default exit option is the user selects via mamewah.cfg) while at the same time still maintain "Exit to windows" via menus?  Or at least have "default menu exit" and "defualt button exit" ??

The ArcadeVGA shouldn't cause any problems, I use one myself.

So when you go into the Exit MAMEWAH menu, 'Exit to Windows' is missing?  I'll check that, it should appear there as normal...

Edit: I re-read what you said and I see what you mean now...most people didn't want to see the choice after picking 'Exit MAMEWAH', which is why it just does the default.  I may do as you suggest and have a 'Default Exit Menu Action' and 'Default Exit Button Action'

[Minwah]

Hey Minwah, just took a bit of time to play w/ the new release.  Very solid.  Fixes all the bugs I told you about from .96.  There is one new(?) bug though.

I recently set up MameWah as my shell in Win2k.  That all works fine, and it starts up, however, when it does the sound in the frontend does not play.  I know its not bad audio on my part since MAME pays game sounds just fine.  This also is not due to the issue I had w/ those big MP3s from 0.96 since I'm using the smaller version.

I did make another user that just has MameWah in the startup folder instead of the shell, and this works as expected, the sound plays in the frontend fine.  So it seems to be some sorta issue w/ setting the frontend to be the Shell.  I can live w/ it the other way, but just wondering if you had any insight?

Thanks for all the hard work!

I really don't know why it has a problem being the shell, I don't believe it used to have this problem.  I don't know what to do to alter this, if the program works at all then it should work as shell...but it doesn't seem to any more.

You will have to just have it in startup for now, and maybe when I've built my cabinet I will be more keen to find out what the problem is.

To everyone:  I apologise for all the problems that seem to have cropped up lately.  The big problem I have is that none of these problems/bugs happen on my system, which makes it very difficult/impossible for me to fix them.  It's also pretty frustrating for me since I would like to have it working perfectly for everyone.  Oh well hopefully one day it will be ok...

[Isometric Bacon]

The screen bug from 96 that I described here http://www.arcadecontrols.org/yabbse/index.php?board=3;action=display;threadid=12313

is still around in 962. Granted it doesn't happen nearly as much as before, but it still seems to happen.

I'm running 640 by 480 in Windows XP with the default layouts if that's any help.

Otherwise, it's been bug free for me Keep up the good work!

OK, are you just launching MAME?  Is there any pattern to when it happens?  It doesn't seem to do it on my system, tho I have my desktop set to 1024x768...

It doesn't seem soley related to MAME. It happens in other emulators too, (project 64 is the one i've noticed the most apart from mame, but then again those two are the ones I have played the most.)

I don't think it is a resolution problem, as I had the same problem with 800 by 600 previously.

To upgrade Mamewah from 9.6 (which originally had the problem as well) I simply overwrote the existing files and deleted the "Mamewah.cfg" Could this have anything to do with it perhaps?

[Minwah]

JoeB & Isometric Bacon: check your PM's...

[Rocky]

For those getting "Input past end of file" errors after playing a game, I found what fixed it for me.

I had to delete all the files in the "Files" folder.  I started by just deleting mamewah.cfg, but still got errors everytime I exited from my first game.

Now that I deleted all the files, it works great.

Running smooth now!

Thanks Minwah! Your frontend keeps getting better,

Rocky

[JoeB]

Hey Minwah..

don't dispair.. your frontend is top notch when it comes to customizability and playability on real arcade hardware in Windows!

We'll get all the bugs out, make it better, etc.. etc...

[Minwah]

For those getting "Input past end of file" errors after playing a game, I found what fixed it for me.

I had to delete all the files in the "Files" folder.  I started by just deleting mamewah.cfg, but still got errors everytime I exited from my first game.

Now that I deleted all the files, it works great.

Running smooth now!

Thanks Minwah! Your frontend keeps getting better,

Great, thanks for letting me know Rocky!

You have given me some insight should this ever be a problem again - I think it could be related to the automatic list creation stuff.  MAMEWAH records the no. of times and length of time each game is played after playing each game (in EMU?.FAV) - it must be related to that...

Incidentally, has anyone tried the new 'Custom List Type's for automatic list creation??

[vitaflo]

I really don't know why it has a problem being the shell, I don't believe it used to have this problem.  I don't know what to do to alter this, if the program works at all then it should work as shell...but it doesn't seem to any more.

You will have to just have it in startup for now, and maybe when I've built my cabinet I will be more keen to find out what the problem is.

To everyone:  I apologise for all the problems that seem to have cropped up lately.  The big problem I have is that none of these problems/bugs happen on my system, which makes it very difficult/impossible for me to fix them.  It's also pretty frustrating for me since I would like to have it working perfectly for everyone.  Oh well hopefully one day it will be ok...

Yeah, the shell runs fine actually, it just doesn't play any music.  That seems to be the only real bug with setting it up as a shell.  I certainly don't mind doing it the other way for now, since I have experience setting up kiosks w/ Win2k and can lock down the OS pretty tight w/out having to resort to using the shell method.

As for the bugs and whatnot, I have seen nothing but improvement since I've started using mamewah.  I honestly don't know what I'd do w/out it.  The fruits of your labor are definitely not being ignored.  I'm just grateful you're sticking with it and making it better.

[vitaflo]

Incidentally, has anyone tried the new 'Custom List Type's for automatic list creation??

I have, and it's AWESOME!  I  have a default Mame list that has every game, and then a filtered list that takes out various games (mahjong games, prelim drivers, etc).  What a godsend.  I thought I'd be spending days filtering out my roms.  This only took me a couple minutes.

[Minwah]

I have, and it's AWESOME!  I  have a default Mame list that has every game, and then a filtered list that takes out various games (mahjong games, prelim drivers, etc).  What a godsend.  I thought I'd be spending days filtering out my roms.  This only took me a couple minutes.

Sounds like you have filtered the list...

What about the 'Most Frequently Played' or 'Longest Played' Custom List Type auto-generated 'favorites' lists?

[vitaflo]

Sounds like you have filtered the list...

What about the 'Most Frequently Played' or 'Longest Played' Custom List Type auto-generated 'favorites' lists?

Wow, I didn't even realize I could do that.  I'll try that out tonight, sounds really cool.

EDIT:  Just tried it.  It's sweet!  Is there any way to have it show how many times, or how long I played each game in these lists?

[Fuzzguitar]

Thanks Minwah, as soon as I put my rom path in "quotes" it all worked fine. I really dig your front end and might post my bubble bobble themed layout somewhere soon. It is really for other Aussies because it has a 20c piece scanned in for the credit instructions - just like the old days!

[Minwah]

Wow, I didn't even realize I could do that.  I'll try that out tonight, sounds really cool.

EDIT:  Just tried it.  It's sweet!  Is there any way to have it show how many times, or how long I played each game in these lists?

Sorry, no .

In an ideal world I would change the LST format to include this info, and add the option to display the times played, and duration played for the current game - similar to the romname/input type etc.  I do not want to change the LST format atm however, so this info is not held in memory for each game (only read when the list is displayed).

[Minwah]

Thanks Minwah, as soon as I put my rom path in "quotes" it all worked fine. I really dig your front end and might post my bubble bobble themed layout somewhere soon. It is really for other Aussies because it has a 20c piece scanned in for the credit instructions - just like the old days!

Cool, I expect Stuzza (http://members.lycos.co.uk/stuzza12/skin.htm) would host your layout if he has any room left...I'd like to see it

[JackTucky]

Sounds like you have filtered the list...
What about the 'Most Frequently Played' or 'Longest Played' Custom List Type auto-generated 'favorites' lists?

I used the Most Frequently played as soon as I installed your latest update.  Went into my full list, started up about 10 games, and now my kids can find what they want.  Awesome.

I got bit by the Xp Welcome screen and running Mamewah as a shell corrupted CFG file.  Turning off the welcome screen worked for me too.

I even got the Daphne.NMS file working!

Thanks for the work, Minwah.

Art

[Minwah]

Sounds like you have filtered the list...
What about the 'Most Frequently Played' or 'Longest Played' Custom List Type auto-generated 'favorites' lists?

I used the Most Frequently played as soon as I installed your latest update.  Went into my full list, started up about 10 games, and now my kids can find what they want.  Awesome.

I got bit by the Xp Welcome screen and running Mamewah as a shell corrupted CFG file.  Turning off the welcome screen worked for me too.

I even got the Daphne.NMS file working!

Thanks for the work, Minwah.

Great, I'll have to note in the Readme to turn off the welcome screen when 'shelling' MAMEWAH.  How did you turn it off?

[kujina]

You must have an account that is part of the administrators group to turn on or turn off  the Welcome screen feature.

Do the following:

Open User Accounts in Control Panel.

Click - Change the way users log on or off.

To specify that users log on to the computer without using the Welcome screen, clear the Use the Welcome screen check box.  The Welcome screen will no longer appear when you start the computer.

(note: you can not use fast user switching when you turn off the welcom screen)

[papaschtroumpf]

Minwah, I think I found another bug:
I was experimenting on my main machine to see how much better things run with a"modern" computer, so I installed MAME in a directory called "My downloads\mame", and the roms in "My dowloads\mame\roms".

Because of the space in the filename, mame can't properly parse its command line. MameWah needs to add quotes (") around the argument list to mame, to generate something like:

My downloads\mame\mamepp.exe "My dowloads\mame\roms\1941".

Not a big deal, I just moved mame to the root folder, but I figured you'd like to know.

[Minwah]

Minwah, I think I found another bug:
I was experimenting on my main machine to see how much better things run with a"modern" computer, so I installed MAME in a directory called "My downloads\mame", and the roms in "My dowloads\mame\roms".

Because of the space in the filename, mame can't properly parse its command line. MameWah needs to add quotes (") around the argument list to mame, to generate something like:

My downloads\mame\mamepp.exe "My dowloads\mame\roms\1941".

Not a big deal, I just moved mame to the root folder, but I figured you'd like to know.

I don't think this is a MW bug.  MAMEWAH doesn't sent the rompath for MAME (unless you configured it to).  Perhaps you need to check your rom path in MAMEPP.INI?

Check \mamewah\debug.log to see exactly what is being sent to the commandline.  It should be something like 'Mydownl~1\mame\mamepp.exe 1941'.

[Minwah]

You must have an account that is part of the administrators group to turn on or turn off  the Welcome screen feature.

Do the following:

Open User Accounts in Control Panel.

Click - Change the way users log on or off.

To specify that users log on to the computer without using the Welcome screen, clear the Use the Welcome screen check box.  The Welcome screen will no longer appear when you start the computer.

(note: you can not use fast user switching when you turn off the welcom screen)

Thanks Kujina

[papaschtroumpf]

I don't think this is a MW bug.  MAMEWAH doesn't sent the rompath for MAME (unless you configured it to).  Perhaps you need to check your rom path in MAMEPP.INI?

Actually in my case it does, that's how I figured out the problem in the first place, by looking at the debug.log
I followed Stuzza's instructions from the link posted on the mamewah news page, and it says to set Send Rom Path to True, so I did.

I'll try it tonight with "Send Rom Path" to false.
By the way, I don't have a mamepp.ini either, I never bothered to run "mamepp -cc" since everything appeared to work fine without it.

Also while we're on the subject, what does "Use Long Filenames" do? Is it ignored for MAME? it doesn't seem to make a difference either way, and Stuzza's page says to set it to True in one place, and flase in another.

Stuzza, if you're monitoring this thread, maybe you can change your page to reflect this situation.

Cheers!

[Minwah]

Actually in my case it does, that's how I figured out the problem in the first place, by looking at the debug.log
I followed Stuzza's instructions from the link posted on the mamewah news page, and it says to set Send Rom Path to True, so I did.

I'll try it tonight with "Send Rom Path" to false.
By the way, I don't have a mamepp.ini either, I never bothered to run "mamepp -cc" since everything appeared to work fine without it.

Also while we're on the subject, what does "Use Long Filenames" do? Is it ignored for MAME? it doesn't seem to make a difference either way, and Stuzza's page says to set it to True in one place, and flase in another.

OK...

You can leave those settings as MAMEWAH's defaults for MAME.  This means Send ROM Path = False, Send ROM Extension = False (can't remember about long filenames, but it doesn't really matter since MAME uses short filenames anyway).

If you set Use Long Filenames to False (with Send ROM Path=True), then you should see your 'long' rom path be converted to something like 'Mydowlo~1\mame\roms\1941'.

Let me know if you still have problems...

[vitaflo]

Hmm..seems I'm having sound issues again.  The music will play in the FE when MameWah starts, but after 5mins (the legth of a song) it stops playing, and doesn't return.  Seems to only play one song and then not any others.  This is only if I leave the FE on and idle.  If I play a game and come back to the FE it seems to work fine (I think).

So there's still sound issues it seems.

[Minwah]

Hmm..seems I'm having sound issues again.  The music will play in the FE when MameWah starts, but after 5mins (the legth of a song) it stops playing, and doesn't return.  Seems to only play one song and then not any others.  This is only if I leave the FE on and idle.  If I play a game and come back to the FE it seems to work fine (I think).

So there's still sound issues it seems.

OK.

I might do a total re-write for the sound stuff at some point - it seems to be a total headache-causer the way it is  

[BlackThorne]

I have a strange problem with the screen saver. The pictures in slide-show mode are way too big. I don't know if this is a bug but it really starts bugging me.

[Minwah]

I have a strange problem with the screen saver. The pictures in slide-show mode are way too big. I don't know if this is a bug but it really starts bugging me.

Which layout are you using?  Whatever, open it in the Layout Designer and check the size of the artwork image object on the screensaver form...

[BlackThorne]

Thanks! Everything's fine now .

[Fuzzguitar]

Minwah, just wondering how does Mamewah handle the event sounds? I'm using my own custom sounds, correctly re-named and I've noticed some are louder/softer than others on average. I'm referring mainly to the Game Launch sound. We used Cool Edit Pro to even up the volume of each file but this one is still very loud - does Mamewah boost the volume for effect?
 

[Minwah]

Minwah, just wondering how does Mamewah handle the event sounds? I'm using my own custom sounds, correctly re-named and I've noticed some are louder/softer than others on average. I'm referring mainly to the Game Launch sound. We used Cool Edit Pro to even up the volume of each file but this one is still very loud - does Mamewah boost the volume for effect?

MAMEWAH reduces the overall sound ouput of your PC based on the 'Sound / Music Volume (%)' setting.  Before launching a game (or quitting MW) it restores the original level (ie 100%).  After exiting the game it should reduce the level again.

I haven't noticed anything working incorrectly on my system, but I will check that I didn't accidentally restore the sound level before playing the Game Launch sound (rather than just afterwards)...

Edit:  I just checked, and you're right - it does get louder.  I think the problem is that it restores the volume after the sound is set to play, but before the sound has finished.  It's on my bug-list...

[vitaflo]

Just curious, can I set my controls in MW to recognize a character that uses a modifier key to display?

What I mean is, I want to have exit MW to be the underscore character.  Thus the person has to use "shift-minus" (two buttons) on the control panel to get and underscore and trigger the exit MW key.  But when I go to set up MW to use underscore, pressing the shift key first of course makes exit MW the shift key.

I notice you're using numbers in the config to store the values for the keys.  Are these just ASCII values?  If I use the ASCII value for underscore and hand type into into my cfg file would that work?

[Pungo76]

I'm currently having two issues when running Mamewah.  First off are all the details:

Mamewah .962 (the latest I believe)
Arcade Monitor with ArcadeVGA
Keywiz
Windows XP Pro
AMD 1300 PC

I currently have the keywiz uploader in my startup, so that upon booting the pc the software uploads to the keywiz then it runs Mamewah.  Everything seems fine, but after selecting and exiting the first game I get the following error:

Runtime Error '384'
A form can't be moved or sized while minimized or maximized.

I then can hit OK and then open back up Mamewah and everything works fine.  However, when I exit Mamewah and go back to windows, then return to Mamewah again I can no longer see my artwork (snaps and marquees).

Have any thoughts?

Thanks,

[Minwah]

Just curious, can I set my controls in MW to recognize a character that uses a modifier key to display?

What I mean is, I want to have exit MW to be the underscore character.  Thus the person has to use "shift-minus" (two buttons) on the control panel to get and underscore and trigger the exit MW key.  But when I go to set up MW to use underscore, pressing the shift key first of course makes exit MW the shift key.

I notice you're using numbers in the config to store the values for the keys.  Are these just ASCII values?  If I use the ASCII value for underscore and hand type into into my cfg file would that work?

You can't really do what you want using the current system  The numbers stored are keycodes; some of which (a-z, 0-9 etc.) happen to be the same as ASCII codes, but they are keycodes nevertheless.

It will always just recognise the first key pressed.  Some MW users may recall before v0.95 I used shifted keys by default a lot, but due to this limitation this is no longer the case.  FWIW multiple keys are on my v2.0 things-to-add list...

[Minwah]

I'm currently having two issues when running Mamewah.  First off are all the details:

Mamewah .962 (the latest I believe)
Arcade Monitor with ArcadeVGA
Keywiz
Windows XP Pro
AMD 1300 PC

I currently have the keywiz uploader in my startup, so that upon booting the pc the software uploads to the keywiz then it runs Mamewah.  Everything seems fine, but after selecting and exiting the first game I get the following error:

Runtime Error '384'
A form can't be moved or sized while minimized or maximized.

I then can hit OK and then open back up Mamewah and everything works fine.  However, when I exit Mamewah and go back to windows, then return to Mamewah again I can no longer see my artwork (snaps and marquees).

Have any thoughts?

Thanks,

This is a bug which I think I've now fixed.  If you (or anyone else) would like a modifed version which fixes just this bug, then let me know you email address

[Isometric Bacon]

Minwah... the problems I mentioned before (screen size bug) still exist, but that is the least of my problems atm.

I'm running your modified version of 962 you sent me via PM.

I noticed that when selecting "Shutdown computer" My PC for some reason simply resets, and doesn't go to the "It is now safe to turn off your computer". screen as it should.

Last time it did this, I impatiently turned the computer whilst it was resetting. Now, turning on the PC again, Windows XP came up with the screen "your disk has not been shutdown, checking drive for integrity" I let it run through it's course, (I usually just skip it) but it suddenly said there was a problem with "Mamewah.cfg" and it would have to be truncated. Upon loading XP, and Mamewah in the startup folder, all the previous config data was lost leaving Mamewah with just the generic "Emulator 1, Emulator 2" information with no actual data in it.

[Minwah]

Minwah... the problems I mentioned before (screen size bug) still exist, but that is the least of my problems atm.

I'm running your modified version of 962 you sent me via PM.

I noticed that when selecting "Shutdown computer" My PC for some reason simply resets, and doesn't go to the "It is now safe to turn off your computer". screen as it should.

Last time it did this, I impatiently turned the computer whilst it was resetting. Now, turning on the PC again, Windows XP came up with the screen "your disk has not been shutdown, checking drive for integrity" I let it run through it's course, (I usually just skip it) but it suddenly said there was a problem with "Mamewah.cfg" and it would have to be truncated. Upon loading XP, and Mamewah in the startup folder, all the previous config data was lost leaving Mamewah with just the generic "Emulator 1, Emulator 2" information with no actual data in it.

Sorry to hear about your probs  

Does is matter how you shut down (menu or default exit action)?  Also, are you running as a shell?  Does this affect it?

It seems to work OK on my system (not running as shell)...

[Syxx]

i get an error when i refresh the game list i get multiple error types, one said something about argument or something, another was a invalid proceedure, and now last few times it has said nothing and just crashed...

any idea whats up?

[Minwah]

i get an error when i refresh the game list i get multiple error types, one said something about argument or something, another was a invalid proceedure, and now last few times it has said nothing and just crashed...

any idea whats up?

Maybe some of your CFG got messed up somehow...try deleting all stuff in your \FILES folder and try again.

Failing that, let me know exactly what errors you get and when and I'll try and see whats wrong...

[Buddabing]

Unfortunately, I can't get MAMEWAH to work, I hear it's a great front end.

I installed the .954 full version into \program files\mamewah, then downloaded the .962 patch on top of it. MAME v0.74 is installed in \mame.

I created a shortcut to \program files\mamewah\mamewah.exe. When the program is launched, it comes back with a Run-Time Error 13 dialog box, and a red "No Games Available" at the bottom. Then my screen is resized to 640x480 and the program aborts.

My system is pretty normal. Windows XP Professional, Geforce 2 Ultra video card, Athlon 1700XP, Asus Nforce2 based motherboard. I normally run my monitor (Samsung SyncMaster 750s 17") at 1024x768.

I expect MAMEWAH to run out of the box if all the settings were set at default.

TIA,
Buddabing

[Minwah]

Unfortunately, I can't get MAMEWAH to work, I hear it's a great front end.

I installed the .954 full version into \program files\mamewah, then downloaded the .962 patch on top of it. MAME v0.74 is installed in \mame.

I created a shortcut to \program files\mamewah\mamewah.exe. When the program is launched, it comes back with a Run-Time Error 13 dialog box, and a red "No Games Available" at the bottom. Then my screen is resized to 640x480 and the program aborts.

My system is pretty normal. Windows XP Professional, Geforce 2 Ultra video card, Athlon 1700XP, Asus Nforce2 based motherboard. I normally run my monitor (Samsung SyncMaster 750s 17") at 1024x768.

I expect MAMEWAH to run out of the box if all the settings were set at default.

Couple of things:

Did you run v0.954 before overwriting?  It sounds like you didn't, but if you did, you'll need to delete everything from the \MAMEWAH\FILES folder.

What regional settings do you use?  In particular, if you have your Decimal Separator set to ',' (as opposed to '.'), then MW will not like it.  Try changing it from Control Panel.

Let me know how you get on...

[jkam]

New Bug? Alright I setup Mamewah and I love it...it is a great front end. The ability for different layouts is awesome. Anyway I am having a problem....when I run a mame rom file through mamewah...it changes the colors of my mame rom. They are wrong. When I run them directly through mame they work like a charm. I heard a few people say they run batch files instead of the actual roms...is this what I should do to fix the problem? Any help would be appreciated.

[Minwah]

New Bug? Alright I setup Mamewah and I love it...it is a great front end. The ability for different layouts is awesome. Anyway I am having a problem....when I run a mame rom file through mamewah...it changes the colors of my mame rom. They are wrong. When I run them directly through mame they work like a charm. I heard a few people say they run batch files instead of the actual roms...is this what I should do to fix the problem? Any help would be appreciated.

You don't need to run a batch file, it should just work OK.

MAMEWAH will not change colors (all it does is launch MAME as normal).  All I can think of is that MW will quite possibly be running in 16bit color, and when you run MAME if it does not switch color depth the games may be displayed not in all their glory.

Make sure you have this in your MAME INI:

switchres               1
switchbpp               1

This will allow MAME to switch resolutions and color depth.

Alternatively, use the layout designer to make a layout which uses 32bit color.

Let me know if that doesnt work...

[jkam]

I am not home right now to try this out but looking at my mamewah and mame directory at work...I don't have a mame.ini file. Also it works ok here and everything is setup the same. Could it be machine specific? Can I create the mame.ini file manually?

[Minwah]

I am not home right now to try this out but looking at my mamewah and mame directory at work...I don't have a mame.ini file. Also it works ok here and everything is setup the same. Could it be machine specific? Can I create the mame.ini file manually?

It could work differently on each machine if you are using a (slightly) different layout - are you using exactly the same one?

Try making a mame ini (this assumes your mame is called mame.exe):

Goto a command prompt (Start > Accessories > MS-DOS Prompt/Command Prompt),
Navigate to your mame folder (eg 'C:', 'CD\MAME'),
Type 'mame -cc',
(You should now have mame.ini within your mame folder)
Edit mame.ini and adjust accordlingly, saving changes.

[Murph]

Woo Hoo!  My Mame Cab is almost done!! (Ok, you guys realize a cab is NEVER done!  There's always something more to be done-- I'm onto console emus next!  Hehe)  I got my setup going as a P4-2ghz, ECS MB, 60 gig HD, XP Pro 512 meg of ram, ArcadeVGA.  

MameWah is running with a kickin' custom layout, no probs using the designer.  Also, the Daphne stuff started working just fine upon upgrade to XP from 98SE.  98 SE didn't like the %1 variables in my setup-- someone suggested using "%1%" as opposed to just "%1" in 98SE, but I was already in mid upgrade, so never got to test it.  Features seem to be working well too, with 2 exceptions I've noted--- both VERY minor.

1.  Exiting the screensaver/slideshow with the "next song/spacebar" button seems to freeze everything.

2.  Letting the screensaver go any length of time (20 min or so it seems), it crashes everything with a Runtime error 6 overflow.

Other than that, everything seems to be working fine.  I did notice one other thing, once I upgraded, I was getting errors on certain functions in mamewah under XP-- I just had to run the MWInstall prg from a seperate folder-- appears some of the runtimes or DLL's or whatever may not have installed or transfered from 98SE.  Keep in mind, I had everything running under 98SE, but some functionality wasn't working as expected so I upgraded... not a full clean install.  Example-- the jerky/slow-refresh scrolling issue on an arcade monitor with the arcadeVGA was resolved before upgrade by changing some mame.ini settings from another post on byoac forums, and it still works fine after upgrade. But LIFE IS GOOD!

Thanks for the best front end I've seen yet, Min!!!  Hope this post helps a couple others out!

Murph

[Minwah]

1.  Exiting the screensaver/slideshow with the "next song/spacebar" button seems to freeze everything.

2.  Letting the screensaver go any length of time (20 min or so it seems), it crashes everything with a Runtime error 6 overflow.

I'll check these out...

Glad you've got your setup going ok

[SirPoonga]

Note sure if this was posted already but I just installed mamewah.  Here's a screenshot.

[papaschtroumpf]

you probably forgot to unzip layout.zip. Do you have a layout directory in mamewah?

[SirPoonga]

Ahh, yes.

Ok, con number 1.  I'm going through the FEs listing what I do and don't like.

Does mamewah support multiple rom paths?

[Minwah]

Ahh, yes.

Ok, con number 1.  I'm going through the FEs listing what I do and don't like.

Does mamewah support multiple rom paths?

(Answered in other thread)

SirP: You may want to overwrite your MAMEWAH exe with the v0.962 update - that version does not require layouts.zip (until you want to try a different res/layout of course).  If you do, be warned that you will probably have to remove + recreate your \MAMEWAH\FILES\*.CFG files tho (try just MAMEWAH.CFG first).

[papaschtroumpf]

I've got a layout problem:
My "emulator 2" is  a jukebox, and I set up the CFG file where the name of the emulator is the name of the jukebox, the ROM extension is TXT and there is a single "ROM"/text file called "start the jukebox".
I then created a custom layout where the only objects are the game list (single entry) and the background picture.
Unfortunately, Mamewah seems to insist on putting the up default mamewah logo thay it uses when it can't find the artwork for that game even though none of the artworks are seected on the form.
Any ideas? (running 0.962)

[Minwah]

I've got a layout problem:
My "emulator 2" is  a jukebox, and I set up the CFG file where the name of the emulator is the name of the jukebox, the ROM extension is TXT and there is a single "ROM"/text file called "start the jukebox".
I then created a custom layout where the only objects are the game list (single entry) and the background picture.
Unfortunately, Mamewah seems to insist on putting the up default mamewah logo thay it uses when it can't find the artwork for that game even though none of the artworks are seected on the form.
Any ideas? (running 0.962)

I heard a report that hiding the games list does not work (it insists on showing the games list always).  It could be that a similar thing happens with the artwork boxes - I haven't tried showing no artwork - I will check it out...

[JoeB]

Is there an ETA for the next release of MAMEWAH?

I think the 2 bugs we got out together should go out to others.. you never know how many others run into that problem (many use the ArcadeVGA card here!)

[Minwah]

Is there an ETA for the next release of MAMEWAH?

I think the 2 bugs we got out together should go out to others.. you never know how many others run into that problem (many use the ArcadeVGA card here!)

I wasn't planning a release for a while - aside from the bug(s) we sorted I haven't done ANY coding since v0.962.  I've been building my cab at weekends/some nights, playing guitar and generally giving my brain a rest lately   ...

That said I agree the things we fixed are pretty important, but I'd like to make some more fixes too.  Maybe next week I'll try and get some more done

[papaschtroumpf]

I heard a report that hiding the games list does not work (it insists on showing the games list always).  It could be that a similar thing happens with the artwork boxes - I haven't tried showing no artwork - I will check it out...

Now that's really weird: I changed the layout to display artwork #1 and redid my artwork so that it would be a background without a title and a big "Jukebox" title that I then saved as "fake" artwork. (I posted pics of my skin in the Jukebox forum if it helps).
When I tried this new layout, the artwork didn't show! (neither my "Jukebox" title nor the default mamewah missing artwork window). Maybe it's because I just dragged an "artwork #1" box in the layout editor without worrying if it was big enough for the art to be displayed in it? (although I think it is) What happen if the art is bigger than the box, does it not display or does it shrink? (PNG file in this case)

This basically solved my problem, I just re-added the title to the background image (JPG) and it now looks the way I want it to, even though I don't understand why.

[papaschtroumpf]

Minwah, I have the following questions about layouts:

will the art get sized down/up if the element on the form are smaller/bigger than the actual art? (I believe the answer is yes, at least for PNG)

In the screen saver, can I pu multiple art elements such as snap, cabinet,marquee and flyer?

It appears that the screen saver shows an erro if it can't fin d somw of the art rather (fro example if I want to display both cab and flyer but the cab is missing)

Do you have a description of how this all works?

Thanks

[papaschtroumpf]

I tried using a gif with a transparent color for the emu?-message.gif and the transparent color doesn't appear to work. What's interesting is that I forced the transparent color to be yellow as an experiment but it still shows as black in mamewah so it does appear to be treated differently.
I have attached the GIF (message for my jukebox skin) so that you can see it really is transparent in the lower right corner. I guess I should mention that since I have only one "ROM" for my jukebox "emulator", I disabled all elements on the form except for the background. I don't know if it makes any difference.

[snowdogg187]

Searched more and found how to fix it, I just needed to redo the config files.
Minwah, this fe rules, thanks again!!

I haven't been able to update to .962. 954 works fine with my mame config setup but when I extract the 962 to overwrite in the directory mamewah won't start.

I get the error msg

Run-Time error 13
Type Mismatch

[Minwah]

Minwah, I have the following questions about layouts:

1) will the art get sized down/up if the element on the form are smaller/bigger than the actual art? (I believe the answer is yes, at least for PNG)

2) In the screen saver, can I pu multiple art elements such as snap, cabinet,marquee and flyer?

It appears that the screen saver shows an erro if it can't fin d somw of the art rather (fro example if I want to display both cab and flyer but the cab is missing)

Do you have a description of how this all works?

Thanks

1) Yes, the image will always be resized to fit the artwork image box.

2) Yes, you just need to refer the the Artwork #? Paths in MAMEWAH, and alter the layout using the designer.  I'll try and duplicate the problem you're having, it certainly shouldn't cause a problem...

[Minwah]

I tried using a gif with a transparent color for the emu?-message.gif and the transparent color doesn't appear to work. What's interesting is that I forced the transparent color to be yellow as an experiment but it still shows as black in mamewah so it does appear to be treated differently.
I have attached the GIF (message for my jukebox skin) so that you can see it really is transparent in the lower right corner. I guess I should mention that since I have only one "ROM" for my jukebox "emulator", I disabled all elements on the form except for the background. I don't know if it makes any difference.

Hmm, it should work OK - I'll check this one out too...

[Minwah]

Searched more and found how to fix it, I just needed to redo the config files.
Minwah, this fe rules, thanks again!!

I haven't been able to update to .962. 954 works fine with my mame config setup but when I extract the 962 to overwrite in the directory mamewah won't start.

I get the error msg

Run-Time error 13
Type Mismatch

The v0.954 CFG files aren't compatible with v0.962.  Either delete the contents of your \MAMEWAH\FILES folder (& re-configure), or give DBut's 'MAMEWAH Setup' program a go - it can work with CFG files of varying versions

[papaschtroumpf]

OK Minwah, I've got another one for you:

When mamewah is launched from the keywiz upload application it allows me to play one game, but when I exit the game I get a run-time 384 error and mamewah crashes.
This only seem to happens when I launch mamewah from the keywiz app (the keywiz reprograms the keyboard then launches mamewah).
Any idea of what might be causing the problem? I've contacted RandyT to let him know about it but you may have ideas of what the keywiz softwareis doing to launch mamewah that is diferrent from from double clicking on it. (I have never programmed in VB and have no idea what this error message might mean). Could this be a focus related issue? or a full screen vs not issue?

Edit: I tried both settings for the "task switching" setting in mamewah and the behavior is the same.

Edit: just to be sure I went back to the "classic 800x600" layout to make surethat the issue was not with my custom skin.

Edit: here's RandyT's response:

      The only thing I can think of is that MAMEWAH siezes control of the system
      in such a way that it doesn't allow the KeyWiz software to exit properly.
      This is just a guess, because I haven't seen the code.
      But I do believe this is a MAMEWAH problem, as I have tested a LOT of
      software without any issues, including a number of other frontends.
      Unfortunately, this one is out of my hands.
      RandyT


Edit (yet again): I guess it looks like Pungo76 has reported this problem in this thread already, I somehow missed it (I hate the search feature on this forum, I can never get it to work for me):

I'm currently having two issues when running Mamewah.  First off are all the details:

Mamewah .962 (the latest I believe)
Arcade Monitor with ArcadeVGA
Keywiz
Windows XP Pro
AMD 1300 PC

I currently have the keywiz uploader in my startup, so that upon booting the pc the software uploads to the keywiz then it runs Mamewah.  Everything seems fine, but after selecting and exiting the first game I get the following error:

Runtime Error '384'
A form can't be moved or sized while minimized or maximized.

I then can hit OK and then open back up Mamewah and everything works fine.  However, when I exit Mamewah and go back to windows, then return to Mamewah again I can no longer see my artwork (snaps and marquees).

Have any thoughts?

Thanks,

This is a bug which I think I've now fixed.  If you (or anyone else) would like a modifed version which fixes just this bug, then let me know you email address

I'll PM you my email address for the update.

[papaschtroumpf]

I tried using a gif with a transparent color for the emu?-message.gif and the transparent color doesn't appear to work. What's interesting is that I forced the transparent color to be yellow as an experiment but it still shows as black in mamewah so it does appear to be treated differently.
I have attached the GIF (message for my jukebox skin) so that you can see it really is transparent in the lower right corner. I guess I should mention that since I have only one "ROM" for my jukebox "emulator", I disabled all elements on the form except for the background. I don't know if it makes any difference.

Hmm, it should work OK - I'll check this one out too...

Does the gif display routine make any assumption of which color is transparent in the palette? A lot of GIFs use the first or last color in the palette but due the to reason I generated mine the transparent color is something like color 87 out of 127. Note that this is perfectly legal per the GIF format (as shown by the fact that the picture attached to my previous post does display as transparent).

[Minwah]

Does the gif display routine make any assumption of which color is transparent in the palette? A lot of GIFs use the first or last color in the palette but due the to reason I generated mine the transparent color is something like color 87 out of 127. Note that this is perfectly legal per the GIF format (as shown by the fact that the picture attached to my previous post does display as transparent).

I don't think it should matter - I use VB's ImageBox's built-in GIF support.  I tried your image (just on a blank VB form), and it worked fine, so I guess something else must be the problem

I'll post when I know more...

[papaschtroumpf]

Try it on top of a background JPG. I can even send the actual JPG and layout file I'm using if you think it might help.

This is what it ends up looking like for me: (this picture is a fake for illustration purpose, it's not an actual screenshot but faithfully represent what I'm seeing). I'd like to see the jukebox under the rolled up edge of the music sheet.

[Minwah]

Try it on top of a background JPG. I can even send the actual JPG and layout file I'm using if you think it might help.

This is what it ends up looking like for me: (this picture is a fake for illustration purpose, it's not an actual screenshot but faithfully represent what I'm seeing). I'd like to see the jukebox under the rolled up edge of the music sheet.

Aahhh, I see  I think it is impossible to do what you want (atm) .  The black you see is the background color of the 'Message' form, so indeed the GIF probably IS being displayed complete with transparency (check the forms background color in the designer - this will confirm).

To achieve what you are trying to do, the (Message) form itself would need to be transparent.  While this is certainly possible to program (using SubClassing IIRC, something I'm not too familiar with), the way it currently is it is not possible for you to do it (using a transparent GIF anyway).

One cheap but do-able way of doing it would be to overlay your 'Loading' image over the suitable section of the main jukebox background image...

[papaschtroumpf]

I guess that's what I'll do!

[Luxury]

I dont know if this has been mentioned before or not (lousy search).  its not really a bug, just something thats a little annoying.  i have set up some custom lists, and got them to how i like them with the latest version of mamewah.  but when i refresh my gamelist, and go back to my custom list, it resets itself and i have to adjust everything again.  does refreshing the list reset the custom lists?  again...its not that big of a deal because it only takes a few minutes to do, but i just wanted to see if this common.  

btw - are there any custom layouts designed for 640x288 out there?  im curious to see how they would look on my monitor.  

[Minwah]

I dont know if this has been mentioned before or not (lousy search).  its not really a bug, just something thats a little annoying.  i have set up some custom lists, and got them to how i like them with the latest version of mamewah.  but when i refresh my gamelist, and go back to my custom list, it resets itself and i have to adjust everything again.  does refreshing the list reset the custom lists?  again...its not that big of a deal because it only takes a few minutes to do, but i just wanted to see if this common.  

btw - are there any custom layouts designed for 640x288 out there?  im curious to see how they would look on my monitor.  

Sorry, this is just the way it works atm (it kindof assumes that the filters will be different every time, so starts afresh).

Haven't seen many 640x288 layouts out there yet.  I started work on a custom 368x240 one a while ago, but probably won't finish it until I've made my cab.  Anyone else?...

[JoeB]

640x288 is not a very MAME friendly resolution...

Let me explain why.

Most games fall into 2 categories:

- less than 240 lines (neo geo and most 80-90's games!)
- more than 240 lines (most are vertical here)

The best way to get both categories to work perfectly on a horizontal monitor is to fix the monitor to 240 lines.  Any thing higher than this, gets HW stretched to 480 lines.

Mind you most monitors can't support 480 lines horizontal.. so video cards (arcadeVGA) actually shows it in interlaced.. or 640x240 twice as fast!

WOW! The same magic 240 lines..  

The biggest problem with running MAMEWAH at 288 lines is that most 240 lines or less games will need to get their vertical hold to be changed every time you start the game and then go back to MAMEWAH..

So my suggestion.. work with the magic 240 line vertical.. it's the most arcade friendly!

[Luxury]

right...but with the arcadevga, the lowest setting it can handle windows is 640x288 - or the highest setting there is for non-interlacing (so i believe).  368x240 would probably look better though because everything in 640x288 seems so stretched out to me.  

[JoeB]

You are correct about the windows resolution,

but MAMEWAH is not windows!  It's an application (just like MAMEWAH) and being an application it can switch to any support resolution on the video card!

So you can run MAMEWAH and 368x240 or any arcadeVGA resolution!!

[rosico]

Hello there,

I recently installed the latest mamewah on my cab (arcade monitor, Win 98 SE, PIII 400, 128 ram) and got a completely white screen as a result.    

Erased everything and did a complete reinstall and still have the same results ... the ghostly white screen ...

I was looking through the pages hoping to see if anyone else has had this to no avail ...

not sure if this is a bug vs. my inability to get mamewah working (more the latter I assume since I had this great FE working before).  

Any advice?  Please?  Thanks for the assistance.

[Minwah]

Hello there,

I recently installed the latest mamewah on my cab (arcade monitor, Win 98 SE, PIII 400, 128 ram) and got a completely white screen as a result.    

Erased everything and did a complete reinstall and still have the same results ... the ghostly white screen ...

I was looking through the pages hoping to see if anyone else has had this to no avail ...

not sure if this is a bug vs. my inability to get mamewah working (more the latter I assume since I had this great FE working before).  

Any advice?  Please?  Thanks for the assistance.

Haven't heard of that problem before...do you use an ArcadeVGA?  If so, try plugging a PC monitor in to see what happens with that...

[meta87]

after i install mamewah and try to open the program it gives me a runtime error and says: path not found.

I've used the older versions with great results but i cant figure out what the error means or how to fix it.

Thanks!

[Minwah]

after i install mamewah and try to open the program it gives me a runtime error and says: path not found.

I've used the older versions with great results but i cant figure out what the error means or how to fix it.

Thanks!

If you installed it to the same folder as a previous version (I expect so), then delete the contents of the \mamewah\files folder - anything previous to v0.962 are not compatible with the latest version  

[meta87]

Thanks for the help

but  it is a completely fresh install. Any other ideas?

Thanks!

[Minwah]

Thanks for the help

but  it is a completely fresh install. Any other ideas?

Thanks!

I've been thinking but I'm not sure what 'path' is giving the problem  

I know you said 'fresh install', but have you ever had MW installed in the folder previously?  What I am getting at is that uninstalling a previous installation will not remove the config files etc...all I can think of atm...

[meta87]

hummm. no it is a completely blank new folder on a computer that hasn't ever had mamewah installed on it. I'll try to do it again on different computer. Thanks for the help.

[Minwah]

hummm. no it is a completely blank new folder on a computer that hasn't ever had mamewah installed on it. I'll try to do it again on different computer. Thanks for the help.

Sorry, I just can't think of what could be wrong  

Perhaps try uninstalling and installing to a different folder - try one with a 'short' name like c:\mamewah.  It shouldn't make any difference but worth a shot

[Nightmare03]

I dunno if someone has already posted this but theres too much to read through.. here it is

I made a new game list, when i go to add a game to it i get subscript error or somethin along them lines and then mamewah closes and leaves my desktop at 640 X 480

Any ideas on how to stop this? Its annoying cuz i want another game list for my favorite games.

-Nightmare

[Minwah]

I dunno if someone has already posted this but theres too much to read through.. here it is

I made a new game list, when i go to add a game to it i get subscript error or somethin along them lines and then mamewah closes and leaves my desktop at 640 X 480

Any ideas on how to stop this? Its annoying cuz i want another game list for my favorite games.

-Nightmare

Haven't had this one reported before...

Could you be quite specific in what you do & what happens because I can't seem to reproduce the error - it seems to work OK for me whether adding to an empty list or a populated one...

[mugwump]

When using the slideshow screensaver option from within MAMEWah all of the MAME snapshot images are about 4 times the size of the screen so only the upper left-hand corner is actually visible on-screen.  The images appear just fine on the main screen using various skins.  Not a big deal but I can't figure out what the problem is.

Also, the exit option "Give Choice" no longer gives a choice but just drops directly to the Windows desktop (Win98).

Thanks.

[Minwah]

When using the slideshow screensaver option from within MAMEWah all of the MAME snapshot images are about 4 times the size of the screen so only the upper left-hand corner is actually visible on-screen.  The images appear just fine on the main screen using various skins.  Not a big deal but I can't figure out what the problem is.

Also, the exit option "Give Choice" no longer gives a choice but just drops directly to the Windows desktop (Win98).

Thanks.

What layout are you using?  Perhaps the creator of the layout did not design the screensaver form properly - open it in the Layout Designer to check.

Not sure about the other one, double check it is set to 'Give Choice' and that you're exiting via the menu (not hitting the quit button).

[mugwump]

Thanks for the quick reply.  For some reason the screensaver form of the 640x480 layout I'm using was at 1024x768.  I couldn't change the size of the screensaver form without it also messing up the main page so I just made a new layout from scratch.

As for the Give Choice upon exit issue, I thought that the choices menu would pop-up when the exit MAMEWah button was pressed but I see now that I have to use the menu to exit this way and not just the one button.

Thanks for the help.

[Minwah]

Thanks for the quick reply.  For some reason the screensaver form of the 640x480 layout I'm using was at 1024x768.  I couldn't change the size of the screensaver form without it also messing up the main page so I just made a new layout from scratch.

As for the Give Choice upon exit issue, I thought that the choices menu would pop-up when the exit MAMEWah button was pressed but I see now that I have to use the menu to exit this way and not just the one button.

Thanks for the help.

Yes I need to add a 'Default Exit Button Action' option or something - some users like to be able to have the escape key do something different to exiting via the menu.

[JackTucky]

Why doesn't Mamewah start?  I installed latest version, it didn't create a files or layout directory.  I don't have a layout.zip.

I used Mamewahsetup to create the files directory.

When I double click mamewah.exe, it doesn't do anything but a quick screen "flash"

Thanks.


Ack.  I reinstalled my video drivers and it's working now.  My fault.

Art

[MadEditor]

Hi,

Just a wierd problem here... Whatever the resolution i choose i get huge text !
The font is so big the list is only 4 or 5 entry long...

I suppose i have a corrupted font file or another problem related to a font but i don't know what.

Could you help ?

Here's a resized screenshot... originally in 1024x768

[MadEditor]

OK got it....

I found out the problems... Seems to be related to the language settings in windows...
The font size is define as 9.75 in most layout file, but in a French windows it should be 9,75 so it assume it a 75 which is pretty big :-)

There's also another problem in the layout designer, again related to the language settings in windows, when the file is saved the labels "True" and "False" are putted in english and in that case apparently the systems want them in FRENCH !!! there's seem to be a little mess in this... but once you find the problem, it's not a problem anymore, right ?

Just wanted to help out a litlle :-)

[Minwah]

OK got it....

I found out the problems... Seems to be related to the language settings in windows...
The font size is define as 9.75 in most layout file, but in a French windows it should be 9,75 so it assume it a 75 which is pretty big :-)

There's also another problem in the layout designer, again related to the language settings in windows, when the file is saved the labels "True" and "False" are putted in english and in that case apparently the systems want them in FRENCH !!! there's seem to be a little mess in this... but once you find the problem, it's not a problem anymore, right ?

Just wanted to help out a litlle :-)

Yes you're right - MAMEWAH likes '.' as a decimal separator and English language settings...it is a know bug that I haven't managed to fix yet...(incidently not entirely really my fault - Windows seems to be inconsistent with how it stores the settings!)

Sorry I didn't reply before, didn't see the post  

[papaschtroumpf]

I set up mamewah to play MP3s while in the screen saver and I eventually get an error along the lines of "end of file while playing" (sorry I don't remember the exact wording). I suspect one of my MP3s might be corrupted?
I have hours worth of arcade "ambience" MP3s it'll take me quite a while to figure it out by trial and error and I can't just sit around waiting for it to crash either.
I assume that mamewah doesn't log the MP3 file it's playing anywhere?
Any idea how I can find out which MP3 is corrupted short of using the trial and error method? I'll post a similar question in the jukebox forum in case someone knows of a utility to detect bad MP3s.

[Harakiri]

Hi!

I'm sorry if this question is dumb or newb but i can't use my sidewinder USB pad with mamewah? Have i gotta option to activate it or it's just disabled as default?

Thks!

[Magnet_Eye]

Hi. I installed MAMEwah a few days ago and have been playing with no problems these past few days. Today when i started up my cab, it gave me "Runtime Error 13"

Any ideas why this happened?

What should I do to fix it?

thanks!

EDIT:

Well, I just reinstalled MAMEwah and its working fine so far... i dunno why it did that.  

[Minwah]

I set up mamewah to play MP3s while in the screen saver and I eventually get an error along the lines of "end of file while playing" (sorry I don't remember the exact wording). I suspect one of my MP3s might be corrupted?
I have hours worth of arcade "ambience" MP3s it'll take me quite a while to figure it out by trial and error and I can't just sit around waiting for it to crash either.
I assume that mamewah doesn't log the MP3 file it's playing anywhere?
Any idea how I can find out which MP3 is corrupted short of using the trial and error method? I'll post a similar question in the jukebox forum in case someone knows of a utility to detect bad MP3s.

The MP3 isn't logged unfortunately...trial and error is probably the only way to detect a bad MP3.  I've had a few reports of MW just being 'picky' about some MP3's, but I haven't figured out why yet

[Minwah]

Hi!

I'm sorry if this question is dumb or newb but i can't use my sidewinder USB pad with mamewah? Have i gotta option to activate it or it's just disabled as default?

Thks!

Well since most people use keyboard encoders, and PC stick support is relatively tricky to add, it doesn't have the feature

But you can use JoyToKey: http://hp.vector.co.jp/authors/VA016823/joytokey/english.html , in my testing it seemed to work very well

[Minwah]

Hi. I installed MAMEwah a few days ago and have been playing with no problems these past few days. Today when i started up my cab, it gave me "Runtime Error 13"

Any ideas why this happened?

What should I do to fix it?

thanks!

EDIT:

Well, I just reinstalled MAMEwah and its working fine so far... i dunno why it did that.  

That's odd, not sure what happened...usually that error applies if either an old config file was used (not the case here) or a config file got corrupted / messed up somehow - either way deleting the \Files\.CFG files usually works if it happens again.

[papaschtroumpf]

I set up mamewah to play MP3s while in the screen saver and I eventually get an error along the lines of "end of file while playing" (sorry I don't remember the exact wording). I suspect one of my MP3s might be corrupted?
I have hours worth of arcade "ambience" MP3s it'll take me quite a while to figure it out by trial and error and I can't just sit around waiting for it to crash either.
I assume that mamewah doesn't log the MP3 file it's playing anywhere?
Any idea how I can find out which MP3 is corrupted short of using the trial and error method? I'll post a similar question in the jukebox forum in case someone knows of a utility to detect bad MP3s.

The MP3 isn't logged unfortunately...trial and error is probably the only way to detect a bad MP3.  I've had a few reports of MW just being 'picky' about some MP3's, but I haven't figured out why yet

FYI, the exact error is Run-Time Error '-2147221493 (8004006) End of file reached while decoding.

I also noticed that when it happened today the music was still playing in the background even though the error message was up. Don't knwo if it means anything. as soon as I clicked OK on the message, mamewah exited. Don't know if it helps. Maybe you could write the current MP3 file to the debug log file if it's trivial to do?

[drunkatuw]

Configuring mouse buttons in mamewah.  I've hooked up my act-lab guns and the cursors correctly follow the guns, but player 2 can't shoot.  I noticed that player 2 button1 wasn't configured to a mouse button.  So I opened the settings and selected player 2 button 1, but when I pull the trigger nothing happens.  I click the button on the mouse and again nothing happens.  I open the same game in mame32 and I can configure the mouse buttons just fine and play two player gun games great.  But I want to stick with mamewah as a front end.  I have mouse 1 set in the mame.ini file, is there something else I need to configure, or is this a bug in mamewah?

[JoeB]

This isn't really a bug, but rather a really cool feature to make I guess (if possible at all).

I've noticed that if there's a bad ROM or something messed up with the OS, then the launch screen in mamewah sits there forever.

I end up plugging the keyboard, killing the app and restarting MAMEWAH.

Is there a way to program MAMEWAH to listen to the ESC key and see if it's in the forground then stop loading/kill the defined emulator from the process list in windows and gain control of the OS??

This would be one of those ULTIMATE features in a front end! No need for keyboard for emergency!

[Minwah]

FYI, the exact error is Run-Time Error '-2147221493 (8004006) End of file reached while decoding.

I also noticed that when it happened today the music was still playing in the background even though the error message was up. Don't knwo if it means anything. as soon as I clicked OK on the message, mamewah exited. Don't know if it helps. Maybe you could write the current MP3 file to the debug log file if it's trivial to do?

Is the screensaver running when this happened?  It looks like it could be refering to decoding of an image (PNG) - if the slide-show is running then that would probably confirm it...

[Minwah]

Configuring mouse buttons in mamewah.  I've hooked up my act-lab guns and the cursors correctly follow the guns, but player 2 can't shoot.  I noticed that player 2 button1 wasn't configured to a mouse button.  So I opened the settings and selected player 2 button 1, but when I pull the trigger nothing happens.  I click the button on the mouse and again nothing happens.  I open the same game in mame32 and I can configure the mouse buttons just fine and play two player gun games great.  But I want to stick with mamewah as a front end.  I have mouse 1 set in the mame.ini file, is there something else I need to configure, or is this a bug in mamewah?

Input mapping for your games is not handled at all by MAMEWAH.  You need to configure MAME itself for that.  Either use the 'Input' options in the TAB menu, or use ctrlr ini files...then again if you're using MAME32 I'm not sure (I recommend not using MAME32).

[Minwah]

This isn't really a bug, but rather a really cool feature to make I guess (if possible at all).

I've noticed that if there's a bad ROM or something messed up with the OS, then the launch screen in mamewah sits there forever.

I end up plugging the keyboard, killing the app and restarting MAMEWAH.

Is there a way to program MAMEWAH to listen to the ESC key and see if it's in the forground then stop loading/kill the defined emulator from the process list in windows and gain control of the OS??

This would be one of those ULTIMATE features in a front end! No need for keyboard for emergency!

I'm sure it's possible, but not something I can do.  I think Howard does something similar in his wrappers tho.

But if you have 'Show DOS Box' set to Auto-Show, then bad dumps shouldn't cause it to hang.  Also if you use ClrMAMEPro checked roms you shouldn't have any bad sets, so it shouldn't hang due to that.  That just leaves 'something messed up with the OS', but if the OS hangs you'd have to restart anyway.

[Brad Lee]

In .963, i can't find the 'generate custom list by filters' option in the config menus. Its in the docs, and after the first run it creates the filter*.ftr files.

This is a brand new install, never had a mamewah folder before. Command line mame .79 if that makes any difference. Windows 2000 is what Im playing on, but my cabinet is running XP

edit- while not a bug at all, is there a way to use marquees (or other artwork elements) in the game list, or is the game list strictly text?

[Minwah]

In .963, i can't find the 'generate custom list by filters' option in the config menus. Its in the docs, and after the first run it creates the filter*.ftr files.

This is a brand new install, never had a mamewah folder before. Command line mame .79 if that makes any difference. Windows 2000 is what Im playing on, but my cabinet is running XP

edit- while not a bug at all, is there a way to use marquees (or other artwork elements) in the game list, or is the game list strictly text?

To see that option you need to first select a custom list (using P1 Coin or in Games List Options) - then the option will become available.

The games list is strictly text I'm afraid.

[papaschtroumpf]

I set up mamewah to play MP3s while in the screen saver and I eventually get an error along the lines of "end of file while playing" (sorry I don't remember the exact wording). I suspect one of my MP3s might be corrupted?
I have hours worth of arcade "ambience" MP3s it'll take me quite a while to figure it out by trial and error and I can't just sit around waiting for it to crash either.
I assume that mamewah doesn't log the MP3 file it's playing anywhere?
Any idea how I can find out which MP3 is corrupted short of using the trial and error method? I'll post a similar question in the jukebox forum in case someone knows of a utility to detect bad MP3s.

The MP3 isn't logged unfortunately...trial and error is probably the only way to detect a bad MP3.  I've had a few reports of MW just being 'picky' about some MP3's, but I haven't figured out why yet

FYI, the exact error is Run-Time Error '-2147221493 (8004006) End of file reached while decoding.

I also noticed that when it happened today the music was still playing in the background even though the error message was up. Don't knwo if it means anything. as soon as I clicked OK on the message, mamewah exited. Don't know if it helps. Maybe you could write the current MP3 file to the debug log file if it's trivial to do?

Minwah, after spending countless hours trying to figure out what MP3 file might cause the problem, I gave up and decided to get rid of the music during screen saver.... The problem still occured! this means that this is not music related but screen saver related, maybe an weird/invalid PNG file?
Any idea how I can troubleshoot this?

[Rocky]

the screensaver in Mamewah was hanging on me and I thought it was a bad .png

In reality it was a .txt file  (changes.txt)

There is a game with a rom name of changes.zip   ....hmmm

I removed the .txt file and now everything works. Check your art folders and remove any non-art files

Good luck,
Rocky

[papaschtroumpf]

Thanks, I'll give that a try

[Minwah]

Minwah, after spending countless hours trying to figure out what MP3 file might cause the problem, I gave up and decided to get rid of the music during screen saver.... The problem still occured! this means that this is not music related but screen saver related, maybe an weird/invalid PNG file?
Any idea how I can troubleshoot this?

Looks like you missed my reply to this prob above

But yes, check what Rocky said first...

[papaschtroumpf]

Sorry, I did miss your earlier answer  
I'll try what Rocky suggested (wife's playing on the cab right now, can't check it out right this minute   )
If that's not the problem I'll have to figure out a script to go through all the PNGs, or maybe just redownload the screens that MagnetEye posted on this forum. (Edit: that thread was marquees, but I was thinking about a different thread about the crashtest site)

[papaschtroumpf]

OK, there was no nasty text file in the directory but I went back to CrashTest's site and downloaded all the screenshots again and the can was up overnight without crashing! whoohooo!
Sorry I missed your original suggestion to do just that Minwah.

[Brad Lee]

Ok this may be a dumb one, but......

Ive got 2 emulators setup. If Im viewing #1, and hitthe 'cycle emulator' key, it goes to #2, as expected. If I hit it again it doesnt cyclearound to #1. Am I missing a an option somewhere, is it by design, or is it a bug?

Thanks!

edit- It seems to work if I hit any other key before cycling again, not sure if its my POS keyboard here, or again ifthis is by design

Also, does the debug file only get added to for mame? I have a winamp emulator setup and it doesnt add anythingto the debug.txt file when one is played

[papaschtroumpf]

By default mamewah defines 20 emus, so you have to cycle through all 20 to go back to #1.
Use mamewah setup or manually edit your config file to set the number of emulators to 2.
There is no "previous emulator" key unfortunately so if you have more than 2 you will have to go around to the first one.

[papaschtroumpf]

I've been having problems lately with the mamewah.cfg file getting corrupted (only keeps the first 12 lines or so). This seems to be new behavior since I upgraded to 0.963. Anyone experiencing similar problems?

[Minwah]

OK, there was no nasty text file in the directory but I went back to CrashTest's site and downloaded all the screenshots again and the can was up overnight without crashing! whoohooo!
Sorry I missed your original suggestion to do just that Minwah.

No worries - glad you fixed it

[Minwah]

Ok this may be a dumb one, but......

Ive got 2 emulators setup. If Im viewing #1, and hitthe 'cycle emulator' key, it goes to #2, as expected. If I hit it again it doesnt cyclearound to #1. Am I missing a an option somewhere, is it by design, or is it a bug?

Thanks!

edit- It seems to work if I hit any other key before cycling again, not sure if its my POS keyboard here, or again ifthis is by design

Also, does the debug file only get added to for mame? I have a winamp emulator setup and it doesnt add anythingto the debug.txt file when one is played

Use the 'Emulator Settings' > 'Misc Settings' > 'No. Emulators to Display' option to set how many emus you have.  What papasch says it correct further to that.

Debug.log should get updated everytime you launch something by hitting '1' (regardless of emulator / app etc).  Check you are looking for debug.log and not debug.txt...

[Minwah]

I've been having problems lately with the mamewah.cfg file getting corrupted (only keeps the first 12 lines or so). This seems to be new behavior since I upgraded to 0.963. Anyone experiencing similar problems?

Hmmm I think a few people were getting this previously (I thought in v0.962 tho).  I never had the problem - could you email me a corrupted .cfg file if it happens again?

Actually, I think the solution some users found was that they were using MAMEWAH as a shell and it caused problems.  I think some of those people may have been using MAMEWAH as shell AND in their Startup folder - this caused 2 instances to be opened and conflict with each other.  Double check this isn't the case here...

[JoeB]

I'm note sure the cause of the corruption, but I can tell you for a fact that you can run multiple instances of MAMEWAH!

I run MAMEWAH @ 368x240 and windows @ 640x480 (on ArcadeVGA card) and in the rare case where MAMEWAH looses focus and window stakes over, MAMEWAH runs in a small window on the a bigger desktop.

I end up starting another instance of MAMEWAH, exiting, and the first instance gets focus again.  I exit that instane, and start a new one.  The new one changes the size back to 368x240.

Hope this makes sense.    

[papaschtroumpf]

I don't run mamewah as a shell and I'm not aware of having ran mutiple instances of mamewah at once, although I will keep an eye on it if the problem ever occurs. I may have left mamewah config open while running mamewah, maybe that's part of it?
I'll post the file next time this happens, but I remember that it looks truncated, if I remember right there are about a dozen lines in it with key definitions and it ends abruptly in the middle of a line.

I also realized that I have been terminating mamewah over XP PRo's remote desktop more often lately: my cab automatically launches mamewah at boot, then I'll use my laptop from another room to log into my cab over the network using XP Pro's remote desktop ability: after I log in I see the mamewah screen, and if I hit escape I don't see mamewah disappear, but if I log out of remote desktop then log back in then mamewah has exited. Maybe this (admitedly unusual) way of doing things causes mamewah to exit improperly? I'll avoid doing that in the future except maybe to test this theory further.

[papaschtroumpf]

I thought this has been mentionned before but I can't find the post: if there a "number of lists to display" setting similar to the "number of emulators to display"? or maybe mamewah should detect that a list is empty and skip over it? I've had users hit the "next list" button accidentally then they complain that "all the games are gone" when they're simply lokoing at the next list (which is empty because atm I only use a single list per emu, although I may change that).

[Minwah]

I don't run mamewah as a shell and I'm not aware of having ran mutiple instances of mamewah at once, although I will keep an eye on it if the problem ever occurs. I may have left mamewah config open while running mamewah, maybe that's part of it?
I'll post the file next time this happens, but I remember that it looks truncated, if I remember right there are about a dozen lines in it with key definitions and it ends abruptly in the middle of a line.

I also realized that I have been terminating mamewah over XP PRo's remote desktop more often lately: my cab automatically launches mamewah at boot, then I'll use my laptop from another room to log into my cab over the network using XP Pro's remote desktop ability: after I log in I see the mamewah screen, and if I hit escape I don't see mamewah disappear, but if I log out of remote desktop then log back in then mamewah has exited. Maybe this (admitedly unusual) way of doing things causes mamewah to exit improperly? I'll avoid doing that in the future except maybe to test this theory further.

Leaving a CFG file open while running MW could be bad...also I have no way of saying 100% if it causes any harm but I would recommend against closing MW remotely if possible...

[Minwah]

I thought this has been mentionned before but I can't find the post: if there a "number of lists to display" setting similar to the "number of emulators to display"? or maybe mamewah should detect that a list is empty and skip over it? I've had users hit the "next list" button accidentally then they complain that "all the games are gone" when they're simply lokoing at the next list (which is empty because atm I only use a single list per emu, although I may change that).

It used to do this automatically, but at some point I added the 'Select Custom Lists to Cycle' option (within Games List Options) - that should do what you need

[Calawala]

First off, I want to thank you Minwah for your time and effort.  I have tried out a number of frontends, around 6 or 7, and Mamewah is by far my favorite.  Easy to set up, easy to navigate, looks great, and is easy to customize.

A little info about my system:
WinXP sp1
AMD Athlon XP 1900+ (1.6Ghz)
512 MB ram
GeForce3 Ti 500  v. 53.03 drivers
DirectX 9.0b


A couple of bugs that I have run into with version 0.963

- I have run into the focus problem that a few above have described.  On occasion when I start Mamewah, the windows taskbar stays visible.  Note that the first time Mamewah starts after booting up a PC never has this problem for me.   This only seems to happen after I have quit Mamewah to windows, then start it up again.    
- A related problem is multitasking with Mamewah.  If I switch to the desktop while Mamewah is running, sometimes Mamewah has trouble regaining focus.  The only way I can get it back is to open the task manager and manually switch to the Mamewah task.  Then sometimes (read once or twice) after I exit from a mame game, only half of Mamewah appears.

Both of these problems don't concern me much as when I finaly set up my cab, I don't plan on multitasking or quiting to the desktop.

- If I set up a custum list to generate from filters, that works great.  But, then I cannot use the Next List key to cycle through my other custom lists, unless the other lists were also set up to generate from filters.  The Main list, and both the Longest Played and Most Freq Played lists are unavailable, unless I navigate to them through the menus.

- I was playing around with veritcal layouts.  Rotating the screen resolution with the Geforce drivers and then creating a layout that matched (600x800), which worked fine.  The only problem I had was with the image aspect ratio of the snapshots.  I attached 2 picts (at least I will try, first time attaching a pict) to better illustrate what I mean.  One for vertical games, one for horizontal


Future feature wish list  
- a shortcut key for selecting custom game lists from a menu
- ditto, but with selecting emulators from a menu
- a key for cycling to the previous custum game list
- ditto, but with emulators
- 2 exit keys (as suggested in another post).  one for exit to windows, another for exit and shutdown.  Or perhaps just a key to exit and shutdown and leave a menu option to exit to windows?  Maybe this is posible already /em scratches head - I'll go look again
- EDIT:  add in a key that will pop up a smallish blank form(like the options menu window) that can be custumized (i.e. a help screen image background).  If you wanna go crazy, add in a number of these blank form windows that can be popped up from a key.  That way I could put in additional art images, gameinfo, history, etc that I couldn't normaly fit into the layout.
- EDIT2:  more custom games lists    (sorry, getting carried away here)

Calawala

[papaschtroumpf]

while we're on the feature request, it would be nice if the layout editor would open the window in the exact size of the layout, I edit my 800x600 layouts on my other desktop which is 1600x1200 and I never know where the 800x600 really ends

[Minwah]

A couple of bugs that I have run into with version 0.963

Here goes:

- I have run into the focus problem that a few above have described.  On occasion when I start Mamewah, the windows taskbar stays visible.  Note that the first time Mamewah starts after booting up a PC never has this problem for me.   This only seems to happen after I have quit Mamewah to windows, then start it up again.

I'm not sure about this one - I can't replicate the problem .  Perhaps try setting a different resolution or colour depth to your desktop.

- A related problem is multitasking with Mamewah.  If I switch to the desktop while Mamewah is running, sometimes Mamewah has trouble regaining focus.  The only way I can get it back is to open the task manager and manually switch to the Mamewah task.  Then sometimes (read once or twice) after I exit from a mame game, only half of Mamewah appears.

This doesn't surprise me - I realise it's not easy to Alt+Tab back to MAMEWAH, I suppose I would just recommend don't do it!

- If I set up a custum list to generate from filters, that works great.  But, then I cannot use the Next List key to cycle through my other custom lists, unless the other lists were also set up to generate from filters.  The Main list, and both the Longest Played and Most Freq Played lists are unavailable, unless I navigate to them through the menus.

From memory the way it works is when you generate a custom list, it automatically switches 'on' that list in the 'Select Custom Lists to Cycle' menu.  Use this menu to select which lists you wish to be able to cycle to using the 'next list' key.

- I was playing around with veritcal layouts.  Rotating the screen resolution with the Geforce drivers and then creating a layout that matched (600x800), which worked fine.  The only problem I had was with the image aspect ratio of the snapshots.  I attached 2 picts (at least I will try, first time attaching a pict) to better illustrate what I mean.  One for vertical games, one for horizontal

Yep one other user pointed this out to me - I have now fixed the problem.  My aspect-ratio-fix code didn't take into account vertical layouts  

Future feature wish list  
- a shortcut key for selecting custom game lists from a menu
- ditto, but with selecting emulators from a menu
- a key for cycling to the previous custum game list
- ditto, but with emulators
- 2 exit keys (as suggested in another post).  one for exit to windows, another for exit and shutdown.  Or perhaps just a key to exit and shutdown and leave a menu option to exit to windows?  Maybe this is posible already /em scratches head - I'll go look again
- EDIT:  add in a key that will pop up a smallish blank form(like the options menu window) that can be custumized (i.e. a help screen image background).  If you wanna go crazy, add in a number of these blank form windows that can be popped up from a key.  That way I could put in additional art images, gameinfo, history, etc that I couldn't normaly fit into the layout.
- EDIT2:  more custom games lists    (sorry, getting carried away here)

I'll add them to the list!

[Minwah]

while we're on the feature request, it would be nice if the layout editor would open the window in the exact size of the layout, I edit my 800x600 layouts on my other desktop which is 1600x1200 and I never know where the 800x600 really ends

There should be a dotted line to show the extents of the layout, is it not there?

[Calawala]

I'm not sure about this one - I can't replicate the problem .  Perhaps try setting a different resolution or colour depth to your desktop.

I will try this out sometime.  To clarify it a bit more: it only seems to happen if I quit to desktop, start up another app (like IE), and then start up Mamewah again.   May I ask what settings you are running at?

This doesn't surprise me - I realise it's not easy to Alt+Tab back to MAMEWAH, I suppose I would just recommend don't do it!

ok  

From memory the way it works is when you generate a custom list, it automatically switches 'on' that list in the 'Select Custom Lists to Cycle' menu.  Use this menu to select which lists you wish to be able to cycle to using the 'next list' key.

err... doh.  Guess my eyes sorta glossed over that menu option.  Thanks for pointing it out.  What threw me off though, was that by default all custom menus were set to 'yes' to cycle.  And then after setting up one to generate from filters, it then set all to 'no' except that list.

Yep one other user pointed this out to me - I have now fixed the problem.  My aspect-ratio-fix code didn't take into account vertical layouts  

Sweet.  Look forward to the next release  

I'll add them to the list!

Thanks!  

Another question: is it possible to have Mamewah automaticaly launch a game upon startup?

Calawala

[Minwah]

I'm not sure about this one - I can't replicate the problem .  Perhaps try setting a different resolution or colour depth to your desktop.

I will try this out sometime.  To clarify it a bit more: it only seems to happen if I quit to desktop, start up another app (like IE), and then start up Mamewah again.   May I ask what settings you are running at?

I run 1280x960 desktop res, and then MAMEWAH in 640x480 or 1024x768.  I've tried just about every combination tho, and it works OK for me...also I open/close it etc. when I'm testing.  Just one of those pain in the behind things

Another question: is it possible to have Mamewah automaticaly launch a game upon startup?

Nope!

[supersinner]

New Bug? Alright I setup Mamewah and I love it...it is a great front end. The ability for different layouts is awesome. Anyway I am having a problem....when I run a mame rom file through mamewah...it changes the colors of my mame rom. They are wrong. When I run them directly through mame they work like a charm. I heard a few people say they run batch files instead of the actual roms...is this what I should do to fix the problem? Any help would be appreciated.

i too am having the same problem when i run it in my laptop its fine but its like it changes the pallette or something when the games start i checked the mameini and they are both set to 1 any other ideas???

[supersinner]

New Bug? Alright I setup Mamewah and I love it...it is a great front end. The ability for different layouts is awesome. Anyway I am having a problem....when I run a mame rom file through mamewah...it changes the colors of my mame rom. They are wrong. When I run them directly through mame they work like a charm. I heard a few people say they run batch files instead of the actual roms...is this what I should do to fix the problem? Any help would be appreciated.

i too am having the same problem when i run it in my laptop its fine but its like it changes the pallette or something when the games start i checked the mameini and they are both set to 1 any other ideas???

i corrected it by setting the display to 32 bit high color thanks anyway

[screaming]

Hello there,

  I'm having layout issues in MAMEWah. I'm sure it's something I'm doing wrong, but I've read and re-read the layouts.txt file to make sure and I can't find anything.. So here goes:

  I would like at least two images to be emulator specific. One is the logo and the other is a layout of the buttons you would use on my CP while playing a game in that emulator.

  I figured the easiest way to do this was to just make a single background image for each emulator that would change when I selected an emulator. After reading layouts.txt, it looks like MAMEWah is supposed to be able to do this.

  I started off with a single layout.lay file and a emu?-main.jpg file for each emulator. That worked great, except whenever I started MAMEWah whichever emulator it was in the background stayed as the background, even when I switched emulator lists. It just didn't change.

  So I thought I'd take a different approach and make an emu?.lay for each emulator and remove the layout.lay file. That worked again for the first emulator list that came up, but now when I change emulators I get an error: Run-time error: '360': Object already loaded.

  Are you loading all the emulator layouts when MAMEWah starts up, then trying to load them again when I switch emulators? That's what it looks like.

  As an aside, when it's in this configuration, it changes resolutions when I change emulator lists. Since all my resolutions are the same, I just get an annoying screen flicker. Is there some way you can put a check in there to see if the new resolution is different than the current resolution, and if so don't change it?

Thanks for any help you can provide.

/Steve
 
*edit*
Okay, I narrowed it down definitely to the layout file. I have two layout files, both were made from the MLD, but one gives me that error 360 and one doesn't.  Ihave all the same elements visible.. I'm not sure what the difference could be. I'll keep looking though.

I'm trying to get the catver.ini stuff to show up with the MAME roms, but I don't see the  'CatVer Filename' under 'Emulator Settings' > 'List Generation Settings' (as stated in the FAQ). Has this moved somewhere else?
*/edit*

[Minwah]

Hello there,

  I'm having layout issues in MAMEWah. I'm sure it's something I'm doing wrong, but I've read and re-read the layouts.txt file to make sure and I can't find anything.. So here goes:

  I would like at least two images to be emulator specific. One is the logo and the other is a layout of the buttons you would use on my CP while playing a game in that emulator.

  I figured the easiest way to do this was to just make a single background image for each emulator that would change when I selected an emulator. After reading layouts.txt, it looks like MAMEWah is supposed to be able to do this.

  I started off with a single layout.lay file and a emu?-main.jpg file for each emulator. That worked great, except whenever I started MAMEWah whichever emulator it was in the background stayed as the background, even when I switched emulator lists. It just didn't change.

  So I thought I'd take a different approach and make an emu?.lay for each emulator and remove the layout.lay file. That worked again for the first emulator list that came up, but now when I change emulators I get an error: Run-time error: '360': Object already loaded.

  Are you loading all the emulator layouts when MAMEWah starts up, then trying to load them again when I switch emulators? That's what it looks like.

  As an aside, when it's in this configuration, it changes resolutions when I change emulator lists. Since all my resolutions are the same, I just get an annoying screen flicker. Is there some way you can put a check in there to see if the new resolution is different than the current resolution, and if so don't change it?

Thanks for any help you can provide.

/Steve
 
*edit*
Okay, I narrowed it down definitely to the layout file. I have two layout files, both were made from the MLD, but one gives me that error 360 and one doesn't.  Ihave all the same elements visible.. I'm not sure what the difference could be. I'll keep looking though.

I'm trying to get the catver.ini stuff to show up with the MAME roms, but I don't see the  'CatVer Filename' under 'Emulator Settings' > 'List Generation Settings' (as stated in the FAQ). Has this moved somewhere else?
*/edit*

Try opening the problem layout with the MLD and re-save - might do the trick    It does load and apply the layout when you switch, not all at the beginning.  Did you email me about this?  If not someone else had the same problem the other day...

To use catver.ini, just place it in your emulators root folder.  I removed the 'CatVer Filename' as it seemed a bit pointless!

[old_computers]

Hi

I have just installed Mamewah 0963 on my W2000 system...
But just after succesfull installation, when I want to run Mamewah,
I get :

"Run-time error '13' : Type Mismatch" error....

I have tried to several install attempts, but still the same problem
Is it a real bug, or is the solution trivial ?

Thanks for your help

[screaming]

Hi

I have just installed Mamewah 0963 on my W2000 system...
But just after succesfull installation, when I want to run Mamewah,
I get :

"Run-time error '13' : Type Mismatch" error....

I have tried to several install attempts, but still the same problem
Is it a real bug, or is the solution trivial ?

Thanks for your help

I got that error when I tried to add extra lines in any of the config files that weren't supposed to be there (like the CatVer Filname= line). Did you add or remove any lines from any of the config files?

/Steve

[Minwah]

Hi

I have just installed Mamewah 0963 on my W2000 system...
But just after succesfull installation, when I want to run Mamewah,
I get :

"Run-time error '13' : Type Mismatch" error....

I have tried to several install attempts, but still the same problem
Is it a real bug, or is the solution trivial ?

Thanks for your help

Yeah screaming is right, usually it means a mistake in the config file(s).  If all else fails try deleting the contents of your \mamewah\files folder and start again.  If you manually edited CFG files before then don't do that this time - use MAMEWAH's menu's and you can't go wrong

[old_computers]

Well in fact, I didn't touch anything !

I just downloaded latest Mamewah.
Installed it through the installer,
Installed the layout folder,
double-clicked on mamewah.exe
and BANG... I get this error...

I tried to install it to different locations, different disks, and two different w2000 computers... I get the same error!

The first time you launch Mamewah, there is not even the FILES folder from what I read... I guess this is normal

I even tried Mamewah configuring tool, to see if it could magicaly correct the error, but no, same error...

So I'm here... quite motivated to use Mamewah for my brand new Mame cabinet (picture attached), but I cannot get it to run

Wouldn't it be the latest version of Mamewah which cannot run on w2000 ?
Thanks for any help

_____

Olivier Boisseau
Webmaster
www.old-computers.com

[Minwah]

Well in fact, I didn't touch anything !

I just downloaded latest Mamewah.
Installed it through the installer,
Installed the layout folder,
double-clicked on mamewah.exe
and BANG... I get this error...

I tried to install it to different locations, different disks, and two different w2000 computers... I get the same error!

The first time you launch Mamewah, there is not even the FILES folder from what I read... I guess this is normal

I even tried Mamewah configuring tool, to see if it could magicaly correct the error, but no, same error...

So I'm here... quite motivated to use Mamewah for my brand new Mame cabinet (picture attached), but I cannot get it to run

Wouldn't it be the latest version of Mamewah which cannot run on w2000 ?
Thanks for any help

_____

Olivier Boisseau
Webmaster
www.old-computers.com

My apologies, I think this could be a regional settings problem (bug).  From your name I'm guessing that you are European...MAMEWAH seems to have a problem with the decimal separator/symbol that some regional settings use, namely the symbol must be a full-stop '.' and not a comma ','.

The only way I know of around this problem atm is to change your decimal symbol in Regional Settings in Control Panel.  Hopefully I will fix that some day  

Cool website btw, my original programming computer was the Amstrad CPC6128  

[old_computers]

From your name I'm guessing that you are European...MAMEWAH seems to have a problem with the decimal separator/symbol that some regional settings use, namely the symbol must be a full-stop '.' and not a comma ','. The only way I know of around this problem atm is to change your decimal symbol in Regional Settings in Control Panel.  Hopefully I will fix that some day  

YES ! you are right !
It solved the problem!
I'm french... But I'm surprise to be the first european to report this bug...
I think it could be important to mention it on the Mamewah website, otherwise most people will not look for a solution like I did, and will try other frontends (what a shame)

Cool website btw, my original programming computer was the Amstrad CPC6128  

hey hey
Thanks for the website... I had a CPC 6128 too, though my first computer was an Oric-1
Haaaa, those days... Message to other readers : if you have not visited www.old-computers.com so far, give it a chance

My last attachment didn't seem to work, I try again (my arcade cabinet)...

Thanks a lot guys for your help

_______

Olivier Boisseau
Webmaster
www.old-computers.com

[Minwah]

YES ! you are right !
It solved the problem!
I'm french... But I'm surprise to be the first european to report this bug...
I think it could be important to mention it on the Mamewah website, otherwise most people will not look for a solution like I did, and will try other frontends (what a shame)

Glad it worked...you're not the first to hit apon it tho, I'm just a bit lazy at making docs etc.  I'm in the middle of making a brand new FAQ mind, so I will make sure I mention it.

Nice cab btw

[cheezeflap]

I found that if you asign the tab key to "next list" then it does not switch around the lists properly.   After flipping the first list, you need to het another key (any)  before you can move to the next list.   The only seems to happen with the tab key.

[Minwah]

I found that if you asign the tab key to "next list" then it does not switch around the lists properly.   After flipping the first list, you need to het another key (any)  before you can move to the next list.   The only seems to happen with the tab key.

OK I'll check it out...

[JoeB]

I found that if you asign the tab key to "next list" then it does not switch around the lists properly.   After flipping the first list, you need to het another key (any)  before you can move to the next list.   The only seems to happen with the tab key.

Just out of curiousity, are you using MAMEWAH as a front end on your regular desktop PC??  

[cheezeflap]

Just out of curiousity, are you using MAMEWAH as a front end on your regular desktop PC??  

I have a cabinet running Windows XP and a homemade CP

[JoeB]

Just out of curiousity, are you using MAMEWAH as a front end on your regular desktop PC??  

I have a cabinet running Windows XP and a homemade CP

If you have a homemade cab, why no remap the switch emulators button to something else and do the same in MAMEWAH?

[cheezeflap]

If you have a homemade cab, why no remap the switch emulators button to something else and do the same in MAMEWAH?

Yah, already done.   I was just reporting it as a bug because it took me a while to figure out that it was what was causing my wierd problem and I didnt want someone else to have to have the same problem.   Its not really a big deal for me anymore

[quarterstringer]

In the Longest Played feature, 4 of my games that were in the top 10 are now at the very bottom of the list. Any ideas about what happened?

[screaming]

In the Longest Played feature, 4 of my games that were in the top 10 are now at the very bottom of the list. Any ideas about what happened?

  Is this a test?

[quarterstringer]

Not a test. I looked at the EMU1.FAV and the 4 games that went to the bottom of the list all had negative numbers in them. I just changed the numbers to put the games near the top again.

[Minwah]

Not a test. I looked at the EMU1.FAV and the 4 games that went to the bottom of the list all had negative numbers in them. I just changed the numbers to put the games near the top again.

Not sure why that happened...I'll have to start using the longest played feature in my cab and see if I get any problems.

[MadEditor]

Just a question

Did i miss it or was "mouse/spinner support to browse games" suppose to be in the last build ?

[Minwah]

Just a question

Did i miss it or was "mouse/spinner support to browse games" suppose to be in the last build ?

Nope, the next one

[MadEditor]

Nope, the next one

  I'll wait then ...  

[Minwah]

I'll wait then ...  

Good news is that I have almost done the mouse support

Bad news is that I want to add (PC) joystick support too, and my analog joystick isn't finished yet for testing purposes (I don't have another PC stick)...

[quarterstringer]

I'll have to start using the longest played feature in my cab and see if I get any problems.

You should use it, it's a great feature . I'll be waiting for joystick support too, so I won't have to use JoytoKey anymore.

[esfb8zs]

I just started using MAMEWAH, and LOVE it.  I've been using a DOS cabinet with AdvanceMenu.  

I like that you can lock the MAMEWAH menu by holding down the player 2 key.  Is there anyway to make this the default behaviour when starting up?  I'd like for my cabinet to boot into this mode, and I could hold the player 2 button down to access the menus if I need them.  

Also, can the esc key be made to take a menu off the screen also?  Say if I press esc (menu is not locked of course), and the shutdown menu comes up.  I'd like to be able to press esc again and the menu go away without me having to make a choice on the menu, or hitting start2 to bring up the other menu, then start2 again to exit.  I hope I am explaining this so you can understand.

Again, I really like the menu system, I appreciate all the hard work!

Jay    

[Minwah]

I like that you can lock the MAMEWAH menu by holding down the player 2 key.  Is there anyway to make this the default behaviour when starting up?  I'd like for my cabinet to boot into this mode, and I could hold the player 2 button down to access the menus if I need them.  

Lock the menu, and quit MAMEWAH using the Exit button...next time you start MAMEWAH the menu will be locked

Also, can the esc key be made to take a menu off the screen also?  Say if I press esc (menu is not locked of course), and the shutdown menu comes up.  I'd like to be able to press esc again and the menu go away without me having to make a choice on the menu, or hitting start2 to bring up the other menu, then start2 again to exit.  I hope I am explaining this so you can understand.

Yeah sounds like a good idea...

[AGGIEZ]

Is there no solution for the "Run-time error '70' & '75' in Windows 98???

[AGGIEZ]

Is there no solution for the "Run-time error '70' & '75' in Windows 98???

Well, after some work, I think I have a solution for these two errors. It seems to be working form me now.

I've created two batch files, one that MINWAH recommended and one that deletes everything in the c:\Program Files\Mamewah\Files folder except for the Emulator 1 and mamewah.cfg files. I put both of these batch files into the startup folder along with MAMEWAH. Upon bootup, the two batch files run and then MAMEWAH opens. No issues so far...

If that somehow doesn't work in the near future I'm just going to have to bite it and upgrade to XP.

[JoeB]

Great job with fixing the 1.5 bugs..  here's some stuff I noticed:

- When scrolling through the games, the images do not referesh the way they did pre-1.5.  They do not refresh until you're done scrolling.  Pre-1.5 they always refreshed.  It looks wierd on my layout to have the big empty spot with no snap.

- Has anyone managed to get the "next emulator" button to work?  I set it to the letter C (button 7 for me on my JPAC) and it doesn't work.  Even with the keyboard plugged in, and pressing C doesn't do anything.
I've checked the ini file for other "c" keyword names, but it's not there!  

My feature request:

- Have the ability to modify the menus strings.  For example, I don't want to see "Exit to windows" but rather might want "Exit to OS" etc..  or what about people that don't speak English and would want to translate the menu strings?  It'd be great if MAMEWAH can read it from an ini file.
- Have the ability to change the menu font color.  Green is cool.. but blue will be cooler.  

Apart from that, great job!

[Minwah]

- When scrolling through the games, the images do not referesh the way they did pre-1.5.  They do not refresh until you're done scrolling.  Pre-1.5 they always refreshed.  It looks wierd on my layout to have the big empty spot with no snap.

Actually, for the most part it works the same - set refresh_images              1 in mamewah.ini to have the images refresh each time.  The one difference is that rather than getting the 'no snap' image while scrolling (with refresh_images 0), you now get nothing - there is a reason for this but don't ask!

- Has anyone managed to get the "next emulator" button to work?  I set it to the letter C (button 7 for me on my JPAC) and it doesn't work.  Even with the keyboard plugged in, and pressing C doesn't do anything.
I've checked the ini file for other "c" keyword names, but it's not there!  

How about this?:

LAUNCH_CONTROL_VIEWER      "DIK_C"

- Have the ability to modify the menus strings.  For example, I don't want to see "Exit to windows" but rather might want "Exit to OS" etc..  or what about people that don't speak English and would want to translate the menu strings?  It'd be great if MAMEWAH can read it from an ini file.

Someone requested this before, for the sake of different languages.  I will add it eventually (for v2), but it is far from the top of my todo list atm.

- Have the ability to change the menu font color.  Green is cool.. but blue will be cooler.  

Use the Layout Designer - I have yellow text in my menu

[JoeB]

never mind.. works!

[gap]

Possibly bugs, but more likely my own ignorance... but here goes anyway.

1. Sometimes I lose my controls for a while (older Ipac).  Everything stops responding for maybe 30 seconds or so, then the big "mame wah" full-screen image appears, then my controls are again active.

2. Sometimes I have problems getting to the main menu.  I'll be in a games list and want to regenerate my list, but can't seem to pull up the menu.  Hitting P2 Start (mapped to "2") doesn't pull it up.  Original ctrlr/default.ini file.  Can't always reproduce.

3. Having trouble getting VisualBoyAdvance.exe correctly configured.  I've tried various param combinations and have the same problem each time.  The exe comes up with an error message "Unsupported file type: (name of rom)."  I press "ok" to get rid of the error dialog, then select File -> Exit to close visualboyadvance.exe.  

Then visualboyadvance.exe is immediately executed again, but this time it works fine and the game starts up as expected.

If I run the command line in mamewah.log, it works fine.

rom_path                                  f:\gba\gbaroms
rom_extension                             zip

emulator_executable                       f:\gba\visualboyadvance.exe
send_rom_path                             1
send_rom_extension                        1

[ edited: never mind on #3.  This was fixed by setting show_dos_box to "yes".  Evidently "auto" results in a call to verify roms, which doesn't work with anything except mame. ]

[SirPoonga]

Minwah, I don't know if this was discussed and I wouldn't have brought this up because I don't use mamewah enough but a chat user was having a simular problem.

His problem was vdeo was different in mame when running mame at commandline vs through mamewah.  Now I have some weird issues too.  I think they are due to the fact that you might be running mame from NOT in the mame folder.  It ther is a c:\mamewah folder.  Mamewah runs fromt hat.  Mame is in c:\mame.  In mamewah you just call a "C:\mame\mame.exe -someoption romfolder romname".  If oyu run it like that it will easily cause these issues.  As mame will look for all it's file save and setting from the folder it is being run in, in this case c:\mamewah.  Y

What should be done is temporarily remember the current directory(temp = CurrentDirectory()).  Then switch to mame directoryusing file system functions.  Run mame without the directoryinfo.  When mame quits restore old working directory.

But I have an old mamewah too so my issues could be something that was fixed but I have been too lazy on modem to download a new mamewah.  But the symptoms are of that of this type of problem.

[Minwah]

1. Sometimes I lose my controls for a while (older Ipac).  Everything stops responding for maybe 30 seconds or so, then the big "mame wah" full-screen image appears, then my controls are again active.

Are you re-programming the IPAC from MW?  Someone else had a similar problem when doing this - I'm about to start looking at it.

2. Sometimes I have problems getting to the main menu.  I'll be in a games list and want to regenerate my list, but can't seem to pull up the menu.  Hitting P2 Start (mapped to "2") doesn't pull it up.  Original ctrlr/default.ini file.  Can't always reproduce.

I *think* I have encountered a similar problem, but I couldn't close the options menu.  Hopefully this will be resolved in the next release.

3. Having trouble getting VisualBoyAdvance.exe correctly configured.  I've tried various param combinations and have the same problem each time.  The exe comes up with an error message "Unsupported file type: (name of rom)."  I press "ok" to get rid of the error dialog, then select File -> Exit to close visualboyadvance.exe.  

Then visualboyadvance.exe is immediately executed again, but this time it works fine and the game starts up as expected.

<snip>
[ edited: never mind on #3.  This was fixed by setting show_dos_box to "yes".  Evidently "auto" results in a call to verify roms, which doesn't work with anything except mame. ]

Yes, never use 'auto' for anything other than MAME.

[Minwah]

His problem was vdeo was different in mame when running mame at commandline vs through mamewah.  Now I have some weird issues too.  I think they are due to the fact that you might be running mame from NOT in the mame folder.  It ther is a c:\mamewah folder.  Mamewah runs fromt hat.  Mame is in c:\mame.  In mamewah you just call a "C:\mame\mame.exe -someoption romfolder romname".  If oyu run it like that it will easily cause these issues.  As mame will look for all it's file save and setting from the folder it is being run in, in this case c:\mamewah.  Y

What should be done is temporarily remember the current directory(temp = CurrentDirectory()).  Then switch to mame directoryusing file system functions.  Run mame without the directoryinfo.  When mame quits restore old working directory.

I can assure you I do change to the emulators directory before launching.  I think the issue/problem is this: MAMEWAH runs @ 640x480 (by default).  Many people run their desktop at a different res.  When MAME is run with 'resolution auto', it will sometimes pick a different mode, depending on what mode is currently selected - ie it might pick a different mode when launched from MW (eg 640x480) than desktop (eg 1024x768).

I'm not saying 100% this is the case, but it seems to explain most if not all cases of this I have encountered.

[gap]

MW:  I am not using MW to reprogram the Ipac.

I'm not even sure this is a MW problem, btw.  Even my pass-through keyboard LEDs stop working during the lockup period.

The only thing making me wonder if MW is involved is that the keys stay locked until the screen changes to the full-screen MW logo.  What makes that come up, btw?  Screen saver?

Thanks for the reply and for the great FE.

[Minwah]

The only thing making me wonder if MW is involved is that the keys stay locked until the screen changes to the full-screen MW logo.  What makes that come up, btw?  Screen saver?

I'm not sure which screen you mean...what do you have saver_type set as in your emuname.ini file?

[gap]

I'm not sure which screen you mean...what do you have saver_type set as in your emuname.ini file?

I'll check when I get home, but I haven't changed any screen saver settings, so it should still be set as distributed.

The full-screen I'm seeing is all black with a large centered mamewah logo on two lines.  Kind of like this:
....................
....MAME........
........WAH......
....................

The weird part is that when the controls stop responding, about 30 seconds later this screen appears and the controls start working again.

Hope this helps.

[Minwah]

The full-screen I'm seeing is all black with a large centered mamewah logo on two lines.  Kind of like this:
....................
....MAME........
........WAH......
....................

The weird part is that when the controls stop responding, about 30 seconds later this screen appears and the controls start working again.

It must be the screensaver...it should be set on slide_show by default.  Adjust the 'delay' in mamewah.ini to see for sure...I'm not sure why it is showing the MW logo tho, do your snaps show up in the main screen?

Next time the controls stop working, click your mouse button.  This will return focus to MW if it has lost it (sounds like this might be the case).

[lcddream]

+edit+

moving my prob to a separate thread as it probably isnt a bug.

[headkaze]

MameWah won't allow command line parameters when dealing with .lnk shortcut files. [Adding parameters to the shortcut file by right-clicking and selecting properties, then adding the appropriate switches]

Any chance you fix it so that it will launch them using the entire command line, that way I can use some wrappers and such to launch games.

[Minwah]

MameWah won't allow command line parameters when dealing with .lnk shortcut files. [Adding parameters to the shortcut file by right-clicking and selecting properties, then adding the appropriate switches]

I forget exactly why but I decided to work around this by using the 'commandline_format' setting to supply additional switches etc.  See the thread you recently replied to for more info.

Also (TO ALL): please don't bother replying to this thread any more, it's outdated and so I never really check it.  Any bugs with the latest beta's should be reported in the relevant thread here: http://www.mameworld.info/ubbthreads/postlist.php?Cat=&Board=arcadeospc2jamma

[Mark70]

I think I read somwhere else that "remove game from list" doesn't work on the main game list but works on custom lists, and this is intentional.  It seems to me like a bug.

Additionally, for some reason I have two instances of MAME in my Select Platform List.

[Minwah]

I think I read somwhere else that "remove game from list" doesn't work on the main game list but works on custom lists, and this is intentional.  It seems to me like a bug.

No, it's intentional as the main list is used to build other lists (using filters etc.).

Additionally, for some reason I have two instances of MAME in my Select Platform List.

You probably have multiple mame ini's in the \ini folder then.

PS did you read my last reply?

[papaschtroumpf]

MameWah won't allow command line parameters when dealing with .lnk shortcut files. [Adding parameters to the shortcut file by right-clicking and selecting properties, then adding the appropriate switches]

Any chance you fix it so that it will launch them using the entire command line, that way I can use some wrappers and such to launch games.

I hadn't realized that until I started adding an AHK wrapper to a few new games I got from Reflexive Arcade. The wrapper automatically cancels out ofthe window that stays on the screen for 20s after you exit a Reflexive Arcade game.

The workaround for now is to create a batch file and use a link to the batch file in the game list. The batch file can then call the wrapper with all the options it needs. Note that in some cases the shortcut "workign directory" needs to be the one of the final game, not the one where the batch file is truly ran.


It would be nice not to have to use batch files.

[Minwah]

I hadn't realized that until I started adding an AHK wrapper to a few new games I got from Reflexive Arcade. The wrapper automatically cancels out ofthe window that stays on the screen for 20s after you exit a Reflexive Arcade game.

I've almost no idea what you're talking about! 

The workaround for now is to create a batch file and use a link to the batch file in the game list. The batch file can then call the wrapper with all the options it needs. Note that in some cases the shortcut "workign directory" needs to be the one of the final game, not the one where the batch file is truly ran.

Put the batch file in the same location as the .exe and it shouldn't matter.

It would be nice not to have to use batch files.

As I say I don't really know what you're getting at...sounds like a problem with the game you're using rather than a Mamewah issue.

[papaschtroumpf]

I don't think so.

for example I have  an AHK wrapper for several Reflexive Arcade games.
The program to execute in the windows shortcut properties looks like: (I'm making it up but it's close enough to the real thing)

"c:\ahk\autohotkey.exe" "d:\PC Games\scripts\reflexive.ahk" "d:\Program Files\Feeding Frenzy\FeedingFrenzy.exe"

Basically it calls AHK passes it a script name and the script itself gets passed the name of the game to run and monitor.

When the link (in d:\PC Games) is launched from mamewah, it seems to only see the first part of the command and doesn't start the game, in fct I can't remmeber for sure but I think it doesn't start the script either. If I put the command line in a batch and execute the link to it from mamewah, everything works fine (as long as the execution folder in the shortcut is set to d:\Program Files\Feeding Frenzy)

I'm using XP Pro if it makes a difference.




As far as putting the batch file in the same folder as the game, that works too, but I prefer to have my batch files all in the same spot, it makes backup easy (I don't backup the games themselves, I can always re-isntall if needed). I prefer to modify the shortcut, but your solution works too. Either way I wasn't complaining about that part. In fact, I'm not really complaining at all, I can live with the batch file trick.

[Minwah]

"c:\ahk\autohotkey.exe" "d:\PC Games\scripts\reflexive.ahk" "d:\Program Files\Feeding Frenzy\FeedingFrenzy.exe"

Basically it calls AHK passes it a script name and the script itself gets passed the name of the game to run and monitor.

That makes sense...when Mamewah retrieves the 'Target' using a Windows API, all that is returned is the first filename...any parameters are ignored.  So your assesment of the situation is correct...Mamewah only launches the first part of the target (it is the only info it has).

I thought of using ShellExecute which would launch the shortcut exactly like double-clicking it...but the major drawback with this method is that I cannot wait for the application to quit, which is crucial really.  If anyone can point out how to 'ShellExecute' and wait for the app to finish then I'd be more than happy to add it.

As a workaround you could use game-specific ini files in Mamewah (latest beta's only)...but you might decide your current batch file method is just as easy.

[papaschtroumpf]

I might have to check out your game specific ini feature though. Does it allow you to change some of the {dosbos} and {cursor} flags on a per game basis?

[Minwah]

I might have to check out your game specific ini feature though. Does it allow you to change some of the {dosbos} and {cursor} flags on a per game basis?

Yes

What you would do is this: in your normal pcgames.ini file use the generic 'pc app' setting as follows:

emulator_commandline pc

...this would launch pc apps as you do currently.  For special cases you could use \game\gamename.ini files to specify some alternative launching method, such as:

emulator_commandline c:\ahk\autohotkey.exe "d:\PC Games\scripts\reflexive.ahk" "d:\Program Files\Feeding Frenzy\FeedingFrenzy.exe"

This combined with the {dosbox} etc. flags you mention mean it should hopefully be able to launch just about anything.

[Boz]

Any idea why Mamewah would do this?

I run pacman and it plays just fine. If I quit the game and try to run it again, it flashes a DOS box, then goes away. I've attached the pertinent section of my log file. I am able to duplicate it regularly. If I delete the CFG file for the game in my Mame folder, I can run the game again.

(log entries put into attached text file below so the message board CSS doesn't go crazy)

[Minwah]

This looks very odd:


9/3/2006 10:32:42 PM Commandline run: CMD.EXE /c D:\mame\mame.exe PACMAN -verifyroms > D:\Mamewah\files\verify {flags=17}
9/3/2006 10:32:42 PM Commandline run: D:\mame\mame.exe PACMAN {flags=12}
9/3/2006 10:33:15 PM Commandline run: D:\mame\mame.exe MAMECFG   4

[Boz]

What version of Mame are you using?  I see you are using {autodosbox}...I suggest you try {dosbox} or {nodosbox}.

I thought it might be the very old version of mame I was running (.80) so I finally bit the bullet and got ahold of the very latest version of ROMS and Mame binaries. I haven't tested it out yet, but I will get back to you here when I do.

Incidentally, I poked around a little more and found that if I set the path of game specific CFG files in my Mamewah --> ini --> mame.ini, that's where the problem originated from. If I remove that path from the INI, game specific CFG files are fine and I can run the game multiple times without issue.

Seems to me the <mame folder>\CFG files are being referenced twice in Mamewah giving the crazy commandline launch I posted. I'm probably wrong, but it's something to think about.

I'll let you know what I find out later.

[Minwah]

Incidentally, I poked around a little more and found that if I set the path of game specific CFG files in my Mamewah --> ini --> mame.ini, that's where the problem originated from. If I remove that path from the INI, game specific CFG files are fine and I can run the game multiple times without issue.

Seems to me the <mame folder>\CFG files are being referenced twice in Mamewah giving the crazy commandline launch I posted. I'm probably wrong, but it's something to think about.

Mame's cfg files have nothing to do with Mamewah, and you have no need to point Mamewah to them - so yes this is probably why wierd things are happening.

I guess you are using Mamewah v1.61....if so, you will need to upgrade to the latest Mamewah beta for Mame v0.107+ to work - see my sig for a link.

[icecreamguys]

Not sure what is happening on my end..

MameWah runs great until I exit the program, then the next time I load it up I have no screenshots or preview videos.

When I look at my INI files, they are completely BLANK.

If I restart the computer, the files are restored but to the default settings and not mine.

What am I doing wrong?

v1.62b12, by the way

[Minwah]

Not sure what is happening on my end..

See my reply at MameWorld....

Can someone close this thread?  Seems stupid to post bugs in a 3 year old thread....especially as there is a dedicated thread at MameWorld for b12 bugs.

[Boz]

Yeah, but their forum software BLOWS!!

Does this mean you will no longer support questions and bug reports on BYOAC?

[screaming]

Hey Minwah:

 If you don't want people posting bugs in this MAMEWAH bug list thread then you should probably have Peale take it out of the sticky post at the top....

[Boz]

Hey Minwah:

 If you don't want people posting bugs in this MAMEWAH bug list thread then you should probably have Peale take it out of the sticky post at the top....

He didn't respond to my question so my guess is that he's taken the topic off notify.

[Minwah]

Yeah, but their forum software BLOWS!!

I disagree, when configured it is actually easier than here...it's just the default expanded thread mode that is terrible!

Does this mean you will no longer support questions and bug reports on BYOAC?

No, just would probably be better to start a new thread...

[Minwah]

If you don't want people posting bugs in this MAMEWAH bug list thread then you should probably have Peale take it out of the sticky post at the top....

Good point...I didn't realise it was stickied!

He didn't respond to my question so my guess is that he's taken the topic off notify.

I don't use notify for any threads, I just reply to ones I see.

[advantis]

Hopefully someone knows the answer to this one.

When I load a rom in mamewah, the I get the hour glass and it just clocks.

I need to hit CTRL ALT DEL to get to task manager and manually end task on the ROM  I was trying to play.

Once I do that, then all ROMS load up.

Thoughts?

[Minwah]

When I load a rom in mamewah, the I get the hour glass and it just clocks.

I need to hit CTRL ALT DEL to get to task manager and manually end task on the ROM  I was trying to play.

Once I do that, then all ROMS load up.

Seems strange, but try using {safelaunch} in your emulator_commandline (instead of {nosafelaunch} if that is there).

[advantis]

I will try that tonight