Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:SYSTEM.CNF (PlayStation boot file)

From ReverseEngineering.wiki
Format
On this wiki Facts · Code · Notes · Topics

The text file in the root of a PlayStation or PlayStation 2 disc that names the boot executable: BOOT = cdrom:\SLUS_xxx.xx;1 on a PS1 disc, BOOT2 = cdrom0:\SLUS_xxx.xx;1 on a PS2 disc, plus VER and VMODE lines.

Overview

The BIOS reads SYSTEM.CNF from the ISO 9660 root (Format:ISO 9660) and starts the executable it names: a Format:PS-X EXE on Platform:PlayStation discs, an ELF (Format:ELF (Executable and Linkable Format)) on Platform:PlayStation 2 discs. The file is plain ASCII text with KEY = value lines, CR/LF or LF line ends.

Keys

  • BOOT = cdrom:\SLUS_000.67;1 PS1 disc. Without SYSTEM.CNF the PS1 BIOS tries PSX.EXE.
  • BOOT2 = cdrom0:\SLUS_203.18;1 PS2 disc (the path prefix is cdrom0:, cdrom: is also accepted by emulators).
  • VER = 1.00 software version of the disc.
  • VMODE = NTSC or PAL video mode (PCSX2 prints it as the disc region type).
  • PS1 files also carry TCB = 4 (maximum threads, hex), EVENT = 10 (maximum events, hex) and STACK = 801FFF00 (stack top, hex) lines, per psx-spx (not 801FFFF0, which is the usual stack in boot EXE headers); an argument after the BOOT path (up to 128 bytes) is copied to RAM 0x180. See Fact:SYSTEM.CNF (PlayStation boot file)/behavior/PS1 keys TCB EVENT STACK.
  • Unverified: PS2 discs may add HDDUNITPOWER = NICHDD. Not read in a source here.

How emulators read it

PCSX2 scans the file line by line for BOOT2, BOOT, VMODE and VER. A disc is a PS2 disc when the file contains the text BOOT2, a PS1 disc when it contains BOOT only; a disc without SYSTEM.CNF is a PS1 disc when PSX.EXE exists, and Linux disc 2 is recognised by the file P2L_0100.02. The version suffix ;1 of the executable path is ignored (it can be missing, 10 characters long, or different from the ISO entry), and a stray character on the last line is tolerated. The serial is taken from the file name: SCES_123.45 becomes SCES-12345.

How PCSX2 resolves the BOOT2 path to the ELF in the ISO (prefix, leading slashes, ';' suffix, serial) is in Fact:SYSTEM.CNF (PlayStation boot file)/behavior/PCSX2 boot path resolution. Once the name is known, fast boot writes it into the BIOS's EELOAD and the BIOS loads the PS2 executable, see Format:PS2 EE executable (ELF). At the newer PCSX2 commit fc4d0cdf609e, GetPS2ElfName compares the key exactly and the last BOOT2 or BOOT line wins; the older commit cited by the key-parsing fact was 091ab68.

Code & repositories

  • https://github.com/PCSX2/pcsx2 @ 091ab68708a555198d80a7216965481c7ddd0d98 · license: GPL-3.0
    PS2 emulator (GPL-3.0): pcsx2/SIO/Memcard/MemoryCardFolder.h (superblock and directory entry structs), MemoryCardFile.cpp (format check, ECC), pcsx2/CDVD/CDVD.cpp (SYSTEM.CNF parsing).
    Tested on: source read, not run: source read, not run or built · checked 2026-10-19; last activity 2026-10-17; Note: the latest release ships binaries; the wiki links only the source, never the binaries

Pitfalls

  • Games that load their own files do not share the BIOS's tolerance for versions (a PCSX2 comment).
  • The executable name encodes the region prefix: SLUS/SCUS (USA), SLES/SCES (Europe), SLPS/SLPM/SCPS (Japan). Unverified: this mapping is from general knowledge, not read in the PCSX2 source.