github.com/mist-devel.mist-board
1
0
Fork 0
mirror of https://github.com/mist-devel/mist-board.git synced 2026-03-10 20:23:44 +00:00
Code Issues Releases Wiki Activity

Updated CoreDocArcade (markdown)

retrofun
2020-05-23 17:01:41 +02:00
parent 42c6529dda
commit c8762782ed
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CoreDocArcade.md

@@ -11,7 +11,7 @@ Also Jotego's Arcade core collection https://github.com/jotego/jtbin
# Installation #
The arcade cores are normally self-contained in their own `*.rbf` file, so it is enough to copy them and a ROM file (if neeeded) to the root of an SD card.
The arcade cores are normally self-contained in their own `*.rbf` file, so it is enough to copy them and a ROM file (if needed) to the root of an SD card.
# MRA and ARC files #
@@ -21,7 +21,7 @@ Newer updates contains the so-called MRA files (invented in the MiSTer project),
mra -A -z /path/to/mame/roms Defender.mra
```
This will create DEFENDER.ROM and "Defender (Red label).arc" files. Copy both of them next to the core's RBF (Defender.rbf in this case). Why do you need an ARC file? Some cores support more than one arcade machine, and the ARC file contains information about the hardware variant, and the ROM file to load. So instead of having 4 RBFs for the Defender-like hardware, there's only one RBF, and 4 ARC files.
This will create DEFENDER.ROM and "Defender (Red label).arc" files. Copy both of them next to the core's RBF (Defender.rbf in this case). Why do you need an [ARC file](ARC-Files)? Some cores support more than one arcade machine, and the ARC file contains information about the hardware variant, and the ROM file to load. So instead of having 4 RBFs for the Defender-like hardware, there's only one RBF, and 4 ARC files.
In a bash-like shell, you can create ROMs and ARCs from several MRAs easily:
```