Permalink
Browse files

srcclean again (nw)

  • Loading branch information...
1 parent e2c6632 commit 66f1cb5f3a3b229d8192e1a0fd9db867e3f21d5c @cuavas cuavas committed Nov 29, 2016
@@ -10,4 +10,4 @@ Advanced configuration
bgfx
hlsl
glsl
- devicemap
+ devicemap
@@ -27,7 +27,7 @@ Inside the *spyhunt.cfg* file, you will find the following for the input. The ac
| JOYCODE_1_RYAXIS_NEG_SWITCH OR JOYCODE_1_RYAXIS_POS_SWITCH
| </newseq>
| </port>
-|
+|
The line you need to edit will be the port line defining the actual input. For Spy Hunter, that's going to be *P1_BUTTON2*. Add **toggle="no"** to the end of the tag, like follows:
@@ -36,6 +36,6 @@ The line you need to edit will be the port line defining the actual input. For S
| JOYCODE_1_RYAXIS_NEG_SWITCH OR JOYCODE_1_RYAXIS_POS_SWITCH
| </newseq>
| </port>
-|
+|
Save and exit. To disable this, simply remove the **toggle="no"** from each desired .CFG input.
@@ -7,11 +7,11 @@ All Platforms
-------------
* Whenever you are changing build parameters, (such as switching between a SDL-based build and a native Windows renderer one, or adding tools to the compile list) you need to run a **make REGENIE=1** to allow the settings to be regenerated. Failure to do this will cause you very difficult to troubleshoot problems.
-
+
* If you want to add various additional tools to the compile, such as *CHDMAN*, add a **TOOLS=1** to your make statement, like **make REGENIE=1 TOOLS=1**
-
+
* You can do driver specific builds by using *SOURCES=<driver>* in your make statement. For instance, building Pac-Man by itself would be **make SOURCES=src/mame/drivers/pacman.cpp REGENIE=1** including the necessary *REGENIE* for rebuilding the settings.
-
+
* Speeding up the compilation can be done by using more cores from your CPU. This is done with the **-j** parameter. *Note: the maximum number you should use is the number of cores your CPU has, plus one. No higher than that will speed up the compilation, and may in fact slow it down.* For instance, **make -j5** on a quad-core CPU will provide optimal speed.
* Debugging information can be added to a compile using *SYMBOLS=1* though most users will not want or need to use this.
@@ -21,12 +21,12 @@ Putting all of these together, we get a couple of examples:
Rebuilding MAME for just the Pac-Man driver, with tools, on a quad-core (e.g. i5 or i7) machine:
| **make SOURCES=src/mame/drivers/pacman.cpp TOOLS=1 REGENIE=1 -j5**
-|
+|
Rebuilding MAME on a dual-core (e.g. i3 or laptop i5) machine:
| **make -j3**
-|
+|
Microsoft Windows
@@ -36,7 +36,7 @@ Here are specific notes about compiling MAME for Microsoft Windows.
* Refer to `the MAME tools site <http://mamedev.org/tools/>`_ for the latest toolkit for getting MAME compiled on Windows.
-* You will need to download the toolset from that link to begin. Periodically, these tools are updated and newer versions of MAME from that point on will **require** updated tools to compile.
+* You will need to download the toolset from that link to begin. Periodically, these tools are updated and newer versions of MAME from that point on will **require** updated tools to compile.
* You can do compilation on Visual Studio 2015 (if installed on your PC) by using **make vs2015**. This will always regenerate the settings, so **REGENIE=1** is *not* needed.
@@ -96,12 +96,12 @@ It's possible to get MAME working from 10.6, but a bit more complicated:
* You'll need to install clang-3.7, ld64, libcxx and python27 from MacPorts
* Then add these options to your make command or useroptions.mak:
-|
+|
| OVERRIDE_CC=/opt/local/bin/clang-mp-3.7
| OVERRIDE_CXX=/opt/local/bin/clang++-mp-3.7
| PYTHON_EXECUTABLE=/opt/local/bin/python2.7
| ARCHOPTS=-stdlib=libc++
-|
+|
Emscripten Javascript and HTML
@@ -10,4 +10,4 @@ You simply have to download the latest binary archive available from http://www.
Other Operating Systems
-----------------------
-In this case, you can either look for pre-compiled (SDL)MAME binaries (e.g. in the repositories of your favorite Linux distro) which should simply extract all the needed files in a folder you choose, or compile the source code by yourself. In the latter case, see our section on :ref:`compiling-mame`.
+In this case, you can either look for pre-compiled (SDL)MAME binaries (e.g. in the repositories of your favorite Linux distro) which should simply extract all the needed files in a folder you choose, or compile the source code by yourself. In the latter case, see our section on :ref:`compiling-mame`.
@@ -18,10 +18,10 @@ Systems Emulated by MAME
========================
-ProjectMESS contains a complete list of the systems currently emulated. As you will notice, being supported does not always mean that the status of the emulation is perfect. You may want
+ProjectMESS contains a complete list of the systems currently emulated. As you will notice, being supported does not always mean that the status of the emulation is perfect. You may want
1. to check the status of the emulation in the wiki pages of each system, accessible from the drivers page (e.g. for Apple Macintosh, from the page for the mac.c driver you can reach the pages for both **macplus** and **macse**),
-2. to read the corresponding **sysinfo.dat** entry in order to better understand which issues you may encounter while running a system in MAME (again, for Apple Macintosh Plus you have to check this entry).
+2. to read the corresponding **sysinfo.dat** entry in order to better understand which issues you may encounter while running a system in MAME (again, for Apple Macintosh Plus you have to check this entry).
Alternatively, you can simply see the status by yourself, launching the system emulation and taking a look to the red or yellow warning screen which appears before the emulation starts, if any. Notice that if you have information which can help to improve the emulation of a supported system, or if you can directly contribute fixes and/or addition to the current source, you can follow the instructions at the contact page or post to the MAME Forums at http://forum.mamedev.org/
@@ -5,4 +5,4 @@ MAME is not intended or designed to run in secure sites. It has not been securit
**We do not suggest or condone the use of MAME as administrator or root and use as such is done at your own risk.**
-Bug reports, however, are always welcome.
+Bug reports, however, are always welcome.
@@ -115,7 +115,7 @@ Once the cell data stream is extracted decoding depends on the encoding. In the
2.3.2. Sector-level organization
''''''''''''''''''''''''''''''''
-
+
Floppies have been designed for read/write random access to reasonably sized blocks of data. Track selection allows for a first level of random access and sizing, but the ~6K of a double density track would be too big a block to handle. 256/512 bytes are considered a more appropriate value. To that end data on a track is organized as a series of (sector header, sector data) pairs where the sector header indicates important information like the sector number and size, and the sector data contains the data. Sectors have to be broken in two parts because while reading is easy, read the header then read the data if you want it, writing requires reading the header to find the correct place then once that is done switching on the writing head for the data. Starting writing is not instantaneous and will not be perfectly phase-aligned with the read header, so space for synchronization is required between header and data.
In addition somewhere in the sector header and in the sector data are pretty much always added some kind of checksum allowing to know whether the data was damaged or not.
@@ -154,7 +154,7 @@ Then for each sector:
The track is finished with a stream of '1' cells.
-The 125KHz pulse trains are used to lock the PLL to the signal correctly. The specific 16-cells streams allow to distinguish between clock and data bits by providing a pattern that is not supposed to happen in normal FM-encoded data. In the sector header track numbers start at 0, heads are 0/1 depending on the size, sector numbers usually start at 1 and size code is 0 for 128 bytes, 1 for 256, 2 for 512, etc.
+The 125KHz pulse trains are used to lock the PLL to the signal correctly. The specific 16-cells streams allow to distinguish between clock and data bits by providing a pattern that is not supposed to happen in normal FM-encoded data. In the sector header track numbers start at 0, heads are 0/1 depending on the size, sector numbers usually start at 1 and size code is 0 for 128 bytes, 1 for 256, 2 for 512, etc.
The CRC is a cyclic redundancy check of the data bits starting with the mark just after the pulse train using polynom 0x11021.
@@ -209,7 +209,7 @@ Similarly two write splices are created when a sector is written at the start an
3. The new implementation
-------------------------
-
+
3.1. Floppy disk representation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -234,7 +234,7 @@ The last cell implicit end position is of course 200,000,000.
Unformatted tracks are encoded as zero-size.
-The "track splice" information indicates where to start writing if you try to rewrite a physical disk with the data. Some preservation formats encode that information, it is guessed for others. The write track function of fdcs should set it. The representation is the angular position relative to the index.
+The "track splice" information indicates where to start writing if you try to rewrite a physical disk with the data. Some preservation formats encode that information, it is guessed for others. The write track function of fdcs should set it. The representation is the angular position relative to the index.
3.2. Converting to and from the internal representation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -281,7 +281,7 @@ A number of methods are provided to simplify writing the converter classes.
| **UINT8 \*cell stream,**
| **int cell count,**
| **floppy image)**
-|
+|
Takes a stream of cell types (0/1), MSB-first, converts it to the internal format and stores it at the given track and head in the given image.
@@ -344,7 +344,7 @@ A number of methods are provided to simplify writing the converter classes.
| **sector size,**
| **sector count,**
| **UINT8 \*sector data)**
-|
+|
Extract what you'd get by reading in order 'sector size'-sized sectors from number 1 to sector count and put the result in sector data.
@@ -11,4 +11,4 @@ This section covers technical specifications useful to programmers working on MA
floppy
nscsi
luaengine
- m6502
+ m6502
@@ -24,19 +24,19 @@ The nscsi subsystem leverages the slot interfaces and the device naming to allow
First you need to create a list of acceptable devices to plug on the bus. This usually comprises of **cdrom**, **harddisk** and the controller chip. For instance:
-|
+|
| static SLOT_INTERFACE_START( next_scsi_devices )
| SLOT_INTERFACE("cdrom", NSCSI_CDROM)
| SLOT_INTERFACE("harddisk", NSCSI_HARDDISK)
| SLOT_INTERFACE_INTERNAL("ncr5390", NCR5390)
| SLOT_INTERFACE_END
-|
+|
The **_INTERNAL** interface indicates a device that is not user-selectable, which is useful for the controller.
Then in the machine config (or in a fragment config) you need to first add the bus, and then the (potential) devices as sub-devices of the bus with the SCSI ID as the name. For instance you can use:
-|
+|
| MCFG_NSCSI_BUS_ADD("scsibus")
| MCFG_NSCSI_ADD("scsibus:0", next_scsi_devices, "cdrom", 0, 0, 0, false)
| MCFG_NSCSI_ADD("scsibus:1", next_scsi_devices, "harddisk", 0, 0, 0, false)
@@ -46,7 +46,7 @@ Then in the machine config (or in a fragment config) you need to first add the b
| MCFG_NSCSI_ADD("scsibus:5", next_scsi_devices, 0, 0, 0, 0, false)
| MCFG_NSCSI_ADD("scsibus:6", next_scsi_devices, 0, 0, 0, 0, false)
| MCFG_NSCSI_ADD("scsibus:7", next_scsi_devices, "ncr5390", 0, &next_ncr5390_interface, 10000000, true)
-|
+|
That configuration puts as default a CD-ROM reader on SCSI ID 0 and a hard drive on SCSI ID 1, and forces the controller on ID 7. The
parameters of add are:
@@ -5,7 +5,7 @@ Imgtool - *A generic image manipulation tool for MAME*
Imgtool is a tool for the maintenance and manipulation of disk and other types of images that MAME users need to deal with. Functions include retrieving and storing files and CRC checking/validation.
-Imgtool is part of the MAME project. It shares large portions of code with MAME, and its existence would not be if it were not for MAME. As such, the distribution terms are the same as MAME. Please read the MAME license thoroughly.
+Imgtool is part of the MAME project. It shares large portions of code with MAME, and its existence would not be if it were not for MAME. As such, the distribution terms are the same as MAME. Please read the MAME license thoroughly.
**Some portions of Imgtool are Copyright (c) 1989, 1993 The Regents of the University of California. All rights reserved.**
@@ -22,9 +22,9 @@ Imgtool is a command line program that contains several "subcommands" that actua
Example usage:
imgtool dir coco_jvc_rsdos myimageinazip.zip
-
+
imgtool get coco_jvc_rsdos myimage.dsk myfile.bin mynewfile.txt
-
+
imgtool getall coco_jvc_rsdos myimage.dsk
@@ -41,7 +41,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Creates an image
**dir**
@@ -59,7 +59,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Gets a single file from an image
**put**
@@ -68,7 +68,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Puts a single file on an image (wildcards supported)
**getall**
@@ -77,7 +77,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Gets all files off an image
**del**
@@ -86,7 +86,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Deletes a file on an image
**mkdir**
@@ -95,7 +95,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Creates a subdirectory on an image
**rmdir**
@@ -104,7 +104,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Deletes a subdirectory on an image
**readsector**
@@ -113,11 +113,11 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
Read a sector on an image and output it to specified <filename>
**writesector**
-
+
**imgtool writesector <format> <imagename> <track> <head> <sector> <filename>**
* <format> is the image format, e.g. coco_jvc_rsdos
@@ -129,7 +129,7 @@ Imgtool Subcommands
* <format> is the image format, e.g. coco_jvc_rsdos
* <imagename> is the image filename; can specify a ZIP file for image name
-
+
**imgtool identify <imagename>**
**listformats**
@@ -145,7 +145,7 @@ Imgtool Subcommands
**imgtool listdriveroptions <format>**
* <format> is the image format, e.g. coco_jvc_rsdos
-
+
Lists all format-specific options for the 'put' and 'create' commands
@@ -170,7 +170,7 @@ Filters are a means to process data being written into or read out of an image i
**macbinary**
Processes Apple MacBinary-formatted (merged forks) files
-
+
**vzsnapshot**
[todo: VZ Snapshot? Find out what this is....]
@@ -198,7 +198,7 @@ Filters are a means to process data being written into or read out of an image i
**bm13bas**
Basic Master Level 3 Tokenized Basic Files
-
+
Imgtool Format Info
===================
@@ -1672,5 +1672,5 @@ Option Allowed values Description
-
-[todo: fill out the command structures, describe commands better. These descriptions came from the imgtool.txt file and are barebones]
+
+[todo: fill out the command structures, describe commands better. These descriptions came from the imgtool.txt file and are barebones]
@@ -9,7 +9,7 @@ On Microsoft Windows, ledutil.exe can take control of your keyboard LEDs to mirr
Start **ledutil.exe** from the command line to enable LED handling. Run **ledutil.exe -kill** to stop the handler.
-On SDLMAME platforms such as Mac OS X and Linux, **ledutil.sh** can be used. Use **ledutil.sh -a** to have it automatically close when you exit SDLMAME.
+On SDLMAME platforms such as Mac OS X and Linux, **ledutil.sh** can be used. Use **ledutil.sh -a** to have it automatically close when you exit SDLMAME.
Developer-focused tools included with MAME
@@ -45,12 +45,12 @@ ldresample
This tool recompresses video data for laserdisc and VHS dumps. Most users will not need to work with this.
-ldverify
+ldverify
--------
This tool is used for comparing laserdisc or VHS CHD images with the source AVI. Most users will not need to work with this.
unidasm
-------
-Universal disassembler for many of the architectures supported in MAME. Most users will not need to work with this.
+Universal disassembler for many of the architectures supported in MAME. Most users will not need to work with this.
Oops, something went wrong.

0 comments on commit 66f1cb5

Please sign in to comment.