game launcher help!!

[tyweed]

Hello i'm having alot of trouble with the initial config of mame in glaunch. i have set everything up correct in mame.cfg as far as i can tell? i have it in debug mode and it is showing when it tries to execute this

mame.exe .gaunt2

 it's putting a period infront of the rom command and i think that is the problem but i cannot get rid of it?

please if anyone has any ideas help!!!

[romid]

in your mame.cfg file (inside the config directory of glaunch):

make sure you have the following set to "no":

# Use rom_directory when launcher game: "yes" or "no"
#  i.e. yes: "emulator.exe c:\full\path\rom"
#        no: "emulator.exe rom"
use_rom_directory = no



that should do the trick

[tyweed]

This is what i have.


directory- c:\mame065b\

exutable- mame.exe

use_rom_file - yes

use rom directry when launching - no

use ext when launching- no

list of possible ext - zip bin

dir to roms - c:\mame065b\roms\

options before rom - yes

i think i have everything right? if someone can send me there mame.cfg file that be great!

[Odonadon]

Hello i'm having alot of trouble with the initial config of mame in glaunch. i have set everything up correct in mame.cfg as far as i can tell? i have it in debug mode and it is showing when it tries to execute this

mame.exe .gaunt2

 it's putting a period infront of the rom command and i think that is the problem but i cannot get rid of it?

please if anyone has any ideas help!!!

I had the same problem when trying out Fastmame.  All I did was change the directory from "c:\mame" to "c:\fastmame" and the executable from "mame.exe" to "fastmame.exe".  And now it's throwing a "." in front of the ROM name.  I change the directories back, and it works perfect.  Change it back to fastmame, and it does that again.  Doesn't make any sense.  At all.  Has to be a glitch with Game Launcher.  All I did was rename everything "mame" to "fastmame" in the cfg file.

Odonadon

[tyweed]

i fixed mine by going to use_rom_ext-no

[romid]

You should try removing the trailing \'s

for example, change your "directory- c:\mame065b\" to "directory- c:\mame065b"

Also, when you do figure it out, be sure to post what it was so that we will know when/if other people ask

heres mine if it helps:

# Emulator name, i.e. MAME
name = MAME

# Short description of emulator, i.e. Arcade Machines
description = Arcade Games

# Location of emulator, i.e. c:\mame
directory = c:\mame

# Name of emulator executable, i.e. mame.exe
executable = mame.exe

# Global options passed to emulator, i.e. -sound 1
global_options = -skip_gameinfo -resolution 800x600 -hws

# Command to run before running executable. If blank, then nothing
# will be run.
pre_command =

# Command to run after running executable.  If blank, then nothing
# will be run.
post_command =

# Name of map file.  A map file maps short ROM file names to full game
# names.
map_file = mame.map

# Options go before ROM when launching: "yes" or "no".
#  i.e. yes: "emulator.exe -option1 -option2 rom"
#        no: "emulator.exe rom -option1 -option2"
options_before_rom = no

# Directory to look for screen shot images, i.e. c:\mame\snap
# Supported formats are PCX, PNG, and BMP.
screen_shot_directory = mame\snap

# A ROM file is a list of ROMs to use.  If set to "no", ROMs are
# scanned for in the rom_directory.  If set to "yes" a ROM file (which
# is essentially just a list of ROMs) is used instead of trying scan.
# The default is "no".  ROM files are useful for merged ROMs with
# MAME, where the actual ROM names are buried within a ZIP file.
use_rom_file = yes

# rom_dir, rom_extension, use_extension, and use_rom_directory are
# only relevant if a ROM file is not used.  They are ignored if not
# needed.

# Directory to ROMs
rom_directory = c:\mame\roms

# List of possible ROM extensions (without the ".")
rom_extension =

# Use extension when launching game: "yes" or "no"
#  i.e. yes: "emulator.exe rom.ext"
#        no: "emulator.exe rom"
use_extension = no

# Use rom_directory when launcher game: "yes" or "no"
#  i.e. yes: "emulator.exe c:\full\path\rom"
#        no: "emulator.exe rom"
use_rom_directory = no

[Distortion]

I had the exact same problem.  I still have the exact same problem.  That's why I'm using ArcadeFX.  I'd rather use GameLauncher, though.  I played around with every setting possible and got no good results.

[Odonadon]

I had the exact same problem.  I still have the exact same problem.  That's why I'm using ArcadeFX.  I'd rather use GameLauncher, though.  I played around with every setting possible and got no good results.

Exactly, same here.  Can't seem to fix the problems.  It doesn't make any sense - the only thing I changed was directory and the name of the exe file.  I'll play around with it this week and let y'all know if I find something that works.

Odonadon

[Howard_Casto]

You should try removing the trailing \'s

for example, change your "directory- c:\mame065b\" to "directory- c:\mame065b"

Actually unless Dave has changed things again you should do the opposite and fill in any trailing backslashes.  

[Distortion]

I've managed to get rid of the . before the games, but I have another problem.  The batch file seems to be coming out perfect, I run the batch file afterward and it opens the game just fine, but somehow the process crashes and the batch file is never launched.

[Odonadon]

I've managed to get rid of the . before the games, but I have another problem.  The batch file seems to be coming out perfect, I run the batch file afterward and it opens the game just fine, but somehow the process crashes and the batch file is never launched.

Care to share how you got rid of the . ?  

Wow, that's lots of punctuation...

Odonadon

[Distortion]

I don't remember, but it's not doing it any more.  I switched to MameWah.  It's working great for me, so I won't complain.

[Odonadon]

Well, here's what I did:

I told mame.cfg to use full ROM path.  That didn't work:  I had my ROM files stored in c:\mame\roms\ and wanted to use fastmame from c:\fastmame\.  c:\mame\roms being the ROM path.  Kept getting the "." before ROM name.  Makes sense.

SO, I moved the ROMs to c:\fastmame\roms from c:\mame\roms, ran mamescan to make sure all was fine - problem solved .  Good ol' Game Launcher.  Works like a charm.

NOT!  

And yet I continue to use it due to lack of a better product.  Weird how that works...

Odonadon