Skip to main content
This is unreleased documentation for the next Zaparoo Core release.
For up-to-date documentation, see the latest version (Stable).
Version: Next

muOS

Experimental

muOS support is experimental and not listed as a supported platform yet. Expect missing features and rough edges.

Zaparoo Core on muOS launches games through muOS's own content loader. Release builds are available for ARM64 devices.

Install​

Open a terminal on the device or connect to it over SSH, then run:

curl -fsSL https://zaparoo.org/install.sh | sh

The installer copies Core to /mnt/mmc/MUOS/zaparoo/zaparoo, adds a muOS user init script, and starts Core.

muOS only runs user init scripts when they are turned on. To start Core on boot, open Configuration, highlight General, press X for Advanced, and turn on User Init Scripts.

Once Core is running, write your first token from the Zaparoo App or the built-in web UI at http://<device-ip>:7497/app/.

Uninstall​

/mnt/mmc/MUOS/zaparoo/zaparoo -uninstall

This stops Core and removes the init script. Delete /mnt/mmc/MUOS/zaparoo if you also want to remove your settings and data.

File paths​

ItemPath
Config file/mnt/mmc/MUOS/zaparoo/config.toml
Data directory/mnt/mmc/MUOS/zaparoo
Log file/mnt/mmc/MUOS/zaparoo/logs/core.log
Mappings directory/mnt/mmc/MUOS/zaparoo/mappings

Client security​

muOS requires remote clients to pair. Pair the Zaparoo App, a browser, or another client with the six-digit PIN Core shows when you run /mnt/mmc/MUOS/zaparoo/zaparoo -pair. The PIN expires after five minutes. See encryption for how paired clients and their permissions work.

Readers​

Each reader's page has setup steps and troubleshooting. See readers to compare them.

Launchers​

Core adds a launcher for each system in your ROMS folders, using the core muOS has assigned to each folder. It indexes the ROMS folder on a USB drive, the second SD card, and the main SD card. Games launch through muOS's content loader.

The RomM launcher downloads games from a RomM server. See Media Servers.

Input commands type on a virtual keyboard. The virtual gamepad is off by default; turn it on with gamepad_enabled.

Shell scripts can also be launched. Add them to the allow_file list in config.toml.