FreeMCBoot Cross-Region Installs Explained: Normal, Cross-Model, and Multi-Install
A FreeMCBoot (FMCB) card that works perfectly on one PlayStation 2 and does nothing on another is usually not a broken card. It is usually an install made for the wrong console. The direct answer is this: a normal FMCB install is tied to the region and model family of the target console, a cross-model install widens that match to related models, and a multi-install covers several targets at once, but none of these install types changes the console’s region behaviour for original discs. If you want a card that boots on your console, install for that console, test on that console, and treat cross-region installs as a deliberate choice with trade-offs, not as a universal card.
FMCB v1.966, created by Neme and jimmikaelkael and maintained by SP193, works by replacing the standard browser behaviour with files on the memory card that match the console’s system files. That matching is why region and model matter. The console checks the card’s files against its own region and model information, and a mismatch means the custom menu simply does not appear. The installer therefore offers different install types, and understanding them is more useful than memorising which card worked for someone else online.
The three install types, plainly explained
Normal install. This is the default and the right choice for most people. The installer prepares the card for the specific console you are installing from or for, matching its region and model family. A normal install is the simplest and most predictable option when you know exactly which console will use the card. If you only have one PS2, or one PS2 you care about, use a normal install for that console and stop there.
Cross-model install. This widens the match so the card can boot on related models within the same broader family. It exists for people who move a card between similar consoles, for example between two Fat consoles or between related Slim models. The trade-off is that “related” is doing real work in that sentence: a cross-model install is not a promise that the card will boot on every PS2 ever made, and it does not bridge the late-model gap described below.
Multi-install. This prepares the card for several targets at once. It is the most flexible option and the one most likely to be recommended by people who install cards for friends or for multiple consoles in one household. The trade-off is complexity: more targets on one card means more ways for a single mistake to affect the result, and it still does not make the card universal. A multi-install also uses more of the card, which is another reason to use a dedicated card for FMCB rather than trying to combine system files and a large save library on one card.
None of these types should be confused with region-free disc playback. Installing FMCB for a console in another region does not make that console play original discs from other regions. That limit is a hardware matter, explained in What FreeMCBoot Cannot Do, and it applies regardless of install type.
Why a card boots on one console and not another
When a card fails on a second console, work through this list before assuming the card or the console is faulty.
| Symptom | Most likely explanation |
|---|---|
| Card boots on the install console, not on a second console | Install type was normal for the first console’s region or model family |
| Card boots on some consoles in a household, not on others | Cross-model or multi-install covers some targets but not the mismatched one |
| Card does nothing on a late SCPH-90000 Slim | Late-model boot behaviour, not a region problem; see below |
| Card boots, but the menu looks incomplete or an app is missing | The v1.966 package contains no apps; OPL, uLaunchELF, and ESR are added separately |
| Card worked, then stopped after being used in another console | The card may have been reformatted or its files changed, or the second console’s behaviour was misread |
The first row is by far the most common. People install on a friend’s console, take the card home, and conclude the install failed. In most cases the install succeeded exactly as asked; it was simply asked for the wrong target.
The late-model boundary is not a region problem
Late SCPH-90000 Slims with boot ROM 2.30 or newer, and the PS2 TV, do not boot standard FMCB at all, whatever install type you choose. Sony removed the update behaviour FMCB relies on from those consoles, and no normal, cross-model, or multi-install changes that, because the limitation is in the console’s read-only BIOS behaviour, not in the card’s region matching. The route for those consoles is Fortuna or FunTuna, a manual trigger from the on-screen browser, compared in FMCB vs Fortuna, FunTuna, and OpenTuna.
This distinction matters when diagnosing a failure. If the second console is a late Slim, switching install types will not fix it. Check the model, datecode, and ROM version first, using the matrix in FreeMCBoot Compatibility List. If the console is in the late group, change the route, not the install type.
Practical advice for each situation
One console, your own. Use a normal install for that console. Keep the card dedicated to FMCB and saves on a second card. Two or three consoles in one household. Consider a multi-install, but list the consoles, models, and regions first, then test the card on every console on the list before relying on it. Installing for someone else. Install for their console, not yours, or use a multi-install that explicitly includes their console. Buying a card second-hand. Treat the install type as unknown until tested. If it does not boot on your console, plan a fresh install for your console. When you need a blank card for that fresh install, a PS2 memory card gives you a fresh starting point.
Checklist
- Write down each target console’s model, region, and, for 90000 Slims, ROM version.
- Choose normal for one known console, cross-model for related models, multi-install for a known list of targets.
- Do not expect any install type to add import-disc support or to fix late-model boot behaviour.
- Test the card on every console it is meant to serve.
- Get the v1.966 package from /download/ and keep saves on a separate card.
FAQ
What is the difference between a normal and a multi-install? A normal install targets one console’s region and model family. A multi-install prepares the card for several targets at once. Multi-install is more flexible but more complex, and it is still not universal.
Will a cross-model install make my card work on any PS2? No. It widens the match to related models, but it does not cover every model, every region combination, or late Slims, which need a different trigger entirely.
Can I install FMCB for a console in another region to make it region-free? No. The install type affects which consoles the card boots on. It does not change how a console treats original discs from other regions.
My card works on my friend’s PS2 but not mine. Is the card broken? Probably not. The most likely explanation is that it was installed for your friend’s console. Reinstall for your console, or use a multi-install that includes yours, and test it there.
Some links on this page are affiliate links; we may earn a commission at no extra cost to you. See our Affiliate Disclosure.