Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: tyweed on March 01, 2003, 10:15:18 pm
-
hello i just installed game launch and i'm trying to get it to launch a game in mame but when i hit 1 to start game it goes to start then brings me back to the list? i'v read all the trouble shooting and it says it might be a path problem but i have everything perfect! i'm using mame32 is this the problem?
please any help would be great
-
put it in debug mode... check the logs (post the logs here)
i sincerly hope that when you say MAME32 you really mean regular windows mame (commandline) and NOT mame32 the gui version.
*Shrug*
Also make sure your mame config is correct i.e. when you launch mame from the command line manually it works fine and doesn't neeed rom paths etc/defined...
good luck,
rampy
-
i had the same problem. for me, it would work in debug mode. Here is what i suggest: check to see if the path you installed glauncher in has a space in it. For example, mine was on my desktop so it was in the "My documents and files" or whatever folder, and that has spaces... would not work. I finally just moved it to c:\glaunch\ and it worked like a charm! Id say give that a try and tell us what happens.
-
That's a good point... It may seem obvious to some (like me) but as gamelauncher was originally a dos app, all directories pretaining to gl should be in the old dos 8.3 format. (max 8 characters per folder name, no spaces, ect...)
-
That's a good point... It may seem obvious to some (like me) but as gamelauncher was originally a dos app, all directories pretaining to gl should be in the old dos 8.3 format. (max 8 characters per folder name, no spaces, ect...)
It has nothing to do with GL being a DOS app. It's just a plain old ordinary bug where spaces are not handled appropriately. There are 2 versions of GL, one is compiled for DOS, the other for Windows, just like MAME. The Windows version has *no* ties to DOS and is a 100% full-fledged Windows app. It even uses Direct X.
-Dave
-
I realise this dave but I'm guessing you created the string parsing back in the dos days and you didn't change it that much over the years. In other words spaces weren't even an issue back then and thus they aren't handled properly.