and it will change the mame.ini in the /ini directory to read just that, eliminating all the presets.

With no mame.ini in the /ini directory, MAMEUI reads the mame.ini in the root directory, and the ini path is set to ini/presets. It then puts mame.ini in the presets directory.

My solution so far is to have a mame.ini file in the ini directory, along with copies of all the presets. MAMEUI seems to be able to handle this.

If anyone is still maintaining the code, however, it might be better to allow MAMEUI to accept multiple inipath variables, and know to drop its .ini changes into the /ini directory, or perhaps the first directory in the list: no reason the variable can't be set to -

Code:

inipath ini;.;ini/presets

In any event, the code may need an update. The current workaround is to have a mame.ini in the /ini directory that sets inipath to just ini, and one in the root directory that sets the multiple paths for vanilla MAME.

(MAMEUI fortunately handles diff ini's just fine. I have a couple of games where the only line is HLSL_enable 0, and MAMEUI reads it just fine.)