Not stock POPStarter#
POPSLoader is a separate launcher line. It can make a POPStarter library easier to browse, and modern forks add device support that stock POPStarter never had, but its folder rules and settings should not be presented as original POPStarter core behavior.
Original POPSLoader#
El_isra's POPSLoader is described as a Lua/Enceladus launcher for POPStarter. Its practical rule is simple: keep POPSLOADER.ELF and the POPSLDR/ folder together. If that folder is missing or moved, the launcher may boot but lose its resources, list handling, or expected UI files.
mass:/APPS/PS1_POPSLDR/POPSLOADER.ELF
mass:/APPS/PS1_POPSLDR/POPSLDR/
mass:/APPS/PS1_POPSLDR/title.cfg
Modern fork boundary#
| Capability | Where it belongs | Do not confuse it with |
|---|---|---|
| MX4SIO / MMCE / expanded USB device flow | POPSLoader fork behavior. | Original POPStarter storage support. |
| BDMA mode selection | Fork setting for non-HDD devices; only one active BDMA mode should be selected. | Native exFAT support inside POPStarter core. |
| APAHDD support and HDD launch fixes | Fork release behavior and hardware-tested notes. | The older POPStarter HDDOSD/KELF install route. |
| Triangle exit-menu shortcut | POPSLoader fork exit menu behavior. | Stock POPStarter IGR menu commands. |
| Art paths and UI resources | Fork/launcher presentation layer. | POPStarter compatibility, VMC, or POPS emulator behavior. |
Device-mode checklist#
- Confirm the fork expects
mc0for the current setup before moving support files tomc1. - For USB, MX4SIO, or MMCE paths, enable BDMA only for the device family you are actually using.
- Keep
POPSTARTER.ELFon a path the fork documents for the selected backend. - Keep VCDs in the backend's normal POPS location: USB-style
POPS/for removable devices or HDD__.POPSfor APA/PFS. - If games vanish from the fork UI, debug the launcher device setting before rewriting POPStarter game folders.
Documentation rule#
If a setup step names POPSLoader, BDMA, MX4SIO, MMCE, fork art, or fork exit-menu behavior, label it as launcher/fork behavior. If a setup step names CHEATS.TXT, PATCH_#.BIN, TROJAN_#.BIN, DISCS.TXT, VMCDIR.TXT, or POPStarter's storage prefixes, it may belong to POPStarter core.