summaryrefslogtreecommitdiffstatshomepage
path: root/docs
diff options
context:
space:
mode:
author Firehawke <firehawke@gmail.com>2016-10-29 23:32:36 -0700
committer Firehawke <firehawke@gmail.com>2016-10-29 23:32:36 -0700
commitce943bd45b06b3af9d0125c8ce6d1da8b0b6a0d2 (patch)
tree472446230fefcdd487f7562460be77f39a6dfa48 /docs
parent4cfffd8b336bdee7da125d2547bd177212d6913c (diff)
NW - More documentation updates..
* Fix a few 'mess' references. * Add important note for -listslots * FAQ: Wouldn't MAME be faster if X?
Diffstat (limited to 'docs')
-rw-r--r--docs/source/commandline/commandline-all.rst8
-rw-r--r--docs/source/usingmame/commonissues.rst18
2 files changed, 22 insertions, 4 deletions
diff --git a/docs/source/commandline/commandline-all.rst b/docs/source/commandline/commandline-all.rst
index c15a98259a4..e10d4769025 100644
--- a/docs/source/commandline/commandline-all.rst
+++ b/docs/source/commandline/commandline-all.rst
@@ -113,7 +113,9 @@ Note: By default, all the '**-list**' commands below write info to the screen. I
**-listslots** [<*gamename|wildcard*>]
- Show available slots and options for each slot (if available). Primarily used for MESS to allow control over internal plug-in cards, much like PCs needing video, sound and other expansion cards.
+ Show available slots and options for each slot (if available). Primarily used for MAME to allow control over internal plug-in cards, much like PCs needing video, sound and other expansion cards.
+
+ The slot name (e.g. **ctrl1**) can be used from the command line (**-ctrl1** in this case)
**-listmedia** / **-lm** [<*gamename|wildcard*>]
@@ -365,7 +367,7 @@ Core state/playback options
In addition to the above, for drivers using different media, like carts or floppy disks, you can also use the %d_[media] indicator. Replace [media] with the media switch you want to use.
- A few examples: if you use 'mame robby -snapname foo/%g%i' snapshots will be saved as 'snaps\\foo\\robby0000.png' , 'snaps\\foo\\robby0001.png' and so on; if you use 'mess nes -cart robby -snapname %g/%d_cart' snapshots will be saved as 'snaps\\nes\\robby.png' ; if you use 'mess c64 -flop1 robby -snapname %g/%d_flop1/%i' snapshots will be saved as 'snaps\\c64\\robby\\0000.png'.
+ A few examples: if you use 'mame robby -snapname foo/%g%i' snapshots will be saved as 'snaps\\foo\\robby0000.png' , 'snaps\\foo\\robby0001.png' and so on; if you use 'mame nes -cart robby -snapname %g/%d_cart' snapshots will be saved as 'snaps\\nes\\robby.png' ; if you use 'mame c64 -flop1 robby -snapname %g/%d_flop1/%i' snapshots will be saved as 'snaps\\c64\\robby\\0000.png'.
**-snapsize** *<width>x<height>*
@@ -391,7 +393,7 @@ Core state/playback options
In addition to the above, for drivers using different media, like carts or floppy disks, you can also use the %d_[media] indicator. Replace [media] with the media switch you want to use.
- A few examples: if you use 'mame robby -statename foo/%g' save states will be stored inside 'sta\\foo\\robby\\' ; if you use 'mess nes -cart robby -statename %g/%d_cart' save states will be stored inside 'sta\\nes\\robby\\' ; if you use 'mess c64 -flop1 robby -statename %g/%d_flop1' save states will be stored inside 'sta\\c64\\robby\\'.
+ A few examples: if you use 'mame robby -statename foo/%g' save states will be stored inside 'sta\\foo\\robby\\' ; if you use 'mame nes -cart robby -statename %g/%d_cart' save states will be stored inside 'sta\\nes\\robby\\' ; if you use 'mame c64 -flop1 robby -statename %g/%d_flop1' save states will be stored inside 'sta\\c64\\robby\\'.
**-[no]burnin**
diff --git a/docs/source/usingmame/commonissues.rst b/docs/source/usingmame/commonissues.rst
index 110c97f524a..b47b55aaf31 100644
--- a/docs/source/usingmame/commonissues.rst
+++ b/docs/source/usingmame/commonissues.rst
@@ -13,6 +13,7 @@ This is not a bug in MAME. On original arcade hardware, you simply could not ins
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?
--------------------------------------------------------------
@@ -20,20 +21,35 @@ In many cases, updates to various subsystems such as HLSL, BGFX, or Lua plugins
As we have no control over how third parties distribute these, all we really can do is disclaim the use of sites like EmuCR and say that we cannot provide support for packages we didn't build. Compile your own MAME or use one of the official packages provided by us.
+
+Why does MAME support console games and dumb terminals? Wouldn't it be faster if MAME had just the arcade games? Wouldn't it take less RAM? Wouldn't MAME be faster if you just X?
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+This is a common misconception. The actual size of the MAME file doesn't affect the speed of it; only the parts that are actively being used are in memory at any given time.
+
+In truth, the additional supported devices are a good thing for MAME as they allow us to stress test sections of the various CPU cores and other parts of the emulation that don't normally see heavy utilization. While a computer and an arcade machine may use the exact same CPU, how they use that CPU can differ pretty dramatically.
+
+No part of MAME is a second-class citizen to any other part. Video poker machines are just as important to document and preserve as arcade games.
+
+There's still room for improvements in MAME's speed, but chances are that if you're not already a skilled programmer any ideas you have will have already been covered. Don't let that discourage you-- MAME is open source, and improvements are always welcome.
+
+
Why do my Neo Geo ROMs no longer work? How do I get the Humble Bundle Neo Geo sets working?
-------------------------------------------------------------------------------------------
-Recently the Neo Geo BIOS was updated to add a new version of the Universal BIOS. This was done between 0.171/0.172, and results in an error trying to load Neo Geo games with an un-updated **neogeo.zip** set.
+Recently the Neo Geo BIOS was updated to add a new version of the Universal BIOS. This was done between 0.171 and 0.172, and results in an error trying to load Neo Geo games with an un-updated **neogeo.zip** set.
This also affects the Humble Bundle set: the games themselves are correct and up to date as of MAME 0.173 (and most likely will remain so) though you'll have to pull the ROM set .ZIP files out of the package somehow yourself. However, the Neo Geo BIOS set (**neogeo.zip**) included in the Humble Bundle set is incomplete as of the 0.172 release of MAME.
We suggest you contact the provider of your sets (Humble Bundle and DotEmu) and ask them to update their content to the newest revision. If enough people ask nicely, maybe they'll update the package.
+
How can I use the Sega Genesis & Mega Drive Classics collection from Steam with MAME?
-------------------------------------------------------------------------------------
As of the April 2016 update to the program, the ROM images included in the set are now 100% compatible with MAME and other Genesis/Mega Drive emulators. The ROMs are contained in the **steamapps\\Sega Classics\\uncompressed ROMs** folder as a series of *.68K* and *.SGD* images that can be loaded directly into MAME. PDF manuals for the games can be found in **steamapps\\Sega Classics\\manuals** as well.
+
Why does MAME report "missing files" even if I have the ROMs?
-------------------------------------------------------------