| Main > Software Forum |
| Getting INI file to load within MameWah |
| << < (2/4) > >> |
| dax:
MameWah is really a mysterious, strange thing, kind of like Bigfoot. Some people have apparently seen it [work] and others think it's just a myth [that it can be properly configured]. I'm still waiting for my bigfoot sighting. I have Mame 0.69 DOS working perfectly now. I have Mame32 .102 working perfectly now. I have ArcadeOS running rock solid using 0.69. HOWEVER, running MameWah with 102 just does not work, and I've gone over the configs tons of times. I've started doing my own debugging traces to figure out what is going on and what weird things MameWah does. From what I can see, there isn't a command line parameter to tell Mame (102) where to look for the mame.ini file, and I am not sure what is the default path when MameWah spawns Mame.exe so I move the mame.ini file all around trying to find where it can be located so that when Mamewah spawns mame, it will be findable (if Mamewah is not in the same directory as Mame.exe, it sure doesn't seem to look by default where the executable mame.exe is located). In one configuration I could get it to find the .ini file HOWEVER MameWah shows every game in the same 800x600 resolution. Every other instance and version of Mame works perfectly... except Mamewah and I have no idea why or how MameWah is causing Mame to ignore all the resolution and configuration information. Very frustrating. |
| brophog:
Dax, trust us on this one. STOP USING MAME32 WITH MAMEWAH. :police: |
| 2600:
--- Quote from: dax on January 04, 2006, 01:30:08 pm ---MameWah is really a mysterious, strange thing, kind of like Bigfoot. Some people have apparently seen it [work] and others think it's just a myth [that it can be properly configured]. I'm still waiting for my bigfoot sighting. From what I can see, there isn't a command line parameter to tell Mame (102) where to look for the mame.ini file, and I am not sure what is the default path when MameWah spawns Mame.exe so I move the mame.ini file all around trying to find where it can be located so that when Mamewah spawns mame, it will be findable (if Mamewah is not in the same directory as Mame.exe, it sure doesn't seem to look by default where the executable mame.exe is located). In one configuration I could get it to find the .ini file HOWEVER MameWah shows every game in the same 800x600 resolution. Every other instance and version of Mame works perfectly... except Mamewah and I have no idea why or how MameWah is causing Mame to ignore all the resolution and configuration information. Very frustrating. --- End quote --- I think your frustration lies with MAME not MAMEWAH. MAME has it's own mame.ini file. Have you created this file and put all your settings FOR MAME in it? I'd suggest you read the folowing after you read the documentation: http://www.mameworld.net/easyemu/ specifically http://www.mameworld.net/easyemu/mameguide/mameconfig.htm BTW, I'd stop spewing theories and badmouthing things you don't know or assume. |
| dax:
--- Quote from: brophog on January 04, 2006, 01:39:02 pm ---Dax, trust us on this one. STOP USING MAME32 WITH MAMEWAH. :police: --- End quote --- Excuse me? I am using the command line version of mame with Mamewah. I think I can tell the difference. Mame32 is 32MB in size. Command line version if 8MB. These were separate downloads. How could I possibly be using Mame32 from Mamewah? |
| brophog:
--- Quote ---I have Mame 0.69 DOS working perfectly now. I have Mame32 .102 working perfectly now. I have ArcadeOS running rock solid using 0.69. HOWEVER, running MameWah with 102 just does not work, --- End quote --- My mistake then. From that quote it wasn't clear that you were using commandline with mamewah. |
| Navigation |
| Message Index |
| Next page |
| Previous page |