Game launcher problem

[RoadhawK]

Hi folks, when i launch Game launcher it comes up with the error "could not create logs directory"

I've edited the cfg files to point to mame.exe and that, run mamescan.exe and it still persists.
I also deleted the logs dir to let it create it's own dir but no luck. Any ideas?, running WinXP home if thats any help.

Tia.

[Dave Dribin]

Hi folks, when i launch Game launcher it comes up with the error "could not create logs directory"

I've edited the cfg files to point to mame.exe and that, run mamescan.exe and it still persists.
I also deleted the logs dir to let it create it's own dir but no luck. Any ideas?, running WinXP home if thats any help.

Tia.

I think I've heard of this before.  I don't know what the solution is, since it only occurs on XP and I don't run XP.  Could it be a permissions problem somewhere?  I know zilch about XP/NT/2000, sorry.

-Dave

[RoadhawK]

Ok thanks mate. I'll have a dig around and if i solve it i'll post the solution.

[jets]

Try turning off debug mode? I find the logs useless anyway. Maybe that will solve it. I have been setting it up and its easy to miss a line thats not quite right. I run XP and haven't had this error though...

Note that mamescan is a separte program altogether and has nothing to do with the program while GL is actually running.

[Dave Dribin]

Try turning off debug mode? I find the logs useless anyway. Maybe that will solve it. I have been setting it up and its easy to miss a line thats not quite right. I run XP and haven't had this error though...

Logs are still created even with debug mode off.  The logs aren't meant to be useful to the end user, they're supposed to be useful to me.  Works well if someone is having a problem since I can just say "send me the logs" and I know what that person tried to do.

BTW, maybe using NTFS vs. FAT32 on XP causes issues?  Jets, which one are you using?

Note that mamescan is a separte program altogether and has nothing to do with the program while GL is actually running.

Correct.  Disregard mamescan until you get Game Launcher working.  It's more of an "advanced" configuration option.

-Dave

[jets]

Hey Dave! Great program, thanks.

I am using NTFS w/ XP Pro on both my PCs. Perhaps the game launcher directory is nested too far in a directory tree or a long file named dir is in GL's path. I use XP alot and sometimes stupid errors with all sorts of programs get fixed when I move them into a dir with intentional short names (for folders). DVD2SVCD is one that comes to mind...Since I know you'll be reading this, There are two issues that I have not figured out yet.

a) How do I get rid of the grey border around screenshots?
b) More than 16 emulators won't work with GL. Any way to support more than this? I use mame catergories as each "emulator" but that also means I have no room to add a genesis or snes emu.

[Dave Dribin]

Hey Dave! Great program, thanks.

I am using NTFS w/ XP Pro on both my PCs. Perhaps the game launcher directory is nested too far in a directory tree or a long file named dir is in GL's path. I use XP alot and sometimes stupid errors with all sorts of programs get fixed when I move them into a dir with intentional short names (for folders). DVD2SVCD is one that comes to mind...

Yeah, give that a shot.  Maybe spaces in the full path are an issue, too?

Since I know you'll be reading this, There are two issues that I have not figured out yet.

Well, I don't read this message board that much any more.  For quicker response, post to the Game Launcher mailing list.

a) How do I get rid of the grey border around screenshots?

GL does not add any grey border.  The screen shot must already have the border in it.  Try viewing the screen shot in an image viewer.

b) More than 16 emulators won't work with GL. Any way to support more than this? I use mame catergories as each "emulator" but that also means I have no room to add a genesis or snes emu.

Unfortunately, 16 is the limit in the current version, sorry.

-Dave

[TroyS]

I had the Could not create "logs" directory in glaunch and could find little help so I am replying to this old post to help others. I found that you get this error on XP (and probably win2k) computers if you are running glaunch located on a large NTFS partition (I suspect larger than 8gig). If you move glaunch to a separate partition that is FAT32 or a small NTFS partition under 4 or 5 gig, glaunch works fine.

[Nailz]

Good call replying to 3 different 2 year old posts with the exact same message.....