Enjoy!
- Aaron

But since I am also updating my romset, I thought I would share a little information about how I maintain my romset using the advscan utility. Way back I downloaded a complete romset (I think it was for version 0.70), and ever since, I have been using differential updates (one for each MAME version) and verifying with advscan. Let me explain how I apply one romset update at a time and check for any missing ROMs. Then I will give a few hints on how to fix it if it turns out some roms are bad.

For instance, today I see that the latest version of AdvanceMAME is 0.104, while the latest version of the official MAME is 0.105. Last time I upgraded my romset was for version 0.101, so I need the updates for 0.101 to 0.102, 0.102 to 0.103 and 0.103 to 0.104. I have already downloaded these, but seeing that there is a 0.105 of the official MAME, I might as well start downloading the romset update for that, since this process can take some time. The easiest way of getting the romset updates these days seems to be by P2P filesharing programs. I am not going to write long instructions on how to use different P2P programs, but it should be possible to find the updates. Try to do a search for "mame roms" or something similar.

The romset updates I get are usually packed up in a RAR-archive, so the next step is to unpack this. Updating from version 0.101 to 0.102 I unrar'ed the files (with full path - the x option) to a tmp directory. In some cases the RAR-archive contains the zip-files of the needed ROMs, but most of the time it is just the files (not zipped). Since advscan works with the ZIP-files, I need to make the ROMs into appropriate zip-files. I know there are easier (and more bulletproof) ways of doing this, but here is what I normally do (from the tmp directory where the rom directories are):

$ for f in *;do cd "$f";zip "../../$f.zip" *;cd ..;done

This is bash-script (so you need to be running the bash shell), and BTW the first $ is the prompt, so it should not be typed. If everything works out, you should now have the zips, one per game. Sometimes these are what is found in the romset update. Of course that only makes it easier, since you don't have to zip it yourself. For this update, I now have 50 ZIPs, which should be placed in a directory that is listed under rom_import in advscan.rc.

The other thing that is needed before we can start updating the romset is the information about checksums of all rom files supported by the particular version of mame we are upgrading to. This information is generated by running MAME (or in this case advmame) with the --listxml option (older versions used --listinfo). The size of the generated file is currently arround 25MB, so there are probably not many places where this can be downloaded (although it could most likely be zipped quite well). Also, generating the list from the version of MAME that you intend to run will ensure you have the correct list.

So to get the info, go download the version of MAME you are uprgading your romset to. In this case I downloaded advancemame-0.102.0.tar.gz from a sourceforge mirror. Extract the sources, do a ./configure and a make. This will take a while, so go fetch a cup/glass of your favorite caffeinated beverage.

When the compile is done, run
$ ./advmame --listxml >0.102-romset.xml
and then move the xml-file to somewhere handy (e.g. where you normally run advscan). I like to keep these xml-files arround, so I can go back and check my romset against them. When you have the xml-file you don't need the program anymore (for the romset update anyway).

Of course you will also need advscan. This can be found from the AdvanceMAME site

We are now ready to invoke advscan to update the romset. Make sure all the directories exist and are specified correctly in your advscan.rc:

• rom should specify the directory of the old romset


• rom_new is where to put the new (updated) romset


• rom_import should be where you keep the updates (the zip-files)


• rom_unknown is where to store the old roms (the ones that are removed by the update)

My romset is what is called a differential romset. This means that the files needed to run a clone of a game will be residing in two zips: the parent rom zip , and the clone zip. This takes up less space on the drive, but it makes it a little more complicated if you want to copy a particular game somewhere else, since you need to find out what parent roms might be required. Advscan supports the three different types of romsets, so if you want to use a different type, look at the documentation. The rest of this article will use a differential romset.

Run advscan and pipe in the contents of the xml-file:
$ advscan -Rtv <0.102-romset.xml

After processing, the updated roms should be in the directory you specified as rom_new. Move these files into your rom directory, and you have the updated romset.

Now, we can check the romset. This is also done with advancescan:
$ advscan -rp <0.102-romset.xml >0.102check.txt

Sometimes a rom is reported as missing/corrupt when it is actually not playable anyway. You can limit the check to only report games that should be working:
$ advscan -rp -f working <0.102-romset.xml >0.102check.txt

Afterwards, you can check the file to see if all files are up to date. If some are reported missing, try to find the roms. I will not list where to look, but look arround and you should be able to find them. If you find some roms, put them into the directory listed as rom_import, and run the update again. Then redo the list. In this way it should be possible to get the romset fully updated.

All there is to do now is to do the whole thing once more with the next version. I recommend doing the update step by step, since this will allow you to find out which version of the romset updates a certain game was in, in case there was an error in the rom. Sometimes, however, there is not a version of MAME for each romset update. For instance there is no AdvanceMAME 0.103, so I will have to do both update sets for 0.103 and 0.104 at once.

HOW TO: Make a Bob-clock

Congrats, Mikkel. :)

A friend of mine sent me this link yesterday about an iPod running Linux which, in turn, can now run MAME. I've run iPodLinux on an older iPod for fun, but not one with a color screen worthy of MAME. I suspect my wife would spaz if I did this to her iPod Nano.

Yesterday evening, though, I came across an even more amusing link: an iPod Nano MAME Arcade. This has to be one of the most amusing and creative things I've seen recently.

Enjoy!
- Aaron

After taking the computer out of my cabinet (I have the mother board, harddisk and power supply mounted on a piece of particle board - no PC cabinet), and hooking it up to my monitor, I discovered why the cabinet had taken so long to boot the last couple of times I started it up. Aparently there was a problem with my attempt to make LILO switch between maintenance mode and normal play. This resulted in a 60 sec timeout before the system started booting. This has been reverted back to a 5 sec timeout, until I come up with a better solution (perhaps something involving my new homemade keyboard controller).

When the system finally started up, there were a lot of errors. It turned out that there were errors on the filesystem (crosslinks), so the system was having a hard time even starting up. I assume (and hope) the errors were related to the system not being cleanly shut down (it has crashed on me a couple of times, most likely due to bad AdvanceMAME configuration etc).

After fixing the filesystem and rebooting, only one error appeared, related to some ALSA-library, so I hope this will be fixed by recompiling the ALSA subsystem (after I upgrade the kernel).

Right now I'm waiting for the emerge sync to finish. After that I can upgrade packages.

Then I will upgrade the kernel. The newest kernels support rotating the console on the framebuffer, which I want to experiment a bit with. It would be extremely cool with a readable console on a vertical monitor (avoiding the neck-breaking practice of using it).

/Spiff

To sum up the story of how I ended up writing stuff here, Aaron was kind enough to contact me after we had both posted replies to some questions about using matrox cards on the AdvanceMAME mailing list. At this point (november 2005), we realized that we had a lot in common, both in terms of our MAME cabinets, but also in various other respects.

I think the concept of a blog will be an excellent way to get a little more information about my cabinet written, and especially the ability for people to post comments is one I am looking forward to checking out.

So this category is dedicated to my cabinet SpiffMAME. Hope you find it useful. Drop me a note if you want to know more about it.

My aim is of course to help building a community of people building MAME cabinets, and sharing information about how to setup these beasts, in particular with the more intricate issues concerning configuration of Linux, and making the cabinet look as sleek and "finished" as possible. In my opinion this could be a nice addition to other valuable resources (such as the AdvanceMAME mailing list). So the focus here is on cabinets and some inspiration concerning solutions to various problems that may appear in the process of building and configuring such a cabinet. The mailing list should be reserved for issues related to AdvanceMAME and AdvanceMENU.

I have been discussing several interesting project ideas with Aaron, and hopefully some of them will eventually be realized as time goes by. For now, I will try to make some small blog posts about my cabinet, and see where that takes me (and the site).

First off, I've migrated virtually all of the articles and images from the original site and woven them into the more dynamic structure of a blog. This preserves all of the original information both for historical and reference purposes. I can now expand on that information with new entries that document changes to the original machine and illustrate its evolution.

Since the old site had a more static sidebar that allowed for quick, topical navigation, I've attempted to re-establish that by making a MAME'd Millipede Project Index that links to all of the same articles as before within the new site. The categories on the right sidebar will also take you to any sub-section of the project.

The last entries on the old site - almost two years old - alluded to the beginnings of a second MAME arcade based on a Marble Madness. I've finished that system in recent months but haven't documented the project yet. I wanted to get this new blog in place before doing the new write-up, so I'm pleased to say that will be coming over the next few days now that I've migrated all the old writing. The advances I made in that system led to some fundamental changes to my original machine, so I'll add follow-up pieces to show that upgrade process.

I'll be adding a lot of content to the site as time goes on and probably changing around a few things as I get settled with the new structure. I think the blog format will make adding content a far more fluid process compared to the monolithic, static nature of the previous site. The presence of a comment system also starts to open the door to more reader interaction. Depending on traffic, I might also add a forum system in the near future (though this is somewhat unlikely since there are so many good quality MAME forums already well established).

Finally, I hope to have some co-authors joining me here soon starting with a good friend of mine that lives nearby. Adding his project(s) will make the site more dynamic since we have two very different approaches to cabinet design, button layout and gaming preferences. Hopefully the site can gain some momentum and possibly pick up other authors with various viewpoints over time...

In the meantime, thanks for stopping by and I hope you find what's here useful. If you have any suggestions, spot problems or just have general feedback, don't hesitate to leave a comment or drop me an email.

Just ignore it all for the moment... it'll all make more sense once I'm doing futzing around. :)

- Aaron

Control Panel

Electronics

Software

Parts & Sources