Telix supports a very large number of protocols internally. It also allows
users to define up to 4 external protocol implementations, for the utmost in
flexibility.

External protocols are defined in the 'Protocol options' page of the
<Config>uration Menu. When the user selects a transfer with an external
protocol Telix will either run a specified DOS Batch file, or a script file.

Batch File Method

If a Batch file has been configured to be executed when the external protocol
is selected, TELIX will run it and pass 3 parameters to it.

The first parameter is the baud rate. This is accessed within the DOS batch
file as %1. 

The second parameter is the comm port number. This is accessed as %2. 

The third parameter is the reply the user gave when asked what file(s) to
transfer. If this is a download and this protocol has been defined to not need
a download name, this parameter will be blank. This parameter is referred to
as %3 in the Batch file.




It is the responsibility of the Batch file to call a driver program for the
protocol, using the supplied information. For example, if Telix didn't have
built-in Zmodem support, a batch file called ZMOD.BAT could be defined to
perform Zmodem uploads using the DSZ program with the following commands.

DSZ port %2 speed %1 sz %3

This would tell DSZ what files to transfer, and also would specify the proper
baud rate and comm port.


Script File Method

Alternately, Telix can run a SALT script file when the user selects an
external protocol. The user's reply to the question of what files to transfer
is stored in the system variable '_ext_filespec'. The script file is free to
implement the protocol in whatever way it wants to, such as calling an
external driver program using the 'RUN' function, or by actually performing
the transfer itself.