RSS

A Pirate’s Life for Me, Part 3: Case Studies in Copy Protection

Copy-protection schemes, whether effected through software, a combination of software and hardware, or hardware alone, can and do provide a modicum of software protection. But such schemes alone are no better forms of security than locks. One with the appropriate tools can pick any lock. Locks only project the illusion of protection, to both the owner and the prospective thief.

Our focus on copy protection is the primary reason why our industry’s software-protection effort has come under skeptical scrutiny and intense attack. Many users now consider the copy-protection scheme to be just an obstacle to be overcome en route to their Congressionally- and self-granted right to the backup copy.

Dale A. Hillman
President, XOR Software
1985

An impregnable copy-protection scheme is a fantasy. With sufficient time and effort, any form of copy protection can be broken. If game publishers didn’t understand this reality at the dawn of their industry, they were given plenty of proof of its veracity almost as soon as they began applying copy protection to their products and legions of mostly teenage crackers began to build their lives around breaking it.

Given the unattainability of the dream of absolute protection, the next best thing must be protection that is so tough that the end result of a cracked, copyable disk simply isn’t worth the tremendous effort required to get there. When even this level of security proved difficult if not impossible to achieve, some publishers — arguably the wisest — scaled back their expectations yet further, settling for fairly rudimentary schemes that would be sufficient to deter casual would-be pirates but that would hardly be noticed by the real pros. Their games, so the reasoning went, were bound to get cracked anyway, so why compound the loss by pouring money into ever more elaborate protection schemes? Couldn’t that money be better used to make the game themselves better?

Others, however, doubled down on the quixotic dream of the game that would never be cracked, escalating a war between the copy-protection designers who developed ever more devious schemes and the intrepid crackers of the scene, the elite of the elite who staked their reputations on their ability to crack any game ever made. In the long term, the crackers won every single battle of this war, as even many of the publishers who waged it realized was all but inevitable. The best the publishers could point to was a handful of successful delaying actions that bought their games a few weeks or months before they were spread all over the world for free. And even those relative successes, it must be emphasized, were extremely rare. Few schemes stood up much more than a day or two under the onslaught of the scene’s brigade of talented and highly motivated crackers.

Just as so many crackers found the copy-protection wars to be the greatest game of all, far more intriguing and addictive than the actual contents of the disks being cracked, the art of copy protection — or, as it’s more euphemistically called today, digital-rights management or DRM — remains an almost endlessly fascinating study for those of a certain turn of mind. Back in the day, as now, cracking was a black art. Both sides in the war had strong motivations to keep it so: the publishers because information on how their schemes worked meant the power to crack them, and the crackers because their individual reputations hinged on being the first and preferably the only to crack and spread that latest hot game. Thus information in print on copy protection, while not entirely unheard of, was often hard to find. It’s only long since that wild and woolly first decade of the games industry that much detailed information on how the most elaborate schemes worked has been widely available, thanks to initiatives like The Floppy Disk Preservation Project.

This article will offer just a glimpse of how copy protection began and how it evolved over its first decade, as seen through the schemes that were applied to four historically significant games that we’ve already met in other articles: Microsoft Adventure for the TRS-80, Ultima III for the Apple II, Pirates! for the Commodore 64, and Dungeon Master for the Atari ST. Sit back, then, and join me on a little tour through the dawn of DRM.

Microsoft Adventure box art

The release of Microsoft Adventure in late 1979 for the Radio Shack TRS-80 marks quite a number of interrelated firsts for the games industry. It was the first faithful port of Will Crowther and Don Woods’s perennial Adventure, itself one of the most important computer games ever written, to a home computer. It accomplished this feat by taking advantage of the capabilities of the floppy disk, becoming in the process the first major game to be released on disk only, as opposed to the cassettes that still dominated the industry. And to keep those disks from being copied, normally a trivially easy thing to do in comparison to copying a cassette, Microsoft applied one of the earliest notable instances of physical copy protection to the disk, a development novel enough to attract considerable attention in its own right in the trade press. Byte magazine, for instance, declared the game “a gold mine for the enthusiast and a nightmare for the software pirate.”

Floppy Disk

The core of a 5¼-inch floppy disk, the type used by the TRS-80 and most other early microcomputers, is a platter made of a flexible material such as Mylar — thus the “floppy” — with a magnetic coating made of ferric oxide or a similar material, capable of recording the long sequences of ones and zeroes (or ons and offs) that are used to store all computer code and data. The platter is housed within a plastic casing that exposes just enough of it to give the read/write head of the disk drive access as the platter is spun.

The floppy disk is what’s known as a random-access storage medium. Unlike a cassette drive, a floppy drive can access any of its contents at any time at a simple request from the computer to which it’s attached. To allow this random access, there needs to be an organizing scheme to the disk, a way for the drive to know what lies where and, conversely, what spaces are still free for writing new files. A program known as a “formatter,” which must be run on every new disk before it can be used, writes an initially empty framework to the disk to keep track of what it contains and where it all lives on the disk’s surface.

In the case of the TRS-80, said surface is divided into 35 concentric rings, known as “tracks,” numbered from 0 to 34, with track 0 lying at the outer margin of the disk and track 34 closest to the inner ring. Each track is subdivided along its length into 10 equal-sized sectors, each capable of storing 256 bytes of data. Thus the theoretical maximum capacity of an entire disk is about ((256 * 10 * 35) / 1024) 87 K.

Figure 1

Figure 1 (click to expand)

Figure 1 shows the general organization of the tracks on a TRS-80 disk. Much of this is specific to the TRS-80’s operating system and thus further down in the weeds than we really need to go, but a couple of details are very relevant to our purposes. Notice track 18, the “system directory.” It’s just what its name would imply. The entire track is reserved to be the disk’s directory service, a list of all the files it contains along with the track and sector numbers where each begins. The directory is placed in the middle of the disk for efficiency’s sake. Because it must be read from every time a file is requested, having it here minimizes the distance the head must travel both to read from the directory and, later, to access the file in question. For the same reason, most floppy-disk systems try to fill disks outward from the directory track, using the farthest-flung regions only if the disk is otherwise full.

The one exception to this rule in the case of the TRS-80 as well as many other computers is the “boot sector”: track 0, sector 0. It contains code, stored outside the filesystem described in the directory, which the computer will always try to access and execute on boot-up. This “bootstrap” code tells the computer how to get started loading the operating system and generally getting on with things. There isn’t much space here — only a single sector’s worth, 256 bytes — but it’s enough to set the larger process in motion.

Figure 2

Figure 2

Figure 2 shows the layout of an individual disk sector. This diagram presumes a newly formatted disk, so the “dummy data” represents the sector’s 256 bytes of available storage, waiting to be filled. Note the considerable amount of organizing and housekeeping information surrounding the actual data, used to keep the drive on track and aware at all times of just where it is. Again, there’s much more here than we need to dig into today. Relevant for our purposes are the track and sector numbers stored near the beginning of each sector. These amount to the sector’s home address, its index in the directory listing.

Microsoft Adventure introduces a seeming corruption into the disk’s scheme. Beginning with track 1 — track 0 must be left alone so the system can find the boot sector and get started — the tracks are numbered not from 1 to 34 but from 127 to 61, in downward increments of 2. The game’s bootstrap inserts a patch into the normal disk-access routines that tells them how to deal with these weirdly numbered tracks. But, absent the patch, the normal TRS-80 operating system has no idea what to make of it. Even a so-called “deep” copier, which tries to copy a disk sector by sector rather than file by file to create a truly exact mirror image of the original, fails because it can’t figure out where the sectors begin and end.

If one wants to make a copy of a protected program, whether for the legal purpose of backing it up or the illegal one of software piracy, one can take either of two approaches. The first is to find a way to exactly duplicate the disk, copy protection and all, so that there’s no way for the program it contains to know it isn’t running on an original. The other is to crack it, to strip out or ignore the protection and modify the program itself to run correctly without it.

One of the first if not the first to find a way to duplicate Microsoft Adventure and then to crack it to boot was an Australian teenager named Nick Andrew (right from the beginning, before the scene even existed, cracking already seemed an avocation for the young). After analyzing the disk to work out how it was “corrupted,” he rewrote the TRS-80’s usual disk formatter to format disks with the alternate track-numbering system. Then he rewrote the standard copier to read and write to the same system. After “about two days,” he had a working duplicate of the original disk.

But he wasn’t quite done yet. After going through all the work of duplicating the disk, the realization dawned that he could easily go one step further and crack it, turn it into just another everyday disk copyable with everyday tools. To do so, he wouldn’t need his modified disk formatter at all. He needed only make a modification to his customized copier, to read from a disk with the alternate track-numbering system but write to a normal one. Remove the custom bootstrap to make Adventure boot like any other disk, and he was done. This first “nightmare for the software pirate” was defanged.

Ultima III

Released in 1983, Ultima III was already the fourth commercial CRPG to be written by the 22-year-old Richard Garriott, but the first of them to be published by his own new company, Origin Systems. With the company’s future riding on its sales, he and his youthful colleagues put considerable effort into devising as tough a copy-protection scheme as possible. It provides a good illustration of the increasing sophistication of copy protection in general by this point, four years after Microsoft Adventure.

Apple II floppy-disk drives function much like their TRS-80 equivalents, with largely only practical variations brought on by specific engineering choices. The most obvious of the differences is the fact that the Apple II writes its data more densely to the disk, giving it 16 256-byte sectors on each of its 35 tracks rather than the 10 of the TRS-80. This change increases each disk’s capacity to ((256 * 16 * 35) / 1024) 140 K.

Ultima III shipped on two disks, one used to boot the game and the other to load in data and to save state as needed during play. The latter is a completely normal Apple II disk, allowing the player to make copies as she will in the name of being able to start a fresh game with a new character at any time. The former, however, is a different story.

The game’s first nasty trick is to make the boot disk less than half a disk. Only tracks 0 through 16 are formatted at all. Like the TRS-80, the Apple II expects the disk’s directory to reside in the middle of the disk, albeit on track 17 rather than 18. In this case, though, track 17 literally doesn’t exist.

But how, you might be wondering, can even a copy-protected disk function at all without a directory? Well, it really can’t, or at least it doesn’t in this case. Again like the TRS-80, the beginning of an Apple II disk is reserved for a boot block. The Ultima III bootstrap substitutes alternative code for a standard operating-system routine called the “Read Write Track Sector” routine, or, more commonly, the “RWTS.” It’s this routine that programs call when they need to access a disk file or to do just about any other operation to a disk. Ultima III provides an RWTS that knows to look for the directory listing not on track 17 but rather on track 7, right in the middle of its half-a-disk. Thus it knows how to find its files, but no one else does.

Ultima III‘s other trick is similar to the approach taken by Microsoft Adventure in theory, but far more gnarly in execution. To understand it, we need to have a look at the structure of an Apple II sector. As on the TRS-80, each sector is divided into an “address field,” whose purpose is to keep the drive on track and help it to locate what it’s looking for, and a “data field” containing the actual data written there. Figures 3 and 4 show the structure of each respectively.

Figure 3

Figure 3

Figure 4

Figure 4

Don’t worry too much about the fact that our supposed 256 bytes of data have suddenly grown to 342. This transformation is down to some nitty-gritty details of the hardware that mean that 256 logical bytes can’t actually be packed into 256 bytes of physical space, that the drive needs some extra breathing room. A special encoding process, known as Group Code Recording (GCR) on the Apple II, converts the 256 bytes into 342 that are easily manipulable by the drive and back again. If we were really serious about learning to create copy protection or how to crack it, we’d need to know a lot more about this. But it’s not necessary to understand if you’re just dipping your toes into that world, as we’re doing today.

Of more immediate interest are the “prologues” and “epilogues” that precede and trail both the address and data fields. On a normal disk these are fixed runs of numbers, which you see shown in hexadecimal notation in Figures 3 and 4. (If you don’t know what that means, again, don’t worry too much about it. Just trust me that they’re fixed numbers.) Like so much else here, they serve to keep the drive on track and to reassure it that everything is kosher.

Ultima III, however, chooses other numbers to place in these spaces. Further, it doesn’t just choose a new set of fixed numbers — that would be far too easy — but rather varies the expected numbers from track to track and even sector to sector according to a table only it has access to, housed in its custom RWTS. Thus what looks like random garbage to the computer normally suddenly becomes madness with a method behind it when the computer has been booted from the Ultima III disk. If any of these fields doesn’t match with what it should be — i.e., if someone is trying to use an imperfect copy —  the game loads no further.

It’s a tough scheme, particularly for its relatively early date, but far from an unbreakable one. There are a couple of significant points of vulnerability. The first is the fact that Ultima III doesn’t need to read and write only protected disks. There is, you’ll remember, also that second disk in a standard format. The modified RWTS needs to be able to fall back to the standard routine when using that second disk, which is no more readable by the modified routine than the protected disk is by the standard. It relies on the disk’s volume number to decide which routine to use: volume 1 is the first, protected disk; volume 2 the second, unprotected (if the volume number is anything else, it knows somebody must be up to some sort of funny business and just stops entirely). Thus if we can just get a copy of the first disk in an everyday disk format and set its volume number to 2, Ultima III will happily accept it and read from it.

But that “just” is, of course, a tricky proposition. We would seemingly need to write a program of our own to read from a disk — or rather from half of a disk — with all those ever-changing prologue and epilogue fields. That, anyway, is one approach. But, if we’re really clever, we won’t have to. Instead of working harder, we can work smarter, using Ultima III‘s own code to crack it.

One thing that legions of hackers and crackers came to love about the Apple II was its integrated machine-language monitor, which can be used to pause and break into a running program at almost any point. We can use it now to pause Ultima III during its own boot process and look up the address of its customized RWTS in memory; because all disk operations use the RWTS, it is easily locatable via a global system pointer. Once we know where the new RWTS lives, we can save that block of memory to disk for later use.

Next we need only boot back into the normal system, load up the customized RWTS we saved to disk, and redirect the system pointer to it rather than the standard RWTS. Remember that the custom RWTS is already written to assume that disks with a volume number of 1 are in the protected format, those with a volume number of 2 in the normal format. So, if we now use an everyday copy program to copy from the original, which has a volume number of 1, to a blank disk which we’ve formatted with a volume number of 2, Ultima III essentially cracks itself. The copy operation, like all disk operations, simply follows the modified system pointer to the new RWTS, and is never any the wiser that it’s been modified. Pretty neat, no? Elegant tricks like this warm any hacker’s heart, and are much of the reason that vintage cracking remains to this day such an intriguing hobby.

Pirates!

Ultima III‘s copy protection was clever enough in its day, but trivial compared to what would start to appear just a year or so later as the art reached a certain level of maturity. As the industry itself got more and more cutthroat, many of the protection schemes also got just plain nasty. The shadowy war between publisher and pirate was getting ever more personal.

A landmark moment in the piracy wars was the 1984 founding of the Software Publishers Association. It was the brainchild of a well-connected Washington, D.C., lawyer named Ken Wasch who decided that what the industry really needed was a D.C.-based advocacy group and that he, having no previous entanglements within it, was just the neutral party to start it. The SPA had a broad agenda, from gathering data on sales trends from and for its members to presenting awards for “software excellence,” but, from the perspective of the outsider at any rate, seemed to concern itself with the piracy problem above all else. Its rhetoric was often strident to the point of shrillness, while some of its proposed remedies smacked of using a hydrogen bomb to dig a posthole. For instance, the SPA at one point protested to Commodore that multitasking shouldn’t be a feature of the revolutionary new Amiga because it would make it too easy for crackers to break into programs. And Wasch lobbied Congress to abolish the user’s right to make backup copies of their software for personal archival purposes, a key part of the 1980 Software Copyright Act that he deemed a “legal loophole” because it permitted the existence of programs capable of copying many forms of copy-protected software — a small semi-underground corner of the software industry that the SPA was absolutely desperate to eliminate rather than advocate for. The SPA also did its best to convince the FBI and other legal authorities to investigate the bulletin-board systems of the cracking scene, with mixed success at best.

Meanwhile copy protection was becoming a business in its own right, the flip side to the business of making copying programs. In place of the home-grown protection schemes of our first two case studies, which amounted to whatever the developers themselves could devise in whatever time they had available, third-party turnkey protection systems, the products of an emerging cottage industry, became increasingly common as the 1980s wore on. The tiny companies that created the systems weren’t terribly far removed demographically from the crackers that tried to break them; they were typically made up of one to three young men with an encyclopedic knowledge of their chosen platforms and no small store of swagger of their own. Their systems, sporting names like RapidLok and PirateBusters, were multifaceted and complex, full of multiple failsafes, misdirections, encryptions, and honey pots. Copy-protection authors took to sneaking taunting messages into their code, evincing a braggadocio that wouldn’t have felt out of place in the scene: “Nine out of ten pirates go blind trying to copy our software. The other gets committed!”

Protection schemes of this later era are far too complex for me to describe in any real detail in an accessible article like this one, much less explain how people went about cracking them. I would, however, like to very briefly introduce RapidLok, the most popular of the turnkey systems on the Commodore 64. It was the product of a small company called the Dane Final Agency, and was used in its various versions by quite a number of prominent publishers from early 1986 on, including MicroProse. You’ll find it on that first bona fide Sid Meier classic, the ironically-titled-for-our-purposes Pirates!, along with all of their other later Commodore 64 games.

The protection schemes we’ve already seen have modified their platforms’ standard disk formats to confuse copy programs. RapidLok goes to the next level by implementing its own custom format from scratch. A standard Commodore 64 disk has 17 to 21 sectors per track, depending on where the track is located; a RapidLok disk has 11 or 12 much larger sectors, with the details of how those sectors organize their data likewise re-imagined. Rapidlok also adds a track to the standard 35, shoved off past the part of the disk that is normally read from or written to. This 36th track serves as an encrypted checksum store for all of the other tracks. If any track fails the checksum check — indicating it’s been modified from the original — the system immediately halts.

Like any protection scheme, RapidLok must provide a gate to its walled garden, an area of the disk formatted normally so that the computer can boot the game in the first place. Further, writing to RapidLok-formatted tracks isn’t practical. The computer would need to recalculate the checksum for the track as a whole, encrypt it, and rewrite that portion to the checksum store out past the normally accessible part of the disk — a far too demanding task for a little Commodore 64. For these reasons, Rapidlok disks are hybrids, partially formatted as standard disks and partially in the protected format. Figure 5 below shows the first disk of Pirates! viewed with a contemporary copying utility.

Figure 5

Figure 5

As the existence of such a tool will attest, techniques did exist to analyze and copy RapidLok disks in their heyday. Among the crackers, Mitch of Eagle Soft was known as the RapidLok master; it’s his vintage crack of Pirates! and many other RapidLok-protected games that you’ll find floating around the disk-image archives today. Yet even those cracks, masterful as they were, were forced to strip out a real advantage that RapidLok gave to the ordinary player, that was in fact the source of the first part of its name: its custom disk format was much faster to read from than the standard, by a factor of five or six. Pirates who chose to do their plundering via Mitch’s cracked version of Pirates! would have to be very patient criminals.

But balanced against the one great advantage of RapidLok for the legitimate user was at least one major disadvantage beyond even the obvious one of not being able to make a backup copy. In manipulating the Commodore 64 disk drive in ways its designers had never intended, RapidLok put a lot of stress on the hardware. Drives that were presumably just slightly out of adjustment, but that nevertheless did everything else with aplomb, proved unable to load RapidLok disks, or, almost worse, failed intermittently in the middle of game sessions (seemingly always just after you’d scored that big Silver Train robbery in the case of Pirates!, of course). And, still worse from the standpoint of MicroProse’s customer relations, a persistent if unproven belief arose that RapidLok was actually damaging disk drives, throwing them out of alignment through its radical operations. It certainly didn’t sound good in action, producing a chattering and general caterwauling and shaking the drive so badly one wondered if it was going to walk right off the desktop one day.

The belief, quite probably unfounded though it was, that MicroProse and other publishers were casually destroying their customers’ expensive hardware in the name of protecting their own interests only fueled the flames of mistrust between publisher and consumer that so much of the SPA’s rhetoric had done so much to ignite. RapidLok undoubtedly did its job in preventing a good number of people from copying MicroProse games. A fair number of them probably even went out and bought the games for themselves as an alternative. Whether those sales were worth the damage it did to MicroProse’s relations with their loyal customers is a question with a less certain answer.

Dungeon Master

No discussion of copy protection in the 1980s could be complete without mentioning Dungeon Master. Like everything else about FTL’s landmark real-time CRPG, its copy protection was innovative and technically masterful, so much so that it became a veritable legend in its time. FTL wasn’t the sort of company to be content with any turnkey copy-protection solution, no matter how comprehensive. What they came up with instead is easily as devious as any dungeon level in the game proper. As Atari ST and Amiga crackers spent much of 1988 learning, every time you think you have it beat it turns the tables on you again. Let’s have a closer look at the protection used on the very first release of Dungeon Master, the one that shipped for the ST on December 15, 1987.

3 1/2 inch floppy disk

With the ST and its 68000-based companions, we’ve moved into the era of the 3½-inch disk, a format that can pack more data onto a smaller disk and also do so more reliably; the fragile magnetic platter is now protected beneath a rigid plastic case and a metal shield that only pulls away to expose it when the disk is actually inserted into a drive. The principles of the 3½-inch disk’s operation are, however, the same as those of the 5¼-inch, so we need not belabor the subject here.

Although most 3½-inch drives wrote to both sides of the disk, early STs used just one, in a format that consisted of 80 tracks, each with 9 512-byte sectors, for a total of ((512 * 9 * 80) / 1024) 360 K of storage capacity. The ST uses a more flexible filesystem than was the norm on the 8-bit machines we’ve discussed so far, one known as FAT, for File Allocation Table. The FAT filesystem dates back to the late 1970s, was adopted by Microsoft for MS-DOS in 1981, and is still in common use today in a form known as FAT32; the ST uses FAT12. The numerical suffix refers to the number of bits allocated to each file’s home address on the disk, which in turn dictates the maximum possible capacity of the disk itself. FAT is designed to accommodate a wide range of floppy and hard disks, and thus allows the number of tracks and sectors to be specified at the beginning of the disk itself. Thanks to FAT’s flexibility, Dungeon Master can easily bump the number of sectors per track from 9 to 10, a number still well within the capabilities of the ST’s drive. That change increases the disk’s storage capacity to ((512 * 10 * 80) / 1024) 400 K. It was only this modification, more a response to a need for just a bit more disk space than an earnest attempt at copy protection, that allowed FTL to pack the entirety of Dungeon Master onto a single disk.

Dungeon Master‘s real protection is a very subtle affair, which is one of the keys to its success. At first glance one doesn’t realize that the disk is protected at all — a far cry from the radical filesystem overhaul of RapidLok. The disk’s contents can be listed like those of any other, its individual files even read in and examined. The disk really is a completely normal one — except for track 0, sectors 7 and 8.

Let’s recall again the two basic methods of overcoming copy protection: by duplicating the protection on the copy or by cracking the original, making it so that you don’t need to duplicate the protection. Even with a scheme as advanced as RapidLok, duplication often remained an option. Increasingly by the era of Dungeon Master, though, we see the advent of schemes that are physically impossible for the disk drives on the target machines to duplicate under any circumstances, that rely on capabilities unique to industrial-scale disk duplicators. Nate Lawson, a reader of this blog who was hugely helpful to me in preparing this article, describes good copy protection as taking advantage of “asymmetry”: “the difference between the environment where the code is executed versus where it was produced.” The ultimate form of asymmetry must be a machine on the production side that can write data in a format that the machine on the execution side physically cannot.

Because FTL duplicated their own disks in-house rather than using an outside service like most publishers, they had a great deal of control over the process used to create them. They used their in-house disk duplicator to write an invalid sector number to a single sector: track 0, sector 8 is labeled sector 247. At first blush, this hardly seems special; Microsoft Adventure, that granddaddy of copy-protected games, had after all used the same technique eight years earlier. But there’s something special about this sector 247: due to limitations of the ST’s drive hardware that we won’t get into here, the machine physically can’t write that particular sector number. Any disk with a sector labeled 247 has to have come from something other than an ST disk drive.

Track 0, sector 7, relies on the same idea of hardware asymmetry, but adds another huge wrinkle sufficient to warm the heart of any quantum physicist. Remember that the data stored on a disk boils down to a series of 1s and 0s, magnetized or demagnetized areas that are definitively in one state or the other. But what if it was possible to create a “fuzzy” bit, one that capriciously varies between states on each successive read? Well, it wasn’t possible to do anything like that on an ST disk drive or even most industrial disk duplicators. But FTL, technology-driven company that they were, modified their own disk duplicator to be able to do just that. By cramming a lot of “flux reversals,” or transitions between a magnetic and demagnetized state, into a space far smaller than the read resolution of the ST disk drive, they could create bits that lived in a perpetually in-between state — bits that the drive would randomly read sometimes as on and sometimes as off.

Dungeon Master has one of these fuzzy bits on track 0, sector 7. When the disk is copied, the copy will contain not a fuzzy bit but a normal bit, on or off according to the quantum vagaries of the read process that created it.

Figure 6

Figure 6

As illustrated in Figure 6, Dungeon Master‘s copy-protection routines read the ostensible fuzzy bit over and over, waiting for a discordant result. When that comes, it can assume that it’s running from an original disk and continue. If it tries many times, always getting the same result, it assumes it’s running from a copy and behaves accordingly.

FTL’s scheme was so original that they applied for and were granted a patent on it, one that’s been cited many times in subsequent filings. It represents a milestone in the emerging art and science of DRM. Ironically, the most influential aspect of Dungeon Master, a hugely influential game on its own terms, might just be its fuzzy-bit copy protection. Various forms of optical media continue to use the same approach to this day.

With duplication a complete non-starter in the case of both this sector numbered 247 and the fuzzy bit, the only way to pirate Dungeon Master must be to crack it. Doing so must entail diving into the game’s actual code, looking for the protection check and modifying it to always return a positive response. In itself, that wasn’t usually too horrible; crackers had long ago learned to root through code to disable look-up-a-word-in-the-manual and code-wheel-based “soft” protection schemes. But FTL, as usual, had a few tricks up their sleeves to make it much harder: they made the protection checks multitudinous and their results non-obvious.

Instead of checking the copy protection just once, Dungeon Master does it over and over, from half-a-dozen or so different places in its code, turning the cracker’s job into a game of whack-a-mole. Every time he thinks he’s got it at last, up pops another check. The most devious of all the checks is the one that’s hidden inside a file called “graphics.dat,” the game’s graphics store. Who would think to look for executable code there?

Compounding the problem of finding the checks is the fact that even on failure they don’t obviously do anything. The game simply continues, only to become unstable and start spitting out error messages minutes later. For this reason, it’s extremely hard to know when and whether the game is finally fully cracked. It was the perfect trap for the young crackers of the scene, who weren’t exactly known for their patience. The pirate boards were flooded with crack after crack of Dungeon Master, all of which turned out to be broken after one had actually played a while. In a perverse way, it amounted to a masterful feat of advertising. Many an habitual pirate got so frustrated with not being able properly to play this paradigm-shattering game that he made Dungeon Master the only original disk in his collection. Publishers had for years already been embedding their protection checks some distance into their games, both to make life harder for crackers and to turn the copies themselves into a sort of demo version that unwitting would-be pirates distributed for them for free. But Dungeon Master used the technique to unprecedented success in terms of pirated copies that turned into sold originals.

Dungeon Master still stands as one of copy protection’s — or, if you like, DRM’s — relatively few absolutely clear, unblemished success stories. It took crackers more than a year, an extraordinary amount of time by their usual standards, to wrap their heads around the idea of a fuzzy bit and to find all of the checks scattered willy-nilly through the code (and, in the case of “graphics.dat,” out of it). After that amount of time the sales window for any computer game, even one as extraordinary as Dungeon Master, must be closing anyway. Writing about the copy protection twenty years later, Doug Bell of FTL couldn’t resist a bit of crowing.

Dungeon Master exposed the fallacy in the claims of both the pirates and the crackers. The pirates who would never have paid for the game if they could steal it did pay for it. Despite a steadily growing bounty of fame and notoriety for cracking the game, the protection lasted more than a year. And the paying customer was rewarded with not just a minimally invasive copy-protection scheme, but, just as importantly, with the satisfaction of not feeling like a schmuck for paying for something that most people were stealing.

As the developer of both Dungeon Master and the software portion of its copy protection, I knew that eventually the copy protection would be broken, but that the longer it held out the less damage we would suffer when it was broken.

Dungeon Master had a greater than 50-percent market penetration on the Atari ST—that is, more than one copy of Dungeon Master was sold for each two Atari ST computers sold. That’s easily ten times the penetration of any other game of the time on any other platform.

So what’s the lesson? That piracy does take significant money out of the pocket of the developer and that secure anti-piracy schemes are viable.

Whether we do indeed choose to view Dungeon Master as proof of the potential effectiveness of well-crafted DRM as a whole or, as I tend to, as something of an historical aberration produced by a unique combination of personalities and circumstances, it does remain a legend among old sceners, respected as perhaps the worthiest of all the wily opponents they encountered over the years — not just technically brilliant but conceptually and even psychologically so. By its very nature, the long war between the publishers and the crackers could only be a series of delaying actions on the part of the former. For once, the delay created by Dungeon Master‘s copy protection was more than long enough.

And on that note we’ll have to conclude this modest little peek behind the curtain of 1980s copy protection. Like so many seemingly narrow and esoteric topics, it only expands and flowers the deeper you go into it. People continue to crack vintage games and other software to this day, and often document their findings in far more detail than I can here. Apple II fans may want to have a look at the work of one “a2_4am” on Mastodon, while those of you who want to know more about RapidLok may want to look into the C64 Preservation Project‘s detailed RapidLok Handbook, which is several times the length of this article. And if all that’s far, far more information than you want — and no, I really don’t blame you — I hope this article, cursory as it’s been, has instilled some respect for the minds on both sides of the grand software-piracy wars of the 1980s.

(Sources: Beneath Apple DOS by Don Worth and Pieter Lechner; The Anatomy of the 1541 Disk Drive by Lothar Englisch and Norbert Szczepanowski; Inside Commodore DOS by Richard Immers and Gerald G. Newfeld; The Kracker Jax Revealed Trilogy; Commodore Power Play of August/September 1985; Kilobaud of July 1982; New Zealand Bits and Bytes of May 1984; Games Machine of June 1988; Transactor 5.3; 80 Microcomputing of November 1980; Byte of December 1980; Hardcore Computist #9 and #11; Midnite Software Gazette of April 1986. Online sources include Nick Andrew’s home page, the aforementioned C64 Preservation Project, and The Dungeon Master Encyclopedia. See also Jean Louis-Guérin’s paper “Atari Floppy Disk Copy Protection.” Information on the SPA’s activities comes from the archive of SPA-related material donated to the Strong Museum of Play by Doug Carlston, first fruit of my research here in Rochester.

My huge thanks to Nate Lawson for doing something of a peer review of this article prior to publication!)

 
 

Tags: , , , , , , , , , , , ,

Rochester Ho!

No new article this week, I’m afraid. I’ve been planning for some time to take a bye week in January, but had thought it would be next week rather than this one. The next article will, however, be a bit of a technical one, and it seemed wise to give it a round or two of peer reviewing before I published. So, that one will be coming out next Friday instead of this one.

But I should tell you why I planned a bye week in the first place because it’s quite exciting (for me, anyway). I’ll be spending next week at the Strong Museum of Play in Rochester, New York. They’ve assembled an impressive archive of internal papers and other documents there from quite a number of prominent players in the games industry of the 1980s and 1990s: SSI, Sierra, Brøderbund, just to name a few that most interest me. If all goes as I expect, what I collect next week will inform my writings here for months or even years to come. A trip like this wouldn’t be practical without your support through Patreon and PayPal, so thanks so much for that!

Be seeing you!

 

A Pirate’s Life for Me, Part 2: The Scene

Fair warning: This article contains a couple of images that qualify as Not Safe For Work. Scroll further with caution!

Disks

The scene, the underground, whatever name you attach to it, there will never be anything like it again. There was a certain degree of innocence about it all, even though the activities were largely illegal. No one really understood that because most of us were still living at home trying to get through primary school! We had no larger world view to place the activities in context, no moral compass to tell us it was wrong. It was just fun, and that’s all we cared about!

— A scener named “Fantasy”

There is no historical instant to label as the beginning of the so-called “scene,” the loose international association of hackers, crackers, phreakers, and traders who dedicated themselves to making every computer game available for free within hours of its release, regardless of where in the world that initial release took place. The scene’s story rather begins with thousands of individual stories taking place in thousands of places, in the playgrounds and computer stores and bedrooms where young people first began to casually trade their latest software purchases among themselves. Someone who had a friend in the next town over, where the pool of games being passed around might be very different, could become a big fish in his own small pond by visiting said friend for a little inter-city trading. Gradually a larger distribution network was formed that offered immense rewards in status for the best-connected traders. It didn’t take long for some of these teenage kingpins to start editing their initials into the games, just so everyone at their school would be sure to know from whose largess they were benefiting. And so it began, driven, as it always would be, by the eternal adolescent need for acceptance and validation as much as it was by the very new technologies of home computers and the games they played.

If we insist on identifying a more concrete point of origin for the scene, we could do worse than the birth of Eagle Soft Incorporated, the oldest of the big cracking groups whose bewildering, ever-changing allegiances and wars would come to dominate life in the scene. In 1982, three Canadians named Dan, Jason, and Jim decided to band together under the Eagle Soft banner, chosen from a literal banner of an eagle that Dan happened to have hanging above his bed. With copy protection now becoming more common on games and other software, Jim, a citizen of Singapore studying in Canada, became one of the the world’s first recognized crackers through his work de-protecting early Commodore 64 games. Then another, even better cracker from the United States named Mitch joined the group. In a matter of months he took it over, as the original Canadian trio all lost interest and got on with their lives in one way or another. Unlike Mitch, who remained an almost unique exception by simply going by his first name, the new members he recruited all adopted online handles, the perfect complement to a social milieu that would come to represent for its participants an alternate, fantastic existence divorced from all the trials and tribulations of high school.

Eagle Soft

Eagle Soft dominated the Commodore 64 cracking scene in North America throughout the 64’s glory years there, thanks not only to their technical chops but also to a network of contacts inside magazines and stores that often resulted in an Eagle Soft crack of a game hitting the scene before an honest buyer could walk into a store and purchase it. The earliest Eagle Soft cracks went entirely unclaimed. Later the group started to edit in their initials (“ESI”) wherever they could find a place — for instance, as a replacement for the usual “loading…” message. Soon, however, the Eagle Soft eagle, one of the most iconic images of the cracking scene as a whole, made its first appearance. It became the centerpiece of the custom-programmed introductions that Eagle Soft took to including in the games they cracked. Such “cracktros” were soon a staple of the emerging scene, a place for the various groups to brag about their accomplishments, greet their friends and flame their enemies, and, teenage boys being teenage boys, quote their favorite rock lyrics (Eagle Soft always had a particular obsession with Rush).

Pirated games cracked by North American groups like Eagle Soft were first released almost exclusively via modem, through a fast-growing underground network of BBS systems. Telecommunications in those days was almost unbelievably primitive. Almost all of the boards were single-user systems, a single Commodore 64 or similar computer attached to a single phone line. Because only one person could be online uploading or downloading at any one time, the boards’ time was precious. A scener was expected to justify his use of a system’s time by uploading new “warez” as well as downloading; many boards had a credit system that might award two “download credits” for every block uploaded. Like everything else about the scene, the boards themselves were ranked according to a hierarchy running from “lame” to “eleet”; the better the board’s ranking, the more connected were its users and the more recent the games hosted there. Games trickled down through the hierarchy, from the “0-dayz” boards to the “3-dayz” to the “5-dayz” to all the others, to be eventually traded in gymnasiums and lunch rooms via the sneaker net by those kids so lame they didn’t even own modems. Primitive though it was, the system was surprisingly efficient. A hot new game could easily be available nationwide on the most eleet boards within 24 hours of its arrival on store shelves — if not before it was actually released, thanks to the scene’s contacts inside publishers and magazines. Within a week or two after that one could expect to find it on even the lamest boards.

In those days, there were few affordable legal ways to call between telephone area codes without incurring minute-by-minute long-distance charges, an expense very few parents of teenagers were willing to tolerate. Thus the grease that lubricated the distribution of pirated games was “phreaking,” the illegal practice of making long-distance calls for free. The PC industry had always had connections to this shady art; Steve Wozniak and Steve Jobs famously first bonded over a “blue box” used to generate the whistling tones that could be used to fool the analog phone systems of the early 1970s, and one of the first pieces of third-party hardware made available for the original Apple II was a similar device. In the 1980s, the scene made phreaking more popular than ever. By now the old analog switches that were vulnerable to blue boxes were on their way out, but the new phenomenon of long-distance calling cards was on the way in. These allowed customers to take their long-distance services with them when they traveled; they needed only dial a local access number, then input the code on their card followed by the long-distance number they were actually wanting to call. In the beginning, many of the calling-card codes consisted of only five digits, meaning that for a company with just 5000 calling-card customers fully one possibility in twenty would be a valid number. Sceners developed programs to brute-force the numbers; these could be set up overnight to try combination after combination until a valid one turned up. Once they were found, the phreaker could either reserve the codes for his own use or trade them on the boards for download credits or other considerations. Most would last a few weeks, until the victim got her first bill for hundreds or thousands of dollars.

Because they were so essential to the workings of the scene, long-distance codes (“codez”) and other means of phreaking were if anything even more sought-after than the games themselves, the fastest way for a new arrival to earn cred and rise through the class hierarchy. Unfortunately, phreaking was also by far the most common if not the only way for a scener to get himself into real legal trouble. The last legal questions surrounding the copyright eligibility of software had been settled by the time the scene came into its own, but enforcement still remained at best problematic. Very few district attorneys saw much profit in hauling teenagers into criminal court for trading computer games, and the game publishers themselves, players in a niche industry as they were, had neither the clout to influence the district attorneys nor the financial wherewithal to pursue civil cases. The case of the big phone companies, however, was another matter entirely. The few police investigations and prosecutions that resulted from the American scene’s activities virtually all revolved not around the software piracy that was the perpetrators’ real raison d’être, but rather around the offense of phone phreaking, or even more dangerous practices like credit-card fraud; desperate for more and better hardware to improve their boards and thus improve their standing, some sceners took to using stolen credit-card numbers to order equipment to convenient nearby vacant houses.

That said, even police involvement of this stripe was uncommon, and often exaggerated within the scene itself. Sceners, being almost universally at that rebel-without-a-cause phase of life, relished the idea of being daring outlaws out of all proportion to the reality of the risk. While the so-called “leet speek” that already characterized the scene by the mid-1980s — replacing “software” with “warez,” “hacker” with “haxxor,” “elite” with “eleet” — was allegedly developed to circumvent electronic law-enforcement filters that might be tracking their activities, one senses that such constructions were more important as typical adolescent markers of inclusion and exclusion.

In 1985 or so a new species of game began to trickle into the American Commodore 64 scene. These new arrivals went unmentioned in the magazines’ review sections and were never spotted on store shelves. And they had a different feel about them as well. Typical American commercial software at the time tended to be fairly high-concept stuff, with lots of earnest simulations, strategy games, and adventure games. The new games, though, unabashedly emphasized fast action and fast graphics over depth. Many already came equipped with cracktros of their own, but these also were different in character from the norm, with audiovisual production values that often smoked even those of the impressive action games to which they were attached. And, while the boasting, greeting, and warring being done by the groups behind these new cracktros wasn’t all that different from what American sceners were used to, it was all being carried on by groups no one had ever heard of before, and often in distinctly broken English that was apt to suddenly lapse into spasms of incomprehensible German or Dutch. The American scene had finally met the European.

A typical Commodore 64 cracktro. Something tells me most sceners greeted this game with particular interest...

A typical Commodore 64 cracktro. Something tells me most sceners greeted this game with particular interest…

The fast-action sensibilities of these new games were right in line with the American scene’s own, ironically much more so than the games commonly made in their own country. They quickly became great favorites, among the most sought-after warez of all. Certain groups became import/export specialists, establishing trading alliances with the groups across the pond. Particularly in the beginning, their trading was often done via the mail. Later, sceners began to practice the risky art of international phreaking. Europeans learned that they could make good use of the calling cards issued by American phone companies to their customers traveling abroad; there followed a booming codez-for-warez trade between the United States and Europe.

The European versions of machines like the Commodore 64 and Amiga were slightly different than the American, with their video signal and internal timings made to conform to the European PAL television standard rather than the American NTSC. This was enough to break certain games that really pushed the hardware, or to make them flicker or run slightly too quickly or too slowly. Some sceners therefore became specialists in PAL or NTSC “fixing,” the art of adapting games to run correctly under the alternate standard. This was far from trivial work — a marker of the fact that, much as the scene may look at times like little more than boys acting out, the best of those boys had real technical chops.

If it’s surprising that the two scenes should have developed so similarly in what was initially all but complete isolation from one another, well, one can only presume that nerdy yet rebellious teenagers really don’t vary all that fundamentally from country to country. More surprising is that the scene took root so strongly in Europe in the face of barriers that must have seemed almost unbelievably confounding to their American counterparts. One was the simple barrier of language. Very few European sceners had English as their native language; computer-mad Britain was, somewhat oddly, never all that huge in the scene, which was biggest in West Germany, the Netherlands, and Scandinavia. Yet they adopted English, the language they all learned to at least some extent in school and also that of most of the pop culture they consumed, as their lingua franca. The European scene’s diction is indescribable but immediately identifiable to anyone who’s spent any time around it, a mixture of stiff, grammatically suspect schoolboy constructions, leet speek, and phrases copied and pasted out of movies and music, with a heaping dose of profanity layered on top to make it all go down easy.

Another barrier facing European sceners was the cost of telecommunications. European telephone systems, unlike their American counterparts, generally still charged even local calls by the minute in the scene’s formative years, and prior to the influx of all those American codez there were few ways to safely phreak one’s way around this situation. Thus trading by post rather than BBS dominated in Europe for some years. Just as American sceners happily cheated the phone companies, European sceners did the same to the postal systems. Stamps were covered with a thin layer of glue or hairspray, which could be peeled away when packages arrived at their destination, taking with it the postal service’s mark showing the stamps had been used. Another possibility was to attend one of the “copyparties” that started sprouting up in Europe by about 1986. At most of them, you needed only turn up, equipped with a computer, dozens of blank disks, and dozens of games of your own for trading, to get in on the action.

An issue of Illegal, one of the scene's newsletters.

An issue of Illegal, one of the scene’s newsletters.

The specter of law enforcement, usually more a theoretical than an actual threat in North America, was a more serious concern in Europe. Plenty of mail swappers had uncomfortable run-ins with the local postal authorities that resulted in hefty fines and very unhappy parents, and in more extreme cases jail terms for international smuggling and/or mail fraud. One French scener by the name of Maximillian, a major trader in the codez used for international phreaking, was tracked down by Interpol and sentenced to several years in prison. The European police also generally took the crime of software piracy more seriously than their American counterparts. The West German and Norwegian police went so far as to institute special task forces to concentrate on the software-piracy problem, although games were seldom if ever their main focus. Still, for sceners in those countries and others the proverbial policeman’s knock on the front door, while not exactly commonplace, was hardly entirely unknown either. The police would arrive armed with search warrants and the full force of the law to ransack the scener’s bedroom while shocked parents looked on in horror.

As if the legitimate authorities weren’t scary enough, then as now the copyright wars attracted a fair number of shady dealers on the side of ostensible law and order. One German lawyer, Günter Freiherr von Gravenreuth, made the war against software piracy a dodgy sort of personal crusade, going so far as to send entrapping letters to suspected sceners in the persona of “Tanja,” a 16-year-old girl looking for new games; whatever else you can say about him, Gravenreuth certainly did know how to capture a teenage boy’s interest. If they replied, the targets could expect to be threatened with a lawsuit, along with a helpful settlement offer for many thousands of marks. (Gravenreuth was himself found in 2004 to be one of the masterminds of an international for-profit software piracy ring that dwarfed in scale and sophistication anything the scene could have imagined.)

Despite all these pressures, the scene not only survived in Europe but thrived, and for far longer than its American equivalent. Much of the reason for the European scene’s comparative longevity had to do with the rise and fall of the computing platforms that both American and European sceners favored. While virtually all viable platforms had their share of cracking groups, the core of the scene always identified most closely with Commodore’s machines, first the 64 and later the Amiga. When the former began to slowly fade and the latter to rise in the late 1980s, European sceners made a natural, gradual migration. Because the Amiga never quite took off in North America as it did in Europe, however, the American scene largely faded away with the 64. Between 1988 and 1990, most of the prominent American groups and crackers disbanded or retired, leaving the scene as a whole a largely European phenomenon, where it would continue to grow for another half-decade. Indeed, it still survives, in a shrunken and more subdued form with little continuing interest in software piracy, right to the present day. So dominant did its identity as a European phenomenon become that today the very fact that a scene ever existed at all in North America is all but forgotten by many.

But how did one get involved in the scene in the first place? In the hope that one individual’s story might take the place of a lot of dull generalities, let me tell you how it happened for “Weasel,” a German scener.

Our hero’s first computer, bought for him by his parents in 1985, was a Commodore 128 that he used in 64 mode all the time because the 128 didn’t have much in the way of games. He started out trading only with his schoolyard chums. But as his mania for collecting grew, his network of contacts grew to match: “People were coming to me now to get the latest games. I had them all!”

He found fascinating the cracktros that came attached to many of the games he was now trading, created by groups with names like the Dynamic Duo, 1001 Crew, Triad, German Cracking Service, and Federation Against Copyright. As the cracktros grew more elaborate almost by the month, he found himself spending more time admiring them and reading their “scrolltexts” than he did playing the games. “One day I want to be one of those guys as well,” he thought, “being part of a group and doing lots of cracks for all the people inside and outside of that so-called ‘scene.'” With that goal in mind, he started learning to program, first in BASIC, then in machine language, following a course in one of the magazines. He used his new knowledge to tinker with the cracktros and the games themselves, changing this and that to see what would happen. And, because every aspiring scener needed a handle, he started to call himself “Wiesel,” from a car advertisement he had stuck to his bedroom door: “Schneller als ein Wiesel!”

One day he took his skateboard to a popular local hill, at the top of which he noticed a rather incongruous stack of floppy disks amid the jumble of backpacks and bags left lying around by the boarders. When he saw the owner of the disks pick them up, he screwed up his courage to walk over and start a conversation. The owner was a fellow who called himself Havok, a music specialist with a cracking group called Frontline. Havok invited him to the next Frontline meeting, to take place in a Burger King in just a few days. Wiesel accepted in a daze, feeling “I must be dreaming.”

At the meeting, he was given an original of a game called Ikari Warriors, whose copy protection was known to be fairly strenuous. His assignment was to crack the game and bring it to the next weekly meeting, thereby to prove himself worthy — or unworthy — of membership.

So I went home and inserted the disk into my computer to have a look at the game. What I first saw looked like a never-be-able-to-crack-that game. So I almost gave up at the beginning, when I noticed the game loading with a track-sector fastloader. I had never seen anything like that before. But I never stopped thinking about a way to get into that damn program. I recalled everything I had already learned about machine language, and tried to find out as much as I could about the loading routine, the protection, the game itself, and how it worked. Finally I found a way to access the game, and after a while I had a working memory backup saved on my disk.

When Wiesel proudly returned to Frontline with crack in hand, they pronounced his work good enough and offered him official membership. There was only one condition: he needed to change his handle from the German “Wiesel” to the English “Weasel,” to “give it an international touch.” Thanks to his boldness, initiative, and technical chops, he was a real participant in the scene at last. He spent the remainder of his teenage years bouncing from group to group — Frontline, Matrix, Crazy, Crest, Enigma, Red Sector, Legend, Avantgarde, Fantastic Four Cracking Group — in the extended soap opera of shifting allegiances and relationships that was the life of a prominent scener. As with so much in life, the hardest part had proved to be just getting through the door.

Cracktros and demos often repurposed — read, stole — graphics and sound from games. The love scene from Defender of the Crown was a great favorite, for obvious reasons.

And once through the door, what was life like then as a real scener? Well, the scene was first and foremost a rough place, dominated as it was by teenage boys with angsty streaks a mile wide. Prominent sceners could be as young as age 13, and most tended to scale back their involvement or drop out entirely before entering their twenties, as jobs and university and girlfriends proved harder and harder to forgo for the all-consuming obligations of being a big wheel in the scene. Sceners mention in interviews already feeling “old” and out of step with the Lord of the Flies politics of the scene as young as age 17.

There were some exceptions to the demographic rule. Eagle Soft, for example, numbered two actual girls within their ranks (Ladyhawk and Scorpio), who served as their artists, drawing their famous eagle among other pictures. Perhaps the most amusing exception of all is that of Derbyshire Ram, an English country gentleman who retired in his fifties, took up the Commodore 64 as a hobby, and became a major trader and member of several big groups. While Derbyshire Ram was by all reports a gentle soul and an all-around good egg, others among the sprinkling of adults who chose to spend so much time hanging out with all these teenage boys may have had more disturbing motivations; one, known as Music Man, was reportedly jailed for child molestation.

But, exceptions aside, we can guess that at least 90 percent of active sceners during the 1980s were boys between the ages of 13 and 19. The reality that the members of this international criminal conspiracy almost all had parents hectoring them to do their homework and spend more time away from their computer could lead to some hilarious juxtapositions. Mitch of Eagle Soft, for instance, who was for years the most respected cracker in North America, worshiped by legions of disciples within the scene, tells of hiding in bed under the covers with his brother and a portable Commodore 64 playing Maniac Mansion into the night. Really, how many international criminal masterminds have a bed time?

It seems safe to say that many of these kids were the sort who don’t have the easiest time of it in high school. Sadly, instead of creating a gentler teenage society, most embraced the “shit rolls downhill” theory of social policy with relish, choosing victims below them in the scene’s pecking order to harass mercilessly. Most of their flames and diatribes will sound very familiar to anyone who’s ever been unwise enough to read YouTube comments. We’ve already encountered one or two of the scene’s cruder productions in passing in earlier articles, like the text adventure Mad Party Fucker, with its tagline “The object of this game is to fuck as many women as you can without getting bufu’ed by fags (contracting AIDS).” Tolerance wasn’t any higher than grammar on the scene’s list of virtues.

Things could get particularly vicious when one of the periodic “warz” broke out between rival groups. If the groups were of sufficient stature, the conflict could quickly become a global one, with every other group forced to align themselves with one side or the other. The largest, most sustained, and most brutal of all the wars was probably the one sparked off in 1987 between Eagle Soft and their only real rival for dominance of the North American scene, a group called Untouchable Cracking Force. Again, some of the techniques used by the combatants will ring sadly familiar to anyone aware of some of the Internet harassment that goes on today. Sceners set up war dialers to call their enemies’ homes, endlessly, with a screeching modem on the other end for anyone who picked up; taped their enemies’ conversations, then sent out edited snippets to place them in a bad light (anything that could somehow be construed to imply that they were gay was particular gold); ordered massive quantities of pizza to their houses; sent them mail-order packages full of useless computer equipment, ordered cash-on-delivery.

Scene from a "war" between Eagle Soft and a rival group. Make no mistake: the scene could be an ugly, ugly place.

A scene from a war between Eagle Soft and Untouchable Cracking Force. Believe it or not, this is actually one of the less offensive images of its type.

A journalist who infiltrated the scene and published a newspaper article about the goings-on — one of its few appearances in the overground media — allegedly suffered even worse indignities at their hands. According to By-Tor, a former member of Eagle Soft:

I remember it caused GREAT disruption in the scene and many major groups got together and we harassed him for 2 weeks straight, (I wish I would remember the groups names involved) his credit cards were given out, were charged up for computer equipment that went to a lot of people in the scene. His MCI cards were phreaked and loaded up with charges. He had to change his phone number 3 times during this time and cancel credit cards as there were people in groups that were great hackers and had inside info to finding out his new phone numbers and credit card numbers. Taught him a lesson he never forgot, that he was forced to write a 2nd story apologizing to all of us for lying to us and writing his story explaining the workings of the ELITE SCENE. We put him through HELL. :)

This doesn’t truly convey in written words what truly went on but that is the main story. It was GREAT!

The worst transgression, considered beyond the pale by even most warring sceners but occasionally practiced nevertheless, was to make an anonymous call to the police (the “pigs”) to out a fellow scener as a phreaker and/or pirate. There were also scattered reports of physical confrontations, particularly at the copyparties in Europe, involving fists, baseball bats, pepper spray, or in one alarming case an allegedly live hand grenade.

Lest we judge all of this too harshly, we should remember that, driven by hormones, frustrations, and most of all peer pressure, almost all of us did and said things as adolescents that we aren’t particularly proud of. Betwixt and between the orgasms of ugliness real friendships were formed. The old sceners have for the most part long since gone on to productive lives and careers, often using the skills they learned cracking games and writing cracktros in those formative years. With the exception of only a few like our friend By-Tor who still remembers the scene’s worst antics as so “great,” most remember the scene fondly when thinking back, but naturally prefer to focus on its more positive aspects if they haven’t managed to forget the worst ugliness entirely. The collision between nostalgia and reality can be a little off-putting when they are, say, confronted with an actual newsletter to which they contributed, as happened with the fellow who once went by the handle of “Punk Executioner.”

The thing that struck me when re-reading this 20 year old text was the level of aggression and gorilla chest thumping. Clearly I owe a lot of apologies. This was more apparent after I penetrated deep into my garage and dug out the old C64. Re-reading some of the scroll texts and Reason 4 Treason articles made me cringe. It appears I took aim at any dork, nerd, drop-out, non-music listener, anti-graffiti, pro-establishment, unfashionable person out there. I’m not sure why, perhaps it was because I occasionally copped a bit of flak myself for being a ‘computer head’ at school. Being a Dungeons & Dragons geek and using a brief-case as a school bag didn’t do me any favours either.

The scene’s saving grace, assuming we’re willing to grant it one, must be that its was an ethos not just of nihilism but also, almost paradoxically, of creation and even artistic excellence. Cracking games wasn’t easy, particularly as time went on and the publishers’ protection schemes grew more and more sophisticated. The best crackers brought a real flair to the job, not just finding a way to copy the disk but also adding cheat modes, conveniences, and new features. See for instance the crack by a group called Nostalgia of Access Software’s Leader Board golf simulation, which combined the core game with the course add-on pack and a simple menu to switch between them, simplifying a rather laborious process of rebooting and switching disks that annoyed many a legitimate purchaser.

And, increasingly over time, cracking was just one of the things that sceners did, and eventually not even the most important. In addition to horrid pornographic text adventures like Mad Party Fucker, sceners produced newsletters on paper and disks, in the case of the latter often with astonishingly good production values if not prose; home-grown utilities to produce graphics and, especially, music (the best of the scene’s so-called “sound trackers” on the Amiga were as good as any commercial music package); reams of art and countless hours of music, some of which wouldn’t sound particularly out of place on a modern dance floor, created with the aid of said utilities; and of course cracktros, which by the end of the 1980s had begun to morph into standalone demos, little showcases of multimedia art of sometimes stunning sophistication and ambition. In an odd but satisfying turnaround, software piracy became the afterthought of a vibrant and creative, if still very much underground, association of digital artists. Latter-day Amiga crackers even took to adding messages to their scrolltexts saying, hey, if you like this game you really ought to buy it — perhaps because by this point many current and former sceners were working in the games industry, snapped up for their audiovisual-programming chops by the very publishers who had once tried so hard to stamp them out. As copyparties turned into “demoparties” and the cracking scene turned into the “demoscene” in Europe in the early 1990s, it also became, relatively speaking, a gentler place, with an idealistic artistic ethos all its own. We’ll drop in on the scene again in a future article, to give you a chance to appreciate with me that unique community and some of its creations and to marvel with me how far it came in such a short time.

To be sure, the crackers and pirates who came before the demo coders were a less idealistic lot, motivated as they were by their teenage lusts for acceptance and for free games, but all their feverish cracking and trading all those years ago has had one supreme benefit. In cracking the games, they made it possible to archive and preserve them, something the companies that published them never spared a moment’s thought for. The sceners didn’t either, of course; they were hardly working for posterity when spreading their “0-day warez” around the world. Nevertheless, I’m hugely in their debt, as is everyone who cares about the history of gaming. The vast majority of the games you’ll find on the various disk-image archives today are the cracked versions, complete with their cracktros chronicling all the most recent wars and alliances, an ephemeral tempest in a teapot preserved forever. That, too, is another marker of our new digital way of living, toward which the scene, the first international digital subculture, pointed the way.

Next time we’ll wrap up this little series with a practical look at the mechanisms of copy protection itself: how it worked and how the scene’s crackers learned to defeat it.

(Sceners have done a very good job of archiving most of the artifacts of the 1980s and 1990s, although most of their own attempts at writing about their history quickly devolve into breathless but bewildering accounts of scene politics — “And then this group was formed, and went to war with this group, but this other group switched sides…,” etc. There’s a lot of that in Freax by Tamás Polgár, the only book I know of about the scene, but it’s nevertheless an essential resource for anyone hoping to really understand it. Otherwise this article is largely drawn from online scene sites. See CSDB, Scenery, Heikki Orsila’s archive of scener interviews, Hall of Fame, the Illegal newsletter archives, and Recollection. Also see the chapter “The Scene” in my own The Future Was Here.)

 
 

Tags: ,

A Pirate’s Life for Me, Part 1: Don’t Copy That Floppy!

Piracy

February 3, 1976

An Open Letter to Hobbyists

To me, the most critical thing in the hobby market right now is the lack of good software courses, books, and software itself. Without good software and an owner who understands programming, a hobby computer is wasted. Will quality software be written for the hobby market?

Almost a year ago, Paul Allen and myself, expecting the hobby market to expand, hired Monte Davidoff and developed Altair BASIC. Though the initial work took only two months, the three of us have spent most of the last year documenting, improving, and adding features to BASIC. Now we have 4 K, 8 K, Extended, ROM, and Disk BASIC. The value of the computer time we have used exceeds $40,000.

The feedback we have gotten from the hundreds of people who say they are using BASIC has all been positive. Two surprising things are apparent, however: 1) most of these “users” never bought BASIC (less than 10 percent of all Altair owners have bought BASIC), and 2) the amount of royalties we have received from sales to hobbyists makes the time spent on Altair BASIC worth less than $2 per hour.

Why is this? As the majority of hobbyists must be aware, most of you steal your software. Hardware must be paid for, but software is something to share. Who cares if the people who worked on it get paid?

Is this fair? One thing you don’t do by stealing software is get back at MITS for some problem you may have had. MITS doesn’t make money selling software. The royalty paid to us, the manual, the tape, and the overhead make it a break-even operation. One thing you do do is prevent good software from being written. Who can afford to do professional work for nothing? What hobbyist can put three man-years into programming, finding all the bugs, documenting his product, and distribute for free? The fact is, no one besides us has invested a lot of money in hobbyist software. We have written 6800 BASIC, and are writing 8080 APL and 6800 APL, but there is very little incentive to make this software available to hobbyists. Most directly, the thing you do is theft.

What about the guys who resell Altair BASIC, aren’t they making money on hobbyist software? Yes, but those who have been reported to us may lose in the end. They are the ones who give hobbyists a bad name, and should be kicked out of any club meeting they show up at.

I would appreciate letters from anyone who wants to pay up, or has a suggestion or comment. Just write me. Nothing would please me more than being able to hire ten programmers and deluge the hobby market with good software.

Bill Gates
General Partner, Micro-Soft

The “open letter” above, written by a 20-year-old Bill Gates, was printed in early 1976 in a number of the publications that served the nascent PC industry, centered at the time on the MITS Altair kit computer. Some of the soldering-iron-wielding visionaries who read it were enraged, a few supportive. Most, however, were merely confused. Sharing, of software the same as all other sorts of information, was simply what they did, the rock upon which their little hacker community was founded. For many the letter marked the first time they had ever confronted the notion of a program being owned by a single entity.

The PC industry was barely a year old, but already its age of innocence was passing. Bill Gates, the man who brought knowledge of the good and evil of copyright to this hacking Eden, was, plenty would soon be arguing, perfectly suited to play the role of the serpent. The change in thinking he set in motion with this open letter of his would soon prove more significant than even his own company’s outsized influence on the industry. From 1976 right up to the present day — and doubtless for many years to come — the PC industry and all of its many offshoots have been tying themselves into knots over the question of copyright, of where the ethical and legal rights of digital-content creators and users begin and end.

Both sides of the debate as it rages today could stand to glance back at copyright as it was once understood. Those who claim that modern copyright law merely applies an eternal principle to a new medium should note that, on the contrary, our notions of copyright have changed in some very fundamental ways in recent decades. And those who see laws like the Digital Millennium Copyright Act as well-nigh fascistic overreaching might do well to remember that even in the pre-DMCA days one could be prosecuted for merely photocopying the pages of a book. At the first conference on “software protection” in Britain in 1981, the first speaker opened with an old joke about an Englishman who asks an Irishman how to get to County Derry. “If I wanted to get to County Derry,” replies the Irishman, “I wouldn’t start from here.” The decades after Bill Gates fired the opening salvo of the digital-copyright wars would be marked by the law’s struggle to get to there from here — from the analog, materialist culture of creation that was to the digital, virtual culture that must now be.

When thinking about any big, overarching concept like that of copyright, it’s often helpful to return to first principles, to think about what the words or phrases themselves literally mean. In those literal meanings we can usually find the meaning of the concept as its originators understood it. Just as, say, “science fiction” once literally meant fiction about science, “copyright” once meant simply the right to copy. As enshrined in the American Copyright Act of 1909, the latest iteration at the time that Bill Gates wrote his open letter of the original Act of 1790, only the author had the right “to print, reprint, publish, copy, and vend the copyrighted work.” The original sin that must come before any printing, reprinting, publishing, or vending by someone who wasn’t the author must be the simple act of copying itself, which was in and of itself illegal. If you purchased a book at your local bookstore and copied its contents — whether on a photocopier, on a typewriter, or freehand on paper — you had already committed an actionable legal offense, even if your purpose in doing so was simply to have a “backup” copy for your own personal use. In the materialist world of arts and letters that held sway prior to the digital revolution, this approach to copyright as a literal right to copy made perfect sense.

Many of the conflicts and controversies that have plagued the idea of copyright in the years since have stemmed from the fact that a right to copy is a prerequisite to making any use at all of digital content. Thus rights-holders have needed to make the act of unauthorized distribution, not that of unauthorized copying, the original sin of the infringer. Much of the story of recent copyright legislation has been the story of how that shift was made.

On this blog, we’ve heretofore largely avoided that long, fraught societal debate and negotiation, but the specter of copyright and its violation in the form of software piracy loomed too large over the games industry of the 1980s to neglect it any more. This, then, is the story of what Gates’s letter wrought for the people who were making the games, the people who were playing them, and, in due time, an underground culture which dedicated itself to defying the legal system and keeping games — all games — available for free.

Pirates

The first programmer ever to attach a notice of copyright to her program, and thus quite likely the first programmer ever to conceive of her program as a potentially marketable creative work, was Betty Holberton, one of the original programmers of the ENIAC, by some definitions the world’s first true computer. In 1951, she was proud enough of a sorting program she had written to attach her name to a copyright notice included therein. It wasn’t until 1964, however, that a programmer made the next step of attempting to actually secure registration through the Copyright Office. That year a Columbia University law student and MIT electrical-engineering graduate named John F. Banzhaf III applied for the registration of two programs he’d written to aid his studies: one to help with the indexing of old court cases and one to compute automobile braking distances. His request was at first rejected, but he put his legal training in progress to good use to lobby for reconsideration. At last a Copyright Office functionary decided that “we could, under the law, make the registration.” The whole transaction was novel enough that the New York Times printed a rather bemused sidebar about it.

Despite Banzhaf’s success, few followed his lead in using copyright as a means of protecting their investment in software. IBM and the other companies who made the big-iron systems that kept the books for corporate America saw their programs not so much as independent entities as components of an entire ecosystem which included both hardware and software. They offered the whole enchilada to their customers as a leased package, complete with lengthy, heavily restrictive licensing agreements that can be seen as the forefathers to all the legalese we click through so impatiently today every time we install a new piece of software. If those contracts, many of which had never been tested in court, should fail, there were always patents, of which IBM in particular had quite a massive portfolio covering most of their systems’ operations.

Meanwhile the smaller systems with their scruffier, more independent-minded hacker culture were so immersed in the ethos of sharing ideas and code alike that copyright was a veritable foreign concept to them. Anyway, what would be the point of copyright really? Nothing like commercial software as we know it today existed prior to the mid-1970s. You either got your software along with your hardware from a big vendor like IBM, you wrote it yourself, or you pulled it off the hacker grapevine. You certainly didn’t walk into a store and buy it.

It was probably a good thing that the copyrighting of software felt a little pointless because, Banzhaf’s success with the Copyright Office aside, it wasn’t at all clear that the current copyright law could even be applied to much or all software due to two serious concerns.

The first was the stipulation, stated in the text of the 1909 Act, that copyright applied only to the “writings of an author.” The body of amendments and case law that followed had determined that “writings” encompassed not just traditional literary works but also such creative miscellany as musical compositions and recordings, statues, films, photographs, scientific models, and maps. Multifarious as they were, these forms all had one trait in common: they could all be easily “read” by a human being with the right knowledge or training. Program source code should also qualify under this standard.

But the proprietary software that was most likely to need the protection afforded by copyright wasn’t always distributed as source code. The sequences of ones and zeroes that made up binary code could be read only slowly and laboriously — anything but “easily” — by even the most talented hackers. One might be tempted to make a comparison to film, which like computer programs did require a technological intermediary to be “read” by people but which clearly was covered by copyright thanks to a 1912 amendment to the Act of 1909. Yet the comparison broke down in the question of just what it was that the author was really seeking to copyright. In the case of a film, that was the presentation layer, if you will, the actual imagery being projected onto the screen. In the case of something like Bill Gates’s BASIC, it was the code that generated what appeared on the screen. A comparison with recorded music broke down similarly. Yes, with computer displays so primitive as to make it difficult to distinguish one program from another, it was the code that mattered to companies like the young “Micro-Soft” — and, indeed, that would remain the main if not the exclusive nexus of their attention for many years to come.

The best hope for dodging the requirement of human readability lay in the fact that the copyright to an original work also reserved to its author the exclusive right “to translate the copyrighted work into other languages or dialects, or to make any other version thereof.” Without too much tortured thinking, one could imagine a compiler as “translating” source code into another version, a derivative work — albeit one not human-readable — also covered by the copyright to the original source. Unfortunately, case law seemed to point against such an interpretation. In 1908, the Supreme Court had decided in the case of White-Smith Music Publishing v. Apollo that a player-piano roll, which one might see as analogous to binary code, was not eligible for the same copyright protection as the sheet-music “source code” that had produced it.

And that was if anything the easier legal question. The other concerned the fundamental idea of copyright itself as it was still understood by the law in 1976 — that of it constituting a literal “right to copy.” The thing was, a program was copied every single time it was run — copied from disk or tape or, in the case of Altair BASIC, a spool of punched paper into the memory of the computer. This act would seem to be according to the established law clearly illegal, just as much so as buying a book and photocopying its pages. Thus every legitimate purchaser of Altair BASIC who chose to actually use it immediately became a pirate.

Now, this loophole was at some level fairly ridiculous, sounding more like a gotcha! for a raging pedant than a serious argument for those of good faith. Yet, ridiculous as it was, it was also extremely dangerous. How could a company like Microsoft claim the right to ask people to ignore this part of the law, but not these other parts? A slippery-slope scenario could be all too easily imagined. Even worse, as long as it existed, as long as a law hadn’t been written to explicitly close it, the loophole remained as a legal land mine for any company contemplating the ultimate remedy against piracy, that of hauling the pirates into court; a clever defendant could point to it and collapse the whole concept of copyright as applicable to software at a stroke.

Piracy

Even as Bill Gates was drafting his letter, Congress was in the process of overhauling American copyright law for the first time in well over half a century. Yet the end result directly answered few of the burgeoning software industry’s concerns. In addition to dramatically extending the term of copyright protection from a maximum of 56 years to “the lifetime of the author plus 50 years,” the Copyright Act of 1976, which actually went into effect on January 1, 1978, further broadened the applicability of copyright to “original works of authorship fixed in any tangible medium of expression, now known or later developed, from which they can be perceived, reproduced, or otherwise communicated, either directly or with the aid of a machine or device.” While the Act still failed to cite software among its many examples of same, it seemed more clear than ever that source code at least ought to fit this definition of a copyright-eligible work, while the door for binary code now also seemed, at worst, to have been opened considerably wider. But an unresolved question still remained in the form of the negative legal precedent of White Smith v. Apollo. And the copying that was a necessary part of actually running a computer program remained unaddressed as well.

The software industry therefore started working on solving the problem through technical rather than legal means. Here Bill Gates’s Microsoft was once again at the fore. When Microsoft shipped their version of Will Crowther and Don Woods’s perennial Adventure for the TRS-80 in 1979, they included on the disk one of the first instances of physical copy protection, on the theory that if buyers couldn’t copy the disk in the first place they wouldn’t be tempted to share the game with their friends. Ironically, Microsoft’s own ethical if not legal right to sell Crowther and Woods’s game was far from clear, a classic example of the moral murkiness that always seems to surround issues of piracy and intellectual property in the digital age as soon as you drill beneath the surface.

Only in 1980, with the PC industry beginning to enter the public consciousness as a much-needed American economic-success story and Apple, whose origins in a suburban garage were already becoming the stuff of legend, gearing up for the first big silicon IPO, did Congress at last directly address the question of copyright as it applied to software. The Computer Software Copyright Act of 1980 created an exception in the case of software to the idea of copyright as fundamentally constituting an author’s exclusive right to copy. Henceforward, said the Act, “it is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy” if such a copy is “an essential step in the utilization of the computer program” — thus securing the owner’s right to actually run the software she purchased — or is “for archival purposes only” — thus securing the owner’s right to make backup copies of her purchase. Making the act of distribution rather than the act of copying itself the original sin of software piracy represented a huge development in the evolution of copyright law that went as unremarked by the Act’s own drafters as it remains today. The law’s oft-tardy, clunky, and controversial negotiation with the brave new world of digital content begins here, in a modest little change that even most Congresspeople barely even noticed.

That same year, the question of whether the presentation layer of a program can be afforded copyright protection in its own right was settled in the affirmative in a landmark court case involving Midway, a producer of standup-arcade games, and Dirkschneider, a cloner of same. Atari in particular immediately started applying that precedent with gusto to squash the practice of cloning their standup-arcade and home-console games on computers.

All told, it had been a pretty good year for those on the side of strong software-copyright protection. But still hanging out there at its end, unresolved and dangerous and with case-law precedent still seemingly against it, was the question of copyright protection for binary code.

Piracy

For a long time the question continued to go unresolved, even as IBM entered the PC fray and the software industry went from being a curiosity to one of the biggest stories in the world of business, with names like WordStar and VisiCorp — and, yes, Microsoft — now on every stockbroker and venture capitalist’s lips. But then in 1982 along came a company called Franklin Computer which wished to produce a clone of the Apple II. By far the most difficult part of such a task must be the production of a ROM-based operating system that performed exactly like Apple’s own; the slightest deviation would mean that a subset of the Apple II’s huge software library must fail to work on Franklin’s model. Franklin responded to the challenge through the simple expedient of copying Apple’s ROM verbatim, whereupon Apple responded to Franklin’s solution by suing them in federal court. Franklin didn’t even try to deny that they’d copied Apple’s own ROM — but, they claimed, they were within their rights to have done so. At the root of their complicated defense was the old claim that copyright could not be applied to binary code. The industry held its collective breath; the moment they had half wished for and half dreaded for so long was here. At last the long-standing question was about to be settled in court.

Things didn’t go so well at first. The district court refused an injunction by Apple to force Franklin to take their machines off the market, and then ruled for Franklin in open court, accepting their argument that binary code could not by its nature be subject to copyright — exactly the result the industry had feared. But Apple appealed, and finally, on August 30, 1983, the Third Circuit Court of Appeals ruled that Franklin had indeed violated Apple’s copyright, at the same time definitively settling in the affirmative the question of whether binary code could be copyrighted. Citing the 1976 Act’s stipulation that copyright could also be applied to works readable only “with the aid of a machine or device,” the Court stated that “it is clear from the language of the 1976 Act and its legislative history that it was intended to obliterate distinctions engendered by White-Smith.” Franklin was forced to withdraw their machine from the market until they had written for it a unique ROM of its own. The question of the copyright eligibility of binary code would never be seriously challenged again.

Relatively little remembered today, Apple v. Franklin was, in terms of its impact on the industry at large, easily one of the most significant court cases with which Apple has ever been involved. It had taken more than seven years to get from Bill Gates’s open letter to this point, but the American software industry could at last feel entirely free to zealously guard their intellectual property and sue offenders, with both law and precedent on their side. The rest of the Western world gradually followed the American legal system’s lead. In 1985, for instance, the British Parliament passed the Copyright (Computer Software) Amendment Act, securing once and for all the same strong copyright protection for companies selling their software on British soil.

Piracy

Yet, even with the legalities finally settled, it made little sense to attempt to prosecute most software pirates. Civil or criminal court cases involving software piracy, both in the United States and outside it, remained a relative rarity, reserved for large-scale bootlegging rings and blatant corporate violators like Franklin. Game publishers in particular, a small fraction of the software industry as a whole, lacked the time, money, and energy to legally pursue on any serious scale the mostly teenage pirates who passed games among themselves in school lunch rooms and via the BBS networks. While the threat of legal action always made a good rhetorical tool — “It could happen to you!” — game publishers, following the lead of Microsoft Adventure, came to rely on technical rather than legal remedies to minimize the damage. Their methods encompassed various sorts of manual-look-up schemes — photocopying was still fairly expensive in the 1980s — as well as code wheels, hardware dongles, and bizarre Rube Goldberg contraptions like the British Lenslok. But the bedrock for most publishers remained the protection they applied to the disk or tape itself to make it physically impossible to copy. Virtually all publishers understood that their protection schemes, whatever form they took, were bound to be broken. One hope was that the protection would hold up for at least a little while under the onslaught of the hardcore crackers; another was that it would be enough in and of itself to deter the more casual pirates. The former hope was usually forlorn, while the latter stood on moderately firmer ground.

Meanwhile the larger debate about the rights of software buyers and sellers that had been touched off by Bill Gates’s letter was far from over. Indeed, it continued to rage more violently than ever at users group meetings, in computer stores, and in the magazines, pitting the software industry against a substantial percentage of their theoretical customer base. In 1983 a new Apple II magazine called Hardcore Computist chose to begin publishing information on copy-protection schemes and how to crack many of the most popular games. The response from the software industry was a shitstorm that forced the magazine off of computer-store racks and drove it underground. As a largely subscription-only publication, the editors chose to double down on their stance that a right of users to make backup copies of their expensive software ought to be as fundamental as the right of publishers not to have their programs given away for free. Hardcore Computist quickly became a go-to source for Apple II crackers, both those wanting simply to make the personal backups the law so plainly allowed and those with more nefarious agendas.

That magazine was, however, very much the exception. The others, knowing who buttered their bread, duly toed the industry hard line against any and all forms of copying, with very few exceptions. To do otherwise risked becoming a pariah like Hardcore Computist, cut off from the advertisements, early review copies, and insider scoops on which they depended. Few editors dared to push back in more than the most tepid ways against the industry’s stance. The articles they published on the subject usually weren’t all that different in tone or content from Bill Gates’s original entry in the genre, complete with questionable data (“Industry estimates claim that between four and ten illegally copied programs are circulating for every one sold.”); dire predictions for the future (“Software piracy, which was the casual crime of the 1980s, could actually threaten the survival of the software industry in the 1990s.”); conflations of piracy with shoplifting (“It seems that the same person who would never dream of walking out of a K-mart with a stolen watch hidden in his jacket doesn’t think twice about stealing software.”); fear-mongering (“Those who dip into the questionable waters of pirated software risk virus infection each time their disk drive whirs.”); and a little good old-fashioned name-calling (“Those computerists who copy software are the lowest form of animal life on the planet.”). A more candid debate was allowed to rage only in the letters sections, where the pirates, usually in response to a hand-wringing anti-piracy editorial or feature article, got a chance to state their side of the case.

The core of their argument, one which carried with it a certain practical if not always a legal or moral force, was that games were ridiculously overpriced, and that most of them were terrible to boot. Both assertions were largely correct. The price you pay today per man-hour of game-developer effort is almost invariably well over one if not two orders of magnitude less than it was in the 1980s even without adjusting for inflation. This reality applies almost equally to the good games of yore, the games I’ve praised here, as the bad. Even the typical Infocom game gave you about a novella’s worth of text, various “you can’t do that!” messages included, in return for $30 to $50 in 1980s money. The nostalgic stories of the old days that abound in places like the Get Lamp documentary claim that players routinely got 50 or 100 hours out of such thin gruel, but it’s honestly hard for me to imagine how. And, again, those are the good games. Many others were all but unplayable, insoluble, or missing vital clues due to the fact that most publishers’ testing methodology consisted of “let the developers play it for a few days if there’s time, otherwise just put it in a box and ship it.” Games routinely shipped with flaws serious enough almost to smack of outright fraud, flaws that not even the most mercenary publisher of today would dare allow to go unaddressed. And the magazines, in thrall as they were to the publishers for advertising dollars, were hardly a reliable means of sorting the wheat from all that chaff. The economics of gaming being so hopelessly out of whack, many pirates claimed that they copied games only to test them out and see if they were really worth the money, that they then bought those few that they did indeed judge worthy. Assuming they were telling the complete truth — admittedly a doubtful proposition — this seems to me quite a reasonable response to the situation.

Which is not to say that game publishers were deliberately shafting their customers. Staying in business carries plenty of fixed costs, and requires much larger profit margins when selling 50,000 copies of a successful game rather than 5 million or more. Everyone was doing the best they could, but everyone was feeling their way through, without any precedents to guide them. It was hard for a gamer, eager to play all the latest games highlighted in the magazines, to take too seriously the moral hectoring of the editors of same who were themselves drowning in free review copies.

Underlying the whole debate, conducted though it often was in such strident fashion on both sides, was an uneasy settlement. Publishers recognized that their software was going to be copied and traded, but, through physical copy protection and other means, hoped to keep it to a manageable level. Meanwhile users settled into whatever approach best seemed to balance ethics and practicalities: set up a collective with a few friends to buy a pool of games and trade them with each other; buy every third Infocom game and pirate the others from the BBS network; buy a game if and only if you wound up spending more than a few hours with the pirated version; etc.

But of course there were also the hardcore pirates, the people who wanted to have every game released, who tied their self-worth to the number of “hot warez” in their collection. For them the act of collecting games, not that of playing them, was the real draw. Many would say that the greatest game of all was the one played between the crackers, the elite members of the piracy “scene” who knew how to break copy protection, and the publishers, who were constantly dreaming up nastier and trickier schemes to protect their disks. The scene’s shadowy existence was barely hinted at by the bright, wholesome magazines chronicling the overground of computing. But, existing in a zone between the casual pirates who traded games with their friends and the big for-profit bootlegging rings, the scene was responsible for virtually all of the cracks that gradually trickled down to even many of the least-connected gamers, making it the root of all the evils of piracy in the view of the publishers. And yet, decentralized and anonymous as it was, it was impossible for them to stamp out. Described by historian Anders Carlsson as nothing less than “the first digital global subculture,” the scene was, among other things, a cesspool of adolescent nihilism, teenage posturing, and crude social Darwinism, teeming with racism, sexism, and homophobia. It was, in other words, much like many other gatherings of unsupervised teenage boys. Nevertheless, it’s thanks only to the efforts of the scene’s crackers that many of the games I write about still exist at all for an historian like me to study — one more ironic aspect of an intellectual-property debate that’s never quite as ethically clear as either side would have it. We’ll look more closely at this mysterious scene, at where it came from and what it meant to 1980s gaming, next time.

(Sources: ACM Computing Surveys of March 1975; New York Times of May 8 1964; Byte of September 1976, January 1977, May 1981, September 1981, October 1981, December 1981, January 1982, and May 1982; PC Magazine of October 1982 and November 1982; Computer World of December 5 1983; 80 Microcomputing of November 1982, February 1983 and April 1983; Ahoy! of August 1985, November 1985, and March 1986; Color Computer Magazine of August 1983, November 1983, January 1984, and July 1984; Commodore Magazine of April 1989; Commodore Power Play of August/September 1985; Games Machine of September 1988; Transactor 5.3 and 5.5; Computer Gaming World of September/October 1982; Acorn User of September 1984; Amazing Computing of September 1987; A.N.A.L.O.G. of January 1984; Computer and Video Games of April 1984, May 1984, and June 1984; Creative Computing of November 1984; Electronic Games of January 1985; Enter of April 1984; Hardcore Computist #2; New Zealand Bits and Bytes of September 1982; Popular Computing Weekly of June 7 1984; Sinclair User of September 1984 and November 1984; The Rainbow of March 1984; Your Spectrum of December 1983/January 1984; Zzap! of June 1987. Also the book From Pac-Man to Pop Music, including “Chip Music: Low-Tech Data Music Sharing” by Anders Carlsson. The pictures are all drawn from the magazines’ various anti-piracy articles, which always seem to bring out the fanciful best in their artists. Really, aren’t they great?)

 
37 Comments

Posted by on December 25, 2015 in Digital Antiquaria, Interactive Fiction

 

A Little Christmas Gift

This being the time of year for such things, I have a little surprise that I hope some of you might really enjoy.

I get asked on a fairly regular basis whether this blog will ever become a book — or, more likely, a series of books. While I do have aspirations in that direction, producing even one proper book is a big task that’s hard to turn to now when I’m so focused on this chronological journey we’re on. In the meantime, I can now at least offer you a series of ebooks that simply compile my older articles. Their existence is entirely down to the efforts of reader Richard Lindner, who developed all of the tools to automatically convert the blog’s articles.

Despite his talents, the ebooks are inevitably a little rough around the edges. In particular, multimedia elements — pictures, screenshots, movies, audio — may display imperfectly or not at all on many e-readers. Nevertheless, I hope some of you will find them handy for reading in bed or taking to the beach without bullies kicking sand in your laptop. Richard and I couldn’t quite decide whether to include readers comments or not — they’re a huge and hugely appreciated part of the online experience, but arguably ruin the flow of the ebook versions — so we decided to let you decide, by offering versions both with and without them. You can also choose between Kindle and epub versions, whichever suits your device or software. More ebooks will be appearing as I finish writing about each historical year. I just have a few articles to go to finish up 1987, so you can expect that volume to be joining the others quite soon.

Thanks for being such amazing readers! Your support means the world to me. If you are a regular reader who’s made this blog a part of your weekly routine and you haven’t yet pitched in, please do think about starting the new year with a Patreon pledge or a one-time PayPal donation — assuming, of course, that your personal circumstances permit. For the price of a good cup of coffee each month you can support this ongoing serious, nuanced examination of the history of gaming, and contribute to my own slow crawl toward earning a living wage from what’s long since become as time-consuming as any other full-time job.

To the 160 of you (as of this writing) who have signed up through Patreon and the many others who have donated through PayPal:an extra special thank you! It warms my writerly heart to know that so many of you like what I do enough to voluntarily pay for it. I’ll continue to strive to be worthy of your support.

I wish you all a great Christmas or winter holiday of your choice, and a happy New Year to boot. And I’ll see you all again in a couple of days, with a proper article this time.