From a forgotten TV box to a retro console
By Zhivko Kocev, Software Engineer at CodeChem
I love finding a use for “old” hardware and bringing it back to life, so here's the road from an old TV box to a retro console. I had an old Nexbox A95X-B7N collecting dust in a drawer; now it runs NES, SNES and PlayStation games on the TV.
Requirements: a small chunk of a weekend, an old TV box, and a microSD or SD card (or a USB stick if the box has no card slot). Android on the box stays untouched: with the card in, it boots EmuELEC; without it, Android as before.
This is the whole build in order, including what broke along the way and how I fixed it, so you can skip my mistakes.
What you actually need
- A TV box with an Amlogic chip (not every box works, see below). Mine: Nexbox A95X-B7N, Amlogic S905X, 2 GB RAM, 8 GB storage.
- A microSD card. I used a 32 GB Netac and fit about 1,600 games with 3 GB to spare. Go bigger if you want a lot more.
- A USB card reader, but only if your PC has no SD slot. Mine didn't.
- A USB keyboard for setup. A gamepad is even better: the keyboard gave me trouble (see here).
- A toothpick. 😃
- HDMI and, ideally, an Ethernet cable.
- A PC. I used Omarchy; balenaEtcher also runs on Windows and macOS.
Does any TV box work? Not quite. EmuELEC runs on Amlogic S905X, S905X2, S905X3 and S922X (and their variants, like the S905W). The plain S905 (no X) no longer works, the S912 was dropped in 4.0 (3.9 still supports it), and boxes with Rockchip or Allwinner chips aren't supported. Some (MeCool, Mi Box) have a locked bootloader, and cheap clones can come with fake RAM or boot only from USB. Get a box with at least 2 GB RAM. The full list is on the EmuELEC wiki.
Box isn't Amlogic? Don't give up. Lakka is the closest thing to EmuELEC: it also boots straight into games, just with RetroArch's menu instead of EmulationStation (the differences: see below). It has images for a few Allwinner and Rockchip boxes (Tanix TX6, Beelink A1, Hugsun X99). RK3318/RK3328 boxes have Armbian, with RetroArch on top, but that's more tinkering. And if you don't want to flash anything, RetroArch for Android runs on any Android box, straight from Android.
Know your box
First, flip the box over and see what you're working with. The label on the bottom tells you the two things you'll need later: the chip and the RAM. Mine: Amlogic S905X and 2 GB RAM.
The chip decides which games it can handle. The S905X is roughly Raspberry Pi 3 class: everything up to the original PlayStation runs fine, N64 is hit and miss, and PSP, Dreamcast and anything newer are too heavy.
Remember the RAM: it decides which file you pick in step 4.
Download EmuELEC
EmuELEC is a small operating system (Linux) that boots straight into a game menu, EmulationStation, instead of a desktop. The games themselves run in emulators, programs that pretend to be an old console; the main one is RetroArch.
Why EmuELEC and not Lakka?
Lakka runs on Amlogic boxes too. Here are the differences that matter for a beginner:
- It looks like a console. EmuELEC opens a game list with covers, descriptions and a theme (the video at the top). Lakka opens RetroArch's menu: powerful, but it feels more like a settings screen than a console, and beginners get lost in it easily.
- It's made for exactly these boxes. The whole project targets cheap Amlogic TV boxes, so its guides and forum are full of the same problems you'll run into.
- More emulators. Lakka is RetroArch only. EmuELEC also ships standalone emulators next to RetroArch, so if a game runs badly in one, you try another.
Let's get it. Head to the releases on GitHub and grab the latest. I went with 4.8 (3 November 2025).
You'll see a pile of files there (screenshot below). Don't panic, you only need one: Generic, EmuELEC-Amlogic-ng.aarch64-4.8-Generic.img.gz (1.13 GB). That's the one for TV boxes; the rest are for specific boards (La Frite, Le Potato, Odroid).
Each file also has a .sha256 next to it. Optional, but if you want to be sure the download isn't broken, grab it too and compare the hashes. If they differ, download again.
sha256sum EmuELEC-Amlogic-ng.aarch64-4.8-Generic.img.gz
cat EmuELEC-Amlogic-ng.aarch64-4.8-Generic.img.gz.sha256
Flash the card
Flashing means writing the system onto the card. I used balenaEtcher (it's free): Flash from file → the .img.gz you downloaded (don't unzip it, Etcher handles that) → Select target → the card → Flash! Watch what you pick as the target: Etcher wipes the whole disk, so pick the wrong one and say goodbye to your files.
My PC has no SD slot, so the card went into an adapter, the adapter into a USB reader, and the reader into the PC (photos below). If yours has a slot, skip all that and just put the card in.
Linux folks only: instead of Etcher you can use a terminal. Find your card with lsblk and replace /dev/sdX; the wrong letter wipes the wrong disk.
lsblk
gzip -dc EmuELEC-Amlogic-ng.aarch64-4.8-Generic.img.gz | sudo dd of=/dev/sdX bs=4M conv=fsync status=progressPick the device tree
When Etcher is done, pull the card out and put it back in. A disk called EMUELEC shows up. If Windows asks to format a disk, say no: that's a part of the card Windows doesn't understand, not a broken one. On EMUELEC there's a device_trees folder. A device tree (dtb) is a small file that tells the system what hardware is inside the box, which is why you needed the RAM from the label. Find the right one, copy it out of the folder (to the top level of the disk) and rename it to dtb.img. For an S905X with 2 GB RAM that's gxl_p212_2g.dtb; with 1 GB, gxl_p212_1g.dtb.
Which file for which box? Look up your model on CoreELEC's list (EmuELEC uses the same names) or on the EmuELEC forum. If it isn't there, go by the chip and RAM from the label: the name starts with the chip family (gxl is S905X/W/L, g12a is S905X2, sm1 is S905X3, g12b is S922X), and the RAM is in the name (_1g, _2g, _4g). My A95X-B7N isn't on the list, so I went by the chip. If it doesn't boot, try another: the dtb is just a file on the card, nothing breaks.
cd /run/media/$USER/EMUELEC
cp device_trees/gxl_p212_2g.dtb dtb.img
sync
dtb.img is the only new file.Boot from the card: the toothpick
Now the box needs to start from the card instead of Android. This is where the toothpick comes in: Amlogic boxes hide a button deep inside the AV jack (the small hole for the old analogue cable). Hold it while the box powers on, and the box reads the card and remembers to start from it first from now on.
- Unplug the power and put the card in the TF slot.
- Push a toothpick into the AV jack until you feel a click, and keep holding.
- Plug the power in. Keep holding until the EmuELEC logo appears, then let go.
You only do this once. After that the box boots EmuELEC whenever the card is in, and Android when it isn't.
My first try didn't take. Android booted instead and quietly created Android/ and LOST.DIR/ folders on the card. That's harmless, it just means the box never felt the button. Try again and hold it longer.
Android/ and LOST.DIR/ on the EMUELEC partition: a sign that Android booted, not EmuELEC.First boot: hands off
On the first start EmuELEC sets itself up: it grows to fill the whole card and copies its default settings. Don't cut the power while it runs, not even by accident.
Mine broke right there. The screen filled with white text, a system error, while it was still copying files. The box still made it to the menu, but the copy was left half done. I only figured that out later (next step).
If the first boot crashes, the cheapest fix is to flash the card again and boot again. I didn't, and spent an evening finding the damage by hand.
Dead keyboard, broken menus
EmuELEC came up, but there was no screen for setting up the buttons (“hold a button to configure”), the keyboard did nothing, and the menus looked broken. I tried deleting the button config file, no luck. Turned out it was two separate problems.
Problem 1: 758 empty files
The crash on the first start left 758 empty files behind: menu graphics, fonts and sounds. That's why the menus looked broken.
The fix for everyone: flash the card again (Etcher, like above), put dtb.img back and let the first start finish. Done.
For the curious: how I fixed it without reflashing (Linux, terminal)
With the card back in the PC, 803 of the 6,483 files on STORAGE were 0 bytes. 45 of them are empty in the original too. The other 758 were damage:
EmulationStation's log (es_log.txt in the same folder) says the same thing:
[MaxDepth]
To check whether your card got hit too, count the empty files:
[MaxDepth]
The repair needs nothing from the internet: SYSTEM is a squashfs image (a compressed archive) that holds the original files under /usr/config. Extract them with unsquashfs (from squashfs-tools), then copy back every file that differs:
[MaxDepth]
[MaxDepth]
STORAGE is a Linux partition (ext4) and the files belong to root, hence sudo. On my card: restored 758 files, empty files left: 0.
Problem 2: the keyboard does nothing, by design
This one isn't a bug, it's by design: EmuELEC never opens the button setup screen on its own, and for the keyboard it only looks at one file, es_input.cfg. If that file is empty or missing, the keyboard does nothing. That's why a gamepad is the better pick: try it first.
If it has to be a keyboard, you add the keys to that file yourself. It lives on the card's STORAGE part (.config/emulationstation/es_input.cfg), which is a Linux partition: Windows and macOS can't see it without extra software, and on Linux you need sudo. Open the file and paste the block below just before </inputList>. The numbers are key codes; you don't need to understand them, just copy.
My first version (screenshot) used Enter for A and Space for Start. It worked in the menus, but in games RetroArch has its own keys, so the same key did different things. That's why the version below uses the same keys as RetroArch.
<inputConfig type="keyboard" deviceName="Keyboard" deviceGUID="-1">
<input name="up" type="key" id="1073741906" value="1" />
<input name="down" type="key" id="1073741905" value="1" />
<input name="left" type="key" id="1073741904" value="1" />
<input name="right" type="key" id="1073741903" value="1" />
<input name="a" type="key" id="120" value="1" /> <!-- X -->
<input name="b" type="key" id="122" value="1" /> <!-- Z -->
<input name="x" type="key" id="115" value="1" /> <!-- S -->
<input name="y" type="key" id="97" value="1" /> <!-- A -->
<input name="start" type="key" id="13" value="1" /> <!-- Enter -->
<input name="select" type="key" id="1073742053" value="1" /> <!-- Right Shift -->
<input name="leftshoulder" type="key" id="113" value="1" /> <!-- Q -->
<input name="rightshoulder" type="key" id="119" value="1" /> <!-- W -->
<input name="lefttrigger" type="key" id="49" value="1" /> <!-- 1 -->
<input name="righttrigger" type="key" id="50" value="1" /> <!-- 2 -->
<input name="leftthumb" type="key" id="99" value="1" /> <!-- C -->
<input name="rightthumb" type="key" id="118" value="1" /> <!-- V -->
<input name="hotkeyenable" type="key" id="1073742053" value="1" />
</inputConfig>In games RetroArch already uses the same keys. If you also want L2, R2, L3 and R3 (the back triggers and stick clicks), add them to STORAGE/.config/retroarch/retroarch.cfg:
input_player1_l2 = "num1"
input_player1_r2 = "num2"
input_player1_l3 = "c"
input_player1_r3 = "v"| [MaxDepth] | [MaxDepth] | [MaxDepth] |
|---|---|---|
| [MaxDepth] | D-pad | [MaxDepth] |
| [MaxDepth] | A | [MaxDepth] |
| [MaxDepth] | B | [MaxDepth] |
| [MaxDepth] | X | [MaxDepth] |
| [MaxDepth] | Y | [MaxDepth] |
| [MaxDepth] | Start | [MaxDepth] |
| [MaxDepth] | Select + hotkey | [MaxDepth] |
| [MaxDepth] / [MaxDepth] | L / R | [MaxDepth] |
| [MaxDepth] / [MaxDepth] | L2 / R2 | [MaxDepth] |
| [MaxDepth] / [MaxDepth] | L3 / R3 | — |
| [MaxDepth] | [MaxDepth] |
|---|---|
| [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] |
| [MaxDepth] / [MaxDepth] | [MaxDepth] |
| [MaxDepth] / [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] |
If one of them does nothing, hold Right Shift (the hotkey) and press it again.
What's on the card
After the first start the card is split into three parts (partitions), and your PC sees them as three separate disks. Two of them matter. EEROMS is for games and shows up everywhere (Windows, macOS, Linux), it just won't take a single file over 4 GB. STORAGE is for settings and is a Linux partition: Windows and macOS can't see it without extra software, and on Linux edits need sudo.
| [MaxDepth] | [MaxDepth] | [MaxDepth] | [MaxDepth] |
|---|---|---|---|
| [MaxDepth] | 2 GB | [MaxDepth] | [MaxDepth] |
| [MaxDepth] | 6 GB | [MaxDepth] | [MaxDepth] |
| [MaxDepth] | [MaxDepth] | [MaxDepth] | [MaxDepth] |
EEROMS: one folder per system, plus bios, BGM (music), savestates and screenshots.Games, BIOS and formats
ROMs, briefly
A ROM is a game in a file: a copy of the cartridge, or of the disc for PlayStation. The emulator (RetroArch calls it a “core”) pretends to be the console and runs it. EmulationStation is just the menu you pick it from.
Only play games you own: dump your own cartridges and discs, or play homebrew and freeware. itch.io, PDRoms and the NESdev community have plenty, and ScummVM has free adventure games. I won't link ROM sites.
One good file per game
Game collections often have five versions of the same game. The name tells you which is which. My rules:
(USA)or(World)first: that's the speed the games were made for.(Europe)versions are for old European TVs (PAL, 50 Hz): they run slower and judder on a modern screen.(Europe)only when there was no USA release. If there are several revisions, keep the highest(Rev N), it's the most fixed one.- Skip
(Beta),(Proto),(Demo),[b](bad copy), and multi-carts with “ + ” in the name. - NES: if you have a choice, take the files with a header. It's a bit of data at the start of the file that tells the emulator what kind of cartridge it is; without it, the emulator has to guess.
You do this by hand: keep one file per game and delete the rest. It's optional, but the list is much cleaner without five versions of the same game.
PlayStation: CHD (optional)
PS1 games usually come as BIN/CUE, two files per disc, and that works fine. I converted mine to CHD, a compressed format that loses no quality: 30–50% smaller and one file per disc. You don't have to: CHD only fits more games on a 32 GB card. I'd skip ISO, it loses the disc's music. If you go CHD, you need the chdman tool from MAME (on Arch it's in mame-tools); always convert from the .cue, not the .bin:
sudo pacman -S mame-tools
for c in *.cue; do chdman createcd -i "$c" -o "${c%.cue}.chd"; doneMulti-disc games (Final Fantasy VII has three) get a small .m3u text file listing the discs, so they show up only once in the menu. Make it in any plain text editor. Swap discs from the RetroArch menu (F1 → Disc Control):
Final Fantasy VII (USA) (Disc 1).chd
Final Fantasy VII (USA) (Disc 2).chd
Final Fantasy VII (USA) (Disc 3).chdFile names can lie. Three of mine did: a “Final Fantasy VII” turned out to be the 196 MB Interactive Sampler demo (SCUS-94961), “Metal Gear Solid” was VR Missions, and “Suikoden II” was the first Suikoden. You'll catch them when you launch them, and a suspicious size is a good hint (a 196 MB FFVII disc?). Optionally, check the CHDs are intact before copying:
for f in *.chd; do echo "$f: $(chdman verify -i "$f" 2>&1 | tail -1)"; doneBIOS
A BIOS is a small program from the console itself that starts it up and reads the disc. Emulators can't include it (copyright), so you dump it from your own console. PS1 needs a file called scph5501.bin in the EEROMS/bios folder, in lowercase. If you want to check it's the right one, its md5 hash should match the one below:
cp SCPH-5501.BIN /run/media/$USER/EEROMS/bios/scph5501.bin
md5sum /run/media/$USER/EEROMS/bios/scph5501.bin
# 490f666e1afb15b7362b406ed1cea246| [MaxDepth] | [MaxDepth] |
|---|---|
| [MaxDepth] | [MaxDepth] / [MaxDepth] |
| PC Engine CD | [MaxDepth] |
| Famicom Disk System | [MaxDepth] |
| Neo Geo | [MaxDepth] |
| Sega CD (USA) | [MaxDepth] |
Copying to the card
Copy the games with your file manager like anything else, each into its system's folder (EEROMS/psx, EEROMS/snes...). Before pulling the card, always Eject and wait: SD cards are slow, and the PC keeps writing long after the copy has “finished”.
If ejecting says “device busy” while nothing is open, that's exactly it: the PC is still writing gigabytes. Wait (or run sync in a terminal) and try again. I tried udisksctl power-off once; the reader vanished until I unplugged it and plugged it back in. A plain Eject is enough.
How much fits on 32 GB
About 22 GB is left for games. Cartridge games are tiny; PS1 discs are what fill the card, around 320 MB each as CHD. I fit about 1,600 games with 3 GB to spare.
| [MaxDepth] | [MaxDepth] | [MaxDepth] |
|---|---|---|
| NES, SNES, Mega Drive, Game Boy, PC Engine | ~200 | 500 MB |
| GBA | 30 | 400 MB |
| [MaxDepth] | 40 | 1 GB |
| N64 | 15 | 400 MB |
| PS1 (CHD) | ~30 | 12 GB |
| [MaxDepth] | — | 1–2 GB |
| [MaxDepth] | — | ~5 GB |
What runs: everything up to PS1 at full speed on default settings. N64 is mixed (Ocarina of Time plays, with slowdown). PSP, Dreamcast, Saturn, DS, GameCube and newer are too heavy for the S905X.
Box art and screenshots
A game list without pictures looks sad. Scraping means downloading covers, screenshots and descriptions from ScreenScraper, which needs a free account. The easiest way is on the box itself: the main menu has a Scraper, enter your account, pick the systems and start it.
Just turn off the extras first in the scraper options (or in STORAGE/.config/emulationstation/es_settings.cfg). Videos alone are 2–10 MB per game and fill a 32 GB card quickly. “Maps” here are fan-made world maps, not in-game maps.
<bool name="ScrapeBezel" value="false" />
<bool name="ScrapeFanart" value="false" />
<bool name="ScrapeManual" value="false" />
<bool name="ScrapeMap" value="false" />
<bool name="ScrapeVideos" value="false" />I did it on the PC, with Skyscraper (Linux, terminal)
The card was in my PC anyway, so I used Skyscraper there:
[MaxDepth]
An artwork recipe keeps it to one cover, one screenshot and one logo per game, with no composite images:
[MaxDepth]
It runs in two steps: first download into Skyscraper's cache (network), then write gamelist.xml and the images to the card (offline):
[MaxDepth]
-imust be an absolute path, or Skyscraper refuses with relative path which is not valid.- A free ScreenScraper account gets one thread.
-t 8is quietly reduced to 1: about 7 games a minute, so hundreds of games take hours. Don't run two at once; the server refuses and may block you for a while. - Without
marqueein the recipe, logo paths pointed into~/.skyscraperon the PC, which doesn't exist on the box. - Regenerating
gamelist.xmldrops the recorded play time (gametime). Back it up first.
Result for PS1: 52 of 53 games found, 22 MB of images, about 0.25 MB per game.
Settings that matter
Most settings are in the menus (Start → Game Settings, System Settings). They're saved to one file, emuelec.conf, on STORAGE under .config/emuelec/configs/, so you can also edit it by hand. In that file global.something applies to every system, and something like nes.something only to NES.
One trap: don't edit retroarch.cfg for picture and emulation settings. EmuELEC rewrites it from emuelec.conf every time you start a game, so your changes vanish.
-system.timezone=America/Mexico_City
+system.timezone=Europe/Skopje
-updates.enabled=1
+updates.enabled=0
+global.shaderset=sharp/sharp-bilinear-simple.glslp
+global.integerscale=0
+global.smooth=0
+global.rewind=0
+global.autosave=1
+nes.runahead=1
-global.retroarchLogging=1
+global.retroarchLogging=0- A shader is a filter for the picture.
sharp-bilinear-simplekeeps pixels crisp on any TV, without wonky pixels or black borders. That's why integer scale and smoothing (other ways of doing the same) are off. - Rewind (going back in time in a game) off: it costs CPU this chip doesn't have to spare.
- Auto-save on: when you quit, the game is saved, and next time it picks up right there.
- Run-ahead on NES only: buttons respond a bit faster.
- Updates off: I'd rather update on purpose, after backing up the card.
- Logging off: fewer writes to the SD card.
Already right by default: ee_videomode=1080p60hz (the chip can't do 4K well, and 50 Hz judders), global.maxperf=1 (CPU always at full speed) and bezels (frames around the picture) off.
| [MaxDepth] | Core | [MaxDepth] |
|---|---|---|
| NES | FCEUmm | [MaxDepth] |
| SNES | Snes9x | [MaxDepth] |
| PS1 | PCSX ReARMed | [MaxDepth] |
TV and controllers
I haven't set these up yet; this is the plan.
- TV: Game picture mode, motion smoothing off, picture size Just Scan or Screen Fit so nothing is cropped.
- Pads: 2.4 GHz pads with a USB dongle are more reliable than the box's Bluetooth, which I turned off. There are only two USB ports, so use a hub if the keyboard stays plugged in.
- Map each pad from Controller Settings in the main menu and set Hotkey Enable to Select. The hotkey is the button you hold for combos: Select+Start quits the game, Select+R saves, Select+L loads.
Lock it down
This part is optional, for paranoid people like me. Out of the box EmuELEC runs Samba (file sharing over the network) with a password the whole internet knows (root / emuelec), and SSH (remote terminal access) is one setting away. I want the box to reach the internet (for box art, correct time), but nothing on the network to get into it. On startup EmuELEC checks STORAGE/.cache/services to decide which services to run:
cd /run/media/$USER/STORAGE/.cache/services
sudo rm -f samba.conf avahi.conf sshd.conf
sudo touch samba.disabled
printf 'RULES=public\n' | sudo tee iptables.confRULES=public turns on EmuELEC's firewall: nothing gets in from outside, while the box can still go out. On top of that I set ee_ssh.enabled=0 and turned off Wi-Fi and Bluetooth in emuelec.conf.
If you'd rather copy games over the network, keep Samba on, open smb://BOX-IP/ in your file manager and reserve the box's IP in your router. Never expose it to the internet. Expect about 10 MB/s; the Ethernet port is 100 Mbit.
Theme and music
The default Crystal theme is fine (photo below). I wanted something arcade. EmuELEC has a list of 82 themes. I tried Arcadeplanet first, but it's 173 MB and its own authors recommend a Raspberry Pi 4 or faster. Neon Overdrive (gradient) is 28 MB with no videos and looks the part. Without a terminal: on the theme's GitHub page hit Code → Download ZIP, unzip it and copy the folder to STORAGE/.config/emuelec/themes/. With a terminal:
git clone --depth 1 https://github.com/EmuELEC/es-theme-neon-overdrive-gradient
rm -rf es-theme-neon-overdrive-gradient/.git
sudo cp -r es-theme-neon-overdrive-gradient /run/media/$USER/STORAGE/.config/emuelec/themes/Pick it in UI Settings, or set it in es_settings.cfg:
<string name="ThemeSet" value="es-theme-neon-overdrive-gradient" />
<string name="ThemeSystemView" value="" />The theme's licence is personal use only, so I'm not redistributing it. If scrolling feels slow, set the transition style to Instant.
Background music is any MP3 in EEROMS/BGM. I used Eric Skiff's Resistor Anthems: chiptune licensed CC BY 4.0, so it's free with credit. 17 tracks, 62 MB. audio.display_titles=1 in emuelec.conf shows the song title when a track starts.
Will save states fill the card?
No. A save state is a “snapshot” of the game at that moment, so you continue exactly from there. Auto-save keeps one per game and overwrites it each time. Roughly: NES 30–80 KB, SNES 150–300 KB, PS1 1–2 MB. Even if I played every game on my card once, that's about 400 MB. Manual saves in many slots do add up: ten slots for every PS1 game is around 1 GB. They all live in EEROMS/savestates; copy them somewhere else now and then.
What I learned
- Let the first boot finish. If it crashes, flash again.
- If the keyboard is dead, emptying
es_input.cfgwon't help. Use a gamepad or add the keys yourself. - Make the menu keys match RetroArch's defaults, so a key means the same thing everywhere.
- Settings go in
emuelec.conf;retroarch.cfggets rewritten on every launch. - PS1 file names can lie; check them when you launch them.
- On a small card, turn off scraper videos.
- Shut down from the menu (Quit → Shutdown). A power cut during writes is how files end up empty.
What's next
- Two wireless pads, with Hotkey Enable set to Select. Update: this took a whole night and a kernel patch, here's the story.
- Finish the box art for NES and SNES with the scraper on the box (about three hours).
- Quick checks: the PlayStation logo plays (the BIOS is found), auto-save resumes, and the new keys work in games.
- Maybe Game Boy, GBA, Mega Drive and a few arcade games. There's room for them.
Originally published on kocev.mk. Прочитајте на македонски.