The NEW Build Your Own Arcade Controls
Main => Software Forum => Topic started by: Banacek on October 20, 2006, 10:05:30 pm
-
Hey, I'm getting a run time error when I try to run j5. The actual error is "Run Time Error'53': File not found." I wish I knew what file it was looking for. Also "-debug" doesn't work. I get the windows error sound and that's it. Sorry if this is an easy fix, I did a search and couldn't find anything. I have DirectX and VB6 run time files installed, I believe it was SP5. Thanks!
-
bump, still trying to figure this out. Works on my pc, and not on my cab...
-
Well, I solved the issue. I had ctrlr under INPUT DEVICE OPTIONS set in mame.ini to my ctrlr file. If I comment it out johnny5 works fine. So what's the proper way to configure mame and johnny5 so I can use my ctrlr file?
-
plrobably a syntax erron on your part.... for example, the ctrlr setting isn't "c:\mame\hotrod.cfg" it is simply "hotrod" and mame fills in the rest. Also you ctrlr path must be accurate as well as the ctrlr name.
-
plrobably a syntax erron on your part.... for example, the ctrlr setting isn't "c:\mame\hotrod.cfg" it is simply "hotrod" and mame fills in the rest. Also you ctrlr path must be accurate as well as the ctrlr name.
my cfg file is called "mycontrols.cfg", located at e:\mame\ctrlr. In the input box for johnny5 all I have is "mycontrols". Here's my mame.ini:
#
# CONFIGURATION OPTIONS
#
readconfig 1
skip_gameinfo 0
#
# PATH AND DIRECTORY OPTIONS
#
rompath e:\roms
samplepath e:\extras\samples
inipath .;ini
cfg_directory cfg
nvram_directory nvram
memcard_directory memcard
input_directory inp
hiscore_directory hi
state_directory sta
artpath e:\extras\e:\extras\artwork
snapshot_directory e:\extras\snap
diff_directory diff
ctrlrpath e:\mame\ctrlr
comment_directory comments
cheat_file cheat.dat
#
# MISC OPTIONS
#
bios default
cheat 0
#
# STATE/PLAYBACK OPTIONS
#
# state <NULL> (not set)
autosave 0
# playback <NULL> (not set)
# record <NULL> (not set)
# mngwrite <NULL> (not set)
# wavwrite <NULL> (not set)
#
# DEBUGGING OPTIONS
#
log 0
oslog 0
verbose 0
#
# PERFORMANCE OPTIONS
#
autoframeskip 0
frameskip 0
frames_to_run 0
throttle 1
sleep 1
rdtsc 0
priority 0
#
# VIDEO OPTIONS
#
video d3d
numscreens 1
window 0
maximize 1
keepaspect 1
prescale 1
effect none
pause_brightness 0.65
waitvsync 0
syncrefresh 0
#
# VIDEO ROTATION OPTIONS
#
rotate 1
ror 0
rol 0
autoror 0
autorol 0
flipx 0
flipy 0
#
# DIRECTDRAW-SPECIFIC OPTIONS
#
hwstretch 1
#
# DIRECT3D-SPECIFIC OPTIONS
#
d3dversion 9
filter 1
#
# PER-WINDOW VIDEO OPTIONS
#
screen0 auto
aspect0 auto
resolution0 auto
view0 auto
screen1 auto
aspect1 auto
resolution1 auto
view1 auto
screen2 auto
aspect2 auto
resolution2 auto
view2 auto
screen3 auto
aspect3 auto
resolution3 auto
view3 auto
#
# FULL SCREEN OPTIONS
#
triplebuffer 0
switchres 0
full_screen_brightness 1.0
full_screen_contrast 1.0
full_screen_gamma 1.0
#
# GAME SCREEN OPTIONS
#
brightness 1.0
contrast 1.0
gamma 1.0
#
# VECTOR RENDERING OPTIONS
#
antialias 1
beam 1.0
flicker 0
#
# ARTWORK OPTIONS
#
artwork 1
artwork_crop 0
use_backdrops 1
use_overlays 1
use_bezels 1
#
# SOUND OPTIONS
#
sound 1
samplerate 48000
samples 1
volume 0
audio_latency 1
#
# INPUT DEVICE OPTIONS
#
ctrlr mycontrols
mouse 1
joystick 0
lightgun 0
dual_lightgun 0
offscreen_reload 0
steadykey 0
a2d_deadzone 0.3
digital none
#
# AUTOMATIC DEVICE SELECTION OPTIONS
#
paddle_device keyboard
adstick_device keyboard
pedal_device keyboard
dial_device keyboard
trackball_device keyboard
lightgun_device keyboard
#
# OUTPUT DEVICE OPTIONS
#
keyboard_leds 1
led_mode ps/2
Now running "-verbose" shows that Mame finds and uses the mycontrols.cfg file. With this mame.ini Johnny5 won't run. I have to put a # in front of the ctrlr line for johnny5 to start, but then it doesn't load the mycontrols.cfg file. Where did I go wrong?
-
On a lark I put mycontrols.cfg in the mame directory "e:\mame" and it works now. Weird.
-
e:\mame\ctrlr should just be ctrlr
-
e:\mame\ctrlr should just be ctrlr
Changed it, but it still doesn't work without the file in the e:\mame dir. No big deal for me, since it's working. It just seems odd that it doesn't work the normal way.