Why Paper Matters to a Digital Story
When people think about saving computing history, they think of the machines. Yet a preserved computer without its documentation is hard to understand. The hardware shows what existed. The manuals show what people were expected to do with it, how they were taught, and what the designers thought was important to explain.
For historians, this makes documentation a primary source, comparable to letters or diaries in other fields. It is contemporary evidence, produced at the time by the people who built and sold the equipment, and it is often richer than later memories.
Kinds of Documentation
Not all manuals serve the same purpose, and a researcher usually needs several types.
Reference manuals. These describe the details of a machine or language: instruction sets, memory layouts, commands, error messages and wiring. They are written for specialists and are crucial for anyone who wants to repair a machine, write an emulator or understand how a program worked.
User guides and tutorials. These are aimed at newcomers. They show how a company expected ordinary people to use a product and what it assumed they knew. A guide that explains basic ideas like files or saving work can reveal how unfamiliar these concepts once were. Many guides to the BASIC language, for example, were written for readers meeting programming for the first time.
Operator and maintenance manuals. On large machines, specialist staff ran and serviced the equipment. Their manuals describe daily routines, schedules, troubleshooting and the physical care of the installation, which is the working life that outsiders rarely saw.
Program listings and source documentation. Printed code, flowcharts and design notes show how problems were broken down and solved. Early magazines and books often printed whole programs for readers to type in.
Marketing and training material. Brochures, advertisements and course notes show how products were pitched and who they were aimed at. They need more caution, because they present the product favorably.
What Documentation Reveals
How things worked. Technical detail in a manual can settle questions that a surviving machine cannot answer, particularly when the machine is incomplete or broken. Schematics and specifications allow restorers to repair equipment correctly, and they guide the writers of emulators.
How things were used. Early computers were often run by teams using procedures that no longer exist. For instance, the handling of punched cards, with job decks, control cards and operators’ queues, is described in detail in operations manuals, and it is hard to reconstruct from the cards alone.
What people believed. The explanations, analogies and warnings in a guide reflect the assumptions of the time. Looking at how a manual explains a mouse, a disk or a program to a general reader can show what was familiar and what felt new.
Who was involved. Manuals sometimes list authors, editors, illustrators and reviewers, and these credits can help identify people whose work was otherwise unrecorded. This matters because the history of technical writing has often overlooked the writers themselves.
How products changed. Different editions of a manual, with their revision notes and corrected errors, can trace a system’s development. Comparing versions shows which features were added, which problems were fixed and which were quietly dropped.
Reading Documentation Critically
Like any source, a manual has limits.
- It may describe how a system was meant to behave rather than how it actually did. Bugs, undocumented features and later changes often go unmentioned.
- It may be incomplete, since companies sometimes kept details confidential or assumed readers had separate training.
- It may reflect a marketing slant, especially in introductory material.
- It may not tell you how widely a feature was used. A command listed in the reference might never have been popular.
- Undated or unnumbered editions can be confusing, so provenance matters. Knowing which version of a manual matches which version of a machine is part of careful research.
For these reasons, historians typically compare documentation with other sources, such as magazine reviews, user memories, surviving software and the machines themselves.
The Preservation Problem
Documentation is easy to overlook and easy to lose. Many manuals were printed cheaply, shipped in loose-leaf binders and discarded when a new edition arrived. Pages were marked up by users, and the markings can be valuable evidence, but they can also lead to the item being thrown away as damaged. Large reference sets were sometimes destroyed when a company closed.
Archives and volunteer groups have therefore made scanning a priority. Digitized manuals can be searched and shared widely, and the paper can be stored in stable conditions. The scanning process raises its own issues: file formats need to remain readable, scans should record both sides of each page and any handwritten notes, and copyright may restrict how documents can be shared. This is another application of the planning needed to avoid digital decay.
A Companion to the Machine
The best way to understand a historic computer is to combine the machine, its software and its paperwork. The hardware shows the design, the software shows the behavior, and the manuals show the intent and the human context. Taken together, they let a historian describe not only what a machine could do, but how real people tried to make sense of it.