Configuration Files & Paths
Classic CNF compatibility is retained while dashboard/cloud features add their own state.
LAUNCHELF.CNF
Important modern keys include:
| Key | Purpose |
|---|---|
POPSTARTER_ELF | Preferred POPStarter executable for VCD images. |
EMBER_DIR | Preferred Ember umbrella directory. Its ember.elf can be staged into a game device's umbrella when needed. |
NEUTRINO_ELF | Preferred Neutrino executable. |
REBOOT_IOP_ELFLOAD | Generic normal-ELF reset behavior. Neutrino ISO handoff deliberately does not use it. |
CNF_Path | Configuration load/save override. |
USBKBD_FILE / KBDMAP_FILE | USB keyboard driver/map paths. |
Save locations
The dashboard can save classic configuration to the configured folder, next to the running ELF or a memory-card SYS-CONF target. The path used to load configuration is tracked so the UI can explain where state came from.
Device path behavior
Launchstation has user-facing paths such as mass:, usb:, hdd0:/partition/ and mc:/, then resolves them into the concrete driver/mount needed for I/O. External-core launch code must distinguish that internal I/O path from the public path syntax the external core expects.
Cloud files are separate
OAuth client configuration, trust roots and refresh tokens are deliberately kept out of LAUNCHELF.CNF. See Cloud sidecars.