Copy Protection

Publishers wanted to sell software. Users wanted to copy it. Copy protection became an arms race — each new technique defeated, each defeat spawning new protection. From bad sectors to code wheels to manual lookups to hardware dongles, the battle between protection and cracking shaped software distribution and spawned the demoscene’s “crack intro” art form.

Fast facts

Motivation: prevent unauthorised duplication of software sold on easily-copied media.
Methods: deliberate disk errors, manual and code-wheel lookups, hardware dongles, and later online activation.
Effectiveness: rarely stopped determined pirates; the arms race below is the evidence.
Side effects: frequently hindered legitimate buyers — a scratched manual or a lost code wheel could make a paid-for game unplayable.
Preservation cost: protected software is materially harder to archive, because a faithful copy has to reproduce deliberate media defects rather than just the data.

Disk-based protection

Disk protections work by writing data the standard format spec doesn’t allow — the original drive can read it, but a normal copy program can’t write it back.

Method	Technique	How it defeats copying
Bad sectors	Intentional CRC-error sectors at known locations	Standard copiers refuse to write CRC-bad sectors
Non-standard formatting	Tracks with extra/missing/oversized sectors	Standard format-and-copy ignores the unusual layout
Weak bits / fuzzy bits	Bits that read inconsistently every time	A “good” copy is consistent, which is itself a tell
Spiral tracks	Track that drifts radially across the disk	Drives can’t reliably step across track boundaries
Half-tracks	Data between the standard track positions	Most consumer drives can’t write to half-tracks
Long tracks	Sectors larger than the format spec allows	Copy software truncates them
Density variations	Different bit-cell timings on different tracks	Standard formats use uniform timing
Sync-mark detection	Custom sync patterns the protection looks for	Recopied tracks have different sync-mark layout

George Trepal set the C64 version of this out in Ahoy! in October 1985: “Virtually all copy protection takes advantage of the fact that the drive and computer hate anything abnormal. Normal copy programs won’t copy errors because — well, because they’re errors and are therefore WRONG!” The error lives in a part of the disk that holds no program data; the program asks the 1541 to read it and treats the error report as proof of an original. His list of the tricks in use was extra tracks beyond 35 (“Track 36 is the easiest to work with and track 40 is the hardest”), half-tracks, two tracks with the same number, a removed sync character, extra sectors after the last one, and altered bit density. Weak bits were still “a technique that has been proposed”. By then the simple errors that had been “adequate protection two years ago” were being copied by “dozens of copy programs on the market”, and he noted the cost to the customer: a protection check done with block reads “involves a great deal of head banging, which can indeed cause head misalignment. All programs copy protected with block reads work to send your drive to the repair shop.”

Tape-based protection

Simon Goodwin traced the Spectrum’s version of the arms race in CRASH’s Christmas Special 1985, and it ran in a clear sequence:

Step	Protection	Answer
1982	Programs saved as CODE, “partly to make them hard to copy with a normal SAVE command, and partly to give the impression that the program was written in machine code”	Tape-to-tape copying, which degraded after “two or three generations”
Early 1983	—	“Clone” programs “to read any tape into memory and dump all of the data back onto cassette”; “a cloned copy was as good as the original”
1983	Files enlarged “to fill all the Spectrum’s memory”, crowding the cloner out of RAM	Cloners that could copy a 48K file
1983-84	Headerless files loaded by a short custom loader, so “a simple clone program can’t copy the rest of the file”	—
1984	Extra information outside the file: gaps of silence, or a Dk’tronics “tune” after the program that the game checked for and “crashed (pretending there had been a loading error)” without	Cloners that copied the gaps too
1984	Hyperloaders “re-defining the tones used to represent each bit of information on the tape” — Speedlock among them	Unreliable loading; “the densely-packed tape is more prone to the effects of duplication faults”

Speedlock came from David Aubrey-Jones and David Looker, who “put our two ideas together” after each had been building a faster loader; Ocean first used it on Daley Thompson’s Decathlon in November 1984, and CRASH’s letters column then argued for months about whether it made games fail to load. Goodwin’s summary of why the industry did not go further: “Electronics was out — tape scramblers, ‘dongles’, ROMs and so forth are expensive and hard to manufacture in bulk.” Sinclair’s Interface 2 cartridges had already failed on cost and a 16K limit. Tape protection is necessarily weaker than disk because audio is a continuous medium — you can always record the analogue signal and replay it.

Manual-based protection

Type	Implementation	Examples
Colour-code card	Match on-screen coloured blobs to a printed table	Jet Set Willy (1984), Giant’s Revenge
Code wheels	Rotating cardboard decoder	Monkey Island (Dial-a-Pirate), Pool of Radiance
Word lookup	“Word 3, line 5, page 12 of the manual”	Zak McKracken, Indiana Jones and the Last Crusade
Symbol matching	Match a screen image to a manual page	Wing Commander, Ultima series
Dark-text print	Manual printed in red-on-red ink	Hard to photocopy in mono; often paired with red-cellophane decoder
Trivia / age-gates	“What is the capital of …?” pulled from manual	Leisure Suit Larry age-verification, Where in the World Is Carmen Sandiego?

The earliest form the magazines describe is Jet Set Willy’s card: “a colour-coded table printed in the cassette inlay. When the program is loaded it displays a row of randomly coloured blobs — these have to be matched up with the table, and appropriate keys must to be pressed before the game starts.” Goodwin’s objections in 1985 are the ones that would follow every later scheme: “it is irritating for legitimate owners of the game, who have to go through the same ritual every time they want to load their copy”, it defeated “those with poor eyesight or grotty TV’s”, and “once the colours have been written as letters it takes less than 10 minutes to copy the whole chart”. The page-line-word lookup was still standard on C64 disk games in 1991; ZZAP! praised Gateway to the Savage Frontier for asking “only the first time you start, instead of the previous random calls”.

See Manual Protection for the broader picture.

Lenslok

Aspect	Detail
System	A plastic lens of prisms that swaps the columns of an on-screen dot pattern back into two readable characters
Use	Scale the display to the lens holder, hold the lens to the TV, type the two characters within ten seconds
Notable failures	Elite shipped with wrong set-up instructions and, in about 500 copies, the wrong lens; small screens and anti-glare filters threw it off; the lens itself was small enough to lose
Reception	“all set to take over from turbo loaders as The Big Moan” (CRASH, February 1986) — though CRASH also called it “the best anti-piracy device that the home computer market has seen so far”

See Lenslok for the standalone story.

Hardware dongles

Platform	Application
Amiga / Atari ST	Parallel-port dongles for high-end software (CAD, music)
PC	Professional software (AutoCAD, Pro/E, music) into the 2000s
Arcade	“Security chips” embedded in JAMMA boards (Capcom CPS-2 SEGA System 32)
PlayStation 1	Mod-chips and disc-based protections worked the other direction

Dongles eventually evolved into USB security keys (HASP, SafeNet, Sentinel) used by enterprise software through the 2010s.

Notable protection systems

System	Platform	Notes
Copylock (Rob Northen)	Amiga, Atari ST	The dominant 16-bit disk protection; see Copylock
Speedlock (David Aubrey-Jones and David Looker)	ZX Spectrum	Tape hyperloader with protection; first used by Ocean on Daley Thompson’s Decathlon, November 1984
RapidLok	C64	Disk protection named as a target in 1988 copier advertising (“Capable of Archiving RapidLok Protection”)
Macrovision	PlayStation, PS2	Optical-disc subchannel data
SecuROM	PC	Late 90s / 2000s; CD/DVD-based, became infamous for system instability
StarForce	PC	Aggressive 2000s-era driver-level protection
SafeDisc	PC	Microsoft-owned CD protection

Cracker techniques

Method	What it does	Counter from publishers
Disk image analysis	Capture every track’s raw data, find what’s unusual	Move check to encrypted code
Static patching	Find the protection check, NOP it out	Multiple checks, scattered throughout the program
Trainers	Bypass with options menus or cheats	Anti-debug, integrity self-checks
Complete rewrite	Replace the whole loader with a fresh one	Encrypt the actual game code with the protection key

On the C64 the escalation produced a product category of its own. Nibble copiers read whole tracks rather than blocks and so, as Trepal put it, “since the nibble copier doesn’t have to worry about such things as synch characters, it’s harder to protect against”. When protection reached the point that “cannot be duplicated by a Commodore disk drive”, the answer was the parameter copier: a disk of small BASIC programs, each “a detailed set of instructions which when properly applied simply neutralize or modify the program’s copy protection”. Ahoy!’s January 1987 review of Kracker Jax counted 82, 104 and 101 parameters across its three volumes, each “a series of block reads and writes which change specific bytes of the program disk” — one-shot cracks sold by mail order and advertised in COMPUTE!’s Gazette under the headline “ARE YOU CAUGHT UP IN THE COPY PROTECTION ARMS RACE?” The result was a years-long escalation: by the late 1990s most commercial games had layered protections that could only be defeated by reverse-engineering the entire protection runtime.

User impact

Problem	Effect
Backup inability	Can’t make personal copies; original disk wears out
Hardware failures	Floppy drive dies, game dies with it
False positives	Legitimate copies rejected on slightly out-of-spec drives
Load times	Extended by checks (every load runs the protection too)
Lost manuals	Whole game becomes unplayable
Lost dongles	Same

These frustrations drove legitimate users to seek out cracked versions — protection that punishes paying customers is the textbook anti-pattern that the industry took decades to admit.

Legacy

Era technique	Modern equivalent
Disk bit-pattern protections	DRM, online activation servers
Manual lookups	Account systems (Steam, Epic, console accounts)
Hardware dongles	USB security keys, hardware-backed attestation
Crack intro culture	Demoscene endured; the technical skills informed early indie / homebrew
Arms race	Continues today, only the medium changes

The anti-piracy arms race