summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorGravatarGravatar Miodrag Milanović <mmicko@gmail.com>2014-10-20 18:55:13 +0200
committerGravatarGravatar Miodrag Milanović <mmicko@gmail.com>2014-10-20 18:55:13 +0200
commitddbeb7b0e43ea2d158ee4980e16efe8c02e4c836 (patch) (github)
tree1ed1c51bb7f199eb185da3e51e28712f673ad8f8 /README.md
parent327c83d2bc017650e08fc291d1b830b9097e9783 (diff)
downloadmame-ddbeb7b0e43ea2d158ee4980e16efe8c02e4c836.tar.bz2
mame-ddbeb7b0e43ea2d158ee4980e16efe8c02e4c836.zip
Update README.md
Added some breaks
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md
index 095de76a0df..e880abff152 100644
--- a/README.md
+++ b/README.md
@@ -2,5 +2,7 @@ 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)?