One SD Card, the Whole Game Boy Shelf (Almost)

What actually turned up

The cart's an SC Flash Gear Pro+, one of the SuperCard-family carts, which matters because it runs SuperFW: a modern, open-source firmware built for exactly these. That word open-source matters more than it sounds like it should, and I'll come back to it. It turned up with the firmware already flashed, which is a nicer out-of-box experience than I expected. Half the price of the "name" flash carts on a sale, and I'll admit I braced for it to feel like it.

Storage is bring-your-own, so I dropped in a 128GB Samsung EVO I had lying around. Total overkill for a shelf of Game Boy saves, but it was doing nothing in a drawer, so overkill it is.

First job was getting my games onto it: the ones I own, dumped from my own carts with the FlashGBX. Here's the part that pleased me more than it should: pull a cart with the dumper and you get the raw file straight out, ready to go. Drop it on the card and it's there. And you can organise the card into whatever folder system you like, sort it how your own brain sorts things rather than how some menu insists. A tiny freedom, and I liked it immediately.

Booted a Game Boy Color game first, purely as a does-it-work check. Booted clean, first try. Good omen.

The quiet magic: it plays the whole Game Boy line

Here's the bit that genuinely pleased me. I assumed I'd need to feed it something, a BIOS file or some fiddly config, to get older Game Boy and Game Boy Color games running. You don't. The firmware carries its own Game Boy / Color emulator built in, so you drop a .gb or .gbc file on the card and it just loads. And GBA games run through the console's own internal BIOS, which every GBA already has. Nothing to add. Nothing to source.

Pair that with the FlashGBX and the picture gets very tidy: dump the cartridge I own, drop it on the card, play it on real hardware. One little cart covering the entire Game Boy family, all off games I physically own. That's the whole pitch of this hobby in one sentence.

The other headline is saves. My saves now live on an SD card I control, backed up, swappable, instead of trapped on an aging cartridge battery that's going to give up one day without asking. That alone justified the whole exercise for me. The cartridge can die; the save doesn't have to die with it.

The honest asterisk: a clock that doesn't tick

Now the first place the illusion shows its seams, and it's a good one.

The SuperCard has no real-time clock chip in it. None. So games that want to know the actual time and date, your Pokémon day/night cycles, your time-gated events, are asking hardware a question it can't answer. What the firmware does instead is fake it: you can set a starting time by hand, but it won't advance on its own. There's a mode that simulates time passing, and you can nudge the clock forward from the in-game menu, but there's no real clock under the hood. It's software doing an impression of hardware that was never there.

Which is a fascinating little tell, because I've got an N64 flash cart on the way that has a genuine RTC chip in it: a real clock, ticking properly. Same problem, two completely different answers. One system faking it in firmware, one solving it in silicon. There's a whole article in just that contrast, and I'll write it when the N64 cart lands.

For now the honest note is: RTC "works," in the sense that the firmware gives games something clock-shaped to hold onto. But don't expect it to know what day it is on its own. It can't. And that's not a flaw so much as the exact boundary of what a firmware fix can do on hardware that never had the part.

The wall: where modern hacks say no

Here's where I lost the evening, and here's the part I think is actually worth reading.

Commercial games boot beautifully. Emerald, FireRed, the lot. Straight in, no drama. But I went to play a couple of modern ROM hacks (I'm keeping to hacks I've patched myself from the creators' patches onto my own copies) and hit a wall. White screen. Nothing.

The forensics took a while, so let me save you the same evening:

First culprit: fast ROM loading. The big modern hacks are large, and there's a "fast loading" option that big ROMs don't get along with. Turn it off and the white screen cleared instantly. That one setting is the difference between "dead" and "boots" for anything chunky.

Second culprit: the save chip check. Past the white screen, one hack threw a specific error: Flash memory not detected. And here's the mechanism, because it's genuinely clever. Modern Pokémon hacks are built on an expanded codebase that added a hard check on boot: is there real flash memory here? Vanilla Emerald never asks. It just trusts whatever the firmware hands it. The firmware, remember, has no real flash chip; it's faking the save hardware the same way it fakes the clock. Vanilla trusts the fake. The modern hack checks, finds nothing real, and refuses to start.

Same save type. Same everything. The commercial game boots because it's trusting; the hack fails because it's suspicious. That contrast, the forgiving old game versus the paranoid new hack, a faked chip versus a real one, is the cleanest illustration I've ever seen of exactly where firmware emulation ends and hardware begins.

Third culprit: me. After all that, it turned out a couple of the files for one hack simply hadn't copied across. Half a ROM boots exactly as badly as a save-type mismatch, and no amount of settings-fiddling fixes missing data. So the lesson I'm banking for next time, and passing to you: check the file copied complete before you go down the firmware rabbit hole. It's the boring answer and it's top of the suspect list now.