diff options
Diffstat (limited to 'docs/source/usingmame')
-rw-r--r-- | docs/source/usingmame/aboutromsets.rst | 4 | ||||
-rw-r--r-- | docs/source/usingmame/commonissues.rst | 2 | ||||
-rw-r--r-- | docs/source/usingmame/frontends.rst | 6 | ||||
-rw-r--r-- | docs/source/usingmame/index.rst | 2 | ||||
-rw-r--r-- | docs/source/usingmame/mamemenus.rst | 2 |
5 files changed, 8 insertions, 8 deletions
diff --git a/docs/source/usingmame/aboutromsets.rst b/docs/source/usingmame/aboutromsets.rst index c27e0f31d12..e7649e6d9a4 100644 --- a/docs/source/usingmame/aboutromsets.rst +++ b/docs/source/usingmame/aboutromsets.rst @@ -36,7 +36,7 @@ MAME is extremely versatile about where ROM data is located and is quite intelli A **non-merged set** is one that contains absolutely everything necessary for a given game to run in one ZIP file. This is ordinarily very space-inefficient, but is a good way to go if you want to have very few sets and want everything self-contained and easy to work with. We do not recommend this for most users. -A **split set** is one where the parent set contains all of the normal data it should, and the clone sets contain *only* what has changed as compared to the parent set. This saves some space, but isn't quite as efficient as +A **split set** is one where the parent set contains all of the normal data it should, and the clone sets contain *only* what has changed as compared to the parent set. This saves some space, but isn't quite as efficient as A **merged set** takes the parent set and one or more clone sets and puts them all inside the parent set's storage. To use the existing Pac-Man example, combining the Puckman, Midway Pac-Man (USA) sets, along with various bootleg versions-- and combining it all into ((PUCKMAN.ZIP**, would be making a merged set. A complete merged set with the parent and all clones is the most common format MAME sets are stored in as it saves the most space. @@ -70,4 +70,4 @@ ROMs and CHDs ROM chip data tends to be relatively small and gets loaded to system memory outright. Some games also used additional storage mediums such as hard drives, CD-ROMs, DVDs, and Laserdiscs. Those storage mediums are, for multiple technical reasons, not well-suited to being stored the same way as ROM data and won't fit completely in memory in some cases. -Thus, a new format was created for these in the CHD file. **Compressed Hunks of Data**, or CHD for short, are designed very specifically around the needs of mass storage media. Some arcade games, consoles, and PCs will require a CHD to run. As CHDs are already compressed, they should **NOT** be stored in a ZIP or 7Z file as you would for ROM images.
\ No newline at end of file +Thus, a new format was created for these in the CHD file. **Compressed Hunks of Data**, or CHD for short, are designed very specifically around the needs of mass storage media. Some arcade games, consoles, and PCs will require a CHD to run. As CHDs are already compressed, they should **NOT** be stored in a ZIP or 7Z file as you would for ROM images. diff --git a/docs/source/usingmame/commonissues.rst b/docs/source/usingmame/commonissues.rst index b47b55aaf31..b2c5e89d6bb 100644 --- a/docs/source/usingmame/commonissues.rst +++ b/docs/source/usingmame/commonissues.rst @@ -11,7 +11,7 @@ Why does my game show an error screen if I insert coins rapidly? This is not a bug in MAME. On original arcade hardware, you simply could not insert coins as fast as you can mashing the button. The only ways you could get credit feeding at that kind of pace was if the coin mech hardware was defective or if you were physically trying to cheat the coin mech. -In either case, the game would display an error for the operator to look into the situation to prevent cheating them out of their hard-earned cash. Keep a slow, coin-insert-ish pace and you'll not trigger this. +In either case, the game would display an error for the operator to look into the situation to prevent cheating them out of their hard-earned cash. Keep a slow, coin-insert-ish pace and you'll not trigger this. Why is my non-official MAME package (e.g. EmuCR build) broken? diff --git a/docs/source/usingmame/frontends.rst b/docs/source/usingmame/frontends.rst index 0a7caccc2a6..88ef7052a65 100644 --- a/docs/source/usingmame/frontends.rst +++ b/docs/source/usingmame/frontends.rst @@ -9,12 +9,12 @@ This following list is not an endorsement of any of these frontends by the MAME | QMC2 (multiple platforms) | Download: http://qmc2.batcom-it.net/ -| +| | IV/Play (Microsoft Windows) | Download: http://www.mameui.info/ -| +| | EmuLoader (Microsoft Windows) | Download: http://emuloader.mameworld.info/ -| +| The MAME team will not provide support for issues with frontends. For support, we suggest contacting the frontend author or trying any of the popular MAME-friendly forums on the internet. diff --git a/docs/source/usingmame/index.rst b/docs/source/usingmame/index.rst index 6f3fd3f61cd..7e85a5bd871 100644 --- a/docs/source/usingmame/index.rst +++ b/docs/source/usingmame/index.rst @@ -13,4 +13,4 @@ This section describes general usage information about MAME. It is intended to c aboutromsets commonissues -
\ No newline at end of file + diff --git a/docs/source/usingmame/mamemenus.rst b/docs/source/usingmame/mamemenus.rst index 7e005a686e6..38e66c81a35 100644 --- a/docs/source/usingmame/mamemenus.rst +++ b/docs/source/usingmame/mamemenus.rst @@ -1,7 +1,7 @@ MAME Menus ========== -If you started MAME without any command line parameters, you'll be shown the game selection menu immediately. While the keys listed above will let you navigate the menus, you can also use a mouse. +If you started MAME without any command line parameters, you'll be shown the game selection menu immediately. While the keys listed above will let you navigate the menus, you can also use a mouse. [todo: This needs SERIOUS expansion. Waiting on answer to a few questions..] |