root out remaining mame.ini dependencies

[markwkidd]

As discussed in this mame2003 issue, one priority for libretro MAME cores is to not require the use of mame.ini configuration files in lieu of libretro core options: libretro/mame2003-libretro#27 (comment)

However there may be games that do not function correctly in mame2010 without mame.ini, per: RetroPie/RetroPie-Setup#2268 (comment)

[markwkidd]

@msheehan79 if you have a moment, could you post about your experiences with mame2010 ROM sets that require an .ini file in order to work correctly?

[msheehan79]

@markwkidd The one game I can recall offhand is Operation Thunderbolt.

With this game if mame.ini is not found the mouse input is not recognized. When mame.ini is placed in it's correct directory mouse input works as expected.

[markwkidd]

PR #94 has been merged,, which I hope will at least standardize how mame.ini is handled for now and help avoid crashes for people. If there is no mame.ini in the ini folder, a streamlined version will be generated in that location.

I have changed the title of this Issue to be more precise about the situation: mame.ini should be handled by libretro core options so that it is not needed at all.

---

@msheehan79 if you are in the mood to do more testing, the next thing to try would be to backup/remove your mame.ini and rebuild mame2010 from source. I would be curious if Operation Thunderbolt works for you with the default mame.ini that is generated now.

If not, maybe we can change the boilerplate mame.ini to work -- depending on the what the difference is.

It is recognizing mouse clicks on my system, but I am running Windows 7 x64 with a Thinkpad trackpoint that I haven't bothered to configure right in RA. I couldn't test crosshair movement.

[msheehan79]

@markwkidd I haven't had a ton of time to spend on the pi lately, but when I do have some time to recompile mame2010 from source I can certainly give this a shot.

[markwkidd]

I understand very well. Glad for any feedback when you do get back to it.