| Main > Software Forum |
| Mame weirdness |
| << < (2/4) > >> |
| jcrouse:
--- Quote from: Brad on February 28, 2006, 10:35:23 pm --- Take this with a grain of salt. --- End quote --- Sodium is very bad for you. John |
| Brad:
Apparently it hardens your arteries but I prefer to believe it's excessive Ms Pacman ;D Brad |
| jcrouse:
Ms. Pacman makes my artery hard. :) John |
| Brad:
you too! :o Damn hussy! Brad |
| dax:
--- Quote from: jcrouse on February 28, 2006, 10:17:51 pm ---The front end has NOTHING to do with the resolution of games running in Mame. It is controlled globally in the mame.ini file and on an per game basis (for exceptions) on a gamename.ini file placed in the mame\ini folder. --- End quote --- Well, depending upon your perspective, you could be wrong John. If the FE, for example, doesn't CHDIR prior to invoking a shell to call Mame, then it could indeed confuse Mame so that the program cannot find the ini files or directories. I am suspecting this could be a problem and will be experimenting with different settings. Still I would expect some people here to be more familiar with Mame than myself and know for sure what could be causing this. The situation is simple: I can type MAME (gamename) from within c:\mame and the game launches and displays in the proper resolution. I configure MameWah or AtomicFE with the same details regarding program and rom locations, but for the same game, being invoked from within the front end program, the resolution is off. The ini file is where it should be, specifying the proper resolution but for some reason, it isn't read or is ignored. It seems like a simple issue, but nobody seems to have concrete answers as to why/how this is happening and there seems to be many people having this problem. |
| Navigation |
| Message Index |
| Next page |
| Previous page |