The problem here being that an INI solution isn't feasible for console stuff with 30,000 different filenames-- doing CRC/MD5/etc isn't feasible for that sort of thing simply because it would drop a frontend to an utter crawl on any updating.
If it were JUST MAME, an INI is fine. Console? No way.
That's why I said "user specified"-- everyone's going to have their own filenames in the end. I bet if I said here, "Let's mandate GoodXXXX filenames!" I'd get at _LEAST_ ten responses telling me to go to hell within ten minutes. That's not even taking into account all the debates over the existing databases for this sort of material. TOSEC, GoodXXXX, they all have points people argue over.
---
Try checking the MAME manual at http://docs.mamedev.org
Edited by Firehawke (10/29/10 01:26 AM)
|