Main > Software Forum
Forcing resolutions in MAME...
slycrel:
After doing some playing, I found my problem.
It seems that I was doing my mame.ini correctly, the problem has something to do with the way that I have MAMEWAH set up to run mame. my executable is "mamepp.exe". Under the command line, mamepp.exe will use (and expect?) "mamepp.ini". MAMEWAH doesn't seem to do this. However if I use "mame.ini" MAMEWAH will use these settings.
Minwah, any info on why this is? It was a bit frustrating to track down...
Thanks for the help everyone.
Minwah:
--- Quote from: slycrel on July 14, 2004, 02:30:23 am ---
After doing some playing, I found my problem.
It seems that I was doing my mame.ini correctly, the problem has something to do with the way that I have MAMEWAH set up to run mame. my executable is "mamepp.exe". Under the command line, mamepp.exe will use (and expect?) "mamepp.ini". MAMEWAH doesn't seem to do this. However if I use "mame.ini" MAMEWAH will use these settings.
Minwah, any info on why this is? It was a bit frustrating to track down...
Thanks for the help everyone.
--- End quote ---
That doesn't make sense to be honest...MAMEWAH doesn't read/do anything with mame.ini, all it does it launch mame (ie 'mame romname'). MAME itself parses the ini file, based AFAIK on it's exe name.
I decided to give this a try, from a commandline using 'mamex.exe' and found this:
With no ini file, as expected MAME default settings are used,
With mamex.ini present, as expected settings from mamex.ini are used,
With mame.ini present (no mamex.ini), settings from mame.ini are used.
So the last point confirms to some extent what you have found, and does not go with what I said above. Wierd.
All I can think is that MAME has changed so that is uses mameexename.ini if it is present (although you say this doesn't work), or mame.ini if that is present. I'm not sure which would have priority if they are both present*. If this is the case, I'm not sure what version of MAME this happened in, or whether it is intended or a bug. My tests were with MAME v0.84u2 btw.
I still confirm that MAMEWAH does nothing with regards to INI files, it lets MAME do it, so if your 'mamepp.ini' doesn't work, there must be another explanation (tho I don't know what).
Edit: * mameexename.ini has priority over mame.ini when both are present
slycrel:
Yeah, it IS strange. And it's only when using the frontend that the otehr name does not work. I'm wondering if the "new" code for using the mame application name as the .ini file is directory dependant. When I launch mamepp.exe from the commandline, I'm in it's directory. When MAMEWAH is launching my mamepp.exe, I'm guessing that the current directory is the MAMEWAH folder (or whatever mamewah uses underneath). It's possible that there's some really old code in there that looks for "mame.ini" that's been left in, but the "new" way to do it now is to use the application name. I dunno, that's kind of a shot in the dark. Maybe I'll test that some more tonight when I get home. Thanks for checking it out -- glad I'm not crazy. =)
Oh, and for reference, I'm using NoName mame 76 IIRC (From octoberish of last year), though I don't know if it's been in the standard MAME build for that long.
slycrel:
Yeah, it IS strange. And it's only when using the frontend that the otehr name does not work. I'm wondering if the "new" code for using the mame application name as the .ini file is directory dependant. When I launch mamepp.exe from the commandline, I'm in it's directory. When MAMEWAH is launching my mamepp.exe, I'm guessing that the current directory is the MAMEWAH folder (or whatever mamewah uses underneath). It's possible that there's some really old code in there that looks for "mame.ini" that's been left in, but the "new" way to do it now is to use the application name. I dunno, that's kind of a shot in the dark. Maybe I'll test that some more tonight when I get home. Thanks for checking it out -- glad I'm not crazy. =)
Oh, and for reference, I'm using NoName mame 76 IIRC (From octoberish of last year), though I don't know if it's been in the standard MAME build for that long.
Minwah:
--- Quote from: slycrel on July 14, 2004, 01:26:53 pm ---When I launch mamepp.exe from the commandline, I'm in it's directory. When MAMEWAH is launching my mamepp.exe, I'm guessing that the current directory is the MAMEWAH folder (or whatever mamewah uses underneath).
--- End quote ---
Your thinking is right...but MAMEWAH actually changes to the emulators path before launching, for this exact reason...
I really can't explain why your mamepp.ini isn't being used, but I guess if mame.ini does work then use that. I'd be tempted to just rename your mamepp.exe to mame.exe ::)