Sprinter/mame
2
0
Fork 0
mirror of https://github.com/holub/mame synced 2025-06-23 04:48:37 +03:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
32,125 Commits 19 Branches 270 Tags 1.7 GiB
C++ 98.1%
C 0.8%
Lua 0.5%
Python 0.2%
Scala 0.1%
77a91f53db
Go to file
briantro 77a91f53db Minor doc updates 
Casanova is listed a game by Promat on a HK government Approved Game list. Also One Shot One Kill is listed as by "Promet" which is a typo of Promat. - NW
2014-11-13 21:32:07 -06:00
artwork HLSL Updates: [Ryan Holtz, Bat Country Entertainment, austere] 2011-06-06 21:25:38 +00:00
docs and what a fine horse it was 2014-10-26 02:00:27 +02:00
hash (MESS) added a few new FM7 tapes, courtesy of Alex Sal who dug 2014-11-12 18:46:47 +01:00
hlsl - Fixed bloom misalignment with HLSL. [MooglyGuy] 2014-04-08 18:34:47 +00:00
keymaps Added Swedish/Finnish SDL keymaps for OSX and Linux. [Curt Coder] 2012-08-29 18:41:01 +00:00
nl_examples Preliminary support for LTE dynamic time-stepping based on Local truncation error. This enables the possibility to connect a capacitor between ground and a TTL output and get a e.g. 100 ns delay with a 1nF capacitor. 2014-05-15 22:50:40 +00:00
src Minor doc updates 2014-11-13 21:32:07 -06:00
web WebUI: clean up and fixed HTML compliance. [Firehawke] 2014-09-29 03:31:14 +00:00
.gitattributes Treat .jed files as binary so they are not converted as text (nw) 2014-10-22 10:48:21 +02:00
.gitignore ignore inp directory (nw) 2014-10-29 18:21:49 +00:00
makefile Build fixes for Emscripten (nw) 2014-11-05 23:12:54 -08:00
README.md Update README.md 2014-11-09 10:32:44 +01:00

README.md

What is MAME?

MAME stands for Multiple Arcade Machine Emulator.

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)?