Contents

Disk Versus Tape: The Two Different C64s

Two storage formats split one machine's audience for a decade, and the split never fully healed

Contents

Every Commodore 64 came with a spare port on the back for the Datasette, and most machines in Britain never used anything else. Say “C64” to me and the first sound in my head is the motor of a cassette deck kicking in, the slight wow of a stretched belt, and the two minutes of silence you sat through hoping the counter numbers you’d copied off a photocopied inlay were the right ones. The Commodore 64 was, on paper, one machine. In practice it was two computers wearing the same beige case, and which one you owned depended entirely on whether your parents paid an extra chunk of money for a box with a slot in it.

The machine that shipped with a cassette

Advertisement

The Datasette was cheap because a cassette deck was already a commodity part by 1982 — Commodore didn’t have to invent anything, just bolt an edge connector onto the kind of mechanism already sitting in millions of home stereos. It stored data as audio tones, read and wrote sequentially, and had no concept of a directory: you loaded the file that was next on the tape, in the order it was recorded, or you fast-forwarded and guessed how far. A full game could take anywhere from ninety seconds to several minutes depending on how densely it was encoded, and if the tape stretched, the heads needed cleaning, or the volume dial on your hi-fi wasn’t at the exact setting the last successful load used, you started again from nothing. Anyone who owned a C64 in this era owned a small ritual around getting a game to actually run, and swapped tips about it the way people now swap router settings.

Software houses built an entire aesthetic around that wait. Loading screens carried static art and, from the mid-80s, music — Rob Hubbard and Martin Galway wrote entire compositions whose sole job was to fill dead air, and a good loading tune became a selling point in its own right, reviewed alongside the game in the pages of Zzap!64 and Commodore User. Multi-load design, where a game streamed level data from tape between stages rather than holding it all in the 64’s 64 kilobytes of RAM at once, turned the format’s weakness into a structural feature: you could build a bigger game than memory allowed, provided the player accepted intermissions. A game like a licensed film tie-in or an ambitious platformer might load in four or five distinct chunks, each announced by its own screen, and part of what made those games feel substantial was precisely that they’d made you wait for more of them.

A drive that cost almost as much as the computer

The alternative was the 1541, a 5.25-inch floppy drive that in its early UK years retailed for a sum close to what the computer itself cost. That price alone kept it out of most households — a family that had just stretched to a C64 was not stretching again for a drive within the same year, and retailers bundled the machine with the Datasette as the assumed default, selling the 1541 as an accessory for later, for the serious ones, for Christmas the year after. The 1541 held around 170 kilobytes per disk side, accessed data non-sequentially, and let a program load a directory, pick a file, and jump straight to it rather than winding tape past everything that came before. For anyone who could afford one, it transformed what the C64 was for — from a machine you loaded one game into at a time to one you could browse.

The bug that made the 1541 slow

Advertisement

What makes the 1541’s story stranger than a simple rich-owner’s-upgrade tale is that it was also, notoriously, slower at raw transfer than a drive that price had any right to be. The drive and the computer talk over a serial bus, one bit at a time, when the original engineering intent — by the well-documented account that circulates among Commodore hardware historians — was a faster parallel connection using the same VIA chip already doing duty elsewhere in the machine. A bug in that chip’s shift register, discovered late in the drive’s development, forced Commodore’s engineers to disable the parallel path and bit-bang the protocol in software instead, and the workaround shipped because there was no time left to respin the silicon before launch. The result was a drive that, file for file, could be outpaced by a good tape fastloader, which is why an entire third-party industry of turbo-loading cartridges and disk fastloaders — Action Replay chief among them, alongside dozens of software-only loaders bundled quietly into commercial releases — existed for the rest of the machine’s life, patching around a bug baked into launch hardware that Commodore itself never fully fixed.

What disk buys you that tape cannot

Speed complaints aside, disk unlocked things tape structurally could not do, and this is where the split stopped being about money and started being about genre. Random access meant save games — a role-playing game or a graphic adventure could write your progress to a spare part of the disk and read it back later, something a sequential tape format made painfully slow and unreliable by comparison, since finding the right point on a cassette to overwrite without corrupting the rest of the data was a genuinely hard engineering problem that few tape-only games attempted. It meant copy-protection schemes tape couldn’t replicate — non-standard sector formatting, deliberately malformed tracks a legitimate drive could read but a naive copier choked on — which is partly why disk became the format serious software houses defended hardest against piracy, and why disk cracking became its own competitive discipline within the cracking scene. And it meant a directory, which sounds trivial until you’ve owned forty tapes with handwritten labels in biro and forty disks that simply tell you, on screen, what’s on them and how much space is left.

Britain stayed on tape longer than America did

The regional split mattered more than most retrospectives admit. In the United States, disk ownership climbed faster, helped by a market where the drive’s price sat closer to disposable-income norms and where mail-order software culture favoured a format that didn’t wear out in the post the way a cassette’s magnetic coating could. In Britain, the budget label built the opposite economy: Mastertronic priced full games at £1.99 specifically because tape was nearly free to duplicate in bulk, and a £1.99 disk release made no arithmetic sense when the blank media alone cost more than that price point allowed. The budget label model and the tape format needed each other to exist, and between them they kept a generation of British C64 owners tape-only well into the machine’s life, buying a disk drive only once they’d outgrown £1.99 games and started wanting the disk-only releases from the bigger houses that assumed you’d already made the jump.

Two shelves, two magazines

The split showed up in how the games press packaged itself, too. Cover-mounted tapes were the norm for most of the C64’s commercial life — a covertape stuck to the front of a magazine could carry a handful of playable budget titles or demos at a duplication cost publishers could stomach, and it was how a huge number of UK players first encountered software they’d never have bought blind. Cover disks arrived later and stayed rarer, precisely because pressing a floppy cost more per unit than dubbing a cassette, and a magazine gambling on a cover disk was betting that enough of its readership had a drive to make the higher unit cost worthwhile. For years, that bet didn’t pay off for most titles, and the covertape remained the format that actually reached the largest number of bedrooms.

Multi-load tape design reached its most visible form in Ocean Software’s big licensed titles. Robocop and Batman: The Caped Crusader both split their game across several loads, each stage announced with its own screen and its own chunk of loading music, and reviewers of the time treated the wait as part of the experience rather than a defect to apologise for — a longer load implied a bigger game coming, in a way that felt earned rather than punitive. Disk versions of the same titles existed and loaded faster stage to stage, but they were the format for the minority who’d already made the jump, and the tape version was the one most readers of Zzap!64 or Commodore User were actually describing to each other in the school playground on a Monday.

Role-playing and adventure games sat on the other side of the same divide for a more structural reason: they needed to write persistent progress, a capability tape’s read-mostly sequential format never handled comfortably. A game like an imported CRPG that tracked a persistent party across dozens of hours had to save state somewhere a player could trust, and disk’s random access made that a reasonable proposition in a way tape’s sequential, easily-corrupted format did not. Publishers bringing American disk-based RPGs to the UK market sometimes shipped disk-only for exactly this reason, accepting a smaller addressable audience in exchange for a save system that actually worked, and that decision alone tells you how firmly the format determined the genre rather than the other way round.

Living with both

None of this means one format was simply the poor relation to the other. Tape taught patience in a way that shaped how those games were built to reward it — a loading screen was a promise, and a game had to be worth the wait it had just demanded, which is a discipline modern digital storefronts with instant installs have mostly lost the need for. Disk taught a different lesson: that a machine could hold more than one thing in reserve, that progress could persist between sessions, that a directory of forty files was a shelf rather than a shoebox you rummaged through by feel. The Commodore 64 that most people actually played was built around one of those ideas and not the other, and the gap between them is still visible in what got made for it — the multi-load epics that only made economic sense because tape was cheap to fill with data, and the save-driven role-playing and adventure games that only worked because a spinning disk was there to catch your progress and hand it back. Two machines wearing one case, and neither has quite had its due for what the other made possible on the same afternoon, in the same bedroom, from the same beige keyboard.

Advertisement
Advertisement
Jay
Written by Jay

vo.rs's games critic. Jay covers the medium as a system rather than a spectacle — this month's release, the indie nobody bought, and the Amiga game it's quietly descended from — asking what a mechanic makes you feel and why the loop holds. Learned to wait through a C64 tape load, never stopped playing since, and still finishes the odd 60-hour RPG out of spite. Expect argued verdicts, no score ever, spoilers below the line, and a running list of older games worth your weekend.