Type-In Listings

In the 1980s, getting new software meant typing it yourself. Magazines published program listings—pages of BASIC code, sometimes with machine language DATA statements—that readers entered line by line. Hours of typing yielded a working game, and along the way, readers learnt to program.

Magazines built tools to make it survivable

A long machine-code listing is thousands of hexadecimal numbers with no redundancy: one wrong digit and the program crashes with no clue where. The answer was a purpose-built entry program. Compute!’s Gazette shipped MLX, described in its own words:

MLX is a new way to enter long machine language (ML) programs with a minimum of fuss… It checks your typing on a line-by-line basis. It won’t let you enter illegal [values].

Line-by-line verification rather than one checksum at the end — the difference between catching a typo immediately and catching it after two hours.

The trade knew exactly what a listing was worth

Listings were a publishing tier with a recognised ceiling, and the industry said so plainly. Sinclair User, advising readers who hoped to sell a game to a software house in 1985:

There is no point sending in a game only good enough for a magazine listing. The software house will not even look at it.

Which is not a slight on the form. It is what a tier looks like from inside a market — and the reason listings taught programming so well is precisely that they were short enough to type and small enough to hold in your head.

The experience

The process

1. Buy magazine with interesting listing
2. Boot computer to BASIC
3. Type code exactly as printed
4. Debug inevitable typos
5. Save to tape (hopefully working)
6. Play your creation

Time investment

Program type	Typical lines	Entry time
Short game	50-100	30-60 min
Full game	500-2000	3-8 hours
Machine code	Hundreds of DATA	2-4 hours

Educational value

Type-ins taught programming by:

• Forcing attention to syntax
• Demonstrating structure
• Encouraging modification
• Building debugging skills
• Creating ownership of code

Checksum systems

Publications developed error detection:

System	Magazine	Method
MLX	COMPUTE!	Two-byte checksums per line
Proofreader	COMPUTE!	Character-by-character validation
HiSoft BASIC	Your Sinclair	Line checksums

Key publications

Magazine	Platform	Country
COMPUTE!	Multiple	USA
COMPUTE!’s Gazette	C64/VIC-20	USA
Your Sinclair	Spectrum	UK
Crash	Spectrum	UK
INPUT	Multiple	UK
Usborne books	Multiple	UK

Types of listings

Pure BASIC

Short programs anyone could read end to end and modify.

BASIC + DATA

Machine code embedded as DATA statements:

10 FOR I=49152 TO 49200
20 READ A: POKE I,A
30 NEXT I
40 SYS 49152
50 DATA 169,0,162,0,157,0,4...

Hybrid

BASIC framework calling machine code routines for speed.

Machine code challenges

Entering hex data was particularly error-prone:

• One wrong number = crash
• No obvious debugging
• Checksum tools essential
• Often split across issues

The culture

Type-ins created community:

• Shared experiences at school
• Trading modifications
• Letters pages with improvements
• Reader-submitted programs

Usborne books

Particularly influential series:

• Computer Battlegames
• Computer Spacegames
• Write Your Own Adventure Programs
• Clear explanations alongside code
• Now freely available online

Decline

Type-ins faded as:

• Cover tapes/disks became standard
• Programs grew too complex
• Commercial software improved
• Internet distribution emerged

Legacy

Type-ins established:

• Programming as accessible hobby
• Learning through doing
• Magazine-reader relationship
• Foundation for bedroom coders

See also

• Bedroom Coder
• Usborne Computing Books
• COMPUTE! Magazine
• Cover Tapes