getting started

Getting Started

Install the correct app variant, open the four-tab dashboard and begin with the actual file browser.

Real hardware, real risk

Launchstation runs on a physical PlayStation 2 (or PSX DESR). It can write memory cards, HDDs and flash. Back up anything you care about before using destructive tools, and treat "builds in CI" as separate from "verified on my console".

1. Download the current package

Use the verified rolling release. Choose APP_LAUNCHSTATION.zip for standard PS2 controllers or APP_LAUNCHSTATION-DS.zip for the variant that adds PS3/PS4 DualShock USB/Bluetooth support. The matching .psu packages contain the same files for memory-card installation. If unsure, take the standard package.

2. Install the app folder

mc0:/
└── APP_LAUNCHSTATION/
    ├── LAUNCHSTATION.ELF
    ├── title.cfg
    ├── BGM.ADP
    └── WLE-UPDATE-CA.PEM

Extract the ZIP as a folder to any storage your launcher can boot from, or copy the PSU in the File Browser and choose Extract PSU inside a memory-card folder. The DS package uses its own folder, APP_LAUNCHSTATION-DS, and LAUNCHSTATION-DS.ELF. Keep existing settings and customized sidecars when upgrading. The ELF runs without BGM.ADP (music) and WLE-UPDATE-CA.PEM (needed only for HTTPS update checks); the packages include both. See Install & Update for boot locations and the in-app updater.

3. Start it

Run LAUNCHSTATION.ELF from whatever you already use to start homebrew: a memory-card exploit or FreeMcBoot-style menu, Open PS2 Loader, another file manager, or PS2Link. The packaged title.cfg is an OPL-style descriptor (title=, boot=) for launchers that read it. The Memory Card Exploit Installer can also bind an ELF as a console boot target when you supply your own PS2KEYS.dat.

4. Use the four main tabs

Use L1/R1 to move between Home, Files, Tools and Settings. Home includes the Applications library and, once known, Last folder. Files opens the native browser immediately; choose a drive or folder there. Tools contains classic MISC commands and specialist utilities. START opens the global menu. Current UI map and controls.

5. Open a device

Start in Files, at the device root. Memory cards, USB/MASS, MMCE, MX4SIO, internal HDD/ATA, iLink, PC CARD CF and configured network devices have distinct availability rules, and entries that cannot exist on your console model are hidden. Not checked usually means opening the device must start a lazy-loaded driver. USB units can change numbering. Avoid simultaneous writes across recovery or backup operations. Device support.

6. Find applications

Use Home > Applications for the library, or browse and launch an ELF directly from Files. Under Settings > Home & applications > Application library, configure application folders and refresh the library. The default roots currently include mc:/APPS, mc:/BOOT, mass:/APPS and mass:/BOOT, one level deep. Applications outside these folders can still launch from Files. SELECT cycles Grid, List and Carousel views.

7. Optional external cores

Neutrino is needed for PS2 .ISO; POPStarter for PS1 .VCD; Ember for PS1 .CUE/.BIN/.EXE in its save-safe game-folder layout. These external programs and game/BIOS data are not bundled. Set their paths under Settings > Launching > Disc & image loaders if automatic discovery does not find them, and read the specific guide before your first handoff.

8. Make it yours

Pick a theme under Settings > Appearance (themes and wallpapers), choose a language under Settings > System > Language, and review Settings > Sound for music and effects. If your console has a dead CMOS battery, set the software clock under Settings > System. Settings has explicit Save/Discard semantics: changes preview immediately and are stored when you choose Save changes.

9. Configure MMCE backups if needed

Choose a local backup destination under Settings > Storage & devices > MMCE backups. Link Google Drive only if desired. A verified snapshot can be recovered to a new file, not directly over an active MMCE card. See MMCE recovery.

10. Update safely

Before upgrading, retain a backup of your configuration and current working ELF. With a wired network configured, Settings > Storage & devices > MMCE backups > Check for updates verifies that the rolling release is a descendant of your build, checks the package's SHA-256, replaces the ELF only after everything verifies, and leaves the old executable beside it as .BAK for rollback.

If something goes wrong

See Troubleshooting and the FAQ. A useful bug report names the build commit (Tools > About Launchstation), console model, storage devices and exact steps.