a9b8065a5c
to mount the BASIC cart to be loaded, of course). [Fabio Priuli] out of whatsnew: I also set the default tape state to CASSETTE_STOP, because the APF Imagination requires you to immediately press Return after the CLOAD + Press Play sequence. With current CASSETTE_PLAY default, the tape was starting immediately after the first Return press (the one for CLOAD) and I often had the second Return input being ignored by the system, with the result that the tape was not loaded correctly... Having to press play separately seems to give the system enough time to recover from the first Return and being ready to accept a second one ;) |
||
|---|---|---|
| artwork | ||
| docs | ||
| hash | ||
| hlsl | ||
| keymaps | ||
| nl_examples | ||
| src | ||
| web | ||
| .gitattributes | ||
| .gitignore | ||
| makefile | ||
| README.md | ||
What is MAME?
MAME stands for Multiple Arcade Machine Emulator. When used in conjunction with an arcade game's data files (ROMs, CHDs, samples, etc.), MAME attempts to reproduce that game as faithfully as possible on a more modern general-purpose system. MAME can currently emulate many thousands of classic arcade video games from the the very earliest CPU-based systems to much more modern 3D platforms.
The ROM and CHD images that MAME requires are "dumped" from arcade games' original circuit-board ROM chips, hard disks, and CD-ROMs. MAME becomes the "hardware" for the games, taking the place of their original CPUs and support chips. Therefore, these games are NOT ports or rewrites, but the actual, original games that appeared in arcades, complete with all the bugs, glitches, slowdowns, and subtleties of the original game as it appeared in the arcade.
MAME's purpose is to preserve these decades of video-game history. As gaming technology continues to rush forward, MAME prevents these important "vintage" games 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 games are playable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully)?