The shelf of almost-useful machines
Every home lab grows a shelf of retired PCs. Machines too slow to be a hypervisor, too new to e-waste, too loud to keep in the study. The usual fate is a dust-collecting Windows install that nobody signs into. A piece over on XDA Developers nudged me toward a better retirement for at least one of them: turn it into a dedicated retro console with Batocera, an operating system that boots straight into a controller-friendly game library. It’s the right instinct, and it deserves a home-lab treatment — because the way we run services is exactly the way this box should be run.
Why an appliance beats a desktop for this
You can run RetroArch on Windows and get the same emulation. What you can’t get is the experience: press power, wait five seconds, pick a game with a controller, play. No desktop, no login screen, no update dialogues mid-session, no antivirus toast in the corner of Tetris. Batocera’s whole value is that it refuses to be a computer. It boots into EmulationStation, maps your controller across every emulator it bundles, and hides everything else.
That’s the same reason we run appliances in the lab at all. A NAS doesn’t ask you to log into Linux; a Pi-hole doesn’t show you a desktop. The best retirement for old hardware is a single job done without ceremony — and for the machine parked next to the TV, that job is games.
Trial it from USB before you commit anything
Batocera runs entirely from a USB stick before you install anything, and that trial run is the most important step. It answers the only question that matters — can this specific PC emulate the systems I actually want to play? — before you wipe a drive.
- Download the
x86_64image from batocera.org and write it to a USB drive with Raspberry Pi Imager (choose Use custom). - Boot the PC from the stick via its boot menu, picking the UEFI entry if one appears. First boot expands the data partition, so give it a minute.
- Load a handful of games, sit on the couch, and be honest about performance. If it’s sluggish from USB, internal disk won’t save it — the CPU is the ceiling, not the disk.
Only when the trial passes do you commit: connect to the network and run System Settings > Install Batocera on a New Disk. Note that this installs a fresh image rather than cloning your USB setup, so treat the USB build as a throwaway and rebuild your library on the real install.
Your CPU is the compatibility list
The age of the PC matters less than which consoles you want. NES, SNES and Mega Drive are nearly free on any hardware from the last fifteen years. Dreamcast, PSP and PS1 want a bit of grunt. PS2, GameCube and anything newer want a genuinely capable CPU — and the moment you start upscaling beyond native resolution, you’re paying for it in silicon. Pick the five games you actually want to replay, check them against the hardware, and let that decide. A Core 2 Duo with a shelf of SNES classics beats an i7 with a library that stutters.
Storage maths is lopsided: cartridge ROMs are megabytes, disc images are gigabytes. A full set of cartridge-era games plus a handful of PS2 titles fits comfortably in 128GB. Budget 32GB for the OS alone, put the library on an SSD rather than a spinning disk — the UI scrapes box art and video previews, and a spinner makes the whole thing feel old in the wrong way.
Run it like the appliance it is
Here’s the part the gaming guides skip and the home-lab crowd won’t: this box is a service now, so give it service hygiene.
- Load games over the network. Batocera exposes Samba shares — drop ROMs onto
\\batocera\roms(or the box’s IP) from your desk instead of ferrying USB sticks to the lounge. - Back up the userdata partition. Saves, scraped art and configuration all live in one place. Copy it off periodically the way you’d back up any other service’s data directory. Save states especially — Batocera can surface them right in the game list, and they’re the difference between “one more level” and a 40-minute commitment.
- Image the disk once it’s right. A working Batocera install is a cloneable artifact. If an update breaks something, re-image and restore the userdata backup. That’s faster than debugging an emulator at family movie night.
And a quiet word for the small-business readers: this is also the cheapest break-room upgrade there is. A retired SFF box, two controllers and Batocera will outlast any arcade subscription, and it costs you a machine that was bound for the e-waste pile anyway.
Two speed bumps: Secure Boot and BitLocker
Corporate-adjacent machines may refuse to boot Batocera until you enrol Batocera’s signing key or switch Secure Boot off in firmware. If the machine still holds an encrypted Windows install you care about, export the BitLocker recovery key before you touch firmware settings — not after the machine asks for it. This is the one step in the whole project that can cost you data, and it takes two minutes to defuse.
The part nobody puts in install guides
The ROMs. In Australia, downloading copies of games you don’t own sits in murky territory, and I’m not going to pretend otherwise. The defensible library is your own: cartridge dumps from your own hardware, disc images from discs in your cupboard. The good news is that’s also the fun library — the games on your shelf are the ones with the memories attached, and emulation doesn’t need anything more than that.
One job, done perfectly
Not every retired PC should become a VM host. The one within controller-cable reach of the TV should become exactly one thing: a box that boots in seconds into a wall of games, controlled entirely from the couch. Batocera gets the appliance right — controller in, keyboard in a drawer, save states where the whole family can find them. Give the machine one last job, and make it the good one.

