Repository navigation
configuration
Classic CNF compatibility is retained while dashboard features add their own state.
Important modern keys include:
| Key | Purpose |
|---|---|
POPSTARTER_ELF |
Preferred POPStarter executable for VCD images. |
EMBER_DIR |
Ember ELF path; the historical key name is retained. Older folder values still resolve to their ember.elf. The executable 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. |
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.
Launchstation keeps the R3Z startup searches for LAUNCHELF.CNF and IPCONFIG.DAT. The dashboard selects one folder at startup: the configured CNF_Path override when set, otherwise the folder containing the loaded LAUNCHELF.CNF. DASHBOARD.CNF, DASHAPPS.CNF, DASHLIB.CNF and per-game Neutrino profiles all load and save in that same folder.
Missing dashboard files use defaults; they do not trigger searches in CWD, either memory card or another device. App lists in the selected folder can still load when DASHBOARD.CNF is absent. If no main configuration was loaded, the dashboard uses the already-selected startup configuration directory. No files are moved or copied between locations. An unavailable or read-only selected folder does not cause dashboard writes to be redirected elsewhere.
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.
LAUNCHSTATION repository · Live documentation · Release downloads
Maintained from documentation sources. Do not edit generated pages directly; propose changes in the source repository.