> MAME by default has the INI string set as ".;ini;ini/presets". It doesn't matter the > platform. That means it will look for current directory first (".\source\" included), > then ".\ini\", then ".\ini\presets". When no ini, of course it will look for the best > available. And it looks like the best available was "source\" because is near the > executable root.
Well, in Linux platform the default is '$HOME/.mame;.;ini', that means it will look first at '$HOME/.mame' or '/home/username/.mame', working directory '.' (where the executable is located), then the 'ini' folder, there is no 'ini/presets' for Linux. If we would translate that to Windows environment we use the %HOME% variable like '%HOME%\mame;.;ini;ini/presets'.
>If you want to avoid these kind of troubles I suggest you to avoid > configuration collisions and pay more attention to the verbose command.
This configuration conflict are expected according to mame own documentation: https://docs.mamedev.org/advanced/multiconfig.html
What ever setting I put in those files, it will be in a direct conflict with the defaults in 'mame.ini', like setting a lower audio sample rate for an old computers that don't need 48 kHz.
This should not be a trouble, the documentation show one thing, when you do it for real it fails, mame didn't stack the settings as it should, it just ignores it. The verbose command didn't help at all, what helped me to understand what was wrong was an app called GLSOF that is a similar tool like Windows filemon.
|