Text93 Information Page

Copyright © 2002 Don Starr - All Rights Reserved, portions by Ken Plotkin, Bill Petrowsky

Questions or comments- email: Win93@starrsoft.com

Though it is free to use, Text93 is copyrighted software. Please read the License Agreement.

Text93 is a command-line alternative to the GUI program Win93. It allows you to upload to and download from the PRO-93. It will read and write both .P93 and .TXT files (format of the .TXT file described below). It will also convert between the two file formats.

Everything you can do in Text93 can be done in Win93, and vice-versa. Text93 was originally written to test out different pieces of Win93's functionality before the GUI app was actually started. It lives on because there are some people (you know who you are) that prefer a command-line interface instead of the "clicky-pointy-mousey drivel", to quote a certain command-line fan.

Both Text93 and Win93 read and write the same text files. For the rest of this document, I refer to them simply as "the programs".

Important: The programs do not perform any frequency validation when they read a text file. They don't check to see that a frequency is within any of the PRO-93's valid ranges, nor do they verify that the frequency is appropriate for the PRO-93's step sizes. If you decide to enter "funny" frequencies, you do so at your own risk!

Text File (.TXT) Format

The programs will read and write plain text files that you can edit in any text editor (Windows Notepad, Word, vi, etc.). If you use a Unix-ish editor, note that the text files created by the programs contain CR/LF pairs - not just LF. On input, the programs do not care about that, but the difference might affect how you configure your editor. If you use an editor like Word, Wordpad, or Write, make sure you save the file as plain text - don't save it as a "Word Document".

The text file contains two things: descriptive text and data fields. Data fields are delimited by square brackets [ and ]. Nothing outside the square brackets (the descriptive text) is important to the programs - all they care about is what's in the data fields. All of the data fields are important - if you delete just one, the programs will either give you garbage or will refuse to load the text file. Also important is the order of the data fields. Don't go swapping the rows that are labeled "ID Delay Time" and "Fleet Map". Since the descriptive text isn't important to the programs, the only way they have of knowing what a particular data field represents is that data field's position in the file.

Since the data fields are delimited by square brackets, some special considerations are necessary if you actually want to use square brackets in a field (i.e. an alpha tag). For example, if you make the Bank 0 Alpha Tag field look like "[NYC [PD] ]", it will interpreted as "NYC [PD". The programs look for the closing square bracket ] in order to end a field. If you want to put square bracket characters in your tags, you must precede them with the backslash character \. For example, the tag above becomes "[NYC \[PD\] ]". The backslash character tells the programs "interpret the very next character literally". If you want to put a backslash character in a tag, use a double backslash: "[NYC \[PD\\FD\] ]" would give you a tag of "NYC [PD\FD]". If you start using backslashes in your data fields, make sure you don't put them in front of the delimiting [ and ]. This will cause the programs to "miss" data fields, and they'll fail to load the file correctly.

The length of the data fields is not important. [ 858.40000 ] and [858.4] are equivalent. Alpha tags are either truncated on the right (if the field is longer than 12 characters) or padded on the right with blanks (if the field is shorter than 12 characters).

The data fields (along with their descriptive text, if any) are described next. Everything is described in the order in which it appears in the text file.

Next follows information for each bank. It starts with the bank number and it's alpha tag, and continues through the end of the trunk IDs for that bank. There are 10 consecutive blocks of such information.

After all bank information (channels and trunking info) come the CB and Marine search range (SR0 and SR1) settings. Since the format is the same for both, only a Marine example is described here.

Next come the SR2 (Police and Fire) search range settings.

Next come the SR3 (Aircraft) search range settings.

Next come the SR4 (Ham) search range settings.

Next come the SR5 (User-specified limits) search range settings.

After all of the search ranges are other global settings.