Hi MAME fans

Thanks for your comments and feedback. To address some questions:

ROM selection currently uses the default (inbuilt) menu. Because this is built (AFAICT) to work like a ROM, the code is fairly opaque to me and when i've tried to make some changes have broken it. Most MAME derivatives ship with a 3rd party frontend. I've looked at a few and it would probably be easy to port one, but most are designed with a large display in mind and show far too much information.

I'll look around again and see if i can find a lightweight one that would be appropriate, but it will probably be a separate installation as i like having MAME a simple, single package.

The problem with associating file types and starting MAME by clicking ROMs is that you'll most likely be using zipped archives and associating the zip type with MAME wouldn't make a lot of sense. You could still probably register MAME as the handler for zip and have it work though, at least in principle.

Compiling MAME requires you to specify NOASM as a parameter so that it uses the miniwork functions instead of the expected ASM helper functions. That's the cause of the errors you see there. The easiest way to build it would be to grab the source package and then copy the debian directory into the new source code from upstream -- and to use dpk-buildpackage so that you are using the configuration defined in the debian packaging.

New upstream version can certainly be released at some point. I haven't started up scratchbox for more than a month so i'll take a look soon.