If you're volunteering on this side of things, I'll be glad to help-- I'm the guy doing the Apple II softlists right now.
Cracks are fine; in a lot of cases, it's all we actually have.
What I'd want to do before you start your project is to split up the C64 softlist like the Apple softlist is-- one list for cleanly cracked (meaning no crack screens, no ripped content-- as pure of a crack as possible), original disks (where possible to image and run those; I'm not sure if C64's in a state where that's possible), and miscellaneous (basically everything else-- rips, cracks with loader screens and modifications to the title screen, etc, and some legitimately important homebrew)
Take a look at how the A2 softlists are set up:
https://github.com/mamedev/mame/blob/master/hash/apple2_flop_clcracked.xml
https://github.com/mamedev/mame/blob/master/hash/apple2_flop_misc.xml
https://github.com/mamedev/mame/blob/master/hash/apple2_flop_orig.xml
That's how I'd want to approach it. Why? Because you're likely to end up with canonical copies of a game or other software package that goes into multiple categories (e.g. on Apple we have cleanly cracked MECC educational disks alongside the original images) and you'll want to separate them while keeping the filename the same so it's clearly identifiable as the same package.
If you have questions, I can be contacted here or on the MAMEdev IRC channels.
---
Try checking the MAME manual at http://docs.mamedev.org
|
Index 
Flat 
Re: The state of C64 support
Reply
