TURGEN SYSTEM DOCUMENTATION version 8.2.6-01

Michael Kalou

Contents

I TURGEN SYSTEM

1 Introduction 1.1 Primary Functionality. 1.2 Auxiliary Functionality. 1.3 Program Characteristics. 1.4 System Requirements. 1.5 Target Audience. 1.6 Plugins and Turbo systems. 1.7 Conventions and Terminology. 2 Distribution and Installation 3 Operations Guide 3.1 Starting TURGEN SYSTEM. 3.2 Program Controls. 3.3 Conversion of Files to Turbo Systems. 3.3.1 Playlist Items. 3.3.2 Working with Playlist. 3.3.3 Playlist Item Manipulation. 3.4 Wizard for Binary Files. 3.5 Producing Output. 3.5.1 Output of Electric Signal into WAVE File. 3.5.2 Output of Electric Signal to Computers Audio System. 3.5.3 Output of Tape Image. 4 Program Conguration Facility 4.1 Modifying Conguration. 4.2 General Conguration Entries. 4.3 Output of Electric Signal to Computers Audio System. 4.4 Output of Electric Signal into WAVE File. 4.5 Output of Tape Images. 5 Advanced Settings 5.1 Active Plugins. 5.2 Repository of Pulses. 6 Tools 6.1 Merging Segments of Binary Files. 6.1.1 Introduction. 6.1.2 Merging Segments Step by Step. 6.2 Turbo Decoder. 6.2.1 Principles and Capabilities. 6.2.2 Decoder Operations. 2
7 Appendices 7.1 Hints and Tips. 7.2 Data Recorders. 7.3 Data Recorder Replacements. 7.4 Postprocessing. 7.4.1 Postprocessing of WAVE Files. 7.4.2 Postprocessing of Tape Images. 7.4.3 Examples. 7.5 Data Transfer via Serial Port in Collaboration with CAS COM Utility. 7.5.1 Introduction. 7.5.2 Command Line Considerations. 7.5.3 Temporary Files.

II BUILT-IN PLUGINS

8 Turbo 2000 and Super Turbo 8.1 Characteristics. 8.2 Conversion types. 8.3 Header Block. 8.4 Inserting Silence After INIT Segments. 8.5 Conguration Entries. 9 Turbo 2000 - kilobyte blocks 9.1 Characteristics. 9.2 User Interface. 9.3 Binary Loaders. 9.4 Conguration Entries. 10 B-TAPE 10.1 Characteristics. 10.2 User Interface. 10.3 Binary Loaders. 10.4 Conguration Entries. 11 KSO Turbo 2000 11.1 Characteristics. 11.2 User Interface. 11.3 Conguration Entries. 12 Turbo Blizzard 12.1 Characteristics. 12.2 User Interface. 12.3 Conguration Entries.
13 Turbo ROM 13.1 Characteristics. 13.2 User Interface. 13.3 Conguration Entries. 14 Tape Image

III TURBO SYSTEMS

15 Introduction 16 Information encoding 17 Turbo Systems from Former Czechoslovakia 17.1 Common Information. 17.1.1 Switching Data Recorder to Turbo Mode. 17.1.2 Single Purpose or CIO. 17.1.3 Pilot Tone and Data Separation. 17.2 Turbo 2000. 17.2.1 Description. 17.2.2 Header block. 17.2.3 Data block. 17.2.4 Timing. 17.2.5 Loaders. 17.3 Super Turbo. 17.3.1 Description. 17.3.2 Header block. 17.3.3 Data block. 17.3.4 Timing. 17.3.5 Loaders. 17.4 Turbo 2000 - kilobyte blocks. 17.4.1 Description. 17.4.2 Header block. 17.4.3 Data blocks. 17.4.4 Timing. 17.4.5 Loaders. 17.5 Turbo Tape. 17.5.1 Description. 17.5.2 Tape modes. 17.5.3 Structure of the blocks. 17.5.4 Timing. 17.6 B-TAPE. 17.6.1 Description. 4
17.6.2 Tape modes. 17.6.3 Structure of the blocks. 17.6.4 Timing. 17.6.5 Notes. 18 Turbo systems from Poland 18.1 KSO Turbo 2000 and Turbo 2000F. 18.1.1 Description. 18.1.2 Header block. 18.1.3 Data block. 18.1.4 Timing. 18.2 Turbo Blizzard. 18.2.1 Description. 18.2.2 Header block. 18.2.3 Data block. 18.2.4 Timing. 18.3 Turbo ROM. 18.3.1 Description. 18.3.2 Header block for binary les. 18.3.3 Data block. 18.3.4 Timing.

Part I

TURGEN SYSTEM

1 Introduction

1.1 Primary Functionality
TURGEN SYSTEM is an acronym for Turbo generating system. It is a program whose main purpose is conversion of les (with focus on binary les) to various turbo systems used in former Czechoslovakia and Poland. Output of the program is an electric signal that can be stored in WAVE les or can be sent directly to computers audio system. Such electric signal can be then transferred to compact cassettes and read by data recorders equipped with particular turbo system. TURGEN SYSTEM focuses on conversion of binary les. For such purpose, set of special miniature turbo loaders was developed and integrated to the program. Also a Wizard for binary les is available to provide convenience during the conversion preparation.

1.2 Auxiliary Functionality
Apart from primary functionality which is conversion of les to various turbo systems, TURGEN SYSTEM offers auxiliary functions for convenience. Such auxiliary functionality includes: 1. Turbo decoder which can be used to retrieve information from tapes, 2. Output of tape images and interpretation of tape images, 3. Data transfer via serial port in collaboration with CAS COM utility, 4. Tool for merging segments of binary les.
1.3 Program Characteristics
TURGEN SYSTEM is written in Java 2 programming language and it is free software distributed under the terms of GNU General Public Licence, version 2.

1.4 System Requirements

Java Runtime Environment 1.4.2 or newer Solaris, Microsoft Windows 98/2000/ME/XP/Vista/7, GNU/Linux with kernel series 2.4 or 2.6

1.5 Target Audience

Target audience represents owners, users and fans of Atari 8-bit computers who use data recorders equipped with some turbo system (or some replacement devices) for data storage.
1.6 Plugins and Turbo systems
TURGEN SYSTEM provides relatively exible architecture to support various turbo systems, using plugins. Each turbo system supported is handled by one plugin. 6
1.7 Conventions and Terminology
Conventions If not explicitly noted, numbers are decimals. Abbreviation TS is used for TURGEN SYSTEM. Java Runtime Environment is abbreviated to JRE. Java Development Kit is abbreviated to JDK. Terminology Binary les1. Files designed to store programs for Atari 8-bit computers. Binary les were introduced with Atari DOS and have specic, well-dened structure. Their purpose is the same as purpose of load modules on IBM mainframes or ELF les under GNU/Linux operating systems. Binary les consist of segments, that are data blocks augmented with four byte header. The header species addresses where the contents of the particular segment will be placed when binary le is loaded. There are special purpose segments loaded to the addresses 736-739, they are denoted as jump segments. There are three types of them summarised in table 1. Other segments (ordinary, common) will be denoted as data segments. Note that other le formats were developed for program storage, for example those used by SpartaDOS or BW-DOS. These les are not supported by TURGEN SYSTEM. Address 736-737 Name of jump segment and its description RUN segment. When all segments are loaded, jump to the address specied by contents of the segment will be performed (JMP (736) in terms of assembler). Presence of RUN segment is not mandatory. If omitted, jump to the beginning of the rst data segment is performed. INIT segment. After this segment is loaded, jump to subroutine to the address specied by contents of the segment will be performed. In terms of assembler, virtual JSR (738) is simulated. RUNINIT segment. Combination of the previous jump segments. Table 1: Jump segments

5.2 Repository of Pulses

The repository of pulses is stored in pulses/pulses.list le. Repository can be modied, directions are present in the le itself as comments. It is not recommended to modify the repository without serious reasons. Changes take effect after TS is restarted, because the repository is read only once.

6 Tools

6.1 Merging Segments of Binary Files
6.1.1 Introduction TURGEN SYSTEM is equipped with a tool that merges segments of binary les into one segment and adds extra code that emulates the effect of occasional jump segments. This allows to convert segmented binary les that meet certain conditions to monolithic binary les. This tool was created in early times of TURGEN SYSTEM in order to partially cope with limitations of Czechoslovak Turbo 2000 and Super Turbo turbo systems. Conditions that the segmented binary les must meet are the following: 1. Data segments must not overlap, 2. Routines called by the jump segments must work even when all data segments are already loaded, 3. There must be place for code that emulates effect of occasional jump segments. Usually, the only way how to test this conditions is to run the resulting monolithic binary le in some emulator. It should be noted that capabilities of this tool must be considered limited. 6.1.2 Merging Segments Step by Step Display the dialog for merging segments of binary le by selecting item Merge segments of binary le from the Tools menu. Fill-in the Input le text eld and press the Analyze button. The list of segments will be lled-in and you will be able to check whether the rst condition is met. Then ll-in the Output le text eld and specify address of the extra code that will emulate the effect of jump segments. The extra code is not needed only when there are no INIT or RUNINIT segments in the binary le. Click the Merge ! button to merge the segments and create the output binary le. Test the created binary le using some emulator.
Figure 3: Merging segments of binary le

6.2 Turbo Decoder

6.2.1 Principles and Capabilities Turbo decoder is a tool designed to retrieve data from compact cassettes. The decoding algorithm is a Java rewrite of turbo loaders from assembler 6502. The electric signal can be read from WAVE les, these must be obtained by sampling of signal coming from cassette recorder connected to computers audio system. It is recommended to set the cassette recorder to produce maximum signal amplitude. The WAVE le must be in the following format: PCM, 1 channel, 44100 Hz, 8 bits per sample. Another possibility is to read the electric signal directly from the computers audio system. This source of electric signal is available, but not recommended, because turbo decoding is CPU intensive process and the signal is coming in real time, so data loss can occur. Turbo systems supported by the decoder are the following: Turbo 2000, Turbo 2000 - kilobyte blocks, Super Turbo and Turbo Tape or B-TAPE. The decoder can also work as so called Turbo monitor (reading of Turbo 2000 or Super Turbo blocks) capable of reading blocks up to the size of 64 KB. 6.2.2 Decoder Operations Open the decoder window by selecting the Turbo decoder item from the Tools menu. Select source of the electric signal using the Signal source combo box. If the source of the electric signal is a WAVE le, ll-in the WAVE le name and press the Attach decoder button. If the source of the electric signal is the computers audio system, make sure that it is properly congured (capture is enabled and desired input line is selected - use means of your operating system), appropriate channel (mono, left, right) is sellected and press the Attach decoder button. 16

%OD% = /mnt/win_d/emulator/atari/wav %ODS% = /mnt/win_d/emulator/atari/wav/ %OFNE% = river_raid.wav %OFN% = river_raid
Example of conversion to MP3:
lame %ODS%%OFNE% %ODS%%OFN%.mp3
Example of conversion to OGG Vorbis with deletion of the original le:
!oggenc -o %ODS%%OFN%.ogg %ODS%%OFNE%
Conversion to MP3 using LAME in the terminal emulator and consequent playback by xmms media player. The original le is deleted:
!konsole -e bash -c "lame %ODS%%OFNE% %ODS%%OFN%.mp3 && xmms %ODS%%OFN%.mp3"
7.5 Data Transfer via Serial Port in Collaboration with CAS COM Utility
7.5.1 Introduction CAS COM is a small utility for loading tape images to Atari via serial port. It supports standard and Turbo 2000 casette images. CAS COM works with SIO2PC, ATART or compatible hardware interfaces. CAS COM can be used as postprocessor of tape images created by TURGEN SYSTEM. Since CAS COM is currently available only for Microsfoft Windows operating systems, the following text presumes that such operating system is used. 19
CAS COM has a webpage: http://sdq.czweb.org/atari/index.html. 7.5.2 Command Line Considerations Let us presume that CAS COM resides in C:\UTILS\ATARI directory. The conguration entry Tape image generator/Postprocessing command should have the following value:
cmd /x C:\UTILS\CASCOM\CASCOM.EXE %ODS%%OFNE%
It is important to add command line interpreter to the command line, because CAS COM uses console I/O to display important information. Users of Microsoft Windows 95/98/98SE/ME should use command instead of cmd. CAS COM accepts other usefull command line parameters. /S starts tape image loading immediately, /e terminates program after data transfer. Morever /1, /2, /3, /4 or /c<num> parameters allow to choose serial port. 7.5.3 Temporary Files Setting Tape image generator/Auto create temporary les conguration entry can be useful when users intention is only to transfer data via serial port.

Part II

BUILT-IN PLUGINS
In this part, functionality of the plugins that are shipped with TURGEN SYSTEM is described.
8 Turbo 2000 and Super Turbo

8.1 Characteristics

Both plugins convert input les to classic Czechoslovak turbo systems Turbo 2000 and Super Turbo. Both plugins also provide means to circumvent main limitation of both systems - the incapability to hold segmented binary les. User interface is depicted on gure 4.
Figure 4: Turbo 2000, Super Turbo

8.2 Conversion types

In order to cover most of the needs, plugins Turbo 2000 and Super Turbo offer up to 6 conversion types. Choice can be made using the Conversion type combo box. Monolithic binary le to Turbo 2000 or Super Turbo. Conversion of monolithic binary le. The input le must be monolithic binary le. This is classic usage of Turbo 2000 or Super Turbo systems.

Turbo 2000/Pilot tone length for BlockLoading Number of pilot tone pulses of data blocks for BlockLoading conversion type (256-8192) Super Turbo/Header block pilot tone length Number of pilot tone pulses of the header block (256-8192) Super Turbo/Data block pilot tone length Number of pilot tone pulses of the data block (256-8192) Super Turbo/Pilot tone length for BlockLoading Number of pilot tone pulses of data blocks for BlockLoading conversion type (256-8192) Super Turbo/Prolongate pilot tone Increase number of pilot tone pulses with increasing approximate baud rate Super Turbo/Prolongate pilot tone for BlockLoading Increase number of pilot tone pulses with increasing approximate baud rate for BlockLoading conversion type
9 Turbo 2000 - kilobyte blocks

9.1 Characteristics

Plugin converts les to Turbo 2000 - kilobyte blocks Czechoslovak turbo system. There are no special restrictions on input les.

9.2 User Interface

The user interface is depicted on gure 5. The text eld File name corresponds to the same eld of the Turbo 2000 - kilobyte blocks header block. The meaning of the text eld Silence list is described in section 8.4.
Figure 5: Turbo 2000 - kilobyte blocks 23

9.3 Binary Loaders

Turbo 2000 - kilobyte blocks turbo system is suitable to hold binary les. There is a possibility to prepend one of the special miniature built-in binary loaders. For this turbo system, MINITBL, NANOTBL, NANOTBL[UR] and NANOTBL[U2] can be chosen using the Binary loader combo box. The prepent loader is converted to the Turbo 2000 system. MINITBL loader is a combination of strippedT: device handler that allows only READ operation and code for binary load using CIO. NANOTBL loaders are single-purpose binary loaders reading data blocks, not using CIO at all. NANOTBL stores data blocks to the freely available RAM. NANOTBL[UR] stores the data blocks to the beginning of the RAM under ROM, NANOTBL[U2] to the end of RAM under ROM. The Check loader button can be used to verify whether the binary le will destroy the selected binary loader.

9.4 Conguration Entries

Turbo 2000 - kilobyte blocks/Header block pilot tone length Number of pilot tone pulses of the header block (256-8192) Turbo 2000 - kilobyte blocks/Data block pilot tone length Number of pilot tone pulses of the data blocks (256-8192) Turbo 2000 - kilobyte blocks/Loader header block pilot tone length Number of pilot tone pulses of the header block of the binary loader (256-8192) Turbo 2000 - kilobyte blocks/Loader data block pilot tone length Number of pilot tone pulses of the data block of the binary loader (256-8192) Turbo 2000 - kilobyte blocks/Silence after header Number of seconds of the silence inserted after the header block (0-30) Turbo 2000 - kilobyte blocks/Silence after loader Number of seconds of the silence inserted after the binary loader (0-30) Turbo 2000 - kilobyte blocks/Name loader same as le The binary loader will have name same as the converted le

Figure 8: Turbo Blizzard

12.2 User Interface
The user interface is depicted on gure 8. The text eld File name corresponds to the same eld of the header block. The meaning of the text eld Silence list is described in section 8.4.

12.3 Conguration Entries

Turbo Blizzard/Invert polarity of pulses Invert polarity of pulses Turbo Blizzard/Long gaps between blocks Make long gaps between blocks

13 Turbo ROM

13.1 Characteristics
Plugin converts les to Turbo ROM Polish turbo system. Only conversion of Turbo ROM compatible binary les is supported (those binary les consist of exactly one DATA segment at most one RUN segment and at most one INIT segment).

Figure 9: Turbo ROM

13.2 User Interface
The user interface is depicted on gure 9. The text eld File name corresponds to the same eld of the header block. The Auto set header button can be used to automatically set le name and also to verify whether the input le is Turbo ROM compatible binary le.

13.3 Conguration Entries

Turbo ROM/Invert polarity of pulses Invert polarity of pulses

14 Tape Image

Plugin interprets tape images. Only trXX tape image chunks are supported.

Part III

TURBO SYSTEMS

15 Introduction

This part contains information about various turbo systems that have been created in Czechoslovakia and Poland. Descriptions of the systems are sufcient to provide ability to write turbo generators, loaders, copiers and turbo decoders.

16 Information encoding

Information is encoded using pulse width modulation (PWM). In this document, width of pulse is dened as a distance between two transitions from logical zero to logical one. See gure 10.
Figure 10: Pulse and its width
17 Turbo Systems from Former Czechoslovakia

17.1 Common Information

This common information is related only to turbo systems described in this document. These turbo systems are or were widespread in former Czechoslovakia, but of course, there are or were also others. 17.1.1 Switching Data Recorder to Turbo Mode Switching data recorder to turbo mode is done using electronic switch, that switches to turbo mode if signals COMMAND and MOTOR CTRL are active. Reading of data is done by monitoring signal at pin DATA-IN of the SIO connector. Writing of data is performed by direct change of logical value at DATA-OUT pin of the SIO connector. 17.1.2 Single Purpose or CIO Two main kinds of Czechoslovak turbo systems can be distinguished: 1. Systems that use single purpose loaders and simple le format that can hold only one contiguous block of data (Turbo 2000, Super Turbo). These systems are unable to support binary load operation, although capable to hold binary load les themselves. 2. Systems that were created together with tape operating systems: Turbo 2000 - kilobyte blocks, Turbo Tape, B-TAPE. Aim of these systems is to partially or fully replace the disk drive. 29

17.1.3 Pilot Tone and Data Separation All Czechoslovak turbo systems use same way how to separate pilot tone and data. One sync pulse (which is very narrow pulse) or narrow pulse.

17.2 Turbo 2000

17.2.1 Description Turbo 2000 was the rst turbo system available in former Czechoslovakia. It was developed in 1987 by Ji Richter, student of Czech Technical University in Prague and member of Prague Atari user r club. Four types of pulses are distinguished: Narrow pulse, wide pulse, pilot tone pulse and sync pulse. Bits are stored in MSB to LSB order. File stored using Turbo 2000 system consists of two blocks - header block (HEADER) and data block (DATA). Both blocks are preceded by pilot tone (series of at least 256 pilot tone pulses) which is followed by sync pulse (which is very narrow pulse). Recommended number of pilot tone pulses is at least 2000 in order to provide compatibility with Universal turbo loaders. 17.2.2 Header block Offset 2-11 12-13 14-15 16-Description Always 0 File type (1 - plain data, 3 - program, 4 - binary le, 255, 254 - tokenised BASIC) File name Load address Length of le Start address Check sum = (HEADER[0]) xor. xor (HEADER[17])
17.2.3 Data block Offset 0 1-? Last Description Always 255 Data itself Check sum = (DATA[0]) xor. xor (DATA[?])
17.2.4 Timing Standard transfer speed is approximately 2270 bauds. There is a big tolerance for width of all pulses. Pulse Pilot tone Wide Narrow Sync Center width 32/44100 s 26/44100 s 13/44100 s 10/44100 s Tolerated range (25-47)/44100 s (20-40)/44100 s (6-19)/44100 s (4-17)/44100 s
17.2.5 Loaders In early times, Turbo 2000 loaders were distributed on tapes, stored using standard 600 baud system. Then loaders on cartridges became widespread.

17.3 Super Turbo

17.3.1 Description Super turbo system is an enhancement of Turbo 2000 system, developed by Ji Richter. Supported r transfer speeds are approximately from 2725 to 6411 bauds. Two types of pulses are distinguished: Narrow pulse and wide pulse. Bits are stored in MSB to LSB order. File stored using Super Turbo consists of two blocks - header block (HEADER) and data block (DATA). Both blocks are preceded with pilot tone (series of at least 1200 wide pulses) which is followed by narrow pulse. Recommended number of pilot tone pulses is at least 2000 in order to provide compatibility with available loaders. 17.3.2 Header block Offset 2-21 22-23 24-25 26-Description Always 183 File type (1 - plain data, 3 - program, 4 - binary le, 255 - tokenised basic) File name Load address Length of le Start address Check sum = (HEADER[0]) xor. xor (HEADER[27])

17.3.3 Data block Offset 0 1-? Last Description Always 237 Data itself Check sum = (DATA[0]) xor. xor (DATA[?])
17.3.4 Timing Various transfer speeds are supported. For given speed, width of wide pulse is width of narrow pulse simply doubled. Pulse Wide Narrow Width (6/44100 - 22/44100) s (3/44100 - 11/44100) s
17.3.5 Loaders Special loaders for Super Turbo only are very rare. So called Universal turbo loaders capable to load both Turbo 2000 and Super Turbo are widespread, mostly on cartridges. Universal turbo loaders measure speed using examination of three consequent pilot tone pulses. Measured speed is also used to distinguish between Turbo 2000 and Super Turbo. During the time, so called Visiloader has been invented. This loader is capable to display progress of loading using PMG.
17.4 Turbo 2000 - kilobyte blocks
17.4.1 Description Turbo system designed together with various versions of Turbo operating system (TOS). Four types of pulses are distinguished: Narrow pulse, wide pulse, pilot tone pulse and sync pulse. Bits are stored in MSB to LSB order. File stored using this turbo system consists of many blocks. First block is a header block (HEADER), remaining blocks (BLOCK) are data blocks that have 1026 bytes. Every block is preceded by pilot tone (series of at least 256 pilot tone pulses) which is followed by one sync pulse. Recommended number of pilot tone pulses is at least 2000 in order to provide compatibility with available loaders. 17.4.2 Header block Offset 0-1 2-Description Always 0 File name Check sum = HEADER[0] xor HEADER[1] xor. xor HEADER[17]
17.4.3 Data blocks Offset 0 Description 255=Full block, 250=EOF block. Numbers 251-254 indicate partially lled block. If we subtract 251 from this number, we obtain a difference that will be denoted as Z. This difference can be 0,1,2 or 3 and represents higher byte of number of valid data bytes in the block. Data itself. If the block is a full block, there is 1024 bytes of data. If the block is EOF block, there are all zeroes. If the block is a partially lled block, there is data padded with zeroes up to the length of 1023 bytes. Last byte is lower byte of number of valid data bytes in the block. If we denote this lower byte as X , the number of valid bytes in the block is Z 256 + X Check sum = BLOCK[0] xor BLOCK[1] xor. xor BLOCK[1024]

1-1024

17.4.4 Timing Standard transfer speed is approximately 2270 bauds. There is a big tolerance for width of pulses. Pulse Pilot tone Wide Narrow Sync Center width 32/44100 s 26/44100 s 13/44100 s 10/44100 s Tolerated range (25-47)/44100 s (20-40)/44100 s (6-19)/44100 s (4-17)/44100 s
17.4.5 Loaders This turbo system is integrated into to various version of Turbo operating system (TOS) and also to one special version of TURBO BASIC XL widely used in former Czechoslovakia. Usual CIO device installed is T: or D:. CIO functions supported are OPEN, READ, WRITE and CLOSE.

17.5 Turbo Tape

17.5.1 Description Advanced turbo system introduced with TT-DOS operating system sold by JRC company. Aim of this turbo system is to fully replace disk drive. Usual CIO device installed is B: or D:. Four types of pulses are distinguished: Narrow pulse, wide pulse, pilot tone pulse and sync pulse. Bits are stored in MSB to LSB order. File stored using Turbo Tape consists of blocks (BLOCK) that are 1026 bytes long. Every block is preceded by pilot tone (series of at least 256 pilot tone or wide pulses) which is followed by one sync or narrow pulse. Recommended number of pilot tone or wide pulses is at least 2000 in order to provide compatibility with available loaders. 17.5.2 Tape modes Mode SS SD LS LD Description Short gaps between blocks. First block is written twice, others once. Short gaps between blocks. All blocks are written twice. Long gaps between blocks. First block is written twice, others once. Long gaps between blocks. All blocks are written twice.
D modes provide data redundancy for safe data storage. First block is always written twice in order to provide convenient support for READ DIRECTORY CIO function. 17.5.3 Structure of the blocks Offset 2,3 Description Sequential number of the block. Numbering starts from 1. In case of D modes, pairs of blocks have same sequential number. Tape mode: SS=128, LS=0, SD=192, LD=64 Bits 0-11: Offset of last valid byte in the block (16-1024), this offset will be denoted as B. Bit 15: Last block ag. Byte at offset 2: B %256 Byte at offset 3: [B /256] + [128 (EOF i s t r ue)] Undened number. All blocks of one le should have same number here. Undened. File name and extension padded with spaces. First 8 bytes are devoted to le name, last 3 bytes are devoted to extension. Data itself (1008 bytes). Data must be padded with any bytes. Check sum = BLOCK[0] xor BLOCK[1] xor. xor BLOCK[1025]

6-16 17-1024 1025

17.5.4 Timing Timing is compatible with Turbo 2000 and Super Turbo.

17.6 B-TAPE

17.6.1 Description Advanced turbo system introduced with B-TAPE extension for operating system BW-DOS. Aim of this extension is to fully replace disk drive. B-TAPE allows to use both CIO and SIO to exploit data recorder turbo modication. The disadvantage is a big size of the device handler. B-TAPE was designed as improvement of Turbo Tape system. Four types of pulses are distinguished: Narrow pulse, wide pulse, pilot tone pulse and sync pulse. Bits are stored in MSB to LSB order. File stored using B-TAPE consists of blocks (BLOCK) that are 1026 bytes long. Every block is preceded by pilot tone (series of at least 256 pilot tone or wide pulses) which is followed by one sync or narrow pulse. Recommended number of pilot tone or wide pulses is at least 2000 in order to provide compatibility with available loaders. 17.6.2 Tape modes Mode SS SD LS LD Description Short gaps between blocks. First block is written twice, others once. Short gaps between blocks. All blocks are written twice. Long gaps between blocks. First block is written twice, others once. Long gaps between blocks. All blocks are written twice.
D modes provide data redundancy for safe data storage. First block is always written twice in order to provide convenient support for READ DIRECTORY CIO function. 17.6.3 Structure of the blocks Offset 2,3 Description Sequential number of the block. Numbering starts from 1. In case of D modes, pairs of blocks have same sequential number. Tape mode: SS=128, LS=0, SD=192, LD=64 Bits 0-11: Offset of last valid byte in the block (16-1024), this offset will be denoted as B. Bit 15: Last block ag. Byte at offset 2: B %256 Byte at offset 3: [B /256] + [128 (EOF i s t r ue)] Undened number. All blocks of one le should have same number here. Random number. All blocks of one le must have same number here. This random number allows to distinguish les with same le name. File name and extension padded with spaces. First 8 bytes are devoted to le name, last 3 bytes are devoted for extension. Data itself (1008 bytes). Data must be padded with zeroes if needed. Check sum = BLOCK[0] xor BLOCK[1] xor. xor BLOCK[1025]
17.6.4 Timing Timing is compatible with Turbo 2000 and Super Turbo. 35
17.6.5 Notes B-TAPE device handler is able to read les stored using Turbo Tape system. In order to circumvent problems with big size of the device handler, special minimalistic binary loader called MICROB was shipped with B-TAPE.
18 Turbo systems from Poland
18.1 KSO Turbo 2000 and Turbo 2000F

18.1.1 Description Turbo systems used in Poland, originally designed together with KSO Turbo 2000 (Tape operating system) and them adopted for other tape operating systems. Three types of pulses are distinguished: Pilot tone pulse, wide pulse and narrow pulse. Bits are stored in MSB to LSB order. File stored using KSO Turbo 2000 system consists of blocks. First block is a header block (HEADER), other blocks are data blocks (DATA). Every block is preceded by pilot tone (series of pilot tone pulses). Signal is expected on some pin of joystick port (KSO Turbo 2000) or on DATA-IN pin of the SIO connector (Turbo 2000F). 18.1.2 Header block Offset 2-Description Always 0 Always 255 File name (10 characters) Check sum = (HEADER[0] + HEADER[1] +. HEADER[11]) mod 256
18.1.3 Data block Offset 0-1 2-Description Number of valid bytes in the block, 0-3072. Up to 3072 bytes of data padded with zeroes if needed. Check sum = (BLOCK[0] +. + BLOCK[3073]) mod 256
File ends with data block that has less than 3072 valid bytes. If the total le size can be divided by 3072 without a remainder, le must end with block that has 0 valid bytes. 18.1.4 Timing Pulse Pilot tone Wide Narrow Width 44/44100 s 22/44100 s 11/44100 s

18.2 Turbo Blizzard

18.2.1 Description Turbo system used in Poland, suitable for holding binary les (small blocks, high transfer speed). Three types of pulses are distinguished: Pilot tone pulse, wide pulse and narrow pulse. Bits are stored in MSB to LSB order. File stored using Turbo Blizzard system consists of the following blocks.
1. Synchronisation block. This block is preceded with pilot tone (3072 pilot tone pulses) and two narrow pulses. Block does not hold any data. Block is followed with silence lasting for 0.1 second. 2. Header block (HEADER). This block is preceded with pilot tone (302 pilot tone pulses) and two narrow pulses. Then 78 bytes of data follow. Block is followed with silence lasting for at least 3 seconds. 3. One or more data blocks. These blocks are preceded with pilot tone (302 pilot tone pulses) and two narrow pulses. Then 1029 bytes of data follow. Data blocks are separated by short gaps. 18.2.2 Header block Offset 0-77 Description File name Check sum = (HEADER[0] + HEADER[1] +. HEADER[75]) mod 256 Spare byte, always 0

18.2.3 Data block Offset 0-1 2-Description Number of valid bytes in the block, 0-1024. Up to 1024 bytes of data padded with zeroes if needed. Always 0 Check sum = (HEADER[0] + HEADER[1] +. HEADER[1026]) mod 256 Spare byte, always 0
18.2.4 Timing Pulse Pilot tone Wide Narrow Width 24/44100 s 12/44100 s 8/44100 s

18.3 Turbo ROM

18.3.1 Description Turbo system used in Poland, with limitations similar to Czechoslovak Turbo 2000 and Super Turbo Systems. This turbo system can hold Turbo ROM combatible binary les (those binary les consist of exactly one DATA segment at most one RUN segment and at most one INIT segment) or tokenised BASIC programs. Three types of pulses are distinguished: Wide pulse, narrow pulse and stop pulse. Bits are stored in LSB to MSB order. File stored using Turbo ROM system consists of two blocks. 1. Header block (HEADER). This block is preceded with pilot tone (4884 wide pulses) and one narrow pulse. Then 41 bytes of data follow. After header block, there are four wide pulses and one stop pulse. 38
2. Data block. This block is preceded with pilot tone (516 wide pulses) and two narrow pulses. Then data follow. Data blocks are separated by short gaps. After data block, there are four wide pulses and one stop pulse. 18.3.2 Header block for binary les Offset 0 1-2 3-6-7 8-9 10-11 12-15-36 37-Description Header block check sum = (HEADER[1]. xor. HEADER[40]) Header load address (1537) Header length excluding rst byte (40) Data block check sum = (DATA[0] xor DATA[1] xor. DATA[?]) Run address Init address Load address Data block length Padding 0 File name. Internal code is used. Program type ag. For binary les there is 1. 0 - JSR to init address, 1 - No JSR to init address Padding zeros RTS opcode (96)
18.3.3 Data block Offset 0-? Description Bytes of data
18.3.4 Timing Pulse Wide Narrow Stop Width 16/44100 s 6/44100 s 48/44100 s