|Authors:||Nicola Salmoria, MAME Team|
MAME (Multiple Arcade Machine Emulator) is a cross platform multi-system emulator. The philosophy behind the project is to recreate the workings of machines through emulation, and thus the ability to actually play the games is "a nice side effect". MAME is incredibly large, supporting thousands of machines and ROM sets, though what is supported is not what's playable; your mileage may vary. In the event you don't like MAME's own interface, there are many alternative front-ends available.
Much like the name says, MAME was supposed to be for arcade machines like Pac-Man back when it was released in 1997. A similar project called MESS was made to do essentially the same thing for home consoles and other esoteric devices that never got emulated, but it has since been merged into MAME, and now it supports a whole lot more than arcade machines.
- 1 Downloads
- 2 Overview
- 3 How To
- 4 List of Arcade systems emulated
- 5 Frontends
- 6 Versions
- 7 Netplay
- 8 References
MAME was first put out in 1997 by Nicola Salmoria as a Pac-Man emulator, but before he could do any more work on the project, he handed it over to Mirko Buffoni in April 1997 after requiring to do National Service in the Italian army. Since then, even as early as 2003, the emulator has become very extensive, with the majority of arcade system boards from the 1970's, 1980's and early 1990's supported.
However... don't expect support for more recent boards like atomiswave; the project and its team focuses on accuracy (preferably cycle-accuracy) and preservation, which often puts usability at a much lower priority for end users. The program is also very strict about what components of a ROM dump it needs to even function, and it may tell you if something is wrong with the files (i.e. a failed checksum); once developers know more about a system, they'll often have to dump more components like ROMs and BIOSes if necessary, and obtaining newer dumps from the boards isn't exactly the easiest thing in the world for users who only have traditional desktops, and the same goes for anyone with the actual arcade boards. Something as popular as Pac-Man will probably never need newer dumps beyond the current ones because it's been continually researched, and the dumps have been pretty widespread, but other machines you've probably only seen once at an arcade will probably need new dumps for a reason. Only ROM dumps with all the newest information will work in new versions of MAME. Even then, programmers may not have everything implemented. The native interface will tell you about the emulation status of the chosen romset, and whether the one you're using is even emulated at the current time.
MAME either has lots of standardization on how to organize the ROM dumps, or it has very little, and sometimes the given information can be vague and confusing. A single game may need lots of files for the dump to even register, and separate folders for the BIOS files of consoles. For machines that use stuff like hard drives and optical disks to store its data, MAME has a special format called Compressed Hunks of Data (CHD) which uses a number of compression methods to reduce the size of a raw image file.
It is highly recommended to use a ROM management tool such as RomCenter or clrmamepro. Without all the required files and file versions, the game simply will not work.
Convert Bin/Cue files to CHD
Many emulators other than MAME are beginning to support Compressed Hunks of Data, mainly because compared to the alternatives, it offers compression (or better compression) on all fronts. Libretro is making an initiative to support them thanks to a successful bounties initiative, and in many cores such as their Beetle fork, they've begun rolling it out for certain platforms like Saturn and PlayStation so people can test it.
If you're interested in trying this out too, a guide has been provided on how to convert to the format using MAME's very own tool called
chdman. A small warning though; it requires just a small bit of knowledge on how to use the terminal; the developers of MAME seemingly don't have plans to give
chdman an interface so if it scares you too much, you may have to wait.
Install the latest version of MAME. There should be an executable in the main directory called
$ cd (location of folder)
This is optional, but pulling up the manual will give us this information:
$ man chdman (...) createcd -o filename (...) Create a new compressed CD image from a raw file.
Using this, we can type this command in and substitute the placeholder with the name of your ROM.
$ chdman createcd -o "test (!).chd" "test (!).cue"
Recompressing ZIPs to 7-Zip
- Note: If you're confident, you can delete files immediately instead of sending them to the recycle bin or trash bin using the keyboard shortcut
Delete. Always back up the files if you're worried you might do it wrong.
MAME keeps a database of romsets including what each file should be named. If the ROM dump is obtained through a ZIP file, you can uncompress the files inside and transfer them to a 7-Zip file for better compression. The 7-Zip archive HAS to have the exact same name (not the same file extension obviously).
In case you're wondering why 7-Zip is supported in MAME and not RAR, it's because the LZMA development kit that's developed alongside 7-Zip is in the public domain, and the MAME team uses it for CHDs along with FLAC for audio and data compression; RAR is a proprietary format that can only be decompressed by 7-Zip, not compressed to, as per an agreement with both development teams.
|Graphical||Take the zip file:
roms/ (romset).zip/ (game).(rom) (lle1).(rom) (lle2).(rom)
And uncompress it to a folder of the same name.
roms/ (romset).zip/ (game).(rom) (lle1).(rom) (lle2).(rom) (romset)/ (game).(rom) (lle1).(rom) (lle2).(rom)
At this point, you can safely delete the zip file.
Go into the folder, select all the files, and add them to a .7z archive using 7-Zip. Assuming you've installed 7-Zip with the default settings on Windows, the option to do this should come up when you right-click the files. The name of the archive must be the romset's name. The config screen may show an option to "delete files after compression". You can safely select this and, assume you do, the archive will now appear in the folder (unless you've specified a different location):
roms/ (romset)/ (romset).7z
Take the 7-Zip archive, move it into the roms folder, and you can safely delete the romset's folder. It should look like this.
Rinse and repeat for any other romsets you want to do. MAME should be able to read it.
|Terminal||Something like this should work in theory. It has not been tested, so proceed with caution.
7z e (romset).zip -o (romset)/ && 7z a (romset).7z (romset)/*
Just make sure that you've installed 7-zip and it registers to the environment path, that you're in the folder, and that you substitute (romset) for the name of the romset in the command.
List of Arcade systems emulated
- List of arcade games that DON'T work Last updated February 2014. Don't expect most recent games (like Naomi ones) to run at full speed, MAME is very resource intensive.
- NonMAME (2015 Mirror) This is a list of arcade systems that currently are not emulated by MAME or are emulated better by other emulators.
MAME uses many front ends. Please expand this section.
MAME UI 32
MAME UI No longer maintained.
UNOFFICIAL BUILDS MAMEUI x86/x64 unoffical builds
MEWUI is an extension of the internal interface of the MAME / MESS with additional features.
- Display full list of games
- Display snapshot, cabinets, etc... in game selection menu
- Display history, mameinfo in in-game menu
- Options to filter the list of games
QMC2 is a multi-platform MAME/MESS frontend.
A minimal MAME frontend using GTK+ 3 : GitHub.
- Main article: GroovyMAME
It's a fork of MAME made to support arcade CRT monitors
In order to configure your controllers, you need to press TAB once the game is running. Clear every key for Player 1 using "Esc", and only map the directional buttons, and buttons number 1 through 8, which should cover most standard games.
You may also chat in-game by pressing Home twice.
Also, you have to restart the emulator EVERY TIME you load a new game, or attempt to restart the current one. Else, you'll get a black screen.