XL/XE Compatibility: Why Old 800 Software Fails, and How the Translator Fixes It

When Atari replaced the 800 with the 1200XL (announced December 1982, shipped March 1983), and then with the 600XL/800XL, it also replaced the operating system. The old OS was 10K of ROM. The new one was 16K, adding a self-test, relocatable handlers, the international character set and Parallel Bus support. Atari had always published official entry points (the vectors around $E450) and told developers to use only those. Plenty didn't. Programs that jumped straight into OS routines, or used memory the new OS now claimed, broke. Atari's answer was the Translator disk. Later the problem ran the other way, as new software used XL-only features.

This guide explains the causes, shows how to find out exactly which OS and BASIC you have, and covers every practical fix, on real hardware and in emulators.

You need: an XL or XE computer (or an emulator), and for the Translator route a disk drive or SIO device.

1. Identify your machine's firmware

Type these at the BASIC READY prompt.

Which OS family?

? PEEK(64728)

$FCD8 (64728) reads 162 ($A2) on the 400/800 OS and 76 ($4C) on an XL OS.

Which XL OS revision?

? PEEK(65527)
Value Revision Shipped in
10 Rev. A (Oct 1982) 1200XL
11 Rev. B (Dec 1982) 1200XL service upgrade
1 Rev. 1 (Mar 1983) early 600XL/800XL
2 Rev. 2 (May 1983) most 600XL/800XL/65XE/130XE
3 Rev. 3 (Mar 1985) late 65XE/130XE, 800XE
4 Rev. 4 (May 1987) XE Game System
59 Rev. 3B (1987) 65XE Najm (Arabic)

Which 400/800 OS? Read 65528 and 65529. 243/230 is Rev. B NTSC, the common one. 221/87 is Rev. A NTSC, and 214/87 is Rev. A PAL.

Which Atari BASIC?

? PEEK(43234)

162 is revision A, 96 is revision B, and 234 is revision C. Revision B, built into most 600XLs and 800XLs, has serious bugs. The worst: every SAVE appends 16 useless bytes to the file, the growth is cumulative over repeated load/save cycles, and eventually you get errors such as 164. Atari offered revision C on cartridge from mid-1984, and built it into late 800XLs and all XE models. Antic published a type-in Revision C Converter (September 1985) that patches revision B into C in RAM at boot.

2. Why 400/800 programs fail on an XL/XE

Thomas Richter has ranked the usual causes, roughly from most to least common:

  1. Page 3 changed. The XL OS shortened the printer buffer and put new variables there. One of them, at $3FA, shadows GTIA's TRIG3 line, which the XL uses as "cartridge present". The OS compares the two every vertical blank and hangs if they differ. Games that use page 3 for buffers or player-missile data trip this. Ms. Pac-Man and Bacterion! hang for this reason. The Translator fixes it.
  2. Writes to $3F8 or $3EB. $3F8 decides whether BASIC is switched back in on a warm start, so a game that resets itself can find 8K of its RAM replaced by the BASIC ROM. $3EB is the cartridge checksum, and changing it can force a cold start. The Translator fixes these too.
  3. PIA misuse. Some programs set up four-joystick input, or initialise the PIA themselves, and change PORTB bit 0. On an XL that bit switches out the OS ROM, and the machine crashes. This is a hardware difference, so the Translator cannot fix it.
  4. Direct jumps into the OS ROM instead of through the documented vectors. These are rarer in games than you might expect. They are more common in applications, such as QS Forth and programs compiled with it. Translator-fixable.

Utilities that need the old OS include Atari's Word Processor, Synapse's File Manager 800+ and SynAssembler, Monkey Wrench, Text Wizard, Letter Perfect before v6, and the first orange-label MAC/65 1.00. Some programs run with only small glitches: Atari's own Missile Command and Space Invaders cartridges have sound problems. Antic's reviewers caught the same issue in magazine type-ins. "The Wedge", a BASIC DOS-command utility, called the old OS's get-character routine directly, and that routine moved on the XL.

More examples: Ultima I, Protector II, Return of Heracles and The Wizard and the Princess all need OS-B. Missile Command plays on an XL, but its wave-selection keys don't work, because it reads OS-B's keyboard table directly.

The 1200XL has extra problems. Its serial port supplies +5V differently, so devices powered from SIO (some modems, ICD's P:R: Connection) misbehave. It has only two joystick ports, so 800 games that use ports 3 and 4 lose players (Antic I/O Board, 1987).

3. Why XL/XE programs fail on a 400/800

Konrad Kokoszkiewicz lists the causes:

  1. They use the RAM under the OS ($C000–$CFFF, $D800–$FFFF): they need 64K.
  2. They use banked memory at $4000–$7FFF through PORTB ($D301): they need 128K or more.
  3. They call XL-only OS routines, for the HELP key, the PBI, and so on.
  4. They jump directly into XL OS routines that live elsewhere in the old OS.
  5. They use the international character set.

Examples: Parsec XL, Adebar and the 1st Top Demo 1989 jump straight into XL OS code, and DOS II+/D 6.4 calls the XL screen editor directly.

4. Using the Atari Translator

The Translator is a bootable disk that loads a copy of the 400/800 OS into the RAM under the XL OS ROM, then switches to it.

  1. Boot the Translator disk. On an XL/XE, hold OPTION so BASIC is off, unless the target program is a BASIC program.
  2. When prompted, remove it and insert the program disk (or cassette).
  3. Press SELECT. The computer cold-starts into the RAM-based 400/800 OS and boots your program.

Details that matter:

  • The disk is double-sided, with two versions. Side A survives a RESET press without dropping back to the ROM OS. Side B is more compatible, including programs that boot the 850 interface, but RESET throws you back to the XL OS.
  • Atari shipped an NTSC version (DX5063, containing OS Rev. B) and a PAL version (FK100807, containing OS Rev. A). It was distributed through APX and Atari Customer Service. Greg Riker wrote the original (March 1983), and Joe Miller with adding graphics and RESET handling (September 1983).
  • Being RAM-resident, it needs 64K, which every XL except an unexpanded 600XL has.

Alternatives: FIX XL (the "FIXXL" widely distributed by Antic, $10 from the Antic catalog as PD026), CSS's XL Fix, MasterSoft's OldOper, ANALOG's July 1985 type-in "Home-Made Translator", Computer Support's XOS (as software or ROM), Tim Patrick's Ultrafix/XL, and others. Antic's "Mapping the XL/XE" also recommended FIX XL for old programs that test the $C000–$CFFF area for foreign ROMs.

5. Permanent fixes

  • Patched versions. Over the years many 400/800-only titles have been fixed for the XL/XE and re-released. Check software databases such as Atarimania for "OS-B" or "XL fixed" versions.
  • OS switches and replacement ROMs. Commercial replacement OS ROMs and switches, and modern flash upgrades such as Ultimate1MB (whose BIOS menu selects among flashed OS images), let you keep a 400/800 OS on board.
  • SIO servers. RespeQt can activate a Translator automatically when the D1: image's filename contains "OS-B".

6. In an emulator

Don't bother with the Translator. Just emulate the right machine. In Altirra, choose 800 hardware, 48K, OS-B for early titles, and XL/XE with the XL OS for later ones. This is simpler than booting the Translator, although that works too. Atari800's equivalents are -atari with an OS-B ROM, or -xl/-xe.

Troubleshooting

  • Hangs on the title screen on an XL, fine on an 800: suspect the page 3 / $3FA problem. Try the Translator's side A, then side B.
  • Crashes instantly even with the Translator: probably the PORTB problem, cause 3 above. Use a real 400/800, an OS switch, or a fixed version.
  • Game runs but keys or sound misbehave: some 400/800 programs read OS-B's internal tables. Use OS-B.
  • BASIC programs grow and corrupt over time: you have revision B BASIC (PEEK(43234)=96). Get revision C.
  • Peripheral fails only on a 1200XL: it is probably powered from SIO. Give it its own supply.

Further reading

  • Mapping the Atari, revised edition, Appendix 13 ("XL/XE Enhancements And Bugs") and the XL/XE memory map.
  • Atari's XL Addendum to the OS User's Manual (C024515) documents the changes officially.
  • Our guides to the Altirra emulator and SIO2PC/RespeQt.

Credits