Update OPL and Add Apps with uLaunchELF

uLaunchELF is the file manager that lets you maintain a FreeMCBoot setup after installation: copying programs, replacing an old Open PS2 Loader build with a newer one, and adding new applications to the menu. In short, if FreeMCBoot is the launcher and OPL is the game loader, uLaunchELF is the workshop where you keep both up to date. This guide explains how to use it safely, how to update OPL without breaking your menu, and how to add an application so that it actually appears where you expect it.

The direct answer

Launch uLaunchELF from your FreeMCBoot menu, use it to browse the memory card, USB drive, and other storage, copy the new application files to the location your FreeMCBoot menu expects, and, if needed, update the menu entry to point at the new file. The most common mistake is copying a new OPL file to a random folder and expecting the menu to find it. The menu launches whatever path its entry points to, so updating an application means either replacing the file at that path or updating the entry to the new path, not just getting the file onto the console somehow.

What uLaunchELF is, and what it is not

uLaunchELF, often shortened to uLE, is an open-source file manager and executable launcher for the PS2. It lets you copy, move, delete, and rename files across memory cards, USB drives, hard drives, and other devices the console can see, using the device names the PS2 community uses for them, such as mc0 and mc1 for the two card slots and mass for USB storage. It is a separate program from FreeMCBoot, and it is not included in the standard FMCB 1.966 package, which contains only FreeMCBoot’s own files. If your setup already has uLaunchELF, it probably came from a bundle such as the Noobie package or from a previous application install, and that is normal. If your setup does not have it, add it first by the same method described below, using another working entry point to copy it into place.

Before you change anything: back up first

File management on a launcher card is unforgiving, because deleting the wrong file can remove a menu entry or an application you rely on. Before updating OPL or adding applications, back up the contents of your FreeMCBoot card to a USB drive or a computer, if you have a way to read the card, or at least note down which files your menu entries point to. Keep a copy of the working OPL file you are replacing, so you can restore it if the new build behaves worse for your games. This backup habit matters more than any single update, because OPL builds vary, and a newer build is not automatically better for every title.

Step 1: Launch uLaunchELF and learn the device names

Launch uLaunchELF from the FreeMCBoot menu. Its file browser shows devices, and you navigate into a device to see its folders and files. The two memory card slots appear as card devices, USB storage appears as a mass device, and an internal hard drive appears as a hard drive device where applicable. Take a moment to browse without changing anything, and locate three things: your FreeMCBoot card’s main folders, the folder where OPL currently lives, and the USB device carrying your new files. If you cannot find OPL’s current location, check the FreeMCBoot menu configuration, which records the path each menu entry launches, rather than guessing folders at random.

Step 2: Copy the new files from USB

Insert a USB drive carrying the new OPL build or the new application, prepared on your computer as FAT32 with an MBR partition table for compatibility, as described in PS2 USB Drive Not Detected: MBR, FAT32, and USB 1.1 Issues. A simple USB drive suitable for this job can be found through this USB drive link. In uLaunchELF, browse to the USB device, select the files you need, copy them, then browse to the destination folder on the memory card or hard drive and paste them. Copy, do not move, when you are replacing a working application, so the original remains on USB as a fallback until the new version proves itself. If the USB drive is not detected at all, fix detection first; uLaunchELF cannot copy from a device the console cannot see.

Step 3: Update OPL by replacing the file or updating the entry

There are two clean ways to update OPL, and mixing them is what causes confusion. The first way is to replace the existing OPL file in place: copy the new OPL program over the old file at exactly the same path and filename that the menu entry already points to. The menu entry then launches the new build with no further changes. The second way is to place the new OPL file in a new location, then update the menu entry to point at the new path, using the FreeMCBoot configurator. Either way works, but you must do one of them completely. Copying a new OPL file to a new folder and leaving the menu entry pointing at the old file means the menu will keep launching the old build, and you will conclude, wrongly, that the update failed.

After updating, launch OPL from the menu and check that it opens, that your game list still appears, and that a test title launches. Test one title that worked before, and one title you care about, before declaring the update a success. If the new build behaves worse, restore the backed-up old file by the same replace-in-place method. OPL setup and modes are covered in Open PS2 Loader Setup: USB, SMB, and HDD Modes, and game-list problems after an update are usually folder, filename, or mode issues, covered in OPL Games Not Showing or Black Screen When Launching.

Step 4: Add a new application to the menu

Adding an application follows the same pattern: copy its program files to a sensible folder on the card or drive, then create or update a FreeMCBoot menu entry that points at its main executable file. Use the FreeMCBoot configurator to add the entry, giving it a clear name you will recognise later, and save the configuration before exiting. Test the new entry immediately by launching it from the menu, rather than adding several applications at once and then trying to work out which one broke the menu. Keep application folders tidy, with one folder per application, because a card full of loose executable files in the root becomes unmaintainable quickly.

For applications that need their own data folders, such as configuration files or game folders, place those folders where the application’s own documentation says they belong, not where it seems convenient. An application that cannot find its data folder will often launch and then fail silently, which looks like a broken program when it is really a folder placement problem.

Frequently asked questions

Is uLaunchELF included in FreeMCBoot 1.966?

No. The standard 1.966 package contains only FreeMCBoot’s own files. uLaunchELF is a separate program, often supplied in community bundles, which you add afterwards.

Why does the menu still launch the old OPL after I copied the new one?

Because the menu entry still points at the old file. Either replace the old file in place at the same path, or update the menu entry to the new path, and then test again.

Can uLaunchELF damage my FreeMCBoot install?

It can if you delete system files without knowing what they are, which is why backups and careful browsing matter. Copying and replacing application files in their own folders is routine maintenance; deleting unknown files from system folders is not.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

MX4SIO and microSD Setup for Open PS2 Loader

MX4SIO is an adapter that plugs into a PS2 memory card slot and lets Open PS2 Loader read games from a microSD card at much higher speeds than the console’s USB ports allow. In short, it gives Slim owners, and Fat owners who do not want an internal drive, a fast storage route that fits in a card slot. This guide explains what MX4SIO is, which card to use, how to set it up in OPL, and what speed and compatibility limits to expect, so you do not buy the wrong combination and blame OPL for a hardware mismatch.

The direct answer

To use MX4SIO, you need three things working together: a FreeMCBoot setup that can launch Open PS2 Loader, an MX4SIO adapter that fits the memory card slot, and a microSD card that OPL can read through that adapter with a compatible OPL build. Put your own game dumps in OPL’s expected DVD and CD folders on the microSD card, enable the MX4SIO or BDM mode in OPL as your build presents it, and launch games from there. If any one of those three parts is wrong, the card will not appear in OPL, no matter how carefully you copy files.

What MX4SIO is, and why it exists

The PS2’s USB ports run at USB 1.1 speeds, which is slow for game loading and can cause stuttering video in USB mode. The memory card slot, by contrast, connects through a faster interface that the MX4SIO adapter exploits to read a microSD card. MX4SIO adapters are community hardware, often sold under names such as MX4SIO or Bitfunx adapters, and they are not Sony products. That community origin matters: build quality and compatibility vary between sellers, OPL support for MX4SIO depends on using a build that includes it, and setup details can differ slightly between adapter versions. Buy from a seller with clear compatibility information, and keep the adapter packaging and instructions, because they are part of the setup, not an afterthought.

MX4SIO compared with the other OPL storage routes

MX4SIO is most valuable on Slim consoles, which have no internal drive bay, and on Fat consoles where an internal drive setup is not wanted. It does not replace FreeMCBoot, and it does not replace OPL; it is a storage route inside OPL, just as USB, SMB, and HDD are storage routes. If you already have a working internal HDD setup on a Fat console, MX4SIO is an alternative rather than an upgrade you must make.

What you need

For hardware, the adapter and the card should be bought together as a matched pair in your planning, even if you buy them separately. A suitable adapter can be found through this MX4SIO link or this adapter link, and a good quality microSD card through this microSD link. Avoid the cheapest unbranded cards for this job, because a card that is slow or unreliable in a phone will be slow or unreliable in a PS2 as well, and card faults look exactly like OPL faults. Do not buy an adapter or card sold with games preloaded; use only your own dumps.

Step 1: Confirm FreeMCBoot and OPL work first

Before touching MX4SIO, confirm that FreeMCBoot boots and that OPL launches, following How to Install FreeMCBoot 1.966 on PS2: Complete Guide and Open PS2 Loader Setup: USB, SMB, and HDD Modes. If OPL does not launch at all, MX4SIO setup cannot fix that, and you will waste time troubleshooting storage for an application problem. Also confirm that your OPL build includes MX4SIO support. If your build predates MX4SIO support or was built without it, update OPL following Update OPL and Add Apps with uLaunchELF before proceeding.

Step 2: Prepare the microSD card

Format the microSD card as required by your OPL build, and place your own game dumps in OPL’s expected folder layout: DVD games in a folder named DVD and CD games in a folder named CD, at the root of the card. Keep filenames simple, using standard letters, numbers, and usual punctuation, because unusual characters cause games to fail to appear or fail to launch, just as in USB mode. Test with one game first, rather than copying a whole library before you know the adapter and card work. If the card is also used in other devices, do not assume its existing format is suitable; format it for this job, after backing up anything on it you need, since formatting erases the card.

Step 3: Fit the adapter and enable MX4SIO in OPL

Insert the microSD card fully into the MX4SIO adapter, then insert the adapter firmly into a PS2 memory card slot. Which slot to use can matter, depending on the adapter and on whether a FreeMCBoot card also needs a slot, so follow the adapter’s instructions, and if the instructions are silent, try the slot that leaves your FreeMCBoot card in place and working. Launch OPL, enable the MX4SIO or BDM device mode as your OPL build presents it, and refresh the game list. If the list remains empty, check the adapter seating and the card format before changing other settings, because a loose adapter is the most common first-time failure.

Note the slot trade-off: a PS2 has two memory card slots, and MX4SIO uses one of them. If your FreeMCBoot card occupies one slot and the adapter occupies the other, there may be no slot left for a separate save card during MX4SIO play, depending on your setup. Plan for that in advance, for example by keeping saves on the FreeMCBoot card’s free space where appropriate, or by swapping cards between sessions, rather than discovering the trade-off mid-game.

Frequently asked questions

Does MX4SIO replace FreeMCBoot?

No. MX4SIO is a storage adapter used from inside Open PS2 Loader, which itself is launched from FreeMCBoot. You still need a working FreeMCBoot setup first.

Can I use MX4SIO on a Slim PS2?

Yes, and Slim owners benefit most from it, because Slims have no internal drive bay. It fits a memory card slot, which every PS2 has.

Do I need a special OPL version for MX4SIO?

Yes, you need an OPL build that includes MX4SIO support. If your build does not show the relevant device mode, update OPL before troubleshooting the adapter.

Will any microSD card work?

No. Card quality, speed, and format all matter, and a poor card produces faults that look like adapter or OPL faults. Use a good quality card from a reputable brand, formatted as your OPL build requires.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

Open PS2 Loader Setup: USB, SMB, and HDD Modes

Open PS2 Loader, usually called OPL, is the program most FreeMCBoot users actually spend their time in, because it is what loads games from storage instead of from discs. In short, you add OPL to your FreeMCBoot setup, point it at your games on a USB drive, a network share, or an internal hard drive, and launch titles from a menu. This guide covers all three modes, the folder layout OPL expects, and the format choices that cause most first-time failures, without confusing OPL with FreeMCBoot itself.

The direct answer

OPL is a separate program from FreeMCBoot, and it is not included in the standard FMCB 1.966 package. You add it after your FreeMCBoot card or FHDB drive boots, then choose one storage mode: USB for a flash drive or external drive on the console’s USB ports, SMB for games shared over a home network, or HDD for an internal drive in a Fat console. USB is the easiest mode to start with, SMB avoids moving drives around once it works, and HDD is the fastest and most reliable mode on a Fat console, but it requires the network adapter and internal drive setup covered in Install FHDB on a Fat PS2 Internal Hard Drive.

What you need for each mode

For USB mode, an older USB 2.0 drive often works better than a large modern USB 3.0 drive, because the PS2’s USB 1.1 ports are picky about drive controllers. A suitable USB drive can be found through this USB drive link. For HDD mode, match the drive to your network adapter type first, as described in the FHDB guide, with adapters available through this network adapter link and drives through this hard drive link. For SMB mode, you need a stable home network and a share that the PS2 can reach; a wireless bridge or weak Wi-Fi link will cause more problems than the mode itself is worth.

Step 1: Add OPL to your FreeMCBoot setup

Add OPL as an application in your FreeMCBoot menu, following Update OPL and Add Apps with uLaunchELF if you need the file management steps. Place the OPL program where your FreeMCBoot menu expects it, and check that it appears in the menu before worrying about game storage. If OPL itself does not launch, the problem is in the application setup, not in your game folders, and fixing folders first will not help. Once OPL launches and shows its own menu, you are ready to configure a storage mode.

Step 2: Prepare storage and folder layout

OPL expects game files in specific folders at the root of the storage device, with DVD games in a folder named DVD and CD games in a folder named CD. That folder layout is strict: games placed in invented subfolders, or dumped loose at the root, will not appear in OPL’s list. Use only your own dumps and backups, and keep filenames simple, using standard letters, numbers, and the usual punctuation, because unusual characters in filenames are a known cause of games failing to appear or failing to launch. If a game does not appear, folder placement and filename are the first things to check, before assuming the dump or the drive is faulty. Full game-list troubleshooting is in OPL Games Not Showing or Black Screen When Launching.

For USB mode, format the drive as FAT32 with an MBR partition table for maximum compatibility, unless you are deliberately using a modern OPL build with exFAT support for larger files. FAT32 has a file size limit that affects large single files, which is exactly why exFAT support in modern OPL builds matters for some users, but do not switch to exFAT on an older OPL build and expect it to work. If you are unsure which build you have, start with FAT32 and a game that fits comfortably within its limits, confirm that OPL works, and only then experiment with exFAT.

Step 3: Configure USB mode

Connect the prepared USB drive to the console, launch OPL, and enable USB mode in OPL’s settings if it is not already enabled. Refresh the game list and check that your titles appear. If the drive is not detected at all, see PS2 USB Drive Not Detected: MBR, FAT32, and USB 1.1 Issues, because USB detection on the PS2 is a hardware compatibility problem more often than an OPL settings problem. Try a different, preferably older USB 2.0 drive before changing OPL settings repeatedly. USB mode is also the slowest of the three modes in practice, because it runs through the PS2’s USB 1.1 ports, so stuttering video in some games is a known limitation of the mode, not necessarily a sign that anything is broken.

Step 4: Configure SMB mode

SMB mode shares game files over a network from a computer or server to the PS2. In OPL’s network settings, enter the share address, share name, and credentials for your network share, following your network setup, and save the settings. The share must be reachable from the PS2’s network connection, and the game folders on the share must follow the same DVD and CD folder layout as USB mode. Test with one game first, and check that it appears in the list and launches, before copying a large library to the share. If games appear but stutter or fail to load, check the network path first: a wired connection is more reliable than a wireless bridge, and a computer that sleeps during play will interrupt the share. SMB mode avoids moving drives, but it adds a network dependency that USB and HDD modes do not have.

Step 5: Configure HDD mode

HDD mode is for Fat consoles with an internal drive and network adapter. The drive must be prepared for PS2 use, and OPL must be set to HDD mode, with games stored on the drive in OPL’s expected layout. This mode generally gives the best loading performance, because it avoids the USB 1.1 bottleneck, and it is the natural partner to an FHDB install, although HDD mode in OPL and FHDB booting are separate things: you can use OPL HDD mode with a memory card FreeMCBoot install, and you can use FHDB booting with OPL in another mode, if you prefer. If the drive is not detected, check adapter seating and drive compatibility first, as in the FHDB guide, before changing OPL settings.

Frequently asked questions

Is Open PS2 Loader part of FreeMCBoot?

No. OPL is a separate program that you add after FreeMCBoot is installed. The standard FMCB 1.966 package contains only FreeMCBoot’s own files.

Which OPL mode should I start with?

USB mode, because it needs the least extra hardware. Move to SMB if you want network access, or to HDD mode on a Fat console if you want the best performance.

Does OPL support exFAT?

Modern OPL builds support exFAT, but exFAT support belongs to OPL, not to FreeMCBoot. Check the build you are using, and start with FAT32 if you are unsure.

Why do my games not appear in OPL?

The usual causes are wrong folder placement, unsuitable filenames, a drive or share that is not detected, or a mode that is not enabled. Check folders and detection first, as detailed in the OPL troubleshooting guide.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

Install FHDB on a Fat PS2 Internal Hard Drive

FHDB, short for Free Harddisk Drive Boot, is FreeMCBoot installed on a Fat PS2’s internal hard drive instead of on a memory card. Once it is set up, the console boots into the custom menu from the drive, without needing a memory card for the launcher itself. In short, if you have a Fat PS2, a network adapter, and an internal drive, FHDB lets you keep the launcher on the drive and keep both memory card slots free for saves. This guide explains what FHDB is, what hardware it needs, and how to install it without confusing it with a memory card install.

The direct answer

FHDB is only for Fat PS2 consoles that can take an internal hard drive through the network adapter bay. You install it with the FreeMCBoot installer, choosing the hard drive install option, and the finished drive boots the console into the FreeMCBoot menu. Slim consoles cannot use FHDB, because they have no internal drive bay, and late Slims are a separate topic covered in FunTuna and Fortuna for Late PS2 Slim SCPH-9000x. If you have a Fat console and want the launcher on the drive rather than on a card, FHDB is the right tool; if you have a Slim, use a memory card install from How to Install FreeMCBoot 1.966 on PS2: Complete Guide.

What you need

For hardware, the network adapter is the part people most often get wrong, because original IDE adapters and later SATA adapters use different drive types. Match the drive to the adapter you actually have, and do not assume a SATA drive fits an unmodified original adapter. A compatible network adapter can be found through this network adapter link or, for used original hardware, through this used adapter link, and a suitable internal drive through this hard drive link. Check the adapter type first, then buy the drive to match it, not the other way round.

Drive size: the limit you should know before buying

FHDB supports drives up to 2TB, but there is a caveat that matters when buying. If the HDD OSD software on the drive has not had its ATAD module replaced, it may only support up to about 137GB, even on a larger drive. In practice, that means a very large drive is not automatically fully usable, and the usable size depends on the HDD OSD setup, not just on the drive label. Do not buy the largest drive available on the assumption that all of it will be usable in every setup. A moderate drive that matches your adapter and your actual library of your own dumps is usually the better purchase, and you can check how much space the system reports after installation before adding more content.

Step 1: Prepare the drive and adapter

Fit the drive to the network adapter, then fit the adapter to the back of the Fat console, following the adapter’s own fitting instructions. Make sure the drive is seated firmly and the adapter is fully inserted, because a loose adapter produces exactly the kind of intermittent boot failure that looks like a software problem. If the drive is new or previously used for something else, expect it to be prepared or formatted as part of the FHDB process, and do not put data on it that you cannot afford to lose. Back up anything on the drive elsewhere before you start, and keep your game saves on memory cards, since FHDB does not replace save storage.

Step 2: Run the installer and choose the hard drive install

Boot the console through your existing entry point and launch the FreeMCBoot installer. In the installer, choose the hard drive install option rather than the memory card install option. This is the step where a memory card install and an FHDB install diverge, and choosing the wrong target is the most common beginner mistake in this guide. Follow the installer’s screens for the drive target, and do not switch the console off or remove the adapter while the installer is writing. When the installer reports success, exit it cleanly.

If you do not yet have any entry point, build a memory card install first using How to Install FreeMCBoot 1.966 on PS2: Complete Guide, Install FreeMCBoot with FreeDVDBoot (No Modchip), or Install FreeMCBoot from a PC with a PS3MCA Memory Card Adapter, then use that card to run the installer for the hard drive. There is no shortcut that lets a completely stock console install FHDB with no entry point at all.

Step 3: Test booting from the drive

Restart the console with the drive and adapter connected and no FreeMCBoot card inserted, if you want to confirm that the drive itself is doing the booting. A successful FHDB install shows the custom menu on boot from the drive. If the console boots normally instead, check that the adapter is fully seated, that the drive is recognised, and that the installer really completed the hard drive install rather than a card install. If the menu appears only when a FreeMCBoot card is also inserted, the drive install probably did not complete, and you should rerun the installer and check the target selection carefully.

Step 4: Add applications and set up game loading

As with a card install, the standard package adds no applications, so the next step is to add Open PS2 Loader and any other programs you want, following Open PS2 Loader Setup: USB, SMB, and HDD Modes. With FHDB, the hard drive mode of Open PS2 Loader is the natural fit, since the drive is already inside the console, but USB and network modes remain available if you prefer them. Keep your own dumps organised on the drive, and remember that FHDB on its own does not supply games, does not add import-game support, and does not bypass hardware limits on copied discs. Use only your own dumps and backups.

Frequently asked questions

Can I use FHDB on a Slim PS2?

No. Slim consoles have no internal hard drive bay, so FHDB is a Fat-only option. Slim users should use a memory card install, or Fortuna or FunTuna on late Slims.

Do I still need a memory card with FHDB?

Not for booting, but memory cards are still where game saves live, and keeping a FreeMCBoot card as a recovery route is good practice.

Does FHDB include Open PS2 Loader?

No. The standard package contains only FreeMCBoot’s own files. Open PS2 Loader and other applications are added separately after installation.

What is the largest drive I can use?

FHDB supports drives up to 2TB, but if the HDD OSD ATAD module has not been replaced, usable size may be limited to about 137GB. Check what your setup reports after installation.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

FunTuna and Fortuna for Late PS2 Slim SCPH-9000x

Late PS2 Slim consoles cannot boot standard FreeMCBoot on their own, because Sony removed the update behaviour that FreeMCBoot relies on. Fortuna and its FunTuna variant work around that limit with a different trigger: instead of booting automatically at power-on, homebrew is launched manually from the console’s own system browser. If you have a late SCPH-90000 Slim, this is the route to understand before you waste time on a standard install that can never boot on its own on your hardware. This guide explains which consoles are affected, how the trigger works, and how to set it up without overstating what the package contains.

The direct answer

If your Slim is a late SCPH-90000 model made from the third quarter of 2008 onwards, with boot ROM version 2.30 or newer, use Fortuna or FunTuna, not a standard FreeMCBoot install. You prepare a memory card with the Fortuna or FunTuna package, boot the console normally, open the system browser, select the memory card, and back out to the main menu, which triggers the homebrew launcher. It is a manual step on every use, and that manual step is the price of running homebrew on hardware that no longer supports automatic memory card booting.

Which consoles are affected, and how to be sure

FreeMCBoot works on most PS2 consoles, but the exception is specific: late SCPH-90000 Slim models from the third quarter of 2008 onwards, which are usually R-chassis models, with boot ROM 2.30 or newer, plus the PS2 TV. The transition happened during production, so datecode 8C alone does not settle it. Consoles with datecode 8C may or may not be affected, depending on when the patch landed in their production run, and the reliable check is the ROM version. See How to Check Your PS2 Model, Datecode, and ROM Version for how to find the model number, the datecode, and the ROM version, and do that check before choosing a route.

Fortuna itself, released by krat0s in 2019, covers a wide range: from ROM version 1.90, which corresponds to SCPH-18000, through to the last models, including the PS2 TV. It has not been ported to the earliest 10k and 15k models, so those consoles are outside Fortuna’s scope, but they are also not late Slims, and standard FreeMCBoot is the relevant route there. FunTuna is a Fortuna-based variant package aimed at late Slims, and this guide treats it at that level: a package that uses the Fortuna trigger approach for SCPH-9000x consoles. The exact contents of any particular FunTuna package vary by release, so follow the instructions included with the package you actually use, and do not assume a file list from another package or another site applies to yours.

How the manual trigger works

Standard FreeMCBoot replaces the normal browser start-up behaviour, so the custom menu appears automatically. On a late Slim, that automatic path is closed, because the console no longer supports the update mechanism FreeMCBoot depends on. Fortuna instead uses a vulnerability in how the system browser handles memory card data. The practical sequence is: boot the console normally, open the browser, select the memory card, then back out to the main menu. Backing out is the trigger step, and it launches the homebrew environment. That is why guides describe Fortuna as a manual trigger rather than an auto-boot: you repeat the browser step each time you want to enter homebrew, instead of the console doing it for you at power-on.

This difference has everyday consequences worth knowing in advance. A console with Fortuna or FunTuna will look completely normal when switched on, which is expected, not a fault. Family members or guests who just want to play a disc will not be confronted with a custom menu unless they perform the trigger. Conversely, if you expect an automatic menu and do not perform the trigger, you will conclude, wrongly, that the install failed. Judge success by whether the trigger sequence launches homebrew, not by what happens at power-on.

What you need

For the card, use a blank 8MB card where possible, and keep saves on a second card, because preparing a launcher card can involve formatting, which erases saves. A suitable blank card can be found through this memory card link. Do not buy a card sold with software or games preloaded; build the card from the package yourself, so you know what is on it.

Step 2: Prepare the memory card

Prepare the card exactly as the package instructs, using whatever writing method that package supports. Some packages are written from a computer with an adapter, as in Install FreeMCBoot from a PC with a PS3MCA Memory Card Adapter, while others are installed from a console that can already run homebrew. Do not improvise the folder layout, and do not mix files from a standard FreeMCBoot install into a Fortuna card, or vice versa, because the two approaches use different mechanisms. If the preparation step involves formatting the card, back up saves first. Keep the package archive on your computer after preparation, so you can rebuild the card without hunting for the files again.

Step 3: Perform the trigger and check the result

Insert the prepared card, boot the console normally, and open the system browser. Select the memory card, then back out to the main menu, which should trigger the homebrew launcher. If the launcher appears, the setup works, and you can then launch the applications you have added, such as Open PS2 Loader or a file manager, following Open PS2 Loader Setup: USB, SMB, and HDD Modes. If nothing happens, do not immediately rebuild the card; first check that you performed the back-out step correctly, that the card is in the slot the package expects, and that the console really is in the supported range. A trigger that is performed slightly wrong looks identical to a broken install.

Frequently asked questions

Is FunTuna the same as FreeMCBoot?

No. FunTuna is a Fortuna-based variant package for late Slims, while FreeMCBoot is a memory card launcher that auto-boots on compatible consoles. They solve different problems on different hardware, even though both end up launching homebrew.

Do I have to do the browser trigger every time?

Yes. On Fortuna and FunTuna, the trigger is manual on each session. The console boots normally otherwise, which is expected behaviour for this route.

Can I convert a late Slim to auto-boot by installing standard FreeMCBoot as well?

No. The hardware limit that blocks auto-boot on late Slims is not removed by adding a standard install, and mixing the two approaches on one card is likely to cause confusion. Use one approach per card.

Does Fortuna work on the earliest PS2 models?

No. Fortuna has not been ported to the 10k and 15k models. Those consoles are outside its scope, and standard FreeMCBoot is the relevant route there.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

Install FreeMCBoot from a PC with a PS3MCA Memory Card Adapter

A PS3MCA adapter lets you install FreeMCBoot from a computer, without needing a working PS2 disc drive, a modchip, or another modified console. The adapter connects a PS2 memory card to a computer over USB, and installer software on the computer writes the FreeMCBoot files to the card in the console’s own card format. In short, the computer does the job that an already-modified console would normally do, and the finished card then boots a standard PS2 on its own. This guide covers when this route fits, what to buy, and how to run it safely.

The direct answer

If your PS2 disc drive is dead or unreliable, or you have no other entry point at all, the PS3MCA route is the most practical way to build a FreeMCBoot card. You still need a compatible console for the finished card to boot on, and you still need the FMCB 1.966 installer files, but you do not need the PS2 itself to run the installer. Compatibility follows FreeMCBoot’s own rules, so late SCPH-90000 Slim models and the PS2 TV still need Fortuna or FunTuna rather than a standard install, as explained in FunTuna and Fortuna for Late PS2 Slim SCPH-9000x.

What you need

For the card itself, a blank 8MB card is the safest starting point. Large third-party cards cause more install and boot problems than any other single factor, and a card that is awkward to write from a computer is even harder to trust in the console. A suitable blank card can be found through this memory card link. Do not buy a card sold with software or games preloaded; this guide builds your own card from the standard installer.

Step 1: Confirm compatibility before you write anything

Check the console the finished card is meant for. FreeMCBoot works on most PS2 consoles except late SCPH-90000 Slim models made from the third quarter of 2008 onwards, with boot ROM 2.30 or newer, and the PS2 TV. Datecode 8C is a transition period, so check the ROM version if the console falls in that window, using How to Check Your PS2 Model, Datecode, and ROM Version. Writing a standard install for an incompatible console wastes a card preparation, because the card will still not boot on its own on that hardware.

Also decide which card is the FreeMCBoot card and which card holds your saves. The installation process can format the target card, and formatting erases saves. Back up any saves from the target card first, or use a fresh, dedicated card for FreeMCBoot and keep saves on a second card.

Step 2: Install the adapter drivers on the computer

Connect the adapter to the computer and install the drivers supplied with your adapter package, following that package’s instructions exactly. Driver installation is the step where most PC adapter installs stall, usually because a driver was skipped, the wrong architecture version was used, or the adapter was plugged in before the drivers were ready. If the computer does not recognise the adapter at all, try a different USB port, preferably a direct port on the computer rather than a hub, and check whether the driver package distinguishes between 32-bit and 64-bit systems. Do not proceed to writing the card until the computer consistently recognises the adapter with a card inserted, because an intermittent connection during a write is how cards end up half-written.

Step 3: Insert the card and prepare the installer software

Insert the target memory card firmly into the adapter, and open the installer software from your adapter package. The software typically offers a full install, which writes FreeMCBoot plus essential homebrew, and a lighter install, which writes FreeMCBoot with a minimal set. For a first card, the full option is usually the more useful choice, because it leaves you with a file manager available on first boot, but either option produces a working FreeMCBoot card. Read the options in your package before choosing, because package contents vary, and the standard FMCB 1.966 package itself contains only FreeMCBoot’s own files, not Open PS2 Loader, uLaunchELF, or other applications. Any extra applications in a package come from that package, not from the standard 1.966 release, and you can add applications later in any case.

If the installer software asks to format the card first, accept it only if you have backed up saves or are using a fresh card. Formatting is destructive by design, and it is also the step that clears a broken previous install, so it is often the right choice for a recovery rewrite.

Step 4: Write the card and test it in the console

Run the install and leave the card and adapter completely alone until the software reports success. Do not remove the card mid-write, do not let the computer sleep during the write, and do not unplug the adapter early. A half-written card is one of the harder problems to diagnose later, because it can look like a card compatibility problem when it is really an interrupted write. When the software reports success, close it, remove the card from the adapter, insert it into the PS2, and boot the console. A successful install shows the FreeMCBoot menu on boot.

If the console boots normally instead, work through FreeMCBoot Not Booting or Black Screen on Startup and PS2 Memory Card Not Recognized / Third-Party Cards Fail with FMCB. The most likely causes after a PC write are a card problem, a region mismatch, or an incompatible console model, rather than a fault in the adapter itself. If the card boots on one console but not another, suspect region or model differences first.

Frequently asked questions

Do I need a PS2 disc drive for the PS3MCA route?

No. That is the main advantage of this route. The computer writes the card, so the console’s disc drive plays no part in installation, although you still need a compatible console to boot the finished card.

Can I use the adapter on any computer?

Most adapter packages target Windows or Linux. Follow the instructions in the package you have, because driver steps and supported systems vary, and do not assume a package for one system works unchanged on another.

Will a card written by PC work on any PS2?

It will work on compatible consoles, subject to the usual region and model rules. A card written for one region may not boot on a console from another region unless the cross-region option was used correctly, as covered in Cross-Region FreeMCBoot Install Failed or Won’t Boot.

Is the adapter still useful after installation?

Yes. It is the easiest way to rewrite a card, prepare a spare card, or recover from a broken install without needing a console entry point.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

Install FreeMCBoot with FreeDVDBoot (No Modchip)

FreeDVDBoot gives you a way to run the FreeMCBoot installer on a stock PS2 without a modchip, by exploiting the console’s DVD player to launch homebrew from a burned disc. In short, you burn a disc that carries the installer, boot it like a DVD, and use that one-time session to write FreeMCBoot to a memory card. After that session, the memory card itself does the work on every boot, and you no longer need the disc. This guide explains when this route fits, what it requires, and how to run it without confusing FreeDVDBoot with FreeMCBoot itself.

The direct answer

If your console is compatible with FreeMCBoot, has a working disc drive, and you have no modified console, cheat disc, or PC adapter available, FreeDVDBoot is a practical entry point. It does not install anything permanently to the console; it only provides the one-time launch that the FreeMCBoot installer needs. Compatibility still follows FreeMCBoot’s own rules, so late SCPH-90000 Slim models and the PS2 TV are not solved by FreeDVDBoot alone, and you should check your model first in How to Check Your PS2 Model, Datecode, and ROM Version.

When this route is the right choice

Choose FreeDVDBoot when your disc drive still reads burned DVD media reliably, you have a computer with a disc burner, and you do not have another entry point. It is a good fit for Fat consoles and for Slim models that are compatible with FreeMCBoot, provided the laser is healthy enough to read the disc. It is a poor fit when the disc drive is failing, when the console is a late SCPH-90000 that cannot boot standard FreeMCBoot anyway, or when you already have a modified console available, in which case running the installer directly is simpler. If your drive is dead, look at the PC adapter route in Install FreeMCBoot from a PC with a PS3MCA Memory Card Adapter instead, since that route does not need the disc drive at all.

What you need

For hardware, start with a blank 8MB card rather than a large third-party card, because card reliability matters more than card size for a launcher. A suitable blank card can be found through this memory card link. Do not buy a card sold with software or games preloaded; the point of this guide is to build your own card with the standard installer.

Step 1: Confirm the console can use standard FreeMCBoot

Before burning anything, confirm the model. FreeMCBoot works on most PS2 consoles except late SCPH-90000 Slim models from the third quarter of 2008 onwards, with boot ROM 2.30 or newer, and the PS2 TV. Datecode 8C is a transition period, so check the ROM version if your console sits in that window. If you discover a late Slim, stop here and read FunTuna and Fortuna for Late PS2 Slim SCPH-9000x instead, because a standard FreeMCBoot install will not boot on its own on that hardware, no matter which entry point you use.

Step 2: Prepare the FreeDVDBoot disc

Prepare a FreeDVDBoot disc following the FreeDVDBoot project’s own instructions for your console’s DVD player version, since the correct disc image depends on that version. The general pattern is to build or obtain the disc image for your DVD player version, burn it to a DVD-R at a low speed, and verify the burn rather than assuming it worked. Use a fresh, good quality disc, and avoid rewriting the same disc repeatedly while troubleshooting, because a marginal burn looks exactly like a compatibility problem. Keep the disc after installation; you may want it again if you ever need to reinstall or help install a card for another console.

Different DVD player versions need different FreeDVDBoot files, so do not copy a disc image made for another console and expect it to work. If the disc fails to boot, the first suspects are the disc image version, the burn quality, and the laser, in that order, before you blame the FreeMCBoot files.

Step 3: Prepare the installer files

Have the FMCB 1.966 installer ready in the form your FreeDVDBoot setup expects, which usually means the installer program on a USB drive or included in the disc setup, depending on the FreeDVDBoot instructions you are following. Extract the archive on your computer with a tool that handles 7z files, and keep the folder layout intact rather than rearranging files into folders of your own. If your security software quarantines the installer file on extraction, see FMCBInstaller.elf Missing, Quarantined, or Archive Won’t Extract before retrying, because repeatedly extracting into a quarantined folder will keep producing the same missing-file result.

Back up any saves on the target memory card before you begin. The installer may offer to format the card, and formatting erases saves. A dedicated card for FreeMCBoot, with a second card for saves, avoids this risk entirely.

Step 4: Boot the disc and run the installer

Insert the FreeDVDBoot disc and boot the console. When the FreeDVDBoot environment loads, launch the FreeMCBoot installer program from wherever your setup places it. Choose the standard install for your own console unless you have a specific reason to use the multi-install or cross-region options, and read each installer screen before confirming. Do not remove the memory card or switch the console off while the installer is writing. When the installer reports success, exit cleanly, remove the disc, and restart the console with the newly written card inserted.

On a successful install, the console should show the FreeMCBoot menu on boot. If it boots normally instead, check the troubleshooting guide for non-booting installs in FreeMCBoot Not Booting or Black Screen on Startup. Common causes after a FreeDVDBoot session are a card problem, a region mismatch, or a console that was never compatible with standard FreeMCBoot in the first place.

Frequently asked questions

Do I need the FreeDVDBoot disc every time I boot?

No. The disc is only the entry point for installation. Once FreeMCBoot is on the card, the card boots the console on its own, and the disc is only needed again if you reinstall.

Will FreeDVDBoot work if my PS2 laser is weak?

Probably not reliably. FreeDVDBoot depends on the drive reading a burned disc, so a failing laser is a real blocker for this route. In that case, the PC adapter route, which does not use the disc drive, is the better choice.

Can I use FreeDVDBoot on a late SCPH-90000 Slim?

FreeDVDBoot may launch homebrew, but it does not change FreeMCBoot compatibility. A late Slim with boot ROM 2.30 or newer still cannot boot standard FreeMCBoot on its own, so use the Fortuna or FunTuna route for that hardware.

Does the FreeMCBoot installer include Open PS2 Loader?

No. The standard 1.966 package contains only FreeMCBoot’s own files. Open PS2 Loader, uLaunchELF, and ESR are separate programs that you add after the card boots.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.

How to Install FreeMCBoot 1.966 on PS2: Complete Guide

FreeMCBoot 1.966 is installed on a PS2 memory card, not flashed into the console itself, and once it is installed the console boots into a custom menu whenever that card is in the slot. You cannot install it on a completely stock console just by copying files from a computer, because the PS2 needs an existing way to run the installer program first. This guide walks through the full process: checking that your console can use FreeMCBoot, choosing an entry point, preparing a USB drive, running the installer, and checking the first boot.

Before you start: three checks that save most failed installs

First, check compatibility. FreeMCBoot works on most PS2 consoles, but not on late SCPH-90000 Slim models made from the third quarter of 2008 onwards, which have boot ROM version 2.30 or newer, and not on the PS2 TV. For those late Slims you need a different approach, covered in FunTuna and Fortuna for Late PS2 Slim SCPH-9000x. Datecode 8C is a transition period, so if your console falls in that window, check the ROM version rather than guessing from the datecode alone. See How to Check Your PS2 Model, Datecode, and ROM Version for the full method.

Second, back up your saves. Installing FreeMCBoot writes to a memory card, and formatting a card during installation erases everything on it. Copy any saves you care about to a second card or to a USB drive before you begin, and use a dedicated card for FreeMCBoot if you can. A second card for saves is good practice anyway, because it keeps your game saves separate from the launcher files.

Third, pick an entry point. An entry point is simply a way to run the installer program once on a console that does not have FreeMCBoot yet. The common options are a console that already has a softmod or a modchip, a cheat disc that can launch homebrew, FreeDVDBoot, or a PS3MCA memory card adapter connected to a computer. If you have none of these, ask a friend with a modified console to run the installer for you, or use one of the dedicated guides for your situation: Install FreeMCBoot with FreeDVDBoot (No Modchip) or Install FreeMCBoot from a PC with a PS3MCA Memory Card Adapter.

What you need

For hardware, a blank official-style 8MB memory card is the safest starting point, since large third-party cards are the most common source of card problems. You can find a suitable blank card through this memory card link, and a simple USB drive through this USB drive link. Buy a blank card and install FreeMCBoot yourself; do not buy a card sold with software or games already loaded on it.

Step 1: Prepare the USB drive

Format the USB drive as FAT32 with an MBR partition table if your entry point loads files from USB. The PS2 is an old console with USB 1.1 ports, and it is famously picky about modern drives, so an older, smaller USB 2.0 drive often works better than a large, fast USB 3.0 drive. If the console does not see the drive at all, try a different drive before assuming anything else is wrong; drive compatibility is covered in detail in PS2 USB Drive Not Detected: MBR, FAT32, and USB 1.1 Issues.

Extract the FMCB 1.966 archive on your computer with an archive tool that handles 7z files, then copy the installer files to the root of the USB drive, following the folder layout in the package. Do not bury the installer inside extra subfolders you invented yourself. If your computer’s security software removes the installer file as soon as you extract it, that is a known false-positive pattern with homebrew executables, and the fix is covered in FMCBInstaller.elf Missing, Quarantined, or Archive Won’t Extract.

Step 2: Run the installer from your entry point

Boot the console through your chosen entry point and launch the installer program, usually named FMCBInstaller.elf. The installer presents install options, including a standard install for your own console, a multi-install option, and a cross-region option. For a first install on your own console, choose the standard install that matches your console. The cross-region option is a separate topic with its own failure modes, covered in Cross-Region FreeMCBoot Install Failed or Won’t Boot.

Read each screen before confirming, and do not switch the console off or remove the card while the installer is writing. When the installer reports success, exit it cleanly and restart the console with the newly written card in the slot. If the installer offers to format the card first, remember that formatting erases saves, so only accept it if you have already backed them up or are using a fresh card.

Step 3: Check the first boot

On restart, the console should show the FreeMCBoot menu instead of the standard browser, with the card still inserted. If it boots normally as if nothing happened, work through the checks in FreeMCBoot Not Booting or Black Screen on Startup: card in the correct slot, card compatibility, console model, and whether the install actually completed. A card that boots on one console but not another is often a region or model issue, not a broken card.

Once the menu appears, the core install is done. The menu itself is deliberately minimal at this stage, because the standard package does not bundle applications. The next job is to add the programs you actually want to use, such as Open PS2 Loader for loading your own game backups from USB, a network share, or a hard drive, and uLaunchELF for managing files on the card. Those steps are covered in Open PS2 Loader Setup: USB, SMB, and HDD Modes and Update OPL and Add Apps with uLaunchELF.

Frequently asked questions

Do I need a modchip to install FreeMCBoot?

No, not in the usual case. You need an entry point, which can be an already modified console, a cheat disc, FreeDVDBoot, or a PC adapter method. A modchip is one possible entry point, but it is not a requirement for most consoles.

Can I install FreeMCBoot on any PS2?

Almost any, with the known exceptions: late SCPH-90000 Slim models with boot ROM 2.30 or newer, and the PS2 TV. Those consoles need Fortuna or FunTuna, which triggers manually from the system browser instead of booting automatically.

Will installing FreeMCBoot damage my console?

FreeMCBoot does not rewrite the console’s internal BIOS, and removing the card restores normal behaviour. The realistic risks are losing unsaved data on a formatted card, and the general care needed when running any installer, which is why backups and a dedicated card matter.

Why is my FreeMCBoot menu empty after installation?

Because the standard package ships no applications. Add Open PS2 Loader, uLaunchELF, or other homebrew programs afterwards, following their own setup guides, rather than expecting them to appear automatically.

Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.