P1POPStarter DocsRecovered preservation manual
Setup Storage Reference Archive

Setup Paths

The manual chapter for boot flow, launcher selection, minimal files, memory-card folders, and first-boot verification.

Read this before copying files#

POPStarter setup is path-sensitive. A correct file in the wrong folder is effectively missing, and a correct launcher prefix for one backend can select the wrong mode on another backend.

Boot flow#

Frontend or ELF browser
  -> renamed POPSTARTER.ELF or POPSTARTER.KELF
    -> resolve storage backend from prefix/path
      -> locate VCD
        -> locate per-game support folder
          -> apply CHEATS.TXT / PATCH / TROJAN / handlers
            -> hand execution to POPS

Minimal path checklist#

  1. Choose one storage backend: USB, internal HDD, or SMB.
  2. Choose one launcher model: renamed ELF, OPL Apps, OPL DB/PS1 page, wLE_kHn, POPSLoader, or HDDOSD/KELF.
  3. Keep the VCD basename, renamed ELF, and support folder aligned for that model.
  4. Put common POPS files only in the backend-specific common folder.
  5. Put game-specific commands, VMCs, patches, and handlers in the per-game support folder.

First boot verification#

CheckpointWhat to inspectWhere to go next
Frontend sees entrytitle.cfg, app folder, renamed ELF, OPL path prefix.Launcher Matrix
POPStarter startsCorrect backend prefix/path, required POPS support files, VCD basename.Storage Backends
Game reaches PS logoPOPS payload identifiers, config bytes, compatibility mode, display commands.Reference Tables
Save or IGR failsVMC folder, share write permission, IGR command, BOOT.ELF exit chain.Troubleshooting

Memory-card folders#

SMB modules and many driver overrides are loaded from mc0:/POPSTARTER/ with mc1:/POPSTARTER/ fallback in later builds. Do not confuse this memory-card folder with a PC/NAS share named POPSTARTER.