-
-
Notifications
You must be signed in to change notification settings - Fork 35
BIOS
Some platforms need proprietary BIOS files to boot. Argosy syncs BIOS from your RomM server, stores it locally, and copies it into emulators' BIOS folders so games can boot.
When you sync your library, RomM returns firmware metadata (filename, size, hash) for each platform alongside the game list. Argosy uses that metadata to show which BIOS files are available for your platforms and lets you download them on demand.
Go to Settings > BIOS Files. You'll see:
- A summary card with totals ("N of M BIOS files downloaded") and top-level Download Missing and Distribute actions.
- A per-platform list showing "downloaded / total" counts. Platforms with all files present get a green checkmark; incomplete ones show a memory-chip icon.
- Expanding a platform reveals the individual firmware files -- name, size, and whether each one is downloaded.
Tap Download Missing (global or per-platform) to fetch BIOS from your RomM server. Files are verified against the RomM-reported MD5 hash; a mismatched download is discarded and retried.
Once downloaded, BIOS has to be placed where each emulator looks for it:
- Built-in emulator -- Argosy copies required BIOS into the built-in libretro system directory every time you launch a game. You don't have to do anything.
- External emulators that scan a BIOS folder (e.g. RetroArch) -- tap Distribute in Settings > BIOS Files. Argosy writes BIOS into each emulator's known folder path; the emulator picks them up the next time it scans. Filename mapping is handled automatically (RetroArch, for example, expects specific names and Argosy maps them by hash).
- External emulators that import BIOS through their own UI (NetherSX2 is the common example -- see NetherSX2 BIOS Troubleshooting) -- Argosy cannot inject files into these apps. You need to point them at the Argosy BIOS folder from inside that emulator's own import flow.
By default, downloaded BIOS lives in Argosy's internal app directory, which is private to Argosy and not visible to other apps. That is fine for the built-in emulator and for emulators that accept a distributed copy.
If you use an emulator that imports BIOS through its own UI, change Settings > BIOS Files > BIOS Directory to a location that emulator can read (typically shared external storage). Argosy migrates existing downloads to the new location and future downloads land there. You can then point the other emulator at that directory from its import flow.
BIOS is required for cores covering these platforms:
- PlayStation (PS1)
- Nintendo DS
- Game Boy Advance
- Atari 5200, Atari 7800, Atari Lynx
- Intellivision
- 3DO
- Odyssey (Magnavox)
- Amiga, Amiga CD32, CDTV
- Channel F
- Pokemon mini
The per-platform BIOS page in Settings is the authoritative list of exactly which files each platform needs and whether you currently have them.
BIOS files are proprietary firmware. Argosy does not bundle or redistribute them; obtain them legally (e.g. dumped from hardware you own) and upload them to your RomM server, where Argosy can then sync them to the device.
Getting Started
Using Argosy
Features
- RetroAchievements
- RomM Integration
- Media
- Accounts
- Save Sync
- QuayPass
- Netplay
- Steam Integration
- Dual-Screen
- BIOS
Built-in Emulator
Settings
Reference
Emulator Guides