Grab the latest update from the Latest Updates page!
MAME is a multi-purpose emulation framework.
MAME's purpose is to preserve decades of software history. As electronic technology continues to rush forward, MAME prevents this important "vintage" software from being lost and forgotten. This is achieved by documenting the hardware and how it functions. The source code to MAME serves as this documentation. The fact that the software is usable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully?). Over time, MAME (originally stood for Multiple Arcade Machine Emulator) absorbed the sister-project MESS (Multi Emulator Super System), so MAME now documents a wide variety of (mostly vintage) computers, video game consoles and calculators, in addition to the arcade video games that were its initial focus.
The first update of the MAME 0.127 development cycle is now available. Please make note of the fact that the cheat engine is under serious construction right now and has been disabled.
At last, it is time for a full MAME update: grab MAME 0.126 from the Latest Release page.
In addition to the usual large pile of changes and improvements, there
are several big changes come along with this release that you should be
Just posted over at the Source Updates page is hopefully the final update to the MAME 0.125 dev cycle. It's been a long road! Now is the time to check this out and ensure that all your favorites are still in fine working order before we lock down for MAME 0.126.
Time for the weekly MAME update: get MAME 0.125u7 over at the Source Updates page. I anticipate a u8 next week followed shortly thereafter with MAME 0.126, so now would be a great time to verify that there are no showstoppers in any games you care about!
An important note about this release: inclusion of debugging support in MAME is no longer optional. That is, you can still disable it (using the -nodebug option, or setting 'debug' to 0 in your mame.ini file), but you can no longer compile without it. This will give a small-ish performance hit (under 5% in most cases) in exchange for always being able to pull up the debugger and will reduce the test matrix necessary to verify MAME's behavior.
Note that due to a slight oversight, the debugger is enabled by default in this build, so you may need to explicitly turn it off. This will default to off in u8.
The latest in the now long-running series of updates to MAME 0.125 is now available. There will likely be at least two more intermediate updates before 0.126, due to the large number of changes in the dynamic recompilers and elsewhere in the system. So hang in there and please give these updates a try to ensure that everything still works as expected. As usual, report your bugs over at MAMETesters.