Working With the 88 Cowboys Emulation Archive
The 88 Cowboys project is a preservation effort around the MSX2 home computer, specifically focusing on game ROMs and software from the late 1980s that used cartridge hardware. The numbering system in the name refers to a particular set of titles that circulated through Japanese hobbyist circles before being archived. What follows is a practical walkthrough based on actual experience with the ROMset, firmware, and the preservation work around it. You will need an MSX2-compatible emulator first. OpenMSX and XanaduMSX are the two most stable options. OpenMSX runs best on Linux and macOS. It handles cartridge ROM loading cleanly. XanaduMSX is Windows-native and handles the larger ROM packs without crashing. The archive itself is typically distributed as a ZIP or 7z file. Inside you will find ROM files with names like c001.rom, c002.rom, and so on. Some releases include bin files alongside the ROMs. Stick with the ROM files unless a specific title is only distributed in BIN format.
Setting Up the Emulator
Open your emulator of choice and go to the cartridge slot section. Insert the ROM file into cartridge slot A. Make sure you do not mix up cartridge slot A and disk drive slot B — they behave differently and some titles will refuse to boot from the wrong slot. This is the most common mistake I see. After inserting the ROM, set the machine type to MSX2 or higher. If you leave it on MSX1, many cartridges will not initialize correctly. Then press the reset button or use the emulator's reset command. Do not use power off and on. The cartridge initialization only runs on reset. When you first boot, you may see a black screen for up to 30 seconds. That is normal for certain cartridge dumps that require a slow memory scan on startup. Give it time. Pressing RESET repeatedly will not speed this up and may corrupt the session.
88 Cowboys History and Preservation Context
Before the archival work began, these cartridge titles existed almost exclusively on physical hardware in Japan and a handful of US collector circles. The disks were degraded, the cartridges were failing, and there was no centralized backup. Someone started dumping the ROMs and organizing them under a numbering scheme. That organization became known within the MSX community as the 88 Cowboys set. Over time, additional titles were added beyond the original 88 entries, but the name stuck. One counter-intuitive detail most beginners miss: the numbering does not correspond to release date or chronological order. The numbers reflect the order in which the ROMs were dumped and verified. So c088 is not the last title ever made. It is simply the 88th one to be successfully dumped. Another thing people get wrong is assuming all files in the archive work perfectly. Some dumps have incorrect checksums. Some have mirrored halves that need to be handled properly by the emulator. Always check the MD5 or SHA1 hash against the provided manifest if one exists. If the hash does not match, do not assume the ROM is broken. More often, the dump file itself is fine and the manifest was updated later with a corrected value. In that case, trust the emulator's behavior and the gameplay test over an old hash.
Get the Full Details
A Specific Problem I Encountered
I ran into a situation where a specific cartridge, c044, would boot on OpenMSX but freeze during the second stage on XanaduMSX. The freeze happened consistently at the same point. I checked the ROM dump for truncation. Nothing was missing. The issue was a timing mismatch in the VDP register access during the boot sequence. XanaduMSX had a slightly different VDP emulation timing for that version of the firmware. I worked around it by switching to the MSX Turbo R machine type in XanaduMSX instead of standard MSX2, which forced a different timing path and allowed the cartridge to boot normally. If you encounter a similar freeze, try changing the machine type before trying to reinstall the ROM or updating the emulator. The machine type setting is the simplest variable to adjust.
Where to Find the Archive
The archive is generally distributed through MSX preservation sites and community forums. Look for official pages associated with the MSXdev team or the MSX archive. Do not download from random torrent trackers unless you can verify the source. The original dumps include documentation files that help you understand which titles have known issues. Some mirrors host the files for convenience. The official source remains the most reliable for updated versions and corrected ROMs. If a mirror claims to have a newer version, check the manifest date. Old mirrors often stay current on file count but miss hash corrections.
Verification and File Integrity
Run the provided checksum tool if one is included. Most archive releases come with a manifest.txt or shasums.txt file. Compare each ROM. Anything that fails should be replaced. Do not ignore failures because "it probably works anyway." Failed checksums usually indicate a partial download or a corrupted dump. A partial download will cause the cartridge to hang at a random point during boot. A corrupted dump may cause graphical corruption that looks like an emulator bug when it is actually just bad data. I recommend running a quick gameplay test on every ROM after verification. Ten seconds of play is enough to catch most issues. Titles that crash immediately on verification usually need a different dump. Some titles that seem fine but have sound glitches may have incomplete audio ROM data in the archive.
Common Pitfalls and Honest Limitations
This archive is not a complete collection of all MSX2 cartridges. The 88 number is a subset. Many commercially released MSX2 titles are not included. You will also find that some of the included games use special coprocessors or custom sound chips that emulators do not yet fully replicate. Audio output may be silent or distorted on certain entries even on the best emulator builds. Another limitation is controller support. Some cartridge titles expect a joystick with specific pin configurations. Modern USB adapters often do not map correctly by default. You may need to configure the emulator's input settings manually. This takes about five minutes per game and is worth doing if you plan to play more than one or two titles. If you want a more complete experience, the OpenMSX wiki maintains compatibility lists for each cartridge. Check those lists before investing time in troubleshooting a specific title. You can often find that the issue is known and has a workaround documented.
The archive is useful for preservation and nostalgic play. It is not a substitute for original hardware if you care about perfect audio timing or input latency. Original MSX2 hardware with a clean CMOS battery and a good cartridge edge cleaner will always produce a more accurate result than any emulator. The emulator is close enough for most titles but falls short on a small fraction that use borderline hardware timing.
