Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: RedSquirrel on August 31, 2003, 11:52:13 am
-
When I finally get my cab up and running, i would like to run psxe on it. I love mamewah and want to use this as a frontend to all my emulators. Is it possible to use PSXe with mamewah?
-
A quick search would give you the answer :-X ;)
If your to lazy to search read this thread:
http://www.arcadecontrols.org/yabbse/index.php?board=3;action=display;threadid=10196
-
yeah i did do a search, but it all looked complicated - bat files, command lines urghh . ill check your link though
-
Hehe life can be complicated sometimes ;D
Just follow TalkingOctopus instructions, but if you never ever used batchfiles before I can se how its would get confusing and if you have the latest version on MameWah .bat files probably wont work... still its all in that thread, good luck.
-
I have never heard of batch file complications for ePSXe and mamewah. For some reason the zinc + batch files + mamewah causes problems. So make those batches...it really is simple, just annoying.
-
Well for me the problem remains no matter what I try to run via batches, still just make the batches and if it wont run them then you link them ;)
-
Make a new bat file eg. epsxe.bat
then fill the bat file with:
epsxe.exe -nogui -loadbin %1
then in mamewah set this up as your emulator
make you list look for *.bin files and rename all you psx iso exstensions to bin, doesnt matter what format they are.
mamewah will load the command line epsxe.exe -nogui -loadbin %1 replaceing %1 with the game in your list.
Later 8)
-
Waveryder quick question for ya, how have you gotten around the problem with calling psx games via a batch with spaces in them?
I
-
I don't have access to my mamecab right now. :) But, try quotes around the %1. I think this is how I got around that issue.
Waveryder quick question for ya, how have you gotten around the problem with calling psx games via a batch with spaces in them?
I
-
"Waveryder quick question for ya, how have you gotten around the problem with calling psx games via a batch with spaces in them?"
Well in mamewah I just set the emu to not use long file names.
l8r
-
I don't have access to my mamecab right now. :) But, try quotes around the %1. I think this is how I got around that issue.
I did try that but that before but with no joy :( , cheers anyway.
DK passes "ePSXe.cmd d:\emu\psx\isos\Ridge Racer Type4.bin" (without quotes) but the %1 within the cmd file only picks up 'd:\emu\psx\isos\Ridge'.
I suppose I could workaround this by creating a batch file for each game but that seemed messy. :(
-
DK passes "ePSXe.cmd d:\emu\psx\isos\Ridge Racer Type4.bin" (without quotes) but the %1 within the cmd file only picks up 'd:\emu\psx\isos\Ridge'.
Sorry, I'm not 100% sure on DK setup, but it sounds like you need to tell it to send romnames in short (8.3) filename format...
-
I'll try to check my cab tonight and see (might not get a chance since I'm actually mounting the monitor in it tonight!). I'm pretty certain I solved this issue, rather than renaming the files. I might have edited the mamewah EMUxx.CFG file directly. (MAMEWAH's easy enough to use but I'm just an edit the config files directly kind of dude ;).
I don't have access to my mamecab right now. :) But, try quotes around the %1. I think this is how I got around that issue.
I did try that but that before but with no joy :( , cheers anyway.
DK passes "ePSXe.cmd d:\emu\psx\isos\Ridge Racer Type4.bin" (without quotes) but the %1 within the cmd file only picks up 'd:\emu\psx\isos\Ridge'.
I suppose I could workaround this by creating a batch file for each game but that seemed messy. :(
-
I checked how I do it on my machine. I actually have this in the script as the image name argument to epsxe:
"%1 %2 %3 %4 %5 %6 %7 %8 %9"
This works for me. It causes all of the space separated arguments to the script to be collected as a single argument for epsxe. This probably breaks if you have more than one space in a row in an image name or more than 9 words in a filename, but I personally haven't found those restrictions to be unmanageable. ;)
-
I checked how I do it on my machine. I actually have this in the script as the image name argument to epsxe:
"%1 %2 %3 %4 %5 %6 %7 %8 %9"
This works for me. It causes all of the space separated arguments to the script to be collected as a single argument for epsxe. This probably breaks if you have more than one space in a row in an image name or more than 9 words in a filename, but I personally haven't found those restrictions to be unmanageable. ;)
I actually ended up getting it to work like this at the weekend, cheers for the update though. :)