Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06289||Interface||Minor||Always||Jul 12, 2016, 00:12||Jul 25, 2016, 19:27|
|Tester||ozfalcon||View Status||Public||Platform||MAME (Self-compiled)|
|Assigned To||Resolution||Open||OS||Linux (32-bit)|
|Version||0.175||Fixed in Version||Build||Normal|
|Summary||06289: mame.ini: mame.ini settings are reset to defaults when saving configuration|
This is a bug to do with ini paths.
I need to clarify some observed behaviours
1. When Saving Configuration - One mame.ini file is stored in the FIRST ini path.
2. When Saving Machine - Multiple game.ini files are stored in the FIRST ini path.
Now on to the bug:
The pre configured mame.ini file is located in the root folder (~/.mame).
When Mame is run, It loads the mame.ini file from the root folder.
However, If the Configuration (mame.ini) is SAVED the following happens.
1. Mame attempts to "Load" the mame.ini from the "ini" path.
2. Because mame.ini is in the root folder (Not the "ini" path) it can not be loaded and Defaults are set.
3. Mame then proceeds to Save the "Defaults" to the mame.ini in the first ini path.
--> Any attempt to run any roms will fail if your rompath is invalid (ie. Default).
--> If you exit Mame, Then restart - Your mame.ini settings are still Default.
(Because Mame will still read the mame.ini file in the "ini" path - OVERRIDING the mame.ini file in the root folder)
|Steps To Reproduce||
0. Set inipath in "~/.mame/mame.ini" to ONLY "ini".
(Just make sure you don't have any mame.ini files in the ini path you test with)
1. Run Mame (Do NOT use the -inipath option as this produces different results).
2. Save the Configuration (mame.ini will be stored in the "ini" path folder).
3. View rompaths or attempt to load a rom.
4. Observe that the configuration has been reset to defaults.
This bug may be related to 06290
|Affected Sets / Systems||mame.ini|
|There are no relationsihp linked to this issue.|
|There are no notes attached to this issue.|