△◯✕□ launcHER DOCS
Downloads GitHub

Sony POPS & PS1 Setup

Draft PR #23, reviewed at cfebe01, implements substantial independent POPStarter-r13 command, configuration, storage and resident-runtime functionality around user-supplied Sony POPS. It is not a completed drop-in replacement or a claim of compatibility across all storage devices. Current host and component evidence does not establish console behavior.

External Dependencies Notice
launcHER is a loader and environment orchestrator. It does not contain or distribute Sony's proprietary emulator binaries (POPS.PAK, POPS_IOX.PAK, POPS.ELF, IOPRP252.IMG) or PlayStation 1 BIOS images. You must provide clean copies from your own PlayStation 2 installations.

Step 1: External POPS Dependencies

Sony distributed POPS in different package formats across various official releases. launcHER accepts three distinct installation forms:

Package Form Required Files Description
Packed IOX (Recommended) POPS_IOX.PAK Compressed POPS memory image containing the emulator core and an updated ioprp2305a reboot module. Offers the best compatibility on modern storage devices.
Packed Legacy POPS.PAK Compressed POPS memory image containing the emulator core and an ioprp252 reboot module. Standard package from earlier POPStarter releases.
Loose Files POPS.ELF and IOPRP252.IMG Uncompressed EE executable paired with a standalone IOP reboot image. Both files must reside in the same directory.

Discovery Search Order

When you launch a .VCD game, launcHER searches for your POPS dependency files in this priority order:

  1. Target Game Directory: The folder holding the active .VCD disc (for example, mass0:/POPS/).
  2. Device Root POPS Folder: <device>:/POPS/ on the storage volume containing the game (for example, ata:/POPS/ or mass0:/POPS/).
  3. Memory Card Slot 1: mc0:/POPS/.
  4. Memory Card Slot 2: mc1:/POPS/.
  5. Internal APA Partition: hdd0:__.POPS:pfs:/ (for internal HDD setups).

Place your chosen dependency package (such as POPS_IOX.PAK) in any of these locations. Keeping it in your main POPS/ directory or on mc0:/POPS/ allows all games to share one file.

Step 2: Preparing .VCD Disc Images

POPS requires disc images in Sony's Virtual CD (.VCD) format. These images use raw Mode 2 Form 1 CD-ROM sectors (2,352 bytes per sector).

Convert your original PlayStation 1 CD-ROM dumps (BIN/CUE pairs) to .VCD using tools such as CUE2POPS. Place the resulting .VCD files in your games directory:

POPS/
├── POPS_IOX.PAK               # Shared emulator package
├── Crash Bandicoot.VCD        # Single-disc game
├── Spyro the Dragon.VCD       # Single-disc game
└── Metal Gear Solid/          # Multi-disc game subfolder
    ├── Metal Gear Solid (Disc 1).VCD
    ├── Metal Gear Solid (Disc 2).VCD
    └── DISCS.TXT

Step 3: Launch Methods and CNF Configuration

You can launch POPS games using launcHER.CNF, using direct binary names (OPL APPS style), or through command-line invocation.

Method A: Quickboot via launcHER.CNF

Point the path= directive directly to your .VCD file. launcHER detects the .VCD file extension, mounts the parent storage device, and boots POPS automatically:

Storage Transport launcHER.CNF Example
USB Mass Storage
path=mass?:/POPS/Crash Bandicoot.VCD
Internal exFAT HDD (ATA BDM)
path=ata:/POPS/Crash Bandicoot.VCD
arg=-dev9=NICHDD
APA / PFS Partition (hdd0:__.POPS)
path=hdd0:__.POPS:pfs:/Crash Bandicoot.VCD
arg=-dev9=NICHDD
MMCE (Memory Card SD adapter)
path=mmce?:/POPS/Crash Bandicoot.VCD
MX4SIO / MC2SIO
path=mx4sio:/POPS/Crash Bandicoot.VCD
i.Link (FireWire IEEE 1394)
path=ilink:/POPS/Crash Bandicoot.VCD
UDPBD (Network Block Device)
path=udpbd:/POPS/Crash Bandicoot.VCD
arg=-dev9=NIC
UDPFS (Network Filesystem)
path=udpfs:/POPS/Crash Bandicoot.VCD
arg=-dev9=NIC

Method B: Direct Binary Quickboot (draft PR #23)

When running without a launcHER.CNF file, launcHER discovers game images based on its executable filename:

  1. No Prefix (Default POPS APA): An executable named Crash Bandicoot.ELF without a prefix defaults to the internal HDD APA partition: hdd0:__.POPS:pfs:/Crash Bandicoot.VCD, followed by adjacent directory checks.
  2. BDMA and Storage Prefix (XX.): Executables named with an XX. prefix (such as XX.Crash Bandicoot.ELF) check memory card directories (mc0:/POPSTARTER/, mc1:/POPSTARTER/) for external drivers and BDMA markers:
    • When external drivers (USBD.IRX, USBHDFSD.IRX, bdm_assault.irx, BDM.IRX, MX4SIO.IRX, ATA.IRX, MMCE.IRX) exist in mc?:/POPSTARTER/, launcHER skips internal USB modules and uses the external drivers.
    • When external modules are not present, launcHER loads its built-in modules for USB POPS launches.
    • When BDMA mode markers (bdma_mode.txt) exist, launcHER routes targets to the designated hardware backend: ATA / EXFAT (ata:/POPS/<Game>.VCD), MX4SIO (mx4sio:/POPS/<Game>.VCD), MMCE (mmce0:/POPS/<Game>.VCD), or USB (mass0:/POPS/<Game>.VCD).
  3. SMB Network Prefix (SB.): Executables named with an SB. prefix (such as SB.Crash Bandicoot.ELF) load the POPStarter SMB network stack from mc?:/POPSTARTER/ (PS2DEV9.IRX, SMAP.IRX, PS2IP.IRX, SMBMAN.IRX, PS2NETFS.IRX). launcHER applies static IP settings from IPCONFIG.DAT, reads share settings from SMBCONFIG.DAT, and launches smb0:/POPS/<Game>.VCD.
  4. Matching Title Priority: launcHER verifies <Game>.VCD before checking generic IMAGE.VCD.

This maintains POPStarter directory conventions and leverages existing memory card installations while providing built-in drivers for systems without external modules.

Method C: Direct Command-Line Invocation

Launchers, scripts, or menu frontends can pass arguments directly to launcHER.elf without requiring a launcHER.CNF file:

Step 4: Per-Game Configuration Directives

Place optional text configuration files alongside your .VCD image, or inside the per-game VMC subfolder. launcHER reads these files automatically before entering POPS:

Video Mode Directives

POPS runs in NTSC. Like POPStarter, launcHER reads the licence text on the disc and switches European discs to PAL automatically. Nothing on this page has been tested on a console yet.

Directive Description
$NOPAL / $PAL2NTSC / $FORCENTSC Keeps a European disc at 60 Hz NTSC instead of switching to PAL.
$FORCEPAL / $NTSC2PAL Runs any disc in PAL 50 Hz and reports Europe to POPS.
$HDTVFIX / $NOHDTVFIX POPStarter's HDTV fix on or off.
$480p Selects launcHER's independent guarded progressive bridge. Host and component checks pass; progressive picture output on a physical console remains unverified.

Other POPStarter commands

Multiple directives may appear on the same line separated by spaces (e.g. $NOPAL $MUTE_CDDA). The full list, including the commands launcHER cannot do yet, is in POPSTARTER_R13_INVENTORY.md.

Step 5: Compatibility Modes 1 through 8

Certain games require low-level timing or subsystem adjustments within POPS. Specify these modes in MODES.TXT (as bare numbers like 1, 2) or in PATCHES.TXT (using $COMPATIBILITY_0x01 through $COMPATIBILITY_0x08):

Mode Target Memory Site Subsystem Adjustment
Mode 1 0x002148A0 Adjusts SPU2 DMA synchronization loops and wait timing. Resolves audio stutter and lockups in music and FMV sequences.
Mode 2 0x00207EC0 Disables the CD-ROM fast sector cache override. Fixes read errors in games that rely on standard disc seek latency.
Mode 3 0x00210850 Disables the alternate audio channel mixer, restoring original PS1 sound channel routing.
Mode 4 0x00205B10 Skips GPU FIFO synchronization locks. Eliminates visual rendering freezes in high-throughput 3D titles.
Mode 5 0x002061A0 Forces progressive display timing directly inside the emulator display scheduler.
Mode 6 0x0020C1F0 Enables alternate LibCrypt subchannel emulation for protected titles without pre-calculated keys.
Mode 7 0x002010A0 Throttles the R3000A CPU cycle counter (addiu $a0, $zero, 2) to resolve speed-dependent bugs.
Mode 8 0x00207EE8 Adjusts CD-DA streaming buffer parameters, preventing background CD audio loops from dropping out.

Step 6: Title Compatibility Database & LibCrypt

launcHER applies POPStarter r13's own built-in per-game list (the disc is identified from 144 bytes of the VCD; $VCDID_n picks an entry by hand when nothing matched; not yet tested on a console) and includes a built-in database of 568 verified game profiles and 229 validated 16-bit LibCrypt magic keys.

When you boot a game, launcHER performs these actions automatically:

  1. Inspects the ISO9660 Primary Volume Descriptor inside the .VCD file.
  2. Reads SYSTEM.CNF and extracts the official serial (for example, SCES-01422 or SLUS-00870).
  3. Checks the internal database. If the game has known compatibility requirements, launcHER sets the recommended modes automatically.
  4. For a title using European LibCrypt copy protection, the branch applies the measured bypass-patch behavior and programs physical Subchannel Q emulation into the driver using the title's verified 16-bit key. Protected-game compatibility remains unverified on a physical console.

Step 7: Virtual Memory Cards (VMC)

POPS saves game data into Virtual Memory Card (VMC) images on your storage device rather than physical PS2 memory cards.

Naming Conventions

launcHER checks for card images using this filename priority:

For example, for Crash Bandicoot (SCUS-94900), launcHER looks for SCUS-94900.VMC0 and SCUS-94900.VMC1.

Automatic Formatting

If neither card image exists when launching, launcHER creates both 128 KiB files on your storage device, pre-formatting them with valid PlayStation memory card header blocks and XOR checksums. The game recognizes them as formatted memory cards immediately.

Custom Save Folder Redirection

Create a VMCDIR.TXT file in your game folder to redirect card saves to a common directory or subfolder:

SAVES/Crash/

Step 8: Multi-Disc Games (DISCS.TXT)

For games spanning multiple CD-ROMs (such as Final Fantasy VII or Metal Gear Solid), create a DISCS.TXT file in the game directory. List each disc on its own line:

Metal Gear Solid (Disc 1).VCD
Metal Gear Solid (Disc 2).VCD

launcHER reads DISCS.TXT the way POPStarter r13 does:

In-Game Disc Swapping

POPStarter's disc swap, on controller 1, holding nothing else (not yet tested on a console):

  1. Press SELECT + L2 + R2 + TRIANGLE to open the virtual disc lid.
  2. Press SELECT + L2 + R2 with UP, RIGHT, DOWN or LEFT to pick disc 1, 2, 3 or 4 of DISCS.TXT.
  3. Press SELECT + L2 + R2 + SQUARE to close the lid. POPS loads the disc you picked and the game carries on.

Without a DISCS.TXT line for the disc you picked, closing the lid reloads the disc the game started with. launcHER's older SELECT + L1 + R1 swap was removed on November 2, 2026: it could never switch while the game had the disc open, which is all the time in game.

Step 9: GameShark & Action Replay Cheats

Add GameShark or Action Replay cheat codes to CHEATS.TXT in your game folder. Write each code POPStarter style, $ then the code. launcHER reads the file the way POPStarter r13 does:

# Infinite Health (16-bit write)
$8009A120 0004

# All Items (8-bit write)
$3009A135 0063

# Switched off: no $
8009A150 0001

# Master code: every code runs only while 0x0008B000 holds 0x1234
$C008B000 1234

# If 0x0008B200 == 0x0001, run the next code:
$D008B200 0001
$8008B204 00FF

# Repeat: write 0x0010, 0x0011, 0x0012, 0x0013 at 0x0009A200, 0x0009A202, ...
$50000402 0001
$8009A200 0010

POPStarter's code types, all read and run as POPStarter compiles them:

Other GameShark types (10, 20, D1..D3, E0, E1) are skipped, as in POPStarter, so the code after one of them runs on its own.

POPStarter's PS2-format codes are read and run as POPStarter compiles them too. They have an 8-digit value, so a code is 18 characters long:

Their POPStarter quirks are copied as well. Byte and halfword compares read the memory as signed, so a byte of 80 matches the value FFFFFF80, not 00000080. After the first PS2-format conditional, every later conditional and repeat in the file is ignored, and so are $T writes after a $S conditional and $S writes after a $= or $!. A $0/$1/$2 write between a D0 and the code it gates runs on its own and usually makes that code skipped; a $S/$T write there is ignored. A code at an address its size does not divide, which crashes POPStarter, is aligned down instead.

launcHER copies POPStarter's two repeat bugs too, so a file behaves the same in both. When a repeat crosses a 64 KB boundary, every later write lands another 64 KB further up. When a repeat's value reaches 20000 (hex), the rest of the writes repeat the last value that still fitted. In that second case POPStarter's generated code also changes another CPU register; launcHER cannot copy that part, and what it does on a console is unknown. The full list of copied POPStarter quirks is in POPSTARTER_QUIRKS_TO_FIX_LATER.md.

launcHER installs its own small resident program next to POPS and runs these codes against PlayStation 1 RAM (0x00000000 to 0x001FFFFF), and PS2-format codes against the memory they name, from the same place in POPS as POPStarter: each time the game writes the GPU control port with interrupts enabled; how often that is depends on the game and was not measured. A game that stops writing it gets no codes until it writes it again, in POPStarter too. It is independent code, not POPStarter's. Not yet tested on a console.

Step 10: In-Game Reset & Controller Hotkeys

Action Button Combination Behavior
In-Game Reset (IGR) L1 + L2 + R1 + R2 + SELECT + START Shuts down the emulator safely and returns to your PS2 menu (OSDSYS, OPL, or wLaunchELF).
Disc Swap SELECT + L2 + R2 + TRIANGLE, then SELECT + L2 + R2 + a direction, then SELECT + L2 + R2 + SQUARE POPStarter's swap: open the lid, pick disc 1 to 4 of DISCS.TXT (UP, RIGHT, DOWN, LEFT), close the lid to load it. Controller 1.

Custom IGR Background Graphics

Place TIM2 image files in your game directory or VMC folder to customize the exit confirmation interface:

Custom Game Fixes (TROJAN_*.BIN)

If a community patch requires code injection hooks, place TROJAN_0.BIN through TROJAN_9.BIN alongside the game. launcHER verifies the container header, checks the hook address, stages the payload, and applies the injection before starting execution.

Step 11: Custom IRX Modules & Peripherals

launcHER supports user-supplied IOP driver modules and peripheral replacement drivers after storage initialization.

Numbered Driver Modules (MODULE_0.IRX .. MODULE_9.IRX)

These work as in POPStarter r13. Put MODULE_0.IRX through MODULE_9.IRX in the same folder as your POPS files (POPS_IOX.PAK / POPS.PAK), normally the device's POPS folder; other folders are not searched. A module whose IOP name starts like one of POPS's own (sio2man, padman, libsd, sdr_driver, dev9, atad, hdd, pfs) replaces POPS's copy. They start in numerical order after the IOP reset (hdd and pfs get POPStarter's arguments), and one that fails to start stops the launch. For SB. launches modules 5 to 9 start after the network stack. Not yet tested on a console.

Named Peripheral Drivers

Place driver modules into your game directory, VMC directory, or memory card to support specialty hardware:

Driver Manifests (MODULES.TXT & IRX.TXT)

To load arbitrary module files, create MODULES.TXT or IRX.TXT containing file paths or filenames (one module per line). Paths can be absolute (e.g. mc0:/IRX/USBMOUSE.IRX) or relative to the game directory.

Search Locations

launcHER searches for custom IRX modules and manifests in this priority order:

  1. Per-game Virtual Memory Card folder (vmcDir).
  2. The active game .VCD directory (vcdDir).
  3. Dedicated IRX subfolder: <vcdDir>IRX/.
  4. Memory Card slot 1: mc0:/POPSTARTER/ and mc0:/POPS/.
  5. Memory Card slot 2: mc1:/POPSTARTER/ and mc1:/POPS/.