OPL Virtual Memory Cards (VMC): Save Without a Physical Card

One VMC per game, stored on your USB/SD/HDD — no juggling physical cards, and no 8MB limit across your whole library.

Short answer: In OPL, highlight a title, press Triangle for its settings, choose Configure VMC, and assign an 8MB virtual memory card to Slot 1 (and Slot 2 if the game uses it). Save Changes. From then on, that title saves to the VMC file on your storage instead of a physical card. Keep a physical card as a backup for your most important saves.

Create a VMC

• Highlight the title in OPL and press Triangle.
• Choose Configure VMC.
• Set VMC Slot 1 to an 8MB virtual memory card (create a new one if prompted; name it after the title so you can find it later).
• Repeat for Slot 2 only if the title needs two cards.
• Save Changes, then launch the title and save in-game normally — the game sees the VMC as a normal card.

Good practice

• One VMC per title is the cleanest setup. Sharing one VMC across many titles recreates the 8MB squeeze you were escaping.
• Back up VMC files to your PC regularly. A VMC is a file on USB/SD/HDD storage, and storage fails — a backup is a copy on another drive, not a second copy on the same stick.
• If a game reports a corrupt save on a VMC, try the physical card for that title to isolate whether the VMC file or the title’s save code is at fault.
• VMC files live on the same storage as your games, so a storage format change (for example, reformatting USB) deletes them too — back up first.

Next steps

• OPL storage comparison
• Slim MX4SIO setup
• Install FreeMCBoot with FreeDVDBoot

Verified against: OPL VMC workflow (Triangle → Configure VMC → 8MB VMC Slot 1) per MX4SIO/OPL guides, checked 2026-10-24.

OPL Game Naming: GAMEID Titles and OPL Manager

Half of all “game not showing in OPL” reports are a filename problem. The rule is short — and older OPL builds enforce it strictly.

Short answer: Name each image GAMEID.TITLE.iso — for example, SLUS_216.05.Gitaroo_Man.iso — and put it in DVD/ (large images) or CD/ (small images) on your storage. Older OPL builds enforce this naming strictly and will not list a mistitled file. OPL Manager on a PC automates renaming, artwork, and list building so you do not have to do it by hand.

The naming rule

• Format: [GAME_ID].[GAME_TITLE].iso — the ID first, then a dot, then the title, then .iso.
• Example from the FAQ: SLUS_216.05.Gitaroo_Man.iso.
• Find the ID on the original disc sleeve or in the image’s SYSTEM.CNF file (the boot file variable).
• Do not use spaces or special characters the PS2 filesystem dislikes in the title part; underscores are the safe separator.
• Keep the extension .iso lowercase and exact.

Folders

On USB and MX4SIO storage, large images (over 700MB) go in DVD/ and small ones in CD/. On an exFAT HDD (Grimdoomer build) the same split applies. On an HDLoader-formatted HDD, games are installed records, not loose files, so this naming rule does not apply in the same way — see the Fat HDD guide.

OPL Manager

• OPL Manager (OPLM) on a PC reads your storage, renames files to the GAMEID format, downloads cover art, and writes the list OPL displays.
• Use it to fix a whole library at once instead of renaming files one by one.
• After OPL Manager changes, reinsert the storage and refresh the list in OPL. If a title still does not appear, check its ID first — OPL Manager can only work with the ID it finds in the image.
• Do not share artwork or lists built from titles you do not own; OPL Manager’s art server has rules about that, and the point of naming is your own library, not distribution.

If a title still will not list

• Check the ID against SYSTEM.CNF — a wrong ID is the classic cause (see also the magenta debug colour note in OPL colour screens).
• Check the folder (DVD vs CD) and the filesystem (FAT32 for USB; per-build format for MX4SIO/HDD).
• Check the file copied completely — a truncated copy from an interrupted transfer lists nowhere.

Next steps

• OPL storage comparison
• OPL virtual memory cards
• OPL colour screens

Verified against: OPL naming convention (GAMEID.TITLE.iso, DVD/CD folders) per OPL documentation and the FAQ’s worked example SLUS_216.05.Gitaroo_Man.iso, checked 2026-10-24.

PS2 Slim MX4SIO Setup for OPL: SD Card, Folders, and Settings

The Slim storage upgrade: an SD card in the memory-card slot, faster than USB, no network adapter needed.

Short answer: Format a microSD card (exFAT with 32KB clusters per vendor guides, or FAT32 depending on your OPL build — follow your build’s requirement), create DVD/ and CD/ folders at the root, copy your images in, insert the card into the MX4SIO adapter in a memory-card slot, boot with a FreeMCBoot/Fortuna card in the other slot, and in OPL set BDM Mode to BDM Devices with MX4SIO on and HDD off, then Save Changes.

What you need

• An MX4SIO (also sold as MC2SIO/SIO2SD) adapter — a small board that plugs into a PS2 memory-card slot and holds a microSD card.
• A microSD card. Vendor guides recommend exFAT with 32KB clusters; other community guides say FAT32 or exFAT depending on OPL version. If one format fails to list games, try the other before blaming the adapter.
• A FreeMCBoot or Fortuna memory card to boot OPL — the MX4SIO card is not a memory card and cannot boot the console by itself.
• An OPL build with MX4SIO/BDM support (recent OPL builds; older OPL 0.9.x will not do this).

Steps

• Format the microSD card (exFAT 32KB clusters first; FAT32 as the fallback).
• Create DVD/ and CD/ folders at the card root. Put images over 700MB in DVD/ and smaller ones in CD/ — that split mirrors the discs’ real capacities and is how OPL sorts them.
• Copy your OPL configuration files to the card root if your kit/guide provides them.
• Insert the microSD into the MX4SIO adapter, then the adapter into a memory-card slot (the slot may feel slightly uneven on hand-assembled adapters — that is normal per vendor notes).
• Boot with your FMCB/Fortuna card, launch OPL, go to Settings: BDM Mode = BDM Devices, USB = On (harmless), iLink = Off, MX4SIO = On, HDD (GPT/MSR) = Off, Default Menu = BDM Games. Save Changes.
• Return to the game list. If games do not appear after a reboot, remove and reinsert the MX4SIO adapter — vendor guides note the list sometimes needs that refresh.

Limits to know

• Compatibility varies by console, OPL build, and SD card brand — some SD cards that work fine in a camera misbehave here. If one card fails, try another brand before replacing the adapter.
• MX4SIO is faster than USB but slower than a Fat internal HDD. That is the expected trade-off, not a defect.
• Virtual memory cards work from OPL on MX4SIO (highlight a title, Triangle, Configure VMC) — see VMC guide.

Next steps

• OPL storage comparison
• Slim MX4SIO kit buying guide
• OPL virtual memory cards

Verified against: MX4SIO vendor setup guides (exFAT 32KB clusters; DVD/CD folders; BDM Devices, MX4SIO On, HDD off) and community MX4SIO documentation, checked 2026-10-24. FAT32-vs-exFAT variance is stated, not hidden.

PS2 Fat HDD Setup for OPL: Network Adapter, SATA Adapter, and Format

The fastest OPL setup, and the one with the most parts to get right. Get the adapter genuine and the format matches your OPL build.

Short answer: Fit a network adapter (SCPH-10281) to the Fat’s expansion bay, attach a drive with a SATA adapter if you use a SATA drive, format it for OPL (HDLoader format for classic OPL, or exFAT if you use a Grimdoomer OPL build that supports it), copy your library into the right folders, and enable HDD in OPL settings. Test with one title before copying a whole library.

Parts

• Network adapter (SCPH-10281) — the Fat expansion-bay unit with IDE connector and Ethernet port. Genuine adapters are the reliable choice; clone adapters vary (see the Fat HDD kit guide).
• Drive: a 2.5-inch SATA SSD/HDD with a SATA-to-IDE adapter, or a 3.5-inch IDE drive if you already own one. SSDs are silent and draw less power; large HDDs are cheaper per gigabyte.
• SATA adapter if your drive is SATA — the original network adapter speaks IDE, so a SATA drive needs the small adapter board that sits between drive and adapter.

Format: match your OPL build

Classic OPL expects an HDLoader-formatted drive (formatted with a PC tool such as HDL Dump / HDLGameInstaller or from the PS2 itself with a formatter). Grimdoomer’s OPL builds support exFAT-formatted internal HDDs instead, which is much easier to manage from a PC (just copy files into DVD/ and CD/ folders). Pick one path and stick to it: an HDLoader drive and an exFAT drive are not interchangeable, and mixing them is the most common cause of “OPL sees no games on HDD”.

Steps (exFAT path, Grimdoomer build)

• Fit the drive to the network adapter and the adapter to the console’s expansion bay.
• Format the drive exFAT on a PC (or let your OPL build’s tooling do it).
• Create DVD/ and CD/ folders at the root and copy your images in (large images to DVD/, small ones to CD/ — the same split OPL uses on USB/MX4SIO).
• In OPL settings, enable HDD, set the default menu to HDD games if you want, and Save Changes.
• Reboot into OPL and confirm one title lists and boots before copying the rest.

Steps (HDLoader path, classic OPL)

Format with an HDLoader tool, install titles with that tool (which writes the HDLoader game records, not just files), then enable HDD in OPL and test one title. Do not copy ISO files directly onto an HDLoader drive and expect OPL to list them — HDLoader drives store games as installed records, not as loose files.

Next steps

• OPL storage comparison
• Fat HDD kit buying guide
• OPL game naming

Verified against: OPL HDD documentation (network adapter SCPH-10281; HDLoader format; Grimdoomer exFAT support), checked 2026-10-24.

uLaunchELF Basics: mass:, mc0:, and Launching Homebrew

FreeDVDBoot drops you into uLaunchELF. Five minutes here saves an hour of guessing later.

Short answer: uLaunchELF (often written uLE or wLaunchELF in FreeDVDBoot) is a file manager that boots from the FreeDVDBoot disc. Its FileBrowser lists devices by short names: mass:/ is your USB drive, mc0:/ is the memory card in Slot 1, mc1:/ is Slot 2, and cdfs:/ is the disc. Select an .ELF file and press Circle (or the button your uLaunchELF build uses for Execute) to run it.

The device names

• mass:/ — USB storage. Only FAT32 with an MBR partition table is reliably visible; NTFS, exFAT, and GPT drives appear empty or freeze the browser (see mass:/ empty).
• mc0:/ — memory card, Slot 1. The install target for FreeMCBoot and Fortuna.
• mc1:/ — memory card, Slot 2.
• cdfs:/ — the optical disc you booted from.
• hdd0:/ — internal hard drive on a Fat with a network adapter (only if formatted and present).

Everyday tasks

• Run an installer: FileBrowser → mass:/ → find FREE_MCBOOT.ELF or the Fortuna installer → Execute.
• Copy files: highlight a file, use the Copy command (R1 menu in most builds), navigate to the destination device, and Paste. Copying OPL into mc0:/BOOT/ is the standard way to make it a permanent menu item.
• Launch a single homebrew: navigate to its .ELF anywhere (USB or disc) and Execute it. No installation is needed to try something.
• Get unstuck: if FileBrowser freezes on mass:/, the USB drive is the suspect — remove it, reboot, and reformat it FAT32/MBR on a PC.

Buttons and configuration

Button mappings in uLaunchELF are configurable and differ slightly between builds, so check the on-screen help in your build before assuming a key. The two things worth configuring early are the default startup path (so uLaunchELF opens where your tools live) and, if you install FreeMCBoot, the FMCB menu entries that point at OPL and uLaunchELF themselves — that way you never need the disc again for daily use, but you keep it as a recovery tool.

Next steps

• Install FreeMCBoot with FreeDVDBoot
• Fix mass:/ empty (USB)
• Build a custom disc

Verified against: CTurt README (uLaunchELF as initial program; run homebrew over USB mass storage) and standard uLaunchELF device naming, checked 2026-10-24.

How to Install Fortuna / OpenTuna Using FreeDVDBoot

For late Slims and wide Fat coverage, Fortuna is the memory-card trigger that FreeMCBoot cannot be.

Short answer: Boot FreeDVDBoot into uLaunchELF, run the Fortuna (or its open-source version OpenTuna) installer from a FAT32 USB drive, and install to your memory card. Afterwards, booting works by scrolling to a memory-card icon in the browser and backing out — the trigger Fortuna exploits. This is the right permanent install for late 900xx Slims and for Fat models where FreeMCBoot is awkward.

What Fortuna is

Fortuna, released 2019-02-12 by krat0s, is a homebrew launcher that works on most PS2 models from SCPH-18000 onward up to the PS2 TV, triggered from the memory-card browser. OpenTuna is the open-source version of the same idea. Neither has been ported to the 10k/15k models, whose compressed OSDSYS programs made the port difficult — if you own one of those, Fortuna is not your path.

Steps

• Boot FreeDVDBoot into uLaunchELF (any Slim, or a supported Fat).
• Insert a FAT32, MBR USB drive containing the Fortuna/OpenTuna installer for your console version. Different console versions need different Fortuna files — use the set that matches your model, not a random download.
• In uLaunchELF FileBrowser, open mass:/ and run the installer ELF.
• Follow the installer’s prompts to install to the memory card.
• Reboot without the disc, go to the browser, scroll to the memory-card icon and back out to trigger Fortuna, and confirm your homebrew launcher appears.
• Add OPL as a launched application so your storage setup (USB, SMB, HDD, or MX4SIO) is one step away.

Fortuna vs FreeMCBoot: which to install

• Choose FreeMCBoot if your console boots it directly (most Fat and early/mid Slims) and you want the classic FMCB menu.
• Choose Fortuna/OpenTuna if you have a late 900xx Slim, or you want the widest model coverage from one trigger.
• You do not need both on the same card for normal use. Pick one, install it cleanly, and keep the FreeDVDBoot disc as your recovery key if the card ever needs reinstalling.

Next steps

• FreeDVDBoot vs Fortuna (comparison)
• Install FreeMCBoot instead
• uLaunchELF basics

Verified against: PS2 Dev Wiki (Fortuna: released 2019-02-12 by krat0s; SCPH-18000 to PS2 TV; not ported to 10k/15k) and CTurt README (run Fortuna installer from uLaunchELF), checked 2026-10-24.

How to Install FreeMCBoot Using FreeDVDBoot (No Modded Console Needed)

This is the whole point of FreeDVDBoot for most people: the disc is the key that makes the memory card, then the disc can go back on the shelf.

Short answer: Boot FreeDVDBoot into uLaunchELF, plug in a FAT32, MBR USB drive containing the FreeMCBoot installer, run FREE_MCBOOT.ELF from mass:/, and install to a genuine Sony 8MB memory card in Slot 1. Reboot without the disc and the console boots into FreeMCBoot. Never buy a pre-installed FreeMCBoot card as the shortcut — FreeMCBoot is distributed under a non-profit rule, and a DIY install gives you a known-good, current setup.

You need

• A burned FreeDVDBoot disc that already boots to uLaunchELF on your console.
• A USB flash drive formatted FAT32 with an MBR partition table (not GPT, not NTFS/exFAT — uLaunchELF cannot see those; see mass:/ empty).
• The FreeMCBoot installer files on that drive, with FREE_MCBOOT.ELF at a path you can find.
• A genuine Sony 8MB memory card (SCPH-10020) in Slot 1 as the install target. Clone 64MB/128MB cards are a common cause of install failures — see memory card errors.

Steps

• Boot FreeDVDBoot and wait for uLaunchELF.
• Insert the USB drive. In uLaunchELF’s FileBrowser, open mass:/ and run FREE_MCBOOT.ELF.
• In the installer, choose the install target (Slot 1 card) and the install type. A normal install is right for most users; multi-install matters only if you plan to move the card between consoles of different regions — read the installer’s own help before choosing it.
• Let the installer finish completely, then power off, remove the disc, and reboot. The console should now boot into the FreeMCBoot menu from the card alone.
• Copy Open PS2 Loader (OPL) into the card’s BOOT folder or set it as a menu item so it is one click away (see OPL storage options).

If the installer will not start

• mass:/ is empty or freezes — USB format problem. Reformat FAT32/MBR and retry.
• Installer starts but fails writing — suspect a clone card. Retry with a genuine 8MB card in Slot 1.
• Console boots to uLaunchELF but the installer ELF is missing — you copied the wrong folder to USB. Re-copy the installer package to the drive root and check the filename.

Late Slim 900xx note

Standard FreeMCBoot does not boot directly on late 900xx (BIOS 2.30+). FreeDVDBoot still gets you into uLaunchELF on those models, but for permanent memory-card booting on a 900xx, install Fortuna/OpenTuna instead (see the Fortuna guide). Installing standard FMCB onto a 900xx card and expecting it to boot is a known dead end.

Next steps

• Install Fortuna instead (900xx)
• uLaunchELF basics
• Install kit buying guide

Verified against: CTurt README (from uLaunchELF, run FreeMCBoot or Fortuna installer) and ConsoleMods FMCB guide (FreeDVDBoot install path), checked 2026-10-24. FMCB non-profit distribution rule per freemcboot.org.

How to Build a Custom FreeDVDBoot Disc with Your Own Homebrew

The prebuilt ISO boots uLaunchELF. A custom disc boots your homebrew selection directly — same exploit, your payload.

Short answer: Take the Slim filesystem directory from CTurt’s repository, copy your homebrew .ELF files into it, generate a UDF (or ISO9660/UDF hybrid) image with VIDEO_TS at the root, and burn it like a prebuilt ISO. uLaunchELF remains the sensible initial program unless you know exactly what you are replacing and why.

Slim custom disc, step by step

• From the repository, use the directory Filesystems/All PS2 slims (3.10 + 3.11) – English language/ — the one that supports all Slim consoles.
• Copy every homebrew .ELF you want on the disc into that directory.
• Generate a UDF image of the directory so that VIDEO_TS sits at the root. On Windows, ImgBurn works and will warn that VIDEO_TS.BUP is missing — click Continue anyway (the README says the PS2 does not require it). On Linux, use the genisoimage command in the Mac/Linux guide.
• Test the image if you can, then burn it to a DVD-R at the lowest speed, finalised, and boot it with the console language set to English.

Replacing the initial program (advanced)

The default initial program is uLaunchELF, recompiled with DVD support. On Slim, the exploit boots VIDEO_TS/VTS_02_0.IFO as an ELF, so replacing that file with another ELF boots that program instead — with a caveat from the README: the first release’s loader does not reimplement a couple of functions around 0x84000–0x85fff and 0x250000–0x29ffff, so the replacement ELF must not overwrite those regions (check with readelf -l). For Phat, the ELF is read from offset 0x5bb000 in the ISO and replaced with a hex editor. If any of that sounds unfamiliar, keep uLaunchELF as the initial program and launch your ELFs from it — that is the supported path, and it is what the prebuilt ISO does.

Phat custom discs

The README says Phat custom-disc instructions are “coming soon”. Do not copy Slim custom-disc steps onto a Fat and expect them to work: the Phat payload layout differs. For a Fat, the reliable path is the prebuilt ISO for your DVD Player version, plus USB-loaded homebrew from uLaunchELF.

What belongs on a custom disc

Homebrew you wrote or that is openly distributed as homebrew: file managers, installers (FreeMCBoot, Fortuna), emulators, and utilities. Do not put commercial game images or BIOS files on a custom disc, and do not distribute a disc that contains them — the site’s anti-piracy line in the disclaimer applies to custom discs too.

Next steps

• uLaunchELF basics
• Install FreeMCBoot with FreeDVDBoot
• Burn with ImgBurn

Verified against: CTurt FreeDVDBoot README (Custom disc setup – Slim; Replacing the initial program – Slim/Phat), checked 2026-10-24.

How to Burn FreeDVDBoot on Mac and Linux (No Windows Needed)

Windows is not required. The disc your PS2 needs is the same; only the burning tool changes.

Short answer: On macOS, burn the ISO with Disk Utility (Burn) or from Terminal with hdiutil burn, at the slowest speed. On Linux, use Brasero (Burn Image) or genisoimage to make and then burn the image. In every case: DVD-R, lowest speed, finalised disc, and the PS2 language set to English before booting.

macOS: Disk Utility

• Insert a blank DVD-R (use an external USB burner if your Mac has no drive — see the burn kit guide).
• Open Disk Utility, choose File → Open Disk Image, and select the FreeDVDBoot .iso.
• Select the image in the sidebar and click Burn, choosing the slowest speed offered.
• Eject only after the burn completes. Do not rename or mount-then-copy the ISO contents — the PS2 needs the image burned as an image.

macOS: Terminal (hdiutil)

From Terminal: hdiutil burn -speed 1 /path/to/FreeDVDBoot.iso — adjust the speed to the lowest your drive reports if 1 is rejected, and confirm the correct burner device if you have more than one drive attached. Verify the burn by letting hdiutil complete its verification pass where offered.

Linux: Brasero

• Open Brasero and choose Burn Image.
• Select the FreeDVDBoot .iso, insert a blank DVD-R, and set the burning speed to the lowest available.
• Make sure the disc is finalised (Brasero finalises DVD-Video burns by default; do not enable multisession).
• Burn and let the verification pass run.

Linux: genisoimage (custom discs and command-line burns)

For a custom disc, the README’s own command is: genisoimage -udf -o exploit.iso "Filesystems/All PS2 slims..." — with VIDEO_TS at the root of the directory you image. Burn the resulting image with your usual tool (for example, wodim -v -dao speed=1 dev=/dev/sr0 exploit.iso or Brasero’s Burn Image), again at the lowest speed. For a prebuilt ISO you do not need genisoimage at all — burn the downloaded .iso directly.

After burning, the same PS2 steps

Language to English, disc in, wait for uLaunchELF. A Mac/Linux burn that fails to boot has the same suspects as a Windows burn: disc type, speed, finalisation, and laser wear — see black screen.

Next steps

• Burn with ImgBurn (Windows)
• Build a custom FreeDVDBoot disc
• Full compatibility list

Verified against: CTurt FreeDVDBoot README (Linux genisoimage command, verbatim) and standard Disk Utility / hdiutil / Brasero Burn Image workflows, checked 2026-10-24. Speed values are drive-dependent; the guide says lowest available, not a guaranteed 1x on every drive.

How to Burn FreeDVDBoot with CDBurnerXP (The 1x-Speed Path)

The alternative burner the README itself names — useful precisely when ImgBurn fails on your hardware.

Short answer: In CDBurnerXP, choose Burn ISO image, load the FreeDVDBoot ISO, select a DVD-R, set the speed to 1x (or the lowest available), enable finalise, and burn. This path is worth trying when ImgBurn produces a disc your PS2 cannot read, because the README records users for whom CDBurnerXP at 1x with compatibility settings and finalise worked where ImgBurn did not.

Steps

• Open CDBurnerXP and choose Burn ISO image (or Disc → Burn ISO Image).
• Browse to your FreeDVDBoot .iso file. Do not extract it first.
• Insert a blank DVD-R and select your burner.
• Set the burn speed to 1x if offered; otherwise the lowest speed available.
• Make sure Finalise disc is checked, and enable any compatibility setting the program offers.
• Burn, then verify the disc if the program offers a verify pass.
• Set the PS2 language to English and boot the disc.

When to switch burners

Switching burners is a legitimate troubleshooting step, not superstition: different programs write the lead-in and finalisation slightly differently, and an old PS2 pickup is picky about exactly that. The README’s troubleshooting section records this as a user-reported fix, not a guaranteed cure — if CDBurnerXP also fails, the next suspects are the disc brand, the burner itself, and the laser (see red screen and laser replacement).

What not to do

• Do not burn the ISO as a data file (a disc containing one .iso file will not boot).
• Do not use DVD+RW for your first attempt — lower reflectivity plus a worn laser is a bad combination.
• Do not skip finalise: an unfinalised DVD-Video structure is exactly what the DVD Player firmware needs to read cleanly.

Next steps

• Burn with ImgBurn
• Burn on Mac or Linux
• Burn kit buying guide

Verified against: CTurt FreeDVDBoot README troubleshooting (CDBurnerXP with 1x speed, compatibility settings, finalize worked for users where ImgBurn did not), checked 2026-10-24.