It's not quite as simple as it sounds.
Where do you create the INI? Current folder? How do you handle this without the possibility of dumping INIs all over someone's hard drive by loading from current folder fails? A specific location? What location?
How do you make that platform independent so that it works reasonably AND consistently on Linux, Windows, Android, OS X, and your cousin's toaster while not breaking any existing weird setups users may be using?
---
Try checking the MAME manual at http://docs.mamedev.org
|
Index 
Flat 
Re: Why doesn't MAME Auto-generate a default ini on unpacking?....
Reply
