PlayStation discs without a BIOS file
How split BINs become one game, how CHD and disc sets are handled, and why a check on the slowest reference Android device left JIT off.
PlayStation joined in 1.10.0 through PCSX-ReARMed, a core developed for ARM devices with an HLE BIOS implemented as host code. N-EMU uses only that boot path: no Sony BIOS import menu and no replacement firmware image. HLE does not guarantee compatibility with every game.
Importing a disc took more than accepting another extension: one CUE can reference many BINs. Select the CUE and all its files together; N-EMU streams them in track order into one image and writes a new CUE. Even 51 BINs become one library game. Hashing happens during that stream, without loading the whole image into memory.
The core never receives paths from the original CUE. It sees two virtual files: a CUE built from the checked track table and the merged BIN. That prevents a supplied path from leading the core to other files. CHD stays unchanged and is exposed as one virtual CHD.
PSP already used CHD. Routing by extension alone could send an existing PSP image to PS1. The importer identifies PS1 from raw CD track metadata and sends PSP-style tracks or DVD data through the existing PSP check. Sharing an extension does not require the reader to convert files to distinguish them.
Choose an M3U with its discs, or select files named (Disc 1), (Disc 2) and so on together, to form one game. Change discs in the pause menu while sharing one memory card and state history; loading a state restores its disc. Per-game DualShock enables both sticks and rumble, with L1, R1 and SELECT toggling analog mode.
Android JIT was left to measurement. On 21 October 2026, an optimized measurement build ran at 1× on the Galaxy Tab A8, the slowest reference device, and the owner reported a steady on-screen frame counter. This was not a recorded frame-time series and cannot establish performance for every game. Under the rule to enable it only if needed, PS1 uses no JIT on Android or iOS.
Related development stories
- Development storiesv1.9.0Closed beta testing
How 3DS states survive an update
Integrating Azahar meant signing states per installation. We then separated state compatibility from the rest of the app so an app update alone would not close those states.
- Development storiesv0.2.0Early development
Bringing several systems into one app
Several emulator cores are connected so you can choose games and manage saves from the same library across systems.