Main > Software Forum
Forcing resolutions in MAME...
slycrel:
BLEH.
I looked at the MAME source today on my break at work. Barring some wierdness with NoName MAME as opposed to the standard MAME that's out there now, this is just wierd.
(See cli_frontend_init() in src\windows\config.c of the MAME source for the code)
It looks like the MAME code does the following:
- gets the application name that it's running from
- removes any dot extension that it has
- adds the .ini extension
- interestingly, at this point it will load all the settings from "mame.ini" if it exists.
- Loads the mameexename.ini as built above
I've got to say I'm stumped on this one. Unless the name parsing code has a bug in it that's not immediately obvious.
The good news is that I'm very happy to see the MAME code as clean and readable as it is. I suppose I've become jaded because of a few other open source codebases I've looked at that have been a mess. Maybe I'll have to do some checking into Howard's problem/idea. ;)
I'll still play around with it a bit tonight and let you know if there are any other things I find. Thanks again.
slycrel:
Uh, nevermind, I'm a moron.
;D
I was using "noname32.exe" in MAMEWAH. renaming the .ini file to this name took care of the problem.
At least I learned a bit about the source in the process. Color me embarassed. :)
Minwah:
--- Quote from: slycrel on July 15, 2004, 01:47:12 am --- Uh, nevermind, I'm a moron.
;D
I was using "noname32.exe" in MAMEWAH. renaming the .ini file to this name took care of the problem.
At least I learned a bit about the source in the process. Color me embarassed. :)
--- End quote ---
Oh well glad you found an explanation :)
Interesting to confirm also that mame.ini is read regardless of the exe name...