Turbo Tape Systems: Turbo 2000, Blizzard, KSO and Other Cassette Speed-Ups
A standard Atari program recorder moves data at 600 bits per second. With the gaps between records, that comes to roughly 50 bytes per second, and a big game can take ten minutes to load. In the USA most owners moved on to disk drives. In Poland, Czechoslovakia, East Germany and parts of South America, drives were scarce or expensive, so the cassette stayed the main storage device for years. Out of that came dozens of turbo systems: small hardware modifications plus new loader software that pushed the same cheap recorders to between 2,000 and 9,600 bits per second.
This guide explains how those systems work, which one is which, and what to do with a box of turbo tapes today. For ordinary tapes (CLOAD, boot tapes, head alignment, CAS files) see Loading and Saving Atari Cassettes first. This guide picks up where its short turbo section stops.
What you'll learn: why a normal recorder can't go faster, the five ways turbo hardware signals the computer, the main systems and their formats, and how to load, image and convert turbo tapes with Altirra and modern SIO devices.
What you need: turbo tapes or tape images, and either a matching modified recorder or an emulator. To digitise tapes, a working recorder or a stereo deck and a PC line input.
1. Why a stock recorder is slow
Atari recorders are not plain tape decks. The data track is recorded as frequency-shift keying: two tones, about 5.3 kHz for a 1 and 4 kHz for a 0. Inside the 410 or 1010, the playback signal passes through two band-pass filters centred near those frequencies. The recorder compares their outputs and sends a clean digital level to the computer's SIO data in line, where POKEY receives it as ordinary serial data at 600 baud.
Those filters are the bottleneck. A tone has to last several cycles before a filter can recognise it, so the bit rate can't climb much. Every turbo modification attacks this the same way: it adds a second path that bypasses the FSK filters, amplifies the raw signal from the head, and hands it to the computer directly. The loader software then measures the length of each pulse itself. Most turbo formats are pulse-width coded: a short pulse means one bit value and a long pulse the other.
Because the CPU is now doing the timing, the loaders blank the screen while they read or write. The documentation for one later Czech loader says plainly that this is needed for exact timing, since there is no hardware support for the format. A black or striped screen during a turbo load is normal.
2. How turbo hardware talks to the computer
The tricky part is telling the recorder when to use the turbo path, and getting the pulses into the computer without disturbing other SIO devices. Altirra's cassette settings list the methods that real systems used, with an example of each:
| Method | How it works | Example systems |
|---|---|---|
| SIO command line | Turbo path enabled while the COMMAND line is held low and the motor is on; data arrives on SIO data in | Turbo 2000 |
| SIO data out | Turbo enabled when the computer holds its data-out line low | Blizzard Turbo |
| SIO proceed line | Turbo signal always present, read through the PROCEED line | Turbo 6000 |
| SIO interrupt line | Turbo signal always present, read through the INTERRUPT line | Rambit TurboCharger |
| Joystick port 2 | Data read on a port 2 input (PA7), motor switched by PA6 | K.S.O. Turbo 2000 |
| Joystick port 2 | Data read on PA4, motor through the normal SIO line | Turbo D |
The Czech Turbo 2000 modification is well documented. Turbo mode is selected when COMMAND is low and the motor line is on. That combination only occurs while reading the tape, so it doesn't upset other devices on the bus. The amplified tape signal then goes straight to DATA IN. Recording is almost unchanged, and the recorder still loads normal tapes. Joystick-port systems such as K.S.O. need an extra cable to port 2, but they leave the SIO lines alone. That is why K.S.O. could be built for any cassette recorder, not just Atari ones.
3. A field guide to the main systems
Most systems came in two parts: the hardware change, sold as a kit or ready-modified recorder, and a loader on tape or cartridge. Figures below are the speeds their makers quoted.
| System | Origin | Notes |
|---|---|---|
| Turbo 2000 | Jiří Richer (later JRC), Prague, 1987 | For 1010 or XC12. 2,270 bit/s originally; later software went faster on the same hardware. The most widespread Czech system |
| Turbo D | Klub Elektroniky Tlmače, Slovakia, 1987 | Joystick port 2, 6,000 baud; its software also reads Turbo 2000 |
| Atari Super Turbo (AST) | Sławomir Nienałtowski for Atari Studio "AS", Poland, late 1987 | The first Polish system; separate 1010 and XC12 versions; native formats AST, BUT and BOT |
| Blizzard Turbo | Atares, Poland, 1988 | Own data format; early units had a switch to turn turbo on and off |
| K.S.O. 2T06 Turbo | Wojciech Zabołotny, Poland; published in IKS 11/1988 | Joystick port 2, works with any recorder; a K.S.O. Turbo 2000 cartridge followed |
| Turbo 6000 / Schleife '88 | East Germany | For the XC12, 6,000 baud; cloned in Poland as Turbo Star |
| Turbo 2000F | MUEL / Rawa Soft, Poland, 1989 | 6,700 baud, SIO-only version of the K.S.O. design; reads Turbo 2000, AST and AHT tapes |
| Rambit TurboCharger | UK | Board plus conversion utility, 3,300–3,600 bit/s |
| Fast Injektor | Turbo Software, Chile, 1988 | 4,000 baud; Coelsa, Chile's Atari importer, sold XL12 recorders with it preinstalled |
There were many more: Hard Turbo with its "AHT" format, Atari Turbo ROM, Turbo UM, and the 9,600-baud Turbo EMO. Some, such as Iron Turbo, STAC and SITRE, were purely software and squeezed extra speed out of an unmodified recorder.
Formats don't mix. Each system wrote its own block layout, timing and header. A Turbo 2000 tape won't load on a Blizzard loader, and vice versa. Later cartridges tried to be universal: AST 2000 combined AST with Turbo 2000, and the Turbo UM cartridge read ATT, UM, AST, Turbo 2000, K.S.O. and AHT formats. Before you buy hardware or set up an emulator, identify the format. The loader screen, the label, or the country and year of the tape are your best clues.
From game loader to tape DOS
The first Turbo 2000 software was little more than a game loader. Its file format borrowed from the ZX Spectrum, and there was no proper CIO handler, so every "serious" program needed its own tape routines added. Things improved with TT-DOS (JR Computing, 1989–91), a DOS 2.5 clone with a high-speed tape device, B:. In 1996 Jiří Bernášek's B-TAPE brought the same file format to BW-DOS and SpartaDOS 3.2. B-TAPE offers 21 speeds and records the first block of each file twice. Optional "long gaps" let the recorder stop between blocks while BASIC catches up, and its boot tool can write a loader in the original Turbo 2000 format for people who only had the old cartridge.
4. Turbo tapes in Altirra
Altirra has the most complete turbo support. It added turbo decoding in 3.00, K.S.O. Turbo 2000 in 4.00, Turbo Blizzard and turbo data inside CAS files in 4.10, and Turbo D in 4.30.
- Open Configure System → Cassette.
- Set Turbo support to the method that matches the tape: SIO command (Turbo 2000), SIO data out (Turbo Blizzard), SIO proceed (Turbo 6000), SIO interrupt (Rambit Turbo Tape), Joystick port 2 (KSO Turbo 2000) or Joystick port 2 (Turbo D). Always on and Disabled are also available.
- Leave Turbo decoder on Peak + HPF (default) at first. If a raw recording gives errors, try the balance variants or the older Slope decoders. Invert turbo data helps with recordings whose polarity is flipped.
- Mount the tape (WAV, FLAC, Ogg or CAS) and boot the loader the way the original was booted. Many turbo loaders are themselves short standard-format programs: hold START at power-on, or load them from a cartridge.
Altirra decodes raw audio with both its FSK and turbo decoders at once, so a tape with a normal loader followed by turbo data works without any manual switching.
atari800 handles CAS images and raw files (-tape, -boottape). For non-standard tapes, Tomasz Krasuski's A8CAS library extended the CAS format to hold data that ordinary CAS can't describe, and came with tools and an emulator patch.
Real hardware without tapes: the A8PicoSIO project (a Raspberry Pi Pico SIO device, 2024) can play CAS images to turbo loaders over the SIO PROCEED and INTERRUPT lines or through joystick port 2. Its documentation lists support for K.S.O. Turbo 2000, Turbo D, Turbo 6000 and Rambit-style wiring, plus non-standard bit rates and multi-stage loaders.
5. Digitising and converting turbo tapes
Turbo data is much less forgiving than 600-baud FSK. Record with care:
- Line-level stereo into the PC, one tape per file. The data track is the right channel; the left is the audio track.
- No Dolby, bass boost or other enhancements. Standard FSK survives them; turbo pulses often don't.
- Peak level a little below maximum. Clipping breaks turbo decoding even when FSK would still load.
- Lossless only: WAV or FLAC. MP3 and Ogg can corrupt turbo data even at high bitrates.
- Keep the leader at the start of the tape. Silence it if you like, but don't cut it.
Then load the WAV in Altirra with the right turbo type and confirm the program actually runs. Altirra's tape editor shows the waveform alongside the decoded data, and can save the result as a CAS file. Its CAS support includes turbo (PWM) and raw FSK blocks, which makes a much smaller file to share than the audio. Keep the original WAV or FLAC as well, because it is the true preservation copy.
Troubleshooting
- Loader starts, then hangs on a black screen. Wrong turbo type. Check the origin of the tape and try the other methods for that country: Czech tapes usually mean Turbo 2000 or Turbo D, Polish tapes AST, Blizzard or K.S.O.
- Loads a few blocks, then fails. Try another turbo decoder, invert the data, or re-record at a lower level without enhancements.
- Odd behaviour with the C: SIO patch on. Altirra's tape acceleration only speeds up standard OS tape reads and doesn't work for turbo or custom loaders. Turn it off while you experiment.
- Real turbo recorder won't load normal tapes. A correct modification leaves standard mode working. Check the added components and the SIO plug wiring against the kit's instructions.
- Two SIO devices misbehave after a tape load. Some modified recorders hold a line active for a moment after stopping. B-TAPE inserts a one-second pause before the next disk operation for exactly this reason.
Further reading
- comp.sys.atari.8bit FAQ, section 3.1.3, "What speed upgrades are there for Atari program recorders?"
- Atariki (Polish Atari wiki), article Systemy turbo, which covers most of the systems above in detail.
- Jiří Bernášek, B-TAPE manual (BEWESOFT, 1996): history of Turbo 2000 and TT-DOS, and how the hardware modification works.
- Bajtek 4/89 (review of AST) and 8/89 (K.S.O. compared with AST); IKS 11/1988 for the original K.S.O. construction article.
- On this site: Loading and Saving Atari Cassettes, SIO Explained and Atari 8-bit File Formats Explained.
Credits
- comp.sys.atari.8bit FAQ (Michael Current) — 3.1.2/3.1.3 cassette interfaces and speed upgrades; 3.2.x A8PicoSIO; file formats (.CAS, A8CAS) — Michael Current (comp.sys.atari.8bit FAQ)
- Jiří Bernášek (BEWESOFT) — B-TAPE 1.0 manual (Turbo 2000 history, hardware modification, TT-DOS) — Jiří Bernášek (BEWESOFT), 2000
- Altirra 4.40 source — cassette turbo modes and Configure System > Cassette dialog labels — Avery Lee (Altirra)
- Altirra release notes (turbo tape support by version) — Screenshot from Avery Lee's Altirra page, virtualdub.org
- Altirra 4.40 Help — cassette, raw tape images
- Altirra Hardware Reference Manual, 9.17 410/1010 Program Recorder — Avery Lee (Altirra)
- Turbo 2000 to PC transfer tool notes (info_eng.txt) — 2000
