Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: Rawker on May 09, 2004, 09:00:54 pm
-
i placed a shortcut to mamewah in the startup folder of windows xp and it was working fine however now i get an error:
Runtime error '52':
Bad file name or number
now i can run the shortcut just fine and i don't get the error but when it starts up with windows i get this error. does anyone know what could be causing this error?
-
That's pretty odd. I have MAMEWAH in my startup (XP) and it works fine.
Ideas anyone??
-
I have the same problem. (STILL!!).
I've tried putting the shortcut in to startup, into the registry - everything. Either nothing happens at all, or I get the same error message - running Windows XP.
Mamewah - could you give us an idiots guide tutorial, on how to get this into the startup menu and working? I know its the simplest thing, but maybe we are missing something really obvious..
Cheers
T
-
maybe there is another way to launch it other then through the startup
-
I have the same problem. (STILL!!).
I've tried putting the shortcut in to startup, into the registry - everything. Either nothing happens at all, or I get the same error message - running Windows XP.
Mamewah - could you give us an idiots guide tutorial, on how to get this into the startup menu and working? I know its the simplest thing, but maybe we are missing something really obvious..
One thing I would mention: make sure you do not have multiple instances of MAMEWAH running. This will cause the error you are getting - a common cause of this is having MW in your Startup as well as running it as a shell.
Here's the tutorial:
1) Create shortcut to MAMEWAH on desktop,
2) Drag it into your Start > Programs > Startup folder
;D
-
Minwah, we are talking about the "Mamewah.exe" file here aren't we?
(just checking!).
Ta
-
Minwah, we are talking about the "Mamewah.exe" file here aren't we?
(just checking!).
Yes :)
I wonder if still no joy what would happen if you made a batch file which just launched MAMEWAH, but put this batch file in Startup. I can't see it would make any difference but maybe worth a shot...
-
Er...Batch file.....any chance of another tutorial?!
Thanks
T
-
Batch files: http://www.bluffton.edu/~nesterd/batch-files.html
I have a shortcut to MAMEWAH on my desktop and in the startup folder and I have never seen this error.
Is there a space in the path or file name?
And what version of Windows are you using?
if it doesn't work in the startup directory it won't work starting it from system.ini or the registry.
-
Er...Batch file.....any chance of another tutorial?!
Open notepad,
Type 'C:\MAMEWAH\MAMEWAH.EXE' (well use your MW path),
Save as 'mamewah.bat' somewhere (desktop perhaps),
Put 'mamewah.bat' in Startup* in stead of shortcut to MAMEWAH.EXE.
* you might have to make a shortcut to mamewah.bat to put it in Startup, or it may do it automatically - I can't remember ::)
-
hey aeroflott i figured out my problem, my cabinet is networked with my other computer and get's background music files from it. i changed the directory to one that is local and everything works now but now i have the taskbar pop up every time so i have to push the left mouse button to get rid of it. oh well maybe i'll look into a different front end cause mamewah seems to cause alot of problems for me.
-
hey aeroflott i figured out my problem, my cabinet is networked with my other computer and get's background music files from it. i changed the directory to one that is local and everything works now but now i have the taskbar pop up every time so i have to push the left mouse button to get rid of it. oh well maybe i'll look into a different front end cause mamewah seems to cause alot of problems for me.
That makes sense...I hadn't thought of networking. When you say the taskbar pops up every time what do you mean - every time you start MAMEWAH? If so check you don't have some other app running (in the system tray perhaps) which could be nicking focus from MW...
-
no during startup, not sure how to change the startup order to make mamewah the last one which would correct the problem i think.
-
no during startup, not sure how to change the startup order to make mamewah the last one which would correct the problem i think.
Not sure...if all else fails maybe you could try a batch file (in your Startup) which would run all of your startup programs in order.