Downloads GitHub

USB Mass Storage

USB flash drives, hard disks and card readers are the most flexible storage Launchstation supports: application library, file transfers, PS2 ISOs for Neutrino, POPStarter VCDs and Ember games can all live on a FAT32 or exFAT USB disk.

What is supported

Using USB

  1. Plug the drive in. If Auto-start USB storage is on (Settings > Storage & devices > Start devices automatically, default off) USB is ready when the dashboard opens. Otherwise the device card reads Not connected (dim) until you open it.
  2. Open MASS in the Files tab device cards. Launchstation loads the USB drivers (USB host, BDM, BDM file system, USB mass storage), then probes up to four times, 0.6 s apart. It accepts the first drive and waits a short time for a second.
  3. When drives are found there is one card per logical unit (MASS 0, MASS 1…, status Ready). If none is found the card reads Connect a USB storage device.

The USB card also appears with a legacy alias mass: (the first available unit). Do not hard-code mass0:: attach order, partitions and other BDM devices (MX4SIO, iLink) all take numbers from the same massN: namespace.

Using USB for games

ContentLayout
Applicationsmass:/APPS/<app>/ and mass:/BOOT/<app>/ are scanned by default for the Home application library (one sub-folder deep).
PS2 ISO (Neutrino)Any folder; Neutrino can be on the same disk in /neutrino/ (or on a memory card). Backend usb.
PS1 VCD (POPStarter)POPS/*.VCD at the root; POPS/POPSTARTER.ELF is found automatically.
PS1 CUE/BIN/EXE (Ember)<folder>/games/<Game>/ with ember.elf and bios.bin in the folder above games. USB gets a dedicated remount hand-off.

Stability notes

Diagnostics

Tools > USB unit diagnostics shows the cached logical-unit mask with no I/O, or probes unit 0 or unit 1 one at a time. Each manual probe could freeze a failing console; use it deliberately. Logical usb0:/usb1: numbers do not identify physical ports.

Troubleshooting

  1. “No USB storage device was found”. Check the drive is FAT32/exFAT and has a partition table the console can read; try one drive at a time and a different port.
  2. Second drive missing. It may enumerate after the probe window. Use Check again on the USB card, or attach it before opening USB.
  3. A path with a remembered unit number fails. Re-pick the unit from the device list; numbering follows attach order.
  4. Freezes at start. Boot with only one drive, try a powered hub, and record whether MMCE/MX4SIO/UDPFS were started first. Include the exact build hash.