Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: Sephroth57 on December 12, 2004, 07:46:24 pm
-
ok im using the program mamewah setup to help me setup my MAMEWAH, ive done this once before but its been a while and i had to wipe the HD. using mamewah i have ZSNES set up perfect, but cannot get MAME working.
when i start up mamewah it shows my list of games in filename form, even though i have the option to compare to list to show the actual names on. and when i hit P1 start to load a game it says loading, then it goes away and the game never loads.. ideas?
-
MAMEWAH Setup only works with MAMEWAH versions up to 0.97, not sure what version you're using...
If you're using v1.52 (or above), just use the included mame.ini as a start - everything is setup by default for (latest versions of) MAME.
-
i think it is an older version, i havent DLed a new one so i know this one works with MAMEWAH setup. but i will try the new mamewah, which file will have the settings for my ZSNES setup? this way i can get mame working on the new mamewah and then import over my ZSNES settings
-
As you can see by the date of the original thread, I did a search for the problem.
I'm finally REALLY trying to get mamewah going. I can run mame from the winxp command line fine.
I installed mamewah. It found the ROMS and artwork without problem. When I try to start a game, you can briefly see the dos box start with some info (presumably mame looking for the ROMS) but the game doesn't start.
The mame.ini file has the correct directory for the roms. Anybody have any other ideas? I'm sure it's something simple but I'm not familiar enough with Mamewah to figure it out.
I'm using Mamewah 1.6
-
OK, for the sake of others who may have the same problem in the future.
The solution seems to be that Mamewah does not use the mame.ini file to pass the location of the roms to mame. I'm assuming that it only uses the rom location in the ini file to generate the list.
The problem was in the actual mame.ini file (in the mame directory) that had a bad directory for the roms. When I tested command line mame, I just manually entered the rom directory (like I thought that Mamewah would do).
-
The solution seems to be that Mamewah does not use the mame.ini file to pass the location of the roms to mame. I'm assuming that it only uses the rom location in the ini file to generate the list.
You can configure MAMEWAH to send the rompath if you like, but for MAME you don't have to.
Any emulator should be configured correctly whether running it from a FE or not ;)