AtariCom and Other Atari-to-Atari Link Cables

Year
1986
Type
DIY project
Category
Computer-to-computer link
Manufacturer
Homebrew (Nick Kennedy; Arianne Slaager / Alphasys)
Atari screen in blue showing the start of ATARICOM.DOC by Nick Kennedy, with its 'Note to SIO2PC users' explaining that the programs tie two Ataris together

Overview

In late 1986 Nick Kennedy, who later created SIO2PC, had two Atari 800s, only one of which had a disk drive. He wrote a set of assembly-language programs, and worked out the cables, to let the diskless machine load files from the other one. He also wrote a pair of "intercom" programs so two people could type to each other. Years later he released them all, with source code, as the public-domain AtariCom package, which he described as forerunners of SIO2PC.

The package demonstrates both of the Atari's built-in ways of talking to another computer without a modem: the SIO serial port and the joystick ports.

The programs

Program Link Role
TALKSIO (29 Oct 1986), TALKPIA SIO / joystick two-way "intercom", teletype style. The sending station presses CTRL-A to hand over the line
XMTSIO (21 Nov 1986), XMTPIA (22 Dec 1986) SIO / joystick runs on the computer with the disk drive and sends DOS binary-load files on request
RCVSIO, RCVPIA (15 Nov 1986) SIO / joystick runs on the diskless computer. When first run, it writes the real receive program to a cassette boot file, so the diskless machine can start it from tape

The source was written for Atari's AMAC assembler and is included alongside the OBJ files.

The SIO cable

The SIO version drives POKEY's serial port directly, one byte at a time, rather than using the OS's SIO routines, which only send fixed-size blocks to specific devices. Wiring two SIO plugs together:

  • Data: pin 3 (Data In) on computer A to pin 5 (Data Out) on computer B, and pin 5 on A to pin 3 on B.
  • Ground: pins 4 and/or 6 joined.

Four-conductor phone cord is enough. Kennedy started at 600 baud, moved to 19,200, and ran it over 75–100 feet of unshielded telephone wire. It worked, but it occasionally locked up because of a bug he never found. It also meant swapping the cassette cable for the link cable every time. The same crossed 3–5 pair is the basis of the simple two-machine game cables in network games cables.

The joystick-port cable

Kennedy's second design uses joystick port 1 (PIA port A, $D300). Its four direction lines are general-purpose I/O, set as inputs or outputs through PACTL ($D302). He invented his own unclocked, fully handshaked protocol on three lines:

  • pin 1 — data, one bit at a time
  • pin 2 — Data Ready, the transmitter's status (0 = ready)
  • pin 3 — Receiver Ready (0 = ready)
  • pin 8 — ground

Before each byte all outputs go high. The transmitter waits for Receiver Ready to be high, then pulls Data low. The receiver sees that, sets Receiver Ready low, and the transmitter sends the bit and pulls Data Ready low. This version "worked flawlessly". From memory, Kennedy gave the wiring as pin 1 to 1, 2 to 2, 3 to 3 and 8 to 8 between the two ports. Cables from dead joysticks are ideal. Check this against the source before relying on it.

AT-Link and EightLink (Alphasys)

Arianne Slaager (Alphasys) built two similar links:

  • AT-Link: two old joystick cables in a crosslink configuration, with pins 1 and 2 of one going to pins 3 and 4 of the other. She wrote drivers, as relocatable code and as a device handler, for both the Atari and the Commodore 64, and a two-player Battleships-style game with an Atari side and a C64 side.
  • EightLink: a high-speed link through the cartridge port, each end containing a PIA for an 8-bit bidirectional data bus plus a crosslinked 4-bit control bus. The 33-wire ribbon cable alternates grounds and signals to limit crosstalk. Slaager said two Ataris at opposite ends of a large hall could move disk data faster than a drive could read or write it. Frankenstein's hard-disk recording idea was built around the EightLink.

Tips

  • Disconnect other SIO devices when you use a crossed SIO cable. Two computers on one bus will confuse any drive that sees the traffic.
  • On the joystick-port link, only connect lines you know the software uses as handshakes. Two ports both set as outputs and driving opposite levels would fight each other.
  • For modern file transfer between computers, a PC running SIO2PC or RespeQt, a FujiNet or a null-modem cable on an 850 are easier.

Credits