Skip to content

09. Emulators: standalone

Jump to bottom
I would prefer not to edited this page Apr 11, 2021 · 4 revisions

Amiberry

  • Systems: Amiga
  • Rom dir: /storage/roms/amiga
  • Needs assets/bios: true
  • Bios dir: /storage/roms/bios/Kickstarts
  • Bios files:
Filename Description md5sum
kick33180.A500.rom v1.2 rev 33.180 85ad74194e87c08904327de1a9443b7a
kick34005.A500.rom v1.3 rev 34.5 82a21c1890cae844b3df741f2762d48d
kick37175.A500.rom v2.04 rev 37.175 dc10d7bdd1b6f450773dfb558477c230
kick39106.A1200.rom v3.0 rev 39.106 b7cc148386aa631136f510cd29e42fc3
kick40068.A1200.rom v3.1 rev 40.68 646773759326fbac3b2311fd8c8793ee
kick40068.A4000.rom v3.1 rev 40.68 9bdedde6a4f33555b4a270c8ca53297d
  • Config dir:
  • SMB: \\your_system\Configfiles\amiberry
  • SSH: /storage/.config/amiberry

Configuration:

Supported files

Amiberry supports games with .adf .adz .ipf .lha .uae .zip extension. Amiberry also supports WHDLoad and autodetects .lha & .zip files if they contain WHDLoad files.

Default configs

Amiberry comes with default config files for common Amiga systems. The start script will load configs for Amiga A500 or A1200 if the filename contains "AGA" or "CD32" strings. You find the config files in /storage/.config/amiberry/conf

Custom configs

If you need to apply custom configurations for your games then simply copy a default config file to /storage/roms/amiga/yourgamefolder and rename it as you wish. After that you can change the settings and adjust the config file as you need. Add the paths to your floppy images and the emulators can boot your config files straight into the game.

Amiberry example.uae

So for example add to your example.uae file these lines to load images from /storage/roms/amiga/ADF called TSoMI, The_Disk1.adf

floppy0=/storage/roms/amiga/ADF/TSoMI, The_Disk1.adf
floppy1=/storage/roms/amiga/ADF/TSoMI, The_Disk2.adf
floppy2=/storage/roms/amiga/ADF/TSoMI, The_Disk3.adf
floppy3=/storage/roms/amiga/ADF/TSoMI, The_Disk4.adf

Citra

  • Systems: Nintendo 3DS
  • Rom dir: /storage/roms/3ds
  • Needs assets/bios: true
  • Bios dir: /storage/.config/citra-emu/nand
  • Bios files:

Dumping System Archives and the Shared Fonts from a 3DS Console - Citra

  • Config dir:
  • SMB: \\your_system\Configfiles\citra-emu
  • SSH: /storage/.config/citra-emu

Dolphin

  • Systems: Nintendo GameCube / Wii
  • Rom dir: /storage/roms/gc /storage/roms/wii
  • Needs assets/bios: false
  • Config dir:
  • SMB: \\your_system\Configfiles\dolphin-emu
  • SSH: /storage/.config/dolphin-emu

DOSBox-staging

  • Systems: DOS
  • Rom dir: /storage/roms/pc
  • Needs bios: true
  • Bios dir: /storage/roms/bios
  • Bios files
Filename Description md5sum
MT32_CONTROL.ROM Roland MT32 5626206284b22c2734f3e9efefcd2675
MT32_PCM.ROM Roland MT32 89e42e386e82e0cacb4a2704a03706ca
  • Config dir:
  • SMB: \\your_system\Configfiles\dosbox
  • SSH: /storage/.config/dosbox

Configuration:

Game.conf

Check out the dosbox config directory so /storage/.config/dosbox or \\your_device\Configfiles\dosbox then copy the file dosbox-staging.conf into your game directory and rename it appropriate. Finally you have to open the conf file and edit the section [autoexec] which basically executes the commands to run your game.

Example:

So if you want to play i.e. Elder Scrolls Arena you have to create a directory ARENA in your dos folder which should contain all your game files. Then copy the dosbox-staging.conf file into the ARENA directory and rename it to Elder Scrolls Arena.conf afterwards open it with an editor, scroll down to section [autoexec] and change the commands to start arena like this:

Default

[autoexec]

# Lines in this section will be run at startup.

mount c /storage/roms/pc/drive_c

c:

cd example

example.exe

#exit

Arena

[autoexec]

# Lines in this section will be run at startup.

mount c /storage/roms/dos

c:

cd ARENA

ARENA.BAT

exit

Repeat these steps and change the names according to the games you want to play.

MIDI:

Fluidsynth

LibreELEC-RR ships with 2 built in soundfonts,GeneralUser.sf2 & MuseScore_General.sf3, which are located in /usr/share/soundfonts & symlinked to /storage/.config/soundfonts where you could also store new soundfonts you might wish to use. Fluidsynth is compiled with SF2 & SF3 support so you can safe some space by using compressed ones.

The default dosbox-staging.conf will look at /storage/.config/dosbox/soundfonts which is symlinked to /storage/.config/soundfonts so store your soundfonts at this central place, adjust the filename in the config & enjoy MIDI sound.

[fluidsynth]
#     soundfont: Path to a SoundFont file in .sf2 format. You can use an
#                absolute or relative path, or the name of an .sf2 inside
#                the 'soundfonts' directory within your DOSBox configuration
#                directory.
#                An optional percentage will scale the SoundFont's volume.
#                For example: 'soundfont.sf2 50' will attenuate it by 50 percent.
#                The scaling percentage can range from 1 to 500.

soundfont     = MuseScore_General.sf3

MT-32

Dosbox-staging has also munt support which allows the emulation of the MT-32 MIDI synthesizer-module so if you like to use this MIDI sound check out dosbox-staging-template-MT32.conf.

[mt32]
#  model: Model of synthesizer to use. The default (auto) prefers CM-32L
#         if both sets of ROMs are provided. For early Sierra games and Dune 2
#         it's recommended to use 'mt32', while newer games typically made
#         use of the CM-32L's extra sound effects (use 'auto' or 'cm32l')
#         Possible values: auto, cm32l, mt32.
# romdir: The directory holding the required MT-32 and/or CM-32L ROMs
#         named as follows:
#           MT32_CONTROL.ROM or CM32L_CONTROL.ROM - control ROM files(s).
#           MT32_PCM.ROM or CM32L_PCM.ROM - PCM ROM file(s).
#         The directory can be absolute or relative, or leave it blank to
#         use the 'mt32-roms' directory in your DOSBox configuration
#         directory, followed by checking other common system locations.

model  = auto
romdir = /storage/roms/bios

FS-UAE

  • Systems: Amiga
  • Rom dir: /storage/roms/amiga
  • Needs assets/bios: true
  • Bios dir: /storage/roms/bios/Kickstarts
  • Bios files:
Filename Description md5sum
kick33180.A500.rom v1.2 rev 33.180 85ad74194e87c08904327de1a9443b7a
kick34005.A500.rom v1.3 rev 34.5 82a21c1890cae844b3df741f2762d48d
kick37175.A500.rom v2.04 rev 37.175 dc10d7bdd1b6f450773dfb558477c230
kick39106.A1200.rom v3.0 rev 39.106 b7cc148386aa631136f510cd29e42fc3
kick40068.A1200.rom v3.1 rev 40.68 646773759326fbac3b2311fd8c8793ee
kick40068.A4000.rom v3.1 rev 40.68 9bdedde6a4f33555b4a270c8ca53297d
  • Config dir:
  • SMB: \\your_system\Configfiles\fs-uae
  • SSH: /storage/.config/fs-uae

Configuration:

Supported files

FS-UAE supports game files with .adf .adz .fs-uae .ipf .zip extension. Until now FS-UAE won't support WHDLoad in my builds because the FS-UAE-LAUNCHER is needed to load these images.

Default configs

FS-UAE comes with default config files for common Amiga systems. The start script will load configs Amiga A500 or A1200 if the filename contains "AGA" or "CD32" strings. You find the config files in /storage/.config/fs-uae/Configurations

Custom configs

If you need to apply custom configurations for your games then simply copy a default config file to /storage/roms/amiga/yourgamefolder and rename it as you wish. After that you can change the settings and adjust the config file as you need. Add the paths to your floppy images and the emulators can boot your config files straight into the game.

FS-UAE example.fs-uae

So for example add to your example.fs-uae file these lines to load images from /storage/roms/amiga/ADF called TSoMI, The_Disk1.adf

floppy_drive_0=/storage/roms/amiga/ADF/TSoMI, The_Disk1.adf
floppy_image_0=/storage/roms/amiga/ADF/TSoMI, The_Disk1.adf

Hatari

  • Systems: AtariST
  • Rom dir: /storage/roms/atarist
  • Needs bios: true
  • Bios dir: /storage/roms/bios/AtariST
  • Bios files

TOS v1.02 US should have a great compatibility if you want to run games.

Filename Description md5sum
tos.img v1.02 US c1c57ce48e8ee4135885cee9e63a68a2
  • Config dir:
  • SMB: \\your_system\Configfiles\hatari
  • SSH: /storage/.config/hatari

Configuration:

Supported files

Hatari supports game files with .cfg .dim .ipf .msa .st .stx .zip extension

Default configs

Hatari comes with a default config file for the Atari ST system. The start script will load this config when you start a game. You can find it in /storage/.config/hatari/conf

Custom configs

If you need to apply custom configurations for your games then simply copy a default config file to /storage/roms/atarist/yourgamefolder and rename it as you wish. After that you can change the settings and adjust the config file as you need. Add the paths to your floppy images and the emulators can boot your config files straight into the game.

Hatari example.cfg

So for example add to your example.cfg file these lines to load images from /storage/roms/atarist/LX called LX_Disk_1.stx & LX_Disk_2.stx

szDiskAFileName = /storage/roms/atarist/LX/LX_Disk_1.stx
szDiskBFileName = /storage/roms/atarist/LX/LX_Disk_2.stx

Mupen64plus/m64p

  • Systems: Nintendo 64
  • Rom dir: /storage/roms/n64
  • Needs assets/bios: false
  • Config dir:
  • SMB: \\your_system\Configfiles\mupen64plus
  • SSH: /storage/.config/mupen64plus

Configuration:

Edit es_systems.cfg and replace <command>/usr/bin/retroarch.start -L /tmp/cores/mupen64plus_libretro.so %ROM%</command> with either <command>/usr/bin/m64p-cli.start %ROM%</command> or <command>/usr/bin/m64p.start %ROM%</command> to start Mupen64plus with with mupen64plus-ui-console or Qt5 based mupen64plus-gui.

PCSX2

  • Systems: Sony PlayStation 2
  • Rom dir: /storage/roms/ps2
  • Needs bios: true
  • Bios dir: /storage/roms/bios/PCSX2
  • Bios files:

PCSX2 is region-free and will run games regardless if the bios is of a different region. A CPU that has at least SSE4.1 support is mandatory to run PCSX2!

Filename Description md5sum
ps2-0230e-20080220.bin Europe dc69f0643a3030aaa4797501b483d6c4
ps2-0230a-20080220.bin US 21038400dc633070a78ad53090c53017
ps2-0210j-20040917.bin Japan 1ad977bb539fc9448a08ab276a836bbc
  • Config dir:
  • SMB: \\your_system\Configfiles\PCSX2
  • SSH: /storage/.config/PCSX2

Configuration:

PCSX2_ui.ini

For whatever reason you can't select the GS plugin and when you start the emulator the first time it will nag about it. Finish the first time wizard/config process and open (...)/PCSX2/inis/PCSX2_ui.ini in the configfiles directory. Look for the following lines and adjust them apprpriate to your cpu features:

[Filenames]
GS=
BIOS=/storage/roms/bios/PCSX2/ps2-bios.bin
  • libGSdx-AVX2.so = if your CPU supports AVX2
  • libGSdx.so = if your CPU supports SSE4

e.g

[Filenames]
GS=/usr/lib/PCSX2/libGSdx-AVX2.so
BIOS=/storage/roms/bios/PCSX2/ps2-bios.bin

Run PCSX2 again & it should pick up the GSdx lib which can be configured then.

Boot

Some games need the --fullboot option. So editing es_systems.cfg and change the PCSX2 start command from <command>/usr/bin/pcsx2.start %ROM%</command> to <command>/usr/bin/pcsx2.start --fullboot %ROM%</command> and this should do the trick if you miss some language config option for example.

PPSSPP

  • Systems: Sony PSP
  • Rom dir: /storage/roms/psp
  • Needs bios: false
  • Config dir:
  • SMB: \\your_system\Configfiles\ppsspp
  • SSH: /storage/.config/ppsspp

RPCS3

  • Systems: Sony SonyPlaystaion 3
  • Rom dir: /storage/roms/ps3
  • Needs bios: true

Quickstart

  • Config dir:
  • SMB: \\your_system\Configfiles\rpcs3
  • SSH: /storage/.config/rpcs3

Configuration:

Before you run RPCS3 the firt time your have to download the latest PlayStation 3 firmware update PS3UPDAT.PUP from this page and place it on your device. When you start the emulator it will ask you where the file is located, select it & let RPCS3 install it, exit & restart the game. Now RPCS3 will take some time to precompile modules & once finished it'll start your game.

VICE

  • Systems: Commodore C64
  • Rom dir: /storage/roms/c64
  • Needs bios: false
  • Config dir:
  • SSH: /storage/.vice
Clone this wiki locally