Network-Game Cables (GameLink II / Multi-Link)
- Year
- 1991
- Type
- DIY project
- Category
- Multi-computer link
- Manufacturer
- Homebrew designs (Chuck Steinman/DataQue GameLink II; Jiří Bernášek/BeWeSoft)
- Tags
- network, multiplayer, sio, pokey, gamelink, multi-dash, bewesoft, cable, diy, party
Overview
Atari 8-bit owners have been playing multi-computer games since the early 1990s. Each player has their own XL/XE and screen, and the machines exchange joystick data over a shared wire. The hardware is almost trivial because the Atari's POKEY chip already contains a serial transmitter and receiver, the same one used for the SIO bus.
Two designs by Chuck Steinman (DataQue) set the pattern. GameLink (1989/90) joined two computers through the controller jacks. GameLink II (1991/92) links 2 to 8 computers through their SIO ports. One machine acts as Master: it boots the game from disk, then emulates a disk drive so that the others ("Terminals") boot over the link. In Europe the setup became known as Multilink, after the network games by Jiří Bernášek (BeWeSoft): Multi-Dash, Multi-Race and Multi-Worms. The AGDA group's Maze of AGDAgon (1993) uses compatible hardware.
Three ways to wire it
1. Two computers, no parts (bench only)
Take one SIO cable, open one end and swap the wires on pins 3 and 5 (Data In and Data Out). Each machine's output then feeds the other's input. Bernášek's quick version needs no soldering at all: tape the plugs of two SIO cables together face to face and bridge them with three thin wires (both data lines crossed, plus ground). Because this drives POKEY's pins directly, cables must be short, the computers must share a table, and you should handle it with care.
2. The GameLink II hub
The schematic above shows a hub with eight SIO jacks. The Data Out line of every computer goes into two 74LS21 four-input AND gates. Their combined output goes back to every computer's Data In, so a byte sent by any machine reaches all of them. An idle serial line sits high, so ANDing the outputs works like a shared bus: whichever computer pulls low is heard by all.
3. Bernášek's party-network interface
For large meetings, BeWeSoft's Multi-Dash manual describes a small line interface at each computer, joined by a simple 2-wire cable that can run up to about 30 m in total (21 m tested):
- A PNP transistor puts about 4 V on the line when POKEY's data output is active, and leaves the line alone when it isn't.
- NPN transistors in every interface receive the line with over 1 V of noise margin.
- Two small diodes stop current flowing into a switched-off computer. A zener diode with a 10 Ω resistor guards against static and stray currents. A 100 nF capacitor smooths switching spikes on the Atari's supply.
Bernášek urges builders to keep the protection parts, because at a party the cable runs past PCs, power supplies and mains leads, and spare POKEYs are hard to get. Any design you invent must meet three rules: every Data In hears every Data Out, an idle or powered-off computer must not disturb the line, and the computers must be protected.
Using it
- Set up 1–8 XL/XEs (64 KB each) with monitors and their original power supplies. Remove other peripherals: SIO2PC links, modems, audio leads, even antenna cables.
- Boot
MULTIDSH.COM(or another network game) on the Master from disk, then disconnect the disk drive. - Connect the network and switch on the Terminals. They boot from the Master's emulated drive. A red status line shows each terminal number.
- Press START on the Master when everyone is logged in. With more than five machines, or a poor link, play may slow slightly.
How the software copes
Bernášek's "Inside of Network Games" articles, published with the commented source of Multi-Worms, set out the rules:
- POKEY sends and receives asynchronously, with channels 3+4 joined as a 16-bit divider at 1.79 MHz for timing. That leaves only channels 1 and 2 for sound; STIMER is off limits, and AUDCTL bits 3 and 5 must stay set.
- An IRQ arrives about every 940 cycles, so other interrupt code must be short. Simultaneous NMI and IRQ can delay or lose VBIs and DLIs, so start NMI routines with
STA WSYNC, pick DLI actions fromVCOUNT, and double up critical DLIs. - Every computer runs the whole game in lockstep, using only the joystick states received over the network, never local random numbers, keys or timers. All traffic goes through the Master with block type, address and checksum, and every block is acknowledged.
- An existing single-player game can't be patched into a network game. It has to be designed for this from the start.
Credits
- Picture: GameLink II hub schematic: the data outputs of eight SIO jacks are ANDed by 74LS21 gates and fed back to every computer's data input. — GameLink II hub schematic (Gl2_sch.gif), from the pigwa.net Atari FTP archive (Closer To Home Archive / Programming / Action! / Game_Link_II), local copy (used for identification/commentary)
- Jiri Bernasek (BeWeSoft) — MULTI DASH manual (hardware section), Nir Dary collection — Jiri Bernasek (BeWeSoft)
- Jiri Bernasek — The Inside of Network Games, article 1 — Jiri Bernasek
- Jiri Bernasek — The Inside of Network Games, article 2 — Jiri Bernasek
- Jiri Bernasek — The Inside of Network Games, article 3 — Jiri Bernasek
- comp.sys.atari.8bit FAQ, section 5.3.2 (GameLink, GameLink-II, Multilink) (Michael Current, Feb 2026) — Michael Current (comp.sys.atari.8bit FAQ), 2026
- GameLink II schematic Gl2_sch.gif (pigwa.net FTP archive, local copy) — GameLink II hub schematic (Gl2_sch.gif), from the pigwa.net Atari FTP archive (Closer To Home Archive / Programming / Action! / Game_Link_II), local copy (used for identification/commentary)
