home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
World of Ham Radio 1997
/
WOHR97_AmSoft_(1997-02-01).iso
/
packet
/
pak_30
/
amsoft.iii
next >
Wrap
Text File
|
1997-02-01
|
212KB
|
6,397 lines
Programme Terminal PacKet v1.81
12 February 1993
F1EBN , Gerard Regnard
Mocquesouris
77220 Tournan en Brie
France
Terminal PacKet TPK v1.81
Terminal PacKet TPK v1.81
PREFACE
Thanks:
The original french documentation was improved by Claude F1CDC.
To Ivor GI4WRI and George GI1VAZ for the english translation.
To all the OMs who have translated the TPK files.
To Alan G3KFN and Chris KC6IKO sysops of GB7PLY.
A special thanks to Andy G1DIL who has coordinated all the job !
Comment(s) or suggestion(s) : F1EBN or FC1EBN @ F6ABJ.FRPA.FRA.EU
Preface ii
Terminal PacKet TPK v1.81
CONTENTS
1.0 General presentation of TPK. . . . . . . . . . . . . . . 1
1.1 Objectives of TPK. . . . . . . . . . . . . . . . . . . . 1
1.2 Conventions of command writing. . . . . . . . . . . . . . 1
1.3 Main functions of TPK. . . . . . . . . . . . . . . . . . 2
1.3.1 HELP. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.2 LOG. . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.3 BACKSCROLL. . . . . . . . . . . . . . . . . . . . . . 3
1.3.4 CAPTURE. . . . . . . . . . . . . . . . . . . . . . . 3
1.3.5 REMOTE Commands. . . . . . . . . . . . . . . . . . . 3
1.3.6 FILES TRANSFER. . . . . . . . . . . . . . . . . . . . 3
1.3.7 PROGRAMMING. . . . . . . . . . . . . . . . . . . . . 4
1.3.8 The "BROADCAST" function. . . . . . . . . . . . . . . 4
1.3.9 Other functions. . . . . . . . . . . . . . . . . . . 5
1.4 Briefly, how starting up ? . . . . . . . . . . . . . . . 7
1.5 Description of the main screen windows. . . . . . . . . . 8
2.0 Description and use of TPK functions. . . . . . . . . . 10
2.1 On-line help <ALT-H>. . . . . . . . . . . . . . . . . . 10
2.1.1 General points. . . . . . . . . . . . . . . . . . . 10
2.1.2 Choice of a command. . . . . . . . . . . . . . . . . 10
2.1.2.1 With the keyboard. . . . . . . . . . . . . . . . 10
2.1.2.2 With the mouse. . . . . . . . . . . . . . . . . 10
2.1.3 Movements in the text displayed. . . . . . . . . . . 11
2.1.3.1 With the keyboard. . . . . . . . . . . . . . . . 11
2.1.3.2 With the mouse. . . . . . . . . . . . . . . . . 11
2.1.4 Changing the help file. . . . . . . . . . . . . . . 12
2.2 LOG type functions. . . . . . . . . . . . . . . . . . . 12
2.2.1 MHEARD. . . . . . . . . . . . . . . . . . . . . . . 12
2.2.2 LOGBOOK. . . . . . . . . . . . . . . . . . . . . . . 12
2.3 BACKSCROLL. . . . . . . . . . . . . . . . . . . . . . . 13
2.4 CAPTURE mode. . . . . . . . . . . . . . . . . . . . . . 14
2.5 Remote commands. . . . . . . . . . . . . . . . . . . . . 14
2.5.1 Internal commands. . . . . . . . . . . . . . . . . . 14
2.5.2 Commented directory. . . . . . . . . . . . . . . . . 16
2.5.3 External commands. . . . . . . . . . . . . . . . . . 17
2.5.3.1 General points. . . . . . . . . . . . . . . . . 17
2.5.3.2 Structure of EXECAUTO.TPK . . . . . . . . . . . . 17
2.6 File transfers. . . . . . . . . . . . . . . . . . . . . 19
2.6.1 General points. . . . . . . . . . . . . . . . . . . 19
2.6.2 Transfer of text (ASCII). . . . . . . . . . . . . . 21
2.6.2.1 You send an ASCII file to your correspondent. . 21
2.6.2.2 You ask for an ASCII file. . . . . . . . . . . . 22
2.6.2.3 Correspondent send you an ASCII file. . . . . . 22
2.6.2.4 Correspondent asks for an ASCII file. . . . . . 22
2.6.2.5 Summary of ASCII transfers. . . . . . . . . . . 23
2.6.3 BINARY transfer (Datas). . . . . . . . . . . . . . . 23
2.6.3.1 You send a BINARY file to your correspondent. . 23
2.6.3.2 You want to receive a BINARY file. . . . . . . . 24
2.6.3.3 Correspondent sends you a binary file. . . . . . 24
2.6.3.4 Correspodent asks for a BINARY file. . . . . . . 24
2.6.3.5 Summary of BINARY transfers. . . . . . . . . . . 25
2.6.4 Recovery of an abandonned transfer. . . . . . . . . 25
Contents iii
Terminal PacKet TPK v1.81
2.6.5 Menus for transferring files. . . . . . . . . . . . 26
2.6.5.1 Aim. . . . . . . . . . . . . . . . . . . . . . . 26
2.6.5.2 File(s) reception menus <ALT-R> . . . . . . . . . 26
2.6.5.3 File(s) transmission menus <ALT-E> . . . . . . . 27
2.6.5.4 Menu of file(s) choice in a list. . . . . . . . 28
2.7 Programming function. . . . . . . . . . . . . . . . . . 29
2.7.1 General points. . . . . . . . . . . . . . . . . . . 29
2.7.2 Programming of function keys. . . . . . . . . . . . 30
2.7.3 Macro-commands. . . . . . . . . . . . . . . . . . . 32
2.7.3.1 Creating a macro-command. . . . . . . . . . . . 32
2.7.3.2 Carrying out a macro-command. . . . . . . . . . 33
2.7.3.3 Managing macro-commands. . . . . . . . . . . . . 33
2.7.4 Programme files. . . . . . . . . . . . . . . . . . . 33
2.7.4.1 Creation of a programme-file. . . . . . . . . . 33
2.7.4.2 Carrying out a programme-file. . . . . . . . . . 34
2.7.4.3 Example of a programme-file. . . . . . . . . . . 34
2.7.5 Other commands useful in programming. . . . . . . . 35
2.7.5.1 Capture of the date and time. . . . . . . . . . 35
2.7.5.2 Variable PATH. . . . . . . . . . . . . . . . . . 36
2.7.5.3 Programming a waiting period. . . . . . . . . . 37
2.7.5.4 Password management. . . . . . . . . . . . . . . 38
2.7.5.5 Programming an event. . . . . . . . . . . . . . 39
2.7.5.6 Creation of a cycle. . . . . . . . . . . . . . . 39
2.7.5.7 Management of events. . . . . . . . . . . . . . 40
2.8 The BROADCAST function. . . . . . . . . . . . . . . . . 40
2.8.1 Installation of the BROADCAST manager. . . . . . . . 40
2.8.2 List of the BROADCAST function commands . . . . . . . 41
2.8.3 Message transfers between TPK and the BBS. . . . . . 45
2.8.4 Configuration examples of the "BROADCAST" functions. 46
2.9 The LOGBOOK function. . . . . . . . . . . . . . . . . . 48
2.9.1 Contents of the LOGBBOK. . . . . . . . . . . . . . . 48
2.9.2 Management commands of the LOGBOOK. . . . . . . . . 49
2.10 Other functions. . . . . . . . . . . . . . . . . . . . 50
2.10.1 Access to DOS function. . . . . . . . . . . . . . . 50
2.10.2 Keyboard management. . . . . . . . . . . . . . . . 51
2.10.3 Reconnection function. . . . . . . . . . . . . . . 51
2.10.4 QSO messages function. . . . . . . . . . . . . . . 52
2.10.5 Printing function. . . . . . . . . . . . . . . . . 52
2.10.6 Miscellaneous. . . . . . . . . . . . . . . . . . . 52
2.10.6.1 Warning bells. . . . . . . . . . . . . . . . . 52
2.10.6.2 Serial port management. . . . . . . . . . . . . 53
2.10.6.3 Use of external drivers. . . . . . . . . . . . 54
2.10.6.4 Passage into direct terminal mode. . . . . . . 54
3.0 TPK function keys. . . . . . . . . . . . . . . . . . . . 55
3.1 Function keys <F1> to <F10> . . . . . . . . . . . . . . . 55
3.2 <ALT-A> to <ALT-Z> keys. . . . . . . . . . . . . . . . . 56
4.0 Syntax of TPK commands. . . . . . . . . . . . . . . . . 59
4.1 Local commands. . . . . . . . . . . . . . . . . . . . . 59
4.2 Remote commands. . . . . . . . . . . . . . . . . . . . . 67
5.0 Configurations and setting up of TPK. . . . . . . . . . 70
5.1 The serial port. . . . . . . . . . . . . . . . . . . . . 70
5.1.1 Connection between TNC and PC. . . . . . . . . . . . 70
Contents iv
Terminal PacKet TPK v1.81
5.1.2 Configuration of the serial port. . . . . . . . . . 71
5.1.3 Configuration for IBM serial cards. . . . . . . . . 72
5.1.4 Use of an external driver. . . . . . . . . . . . . . 73
5.2 Setting up TPK. . . . . . . . . . . . . . . . . . . . . 73
5.2.1 Decompression. . . . . . . . . . . . . . . . . . . . 73
5.2.2 List of TPK files. . . . . . . . . . . . . . . . . . 74
5.2.3 Starting. . . . . . . . . . . . . . . . . . . . . . 76
5.2.3.1 First attempts. . . . . . . . . . . . . . . . . 76
5.2.3.2 First time starting. . . . . . . . . . . . . . . 76
5.2.3.3 Error messages. . . . . . . . . . . . . . . . . 77
5.2.3.4 Setting up commands. . . . . . . . . . . . . . . 78
5.2.4 Use of TPK with a KAM. . . . . . . . . . . . . . . . 78
5.2.4.1 Setting up. . . . . . . . . . . . . . . . . . . 78
5.2.4.2 Specific commands for the KAM. . . . . . . . . . 79
5.2.5 Use of TPK with a PK232. . . . . . . . . . . . . . . 79
5.3 The different screens. . . . . . . . . . . . . . . . . . 80
5.3.1 Description of screens. . . . . . . . . . . . . . . 80
5.3.1.1 On-line help. . . . . . . . . . . . . . . . . . 81
5.3.1.2 The ALT keys help. . . . . . . . . . . . . . . . 81
5.3.1.3 The main screen. . . . . . . . . . . . . . . . . 81
5.3.1.4 The MHEARD screen. . . . . . . . . . . . . . . . 84
5.3.1.5 The BACKSCROLL screen. . . . . . . . . . . . . . 84
5.3.1.6 The DOS screen. . . . . . . . . . . . . . . . . 85
5.3.1.7 The message listing screen. . . . . . . . . . . 85
5.3.1.8 The message editor screen. . . . . . . . . . . . 86
5.3.1.9 The LOGBOOK screen. . . . . . . . . . . . . . . 88
5.3.2 Configuration of a colour screen. . . . . . . . . . 88
5.3.3 Configuration of a monochrome screen. . . . . . . . 89
6.0 TPK files. . . . . . . . . . . . . . . . . . . . . . . . 90
6.1 The TPK.CFG file. . . . . . . . . . . . . . . . . . . . 90
6.2 The CONFIG.TPK files. . . . . . . . . . . . . . . . . . 90
6.3 The DIRC.TPK file. . . . . . . . . . . . . . . . . . . . 91
6.4 The EXECAUTO.TPK file. . . . . . . . . . . . . . . . . . 93
6.5 The on-line help files. . . . . . . . . . . . . . . . . 93
7.0 Appendix : Extensions to the Yapp protocol . . . . . . . 95
7.1 HEADER extension. . . . . . . . . . . . . . . . . . . . 95
7.2 Data Packets extension. . . . . . . . . . . . . . . . . 95
7.3 Crash Recovery. . . . . . . . . . . . . . . . . . . . . 95
Contents v
Terminal PacKet TPK v1.81
1.0 GENERAL PRESENTATION OF TPK.
1.1 OBJECTIVES OF TPK.
TPK is a software conceived for a TNC2 (or a clone). It works with
a PC or compatible under MSDOS.
It uses the power of the PC to facilitate the use of the TNC and
considerably increase the fields of use of the packet radio.
TPK has the characteristic of beiing largely configurable. The
configurations files and equally many TPK commands can easily be
programmed by the user.
TPK accepts both KAM and PK232 TNCs.
1.2 CONVENTIONS OF COMMAND WRITING.
The commands as an example in this documentation will always be
surrounded by " to differentiate them from the text.
Here is an example of what you will come across:
To send a text file, use the command:
■ "/SEND [x:]FILENAME.EXT A"
Of course, in the real use of the command, the " will not be typed.
The capital letters of TPK commands in this document are the
essential letters to give the command validity.
On the other hand, a command can be written in small or capital
letters.
■ Macro, M, macro, or mAcRo are identical and valid.
■ SEND has no shortening but can be written send, Send etc.
The parameters between hooks are optional.
■ "/SEND [x:]FILENAME.EXT"
In that case the disc where the file can be found is optional.
The pressing of a key on the keyboard is represented by <key>.
■ <ESC> for the escape key.
Commands are usually validated by the key <CR> (carriage return) or
<Return> or <Enter>. In this document validation is often left out
as it is obvious, otherwise it is represented by <RC>.
General presentation of TPK. 1
Terminal PacKet TPK v1.81
Parameters of commands must be separated by spaces. Useless
parameters, or excess ones, are ignored.
1.3 MAIN FUNCTIONS OF TPK.
The TNC mainly directs the transfer of packets according to the
AX25 protocol. TPK adds several new functions of wich i have hereby
made a brief summary. Paragraph 2 gives details and directions for
use.
1.3.1 HELP.
The use of TPK is simple....as long as you know its possibilities,
from where the importance of the documentation.
TPK offers 3 types of help:
■ The TPK.DOC file that you are currently reading: it's the most
complete document. It should be read at least once to find out
what it contains and to find out how to get at it in case you
get stuck
■ A main "online" help which is accessible at any time through the
key <ALT-H>. It is to be used systematically and is the most
practical help available.
■ A table focussing on the list of <ALT> keys accessible with the
function key <F1>.
1.3.2 LOG.
■ MHEARD: List and path of stations heard, list of the last 8
connections or remote commands. It is activated by the function
key <F2>.
(Details paragraph "2.2.1 MHEARD." on page 12)
■ Logbook: summarise connections in a file you can consult at any
time with the command "LOG".
(Details paragraph "2.2.2 LOGBOOK." on page 12 )
■ Another file, LOGDIST.TPK summarise connections, deconnections,
remote commands received. It is an ASCII file, readable with any
text viewer or editor.
General presentation of TPK. 2
Terminal PacKet TPK v1.81
1.3.3 BACKSCROLL.
A circular buffer memorise everything which is written in the
traffic and monitoring window in the connected and disconnected
mode. This buffer can be consulted, erased or saved on disc at any
time.
Keys <ALT-Z>,<ALT-W>,<ALT-P>,HOME,END,PGUP,PGDN are used for the
backscroll functions.
(Details paragraph "2.3 BACKSCROLL." on page 13)
You can control the lenght of this buffer by the command "BUFFER".
(Details paragraph "4.1 Local commands." on page 59)
1.3.4 CAPTURE.
A command very simply allows you to capture on disc the text being
received, for example to recover a message from a BBS. The name of
the file created is parametrable.
This function is activated by the key <ALT-S>.
(Details paragraph "2.4 CAPTURE mode." on page 14)
1.3.5 REMOTE Commands.
Your correspondent can also carry out TPK commands: to gain access
to your discs in order to find the directory (/DIR), the number of
free bytes (/FREE), to change the implicit disc (/DISK), etc....
These commands are attainable by the station to which you are
connected.. In order to be accepted as a command by TPK , the
latter must be preceded by "/".
All "/" received at the beginning of a line is considered by TPK as
preceding a command. This command must be found in the EXECAUTO.TPK
file, then carried out according to the contents of this file, or
ignored if it has not been authorised.
1.3.6 FILES TRANSFER.
TPK allow the transfer of ASCII or BINARY files.
The protocol used for binary transfers is the excellent Yapp by
WA7MBL with some extensions (Crash recovery / Checksum). Your
correspondent must also be equipped with the Yapp protocol or also
be using TPK. But with TPK unlike with Yapp, these binary transfers
can be carried out without any intervention from the correspondent.
Thus it is possible to carry out the transfer in his absence.
General presentation of TPK. 3
Terminal PacKet TPK v1.81
TPK's Yapp protocol is capable of retrieving an interrupted
transfer (interrupted for example by an untimely DISCONNECT !) with
another TPK user or a BBS F6FBB (but in this case only on a
download).
(Details paragraph "2.6 File transfers." on page 19)
1.3.7 PROGRAMMING.
It is possible to carry out a sequence of defined commands in a
file (command "EXecute"). These commands can be programmed to be
carried out at a given time (command "At").
The 10 function keys, as well as the <ALT>,<CTRL> and <SHIFT> keys
can be programmed just as well by you, thus enabling you to
personalise TPK.
So, Macro-commands (the sequence of commands sent out by a given
word key) can easily written, bringing power and flexibility to the
use of TPK.
In all cases, writing these programms requires the setting up and
use of an editor. Remember that in packet, you will avoid annoying
your correspondents with non standard characters as those are
banished from the keyboard (the accented e's, control characters
etc).
(Details paragraph "2.7 Programming function." on page 29)
1.3.8 The "BROADCAST" function.
At the present time, to get a list of the available messages at
your local BBS, you are required to connect to it, and type L.
With TPK and FBB v5.14 and above, you can receive this list direct
to your PC, automatically, by simply running TPK with no manual
intervention. The only requirement is that you check first with
your SysOp and have the facility enabled at the BBS.
You can then view this list of message headers (without connecting
to your BBS), select the particular messages that you would like to
read (using either the keyboard, or mouse) and TPK will arrange for
these to be collected using the FBB compressed forwarding and
stored directly onto your disk ready for you to attend to them.
The built-in text editor in TPK allows you to enter any new
messages, edit messages, or send replies to any of the previously
received messages. Once complete your outgoing mail is sent to your
local FBB BBS again in compressed format.
The BROADCAST command in TPK allows you to configure all of these
features.
General presentation of TPK. 4
Terminal PacKet TPK v1.81
The headers are sent by the FBB BBS in beacon mode (this is why
this function has been named BROADCAST). Their format is identical
to that seen when you type the L command when using the FBB BBS.
Example:
F6ABJ-1>FBB <UI C>
200000 P 432 F6FBB @F6FBB FC1EBN 920709 5.14d Installed. No problems !
These beacon frames are stored in selected files within TPK and you
can consult the files/list at any time. A simple protocol is used
to maintain the listing to be sure that it is up-to-date. TPK MUST
receive all of the message headers in numerical order, if one is
received out of sequence then a request to resynchronise is sent by
TPK to the FBB BBS. This frame can be sent manually using the BR
SYNCHRO command.
1.3.9 Other functions.
Access to DOS: command "SHell" to launch a programm from TPK or key
<F3> to simply pass under DOS. Return from DOS through "EXIT".
(Details paragraph "2.10.1 Access to DOS function." on page 50)
Management of the keyboard: TPK analyses what have been entered
after you have validated it by pressing <CR>. If it recognises a
command, it will carry it out, if not everything is sent towards
the TNC.
(Details paragraph "2.10.2 Keyboard management." on page 51)
Edition: the keyboard is printed in the lower part of the screen.
This text can then be corrected (it is possible to delete, add to,
edit and justify the text).
The lines entered are kept in the memory (20 lines) and can be
examined with keys <high arrow> and <low arrow>.
(Details paragraph "2.10.2 Keyboard management." on page 51)
Connection to a station: the call of the last connection is
memorised and you can request the connection again by hitting <F8>.
(Details paragraph "2.10.3 Reconnection function." on page 51)
QSO Messages: you can prepare up to 10 messages which can be sent
to the correspondent by hitting keys <ALT-n> (n from 1 to 0).
(Details paragraph "2.10.4 QSO messages function." on page 52)
Personal mailer: your correspondent can leave a message to you
(command "/MSG"). The message is incorporated a the end of your
personal mail list.
General presentation of TPK. 5
Terminal PacKet TPK v1.81
(Details par "2.8 The BROADCAST function." on page 40)
Printing: a printer can be brought into service by the keys <ALT-I>
or <F4>.
(Details paragraph "2.10.5 Printing function." on page 52)
Let us note the following possibilities described in paragraph
"2.10.6 Miscellaneous." on page 52
■ It is possible to operate in systems other than packet by using
the key <ALT-A> to put TPK transparent and send everything typed
on the keyboard to the TNC.
■ There are several sounding warning. They are managed by commands
"ALArme", "BELL", "SOnnerie" and key <ALT-B>.
(Details paragraph "2.10.6.1 Warning bells." on page 52)
■ Management of the serial interface: choices and adjustement of
addresses and IRQs of the serial ports, use of internal or
external drivers like COMBIOS, MBBIOS, ESS, G8BPQ.
(Details paragraph "5.1 The serial port." on page 70)
General presentation of TPK. 6
Terminal PacKet TPK v1.81
1.4 BRIEFLY, HOW STARTING UP ?
The setup of the serial port is as follow:
■ Serial port: fixed in TPK.CFG
■ Speed: fixed in TPK.CFG
■ Parity: NONE fixed in TPK
■ Bits: 8 fixed in TPK
■ Stop: 1 fixed in TPK
The installation is done by the programm TPKINST.EXE.
Put the TPK disc in drive A: for example and type:
■ A:
■ TPKINST GB
Set all the parameters (the serial port and speed, etc), and after
validation TPKINST will create the directories if needed,
decompress the zipped files, and install TPK.CFG with your
parameters.
Connect your TNC on the serial port connector, go in the TPK
directory and run TPK.EXE. When TPK is ready (you must not get an
error message !), if you see nothing coming from the TNC, the
parity and bits number are certainly bads. There is the command
TNCINI to set them correctly.
Enter the command:
■ TNCINI
You will see the tries in a small window. When TPK has received the
cmd: from the TNC, the parity and bit number are corrects. You can
now configure your TNC.
According to the type of your TNC, use the file *.SET
correspondent. For instance for a TNC2 with eprom 1.1.8a use the
file TNC2118A.SET. You can send the contents of the file to the TNC
with the /SEND command:
■ "/SEND TNC2118A.SET E"
When all the commands are sent the TNC is configured and you can
trie the first connection !
General presentation of TPK. 7
Terminal PacKet TPK v1.81
1.5 DESCRIPTION OF THE MAIN SCREEN WINDOWS.
The TPK screen can manifest itself in some different ways,
according to the functions in progress (the name of the screens and
windows in capital letters will be used systematically in this
document, in a way which will avoid mistakes in interpretation).
■ The ON-LINE HELP screen. (access by <ALT-H>)
■ The KEYS HELP screen. (access by <F1>)
■ The MAIN screen of reception and transmission.
■ The MHEARD screen. (access by <F2>)
The MHEARD screen is split in 2:
- The stations heard.
- The connections made and remote commands received.
■ The BACKSCROLL screen. (access by <HOME>, <END>, <PGUP>, <PGDN>)
■ The DOS screen. (access by <F3>)
■ The LISTINGS screen. (access by <ALT-L> or BRoadcast List)
■ The LOGBOOK screen. (access by command "LOG")
Paragraph "5.3 The different screens." on page 80 describes these
screens in detail.
Here is a summarised description of the main screen, ie the packet
screen concerning reception and transmission, which consist of at
least two windows:
■ At the top of the screen, the traffic window.
■ At the bottom of the screen, the keyboard window.
However the reception window differs according to whether it is in
the disconnected or connected mode: in the disconnected mode, one
receives the traffic in progress, according to the state of the TNC
command "Monitor". In the connected mode, only the QSO in progress
is displayed (what is sent out and what is received).
In every case the keyboard window will let in TNC and TPK commands.
It is possible to open a third window called monitor window which
will be located at the top of the screen (to the detriment of the
traffic window which will consequently be reduced in size).
In the disconnect mode, it will be possible to receive for example
the only traffic of a given call in the monitor window.
General presentation of TPK. 8
Terminal PacKet TPK v1.81
In the connected mode, on the TNC2 ONLY, under certain conditions,
you can receive the traffic in progress, except for your QSO which
will be displayed in the traffic window.
The windows are separated, according to the number of opened
windows, by 2 or 3 bands of a line. They indicate the state of the
system and the fucntion of various keys.
For more details see paragraph "5.3 The different screens." on page
80 which describe the functions of all the screens.
Now, to fully make use of TPK, you will have to read carefully the
following paragraphs.
General presentation of TPK. 9
Terminal PacKet TPK v1.81
2.0 DESCRIPTION AND USE OF TPK FUNCTIONS.
2.1 ON-LINE HELP <ALT-H>.
2.1.1 General points.
The <ALT-H> key gives you access to the TPK on-line help
screen.This screen gives the the syntax of TPK commands by a menu
in which you choose the command of interest to you.
This help is not however limited to TPK commands and can contain
all the informations you want, because everything displayed in this
screen is contained in the file TPK.HLP. This file is a text file,
whose structure is simple and which can easily be modified with an
editor. Furthermore, you can change the help file by choosing it
in a menu.
2.1.2 Choice of a command.
2.1.2.1 With the keyboard.
You can move the selection line onto the desired command with the
arrows <upwards> and <downwards>. Then validate this with <CR> or
by pressing the <S> key which correspond to the <Selection> button.
To cancel this, press <ESC> or <A> which corresponds to the
<Cancel> button. You will return to the MAIN TPK screen.
<HOME> takes the selection line to the top of the menu.
<END> takes the selection line to the bottom of the menu.
<PGDN> moves on the next page in the list (a height of one window).
<PGUP> moves back to the last page in the sequence.
2.1.2.2 With the mouse.
The mouse can be activated, if present, in the file TPK.CFG with
TPKINST.EXE.
Position the cursor with your mouse onto the command you wish to
select and validate this by pressing the left button.
If the selection line is on the desired command, you can also
validate it by positioning the cursor with the mouse on the
<Select> button and pressing the left button.
Description and use of TPK functions. 10
Terminal PacKet TPK v1.81
To cancel, press the right button or position the cursor on the
<Cancel> button and validate with the left button.
The <Upwards> and <Downwards> arrows on the right side of the menu
windows do the same thing as the corresponding keys on the
keyboard. Position the cursor above and validate with the left
button.
The upward and downward triangles on the right side of the menu
window do the same thing as the <PGUP> and <PGDN> keys of the
keyboard. Position the cursor on top of it and validate with the
left button.
The <HOME> and <END> buttons have the same effect as the
corresponding keys on the keyboard. Position the cursor on top of
them and validate with the left button.
2.1.3 Movements in the text displayed.
The contents of the file TPK.HLP, which corresponds to this
command, are displayed on the screen. If they exceed the height of
the screen you can move within the text using <PGUP> and <PGDN>
keys.
2.1.3.1 With the keyboard.
<PGDN> moves onto the next page of the text (one full length of the
window).
<PGUP> moves up a page in the text (one full window text).
<ESC> or <A> brings you back to the list.
2.1.3.2 With the mouse.
The upward and downward triangles on the right side of the menu
window perform the same action as the <PGUP> and <PGDN> keys on the
keyboard. Position the cursor on top of them and validate with the
left button.
To return to the menu position the cursor on the <Cancel> button
and validate with the left button or press the right button.
The <Upward> and <Downward> arrow keys and the corresponding mouse
buttons pass respectively to the preceding or following command (if
that is possible !).
Description and use of TPK functions. 11
Terminal PacKet TPK v1.81
2.1.4 Changing the help file.
The <C> key or the <Change help file> button validated with the
mouse displays the list of files ".HLP" which can be found in the
help files directory.
You will find the following files which are provided with TPK.
■ TPK.HLP : TPK commands.
■ FBB.HLP : BBS F6FBB commands and menus.
■ TNC2117.HLP : TAPR eprom version 1.1.7 for the TNC2.
■ CLUSTER.HLP : Packet Cluster (tm) commands.
TPK can also read the VK2DHU files supplied with its PACKET
programme. (TNC2 v 1.1.6, PK232, MFJ1278)
2.2 LOG TYPE FUNCTIONS.
2.2.1 MHEARD.
This is the equivalent of the TNC command "MHEARD": it lists the
date/time and call of the stations heard if the monitoring is
validated on the TNC. The repeaters used are also displayed.
The <F2> key enables the display of this information on the upper
part of the LOG screen (within the limits of the length of the
line).
You can return to the MAIN screen by pressing any key, however
return is automatic after 30 seconds.
You can erase this list by the command "EFLogrx".
(See also paragraph "5.3.1.4 The MHEARD screen." on page 84)
2.2.2 LOGBOOK.
With key <F2> you have the last connections, disconnections and
remote commands listed. Two files are updated at the same time if
the function is validated by the command "LOG ON|OFF":
■ The LOGDIST.TPK file which memorises the connections,
disconnections and remote commands possibly dealt with by TPK.
This file is an ASCII text file.
■ The LOGBOOK file which can take different names depending of
your configuration. If you have set your callsign with the TNC
command MYcall TPK will use a file named "<MYcall>.LOG" else it
Description and use of TPK functions. 12
Terminal PacKet TPK v1.81
will use a file named "LOG.DAT".
You can view, edit, print, etc, the LOGBOOK. The command to
access it is LOG without parameter.
(Details par "2.9 The LOGBOOK function." on page 48)
2.3 BACKSCROLL.
Packet traffic or any text coming from the TNC is put into the
memory. Hit a cursor administration key (<HOME> <END> <PGUP>
<PGDN>) and TPK passes into the backscroll mode: you can reread the
memorised lines. The number of lines stored in memory is
configured by the command "BUFFER" (see par "4.1 Local commands."
on page 59). Be careful, if you put too many lines, there will not
be much memory space left for a "SHell" to DOS.
(see par "4.1 Local commands." on page 59)
When the reception buffer is full, the first lines are
progressively lost to leave room for new ones. (Circular movement).
The buffer is ONLY in memory and is lost when you leave TPK.
It can be:
■ Saved on disc using key <ALT-W>.
■ Printed using key <ALT-P>.
Be careful: if the buffer is full, you risk using a lot of paper
!!!
Use <ESC> to stop printing.
■ Erased using key <ALT-Z>.
The keyboard cursor keys allow movement in the buffer:
■ <HOME> to go to the begining.
■ <PGUP> to go up a page.
■ <PGDN> to go down a page.
■ <UP ARROW> to go up a line.
■ <DOWN ARROW> to go down a line.
■ <END> or <ESC> to leave the backscroll mode.
In the disconnected mode, the window takes up the whole screen.
Description and use of TPK functions. 13
Terminal PacKet TPK v1.81
In the connected mode, the screen is divided in 2 parts:
■ The upper window is for the backscroll mode.
■ The lower one is the keyboard entry window.
The keyboard entry window stays active, allowing backscroll
examination, location of information and exploitation of it in the
form of an entry command in the lower window.
Eg. an "R" command can be sent to a BBS, the number of the message
being read in the upper window.
(see paragraph "2.3 BACKSCROLL." on page 13)
2.4 CAPTURE MODE.
Traffic received on the screen can be sent on the disc at the same
time by using the <ALT-S> key. It is a toggle command, ie. the
first time <ALT-S> is pressed the function is brought into service,
and the next time you press it, it stops and the text is recorded
on the disc. The implicit name of the file is TEMP.TPK and is
saved in the CAPTURE directory, but any other name can be chosen.
To do this after pressing <ALT-S>, replace the name displayed in
the window with the name you have chosen. If the file exist, the
text is appended to the end of the file, following on from what is
already there.
This command is especially useful for capturing information in the
connected mode but also works in the disconnected mode. You can
therefore ask for a connection during the capture process.
The capture is closed either by using the <ALT-S> key or by
disconnection.
2.5 REMOTE COMMANDS.
2.5.1 Internal commands.
The remote commands aim to give an OM, connected to you, access to
a certain number of TPK commands.
In order to be accepted as commands by TPK the latter must be
preceded by the sign "/".
Your correspondent can:
■ Get help (/HELP and /AIDE)
■ Change the implicit disc (/DISK)
Description and use of TPK functions. 14
Terminal PacKet TPK v1.81
■ Receive the directory of your disc (/DIR)
■ Receive the commented directory list (/DIRC)
■ Change your current directory (/CHDIR or /CD)
■ Know the number of free bytes (/FREE)
■ Call you by ringing the bell (/OPE)
■ Read your list of stations heard (/LOG)
■ Leave you a message (/MSG)
■ Close and record the message (/EX)
■ Send a disconnection request (/BYE)
■ Request sending a file (/SEND)
(Details par "4.2 Remote commands." on page 67)
The remote command "/DIRC" is explained in the following paragraph
"2.5.2 Commented directory." on page 16.
The <F5> key authorises remote access to all your discs. If you
have set an upload directory with TPKINST.EXE, your correspondents
have ONLY access to this one unless you hit the <F5> key. This is a
toggle so pressing it a second time will close the system to the
upload directory.
If you have not set an upload directory with TPKINST.EXE the system
is opened and hitting <F5> key will close it on the current
directory.
The following commands are equally as functional on your keyboard:
/DIR /DIRC /OPE /DISK /FREE /LOG /HELP /SEND /CHDIR /CD
In the diconnected mode, it is possible to use the command "/SEND",
ONLY in the ASCII mode (!). This, for example, enables you to send
a configuration file to the TNC.
Eg: "/SEND TNC2.SET"
The "SEND" command is detailed in paragraph "2.5 Remote commands."
on page 14.
Remote commands see also paragraph "4.2 Remote commands." on page
67.
Description and use of TPK functions. 15
Terminal PacKet TPK v1.81
2.5.2 Commented directory.
The command "/DIRC" lists the contents of the DIRC.TPK file which
includes a list of the files existing on your PC, at your
correspondents disposal, accompanied by commentaries, giving, for
example, an explanation concerning the contents of these files. The
DIRC.TPK file must be located in the TPK directory. It is created
and modified here by the "COMmente" command.
The command "COMmente [x:\PATH\]FILENAME" enables the introduction
of commentaries into the "DIRC.TPK" file. You must give the
complete path if this file is not in the UPLOAD directory.
"/DIRC Criterion" enables selection of certain files which for
example follow a field of interest. This criterion is noted in the
DIRC.TPK file. A file can have several criteria.
The structure of the DIRC.TPK file is that of a text file: you can
therefore modify it with an editor as it suits you.
Each file description consists of a minimum of two lines which are
automatically created by the "COMmente" command.
■ The first line gives the file path and MUST begin with the &
character.
Eg: &C:\TPK\
The selection criterion is placed behind this path, separated
from it by a space.
Eg: &C:\TPK\ENVOI\ PACKET TPK
In this example, "/DIRC TPK" will list this file as "/DIRC
PACKET".
■ The second line gives the name of the file followed by its
characteristics, resulting from the DOS command DIR, ie. length,
time, date followed by the commentary entered by the "COMmente"
command.
TPK reconstructs the file name by taking the path in the first
line and the name in the second , then tests to find out if the
file is present on the disc. If the file does indeed exist, it
sends the contents of DIRC.TPK until the appearance of the &
character at the begining of the line or even at the end of the
file. If the file does not exist nothing will be sent.
However, if a criterion is requested in the command line, it has
to appear in the first line so that the file is listed.
The criterion must be entered with a text editor. You can enter
as mush as you want. The line however must not exceed 255
characters.
Description and use of TPK functions. 16
Terminal PacKet TPK v1.81
As TPK expects either the character & indicating the following
file or the end of the DIRC.TPK file, you can add more
commentary lines unrestrictedly: they will be sent without being
dealt with further.
2.5.3 External commands.
2.5.3.1 General points.
Any line beginning with a / is understood by TPK to contain a
command and if this is not an internal command in the programme
(the above commands) the EXECAUTO.TPK file is read and the command
is sought in this file.
The function is limited to programmes which provide a response
immediately after they have been carried out, without any extra
dialogue. the result of the command is redirected into a file which
is then sent to your correspondent (or shown on the screen). Any
mistakes are also redirected into this file. The FV.COM programme
is a typical example which lists the contents of compressed files.
Eg: you have received "/FV FileName"
The FV command is searched for in the EXECAUTO.TPK file. if it is
found in this file, it is carried out, if not it is ignored.
If the file EXECAUTO.TPK does not exist (in the TPK path) no
external remote command is accepted.
2.5.3.2 Structure of EXECAUTO.TPK
This file is an ASCII text file. You must create it with an editor.
Contents of the file (line by line):
■ Command
■ Exchange of reception buffer on disc (OUI/NON)
■ Maximum number of parameters for the command (up to 18)
■ Then for each parameter:
- A line for the authorised parameters.
- A line for the prohibited parameters.
■ Next command
■ Etc.
Description and use of TPK functions. 17
Terminal PacKet TPK v1.81
The number of commands in the file is not limited.
Example 1:
■ FV Name of the command, FV in that case.
■ NON No exchange on disc (or in EMS/XMS)
■ 2 Two parametres maximum (filename + option)
■ Blank line everything authorised for the filename.
■ Blank line nothing prohibited for the filename.
■ /W /W is authorised (only list filenames)
■ /X /X is prohibited (conversion to SFX)
Example 2:
■ FV The command is still FV.
■ OUI The buffer will be saved before the command
is carried out
■ 2 Still 2 parameters maximum
■ Blank line everything authorised for the filename.
■ Blank line nothing prohibited for the filename.
■ /W/C "/FV FILENAME /C" is valid
"/FV FILENAME /W" is also valid
■ /X/R "/FV FILENAME /X" is prohibited
Example 3:
■ FV
■ NON
■ 3 3 parameters maximum
■ Blank line everything authorised for the filename.
■ TOTO TOTO.ZIP TOTO.EXE
Except for these filenames which are not allowed.
■ /W/C Authorised
■ /X/R Prohibited
Description and use of TPK functions. 18
Terminal PacKet TPK v1.81
■ /W/C Authorised
■ /X/R Prohibited
In this case, "/FV FILENAME /C /W" are recognised as "/FV FILENAME
/W /C", and "/X" "/R" remains unacceptable. Given that FV accepts
generic filenames (* and ?), screening does not work in these
cases.
Indeed, in the above example, "/FV TOT*" will list the contents of
TOTO.ZIP or TOTA.ZIP etc.
The screening principle is as follow: each parameter is compared to
the authorisations of file EXECAUTO.TPK, then to its banned
commands. If authorisations exists they are sought after in the
parameter and if they don't they are eliminated.
The same applies to prohibited parameters.
Authorisations and interdictions are therefore exclusive.Eg, if you
authorise 3 filenames with the FV command, 3 files and only 3 files
will be dealt with.
However, if the system is closed, the directory names will be
deleted from the parameters .
Screening only takes place on the line of parameters passed after
the "/", therefore you are fully enabled (eg in a batch file) to
carry out exact commands, without worrying about access
authorisations and prohibitions.
2.6 FILE TRANSFERS.
2.6.1 General points.
There are two kinds of file transfers: ASCII (text) and BINARY
(datas)
Two completely different protocols apply to these two types,
although the TPK commands which activate them do not differ much !
Two kinds of transfers (ASCII and BINARY), two transfer directions
(outgoing and incoming files, with one single command ie. "/SEND"),
two possible ways of making these transfers (by local and by
remote), here we are already at eight examples. Furthermore, in
binary, there are two processes guaranteeing transfer: by YAPP and
TPK, based on YAPP but with inscreased usage facilities.
The "/SEND" command uses a parameter which specifies the kind of
transfer to be completed.
Description and use of TPK functions. 19
Terminal PacKet TPK v1.81
The syntax is:
■ "/SEND [x:]FILENAME[.EXT] [Y|A|T|E]"
■ x: the disc the disc where the file is located or if it is not
specified the current disc. (combined command "/DISK")
■ FILENAME.EXT : the name of the file which is to be transferred.
And for the parameters:
■ Y : YAPP
■ A : ASCII with the TNC in CONVERS mode
■ T : ASCII with the TNC in TRANS mode
■ E : ASCII without ECHO in the TRAFFIC window
■ TE : ASCII without ECHO and TNC in TRANS mode
In the connected mode the implicit protocol is YAPP.
In the disconnected mode the ONLY available protocol is ASCII.
To maintain clarity, the BINARY and the ASCII transfers will be
dealt with separately. Two summary tables do this effectively.
In any case, your correspondent must be equiped with a strorage
facility (hard disc or floppy disc) unless he is happy enough to
read the text as it passes across the screen !!!
Anyway TPK accepts DOS jokers for file names
Eg: "/SEND FILENAME.*"
This command will send all the files, in sequence, which are named
FILENAME whatever the extension.
Be careful, *.* will send the contents of the disc !
To avoid mistakes in file transmission brought about by certain
packet equipments (TNC in KISS mode !), a control has been added to
each packet enabling error correction.
WARNING to owners of PMS:
With the TNC2 equiped with an eprom containing a mini-BBS also
called PMS or PBBS or even MAILBOX, programme PACLEN to 255, as
file sending will not work properly if the length of the file
exceeds 2 Ko, this is doubtlessly as a result of bad TNC2 buffer
management.
Conversely, for use of TPK on a clear frequency, you can use
"PACLEN" and "MAXFRAME" with maximum parameters if you have an
Description and use of TPK functions. 20
Terminal PacKet TPK v1.81
eprom without PMS or with the PMS not activated. In good
conditions, you can reach 110 cps with a radio link at 1200 bauds.
On the other hand, the transfer possibilities between 2 packet
stations can be reduced on access to a given directory. (Details
par "2.5.1 Internal commands." on page 14)
2.6.2 Transfer of text (ASCII).
2.6.2.1 You send an ASCII file to your correspondent.
■ Connect with correspondent.
■ Pass into command mode of TPK by hitting <F7> (because we are in
the connected mode).
■ Type "/SEND FILEMNAME.EXT A" (don't forget the A for ASCII !)
■ The transfer process starts.
■ If necessary, send an "/EX" or a <CTRL-Z> to close the file.
If your correspondent has TPK, he must begin the capture process in
a file by using <ALT-S> which is not a very elegant solution ! The
best thing to do in a case like this is to transfer this ASCII file
as a BINARY file.
(See paragraphs "2.6.3 BINARY transfer (Datas)." on page 23 and
"2.6.5.3 File(s) transmission menus <ALT-E>" on page 27)
If it is a BBS, this process enables despatch of text from a
message.When the BBS requests you to enter the text of your
message, passing the command "/SEND " is enough to trigger on
transmission of the text.
Of course you can include the following at the beginning of the
file:
■ S G1DIL@GB7BBS The BBS command SEND
■ This and that ! The title of the message
■ Then your text.
■ And at the end /EX Which will close the message
this is what you must do, rather than paintstakingly connecting up
and typing your text, engaging the BBS and the network uselessly.
Description and use of TPK functions. 21
Terminal PacKet TPK v1.81
2.6.2.2 You ask for an ASCII file.
If your correspondent is equiped with TPK, no problem: you use the
remote command, even in your correspondent abscence ("/SEND"
command in remote mode):
"/SEND [x:]FILENAME.EXT"
The ASCII file will be transmitted as a BINARY file with the YAPP
protocol and reception will begin automatically.
If you use the command:
"/SEND [x:]FILENAME.EXT A"
You must open the capture file of TPK by pressing the <ALT-S> key.
If it is a BBS, you use the BBS commands and you recover the text
on your disc thanks to the TPK CAPTURE function. (See par. "2.4
CAPTURE mode." on page 14)
2.6.2.3 Correspondent send you an ASCII file.
If your correspondent has TPK you don't have anything to do,
evrything is automatic, you don't have to be there: it is adequate
that your station is on.
Your correspondent types the following commands:
<F7> to put TPK into command mode (display of "TPK>")
"/SEND [x:]FILENAME.EXT"
If your correspondent does not have TPK and sends you an ASCII file
you must use the TPK capture function.
(See "2.4 CAPTURE mode." on page 14)
2.6.2.4 Correspondent asks for an ASCII file.
If he is TPK equiped, or if he has no TPK but knows TPK commands,
you have nothing to do, everything is automatic, you can be absent:
as long as your station is on.
You correspondent sends the command:
"/SEND [x:]FILENAME.EXT A" (don't forget the A for ASCII)
Description and use of TPK functions. 22
Terminal PacKet TPK v1.81
2.6.2.5 Summary of ASCII transfers.
┌─────────────────────────────────────────────────────────────────────┐
│ │
│ ASCII TRANSFERS │
│ │
├─────────────────────────────────┬───────────────────────────────────┤
│ │ │
│ You start the process │ Your correspondent start the │
│ │ process │
│ │ │
├────────────────┬────────────────┼─────────────────┬─────────────────┤
│ You want to │ You want to │ He wants to │ He wants to │
│ send a file │ receive a │ send you a │ receive one of │
│ to your │ file from your │ file │ your files │
│ correspondent │ correpondent │ │ │
│ │ │ │ │
├────────┬───────┼────────┬───────┼────────┬────────┼────────┬────────┤
│ He has │He has │ He has │He has │ He has │ He has │ He has │ He has │
│TPK and │ YAPP │TPK and │ YAPP │TPK and │ YAPP │TPK and │YAPP and│
│ enters │ and │ has │ and │ enter │ and │ enter │ enter │
│<ALT-S> │ enter │nothing │ enter │<F7> │ enter │/SEND..A│/SEND..A│
│ │ <F4> │ to do │ <F5> │/SEND..A│ <F5> │<ALT-S> │<F4> │
├────────┴───────┼────────┼───────┼────────┴────────┼────────┴────────┤
│Enter │ Enter │ Enter │ Enter <ALT-S> │ │
│<F7> │ │ │ to open the │ You have nothing│
│/SEND FILE.EXT A│/SEND..A│<ALT-S>│ capture │ to do │
│ │<ALT-S> │ │ │ │
└────────────────┴────────┴───────┴─────────────────┴─────────────────┘
Note: If your correspondent is equiped with binary YAPP protocol,
use it: it's much more effective and far simpler !
2.6.3 BINARY transfer (Datas).
2.6.3.1 You send a BINARY file to your correspondent.
■ Connect up to the correspondent
■ Move into command mode by hitting <F7> (because you are in the
connected mode)
■ Type "/SEND [x:]FILENAME.EXT [Y]" (Y for YAPP is understood)
■ The transfer process begins and progresses automatically.
■ If your correspondent is equipped with TPK, you have nothing to
do: reception will also take place automatically on his
terminal. If he uses YAPP, he must press the BINARY file
reception key (<F8>) and give the filename. Then the transfer
proceed normally.
Description and use of TPK functions. 23
Terminal PacKet TPK v1.81
To send a BINARY file to a BBS, use the BBS command:
"YU FILENAME[.EXT]"
2.6.3.2 You want to receive a BINARY file.
If your correspondent is equipped with TPK, no problem: you use the
remote command, even in your correpondent's abscence (use command
"/SEND" in the remote mode):
"/SEND [x:]FILENAME.EXT [Y]" (Y for YAPP is understood)
If he is equipped with YAPP, you cannot receive any file without
your correspondent's intervention.
If it is a BBS, use BBS command:
"YD FILENAME[.EXT]
2.6.3.3 Correspondent sends you a binary file.
If your correspodent has TPK, do nothing. It will all happen
automatically, you don't need to be there: just make sure your
station is on !
Your correspondent types the commands:
<F7> to put TPK in command mode (display "TPK>")
"/SEND [x:]FILENAME[.EXT] [Y]" (Y for YAPP is understood)
If your correspodent uses YAPP, he will direct the operations. He
must type the send key for BINARY files and give the filename. At
your end, with TPK, the transfer will start on its own.
2.6.3.4 Correspodent asks for a BINARY file.
If your correspondent is TPK equipped, or if he does not have TPK
but knows the commands, you don't do anything, everything works
automatically, just make sure your station is on !
Your correspondent sends the command:
"/SEND [x:]FILENAME[.EXT] [Y]" (Y for YAPP is understood)
If your correspondent uses YAPP, he proceeds as above, then he can
receive a file by pressing key <F8> and giving the filename. At
your end, with TPK, the transfer starts by itself.
Description and use of TPK functions. 24
Terminal PacKet TPK v1.81
2.6.3.5 Summary of BINARY transfers.
┌─────────────────────────────────────────────────────────────────────┐
│ │
│ BINARY TRANSFERS │
│ │
├─────────────────────────────────┬───────────────────────────────────┤
│ │ │
│ YOU START THE PROCESS │ YOUR CORRESPONDENT START THE │
│ │ PROCESS │
│ │ │
├────────────────┬────────────────┼─────────────────┬─────────────────┤
│ │ │ │ │
│ You want to │ You want to │ He wants to │ He wants to │
│ send a file │ receive a │ send you a │ receive one of │
│ to your │ file from your │ file │ your files │
│ correspondent │ correpondent │ │ │
│ │ │ │ │
├────────┬───────┼────────┬───────┼────────┬────────┼────────┬────────┤
│ │ He has│ │ He has│ He has │ He has │ │ He has │
│ He has │ YAPP │ He has │ YAPP │ TPK and│ YAPP │ He has │ YAPP │
│TPK and │ and │TPK and │ and │ enter │ and │ TPK and│ and │
│nothing │ enter │nothing │ enter │ <F7> │ enter │ enter │ enter │
│ to do │ <F8> │ to do │ <F7> │ /SEND │ <F7> │ /SEND │ /SEND │
│ │ │ │ │ │ │ │ <F8> │
├────────┴───────┼────────┴───────┼────────┴────────┴────────┴────────┤
│ │ │ │
│ Enter │ Enter │ │
│ <F7> │ /SEND FILE.EXT │ There is nothing for you to do │
│ /SEND FILE.EXT │ │ │
│ │ │ │
└────────────────┴────────────────┴───────────────────────────────────┘
2.6.4 Recovery of an abandonned transfer.
It is possible to recovery a file transfer which has been
interrupted. Your correspondent must, first of all, be equipped
with TPK version 1.44 or the following ones. You must validate the
recovery by using the command "REPrise". When it is validated, TPK
will find a file on its disc, with the same filename as the one
sent to him, and of a smaller size. this can be regarded as that
file whose transfer has been abandonned. It will recover the
transfer at the exact spot where it was interrupted.
Note: The implicit mode of recovery is ON. (REPrise ON)
Note: The recovery is now used in many packet programmes as the BBS
F6FBB.
Note: So as not to overload the exchanges with information between
the two correspondents, there is no confirmation that any
information has already been received: this facility is therefore
to be handled wisely, but is nevertheless invaluable when a
Description and use of TPK functions. 25
Terminal PacKet TPK v1.81
transfer is interrupted whilst an important part of the file has
already been transmitted.
Note: Appendix A at the end of the document explains in detail the
principle of this recovery.
(See "7.0 Appendix : Extensions to the Yapp protocol" on page 95)
2.6.5 Menus for transferring files.
2.6.5.1 Aim.
To make the task easier for you ! But don't be deceived, the
preceding paragraphs will not be useless. If "it does not work",
consult paragraph "2.6 File transfers." on page 19 again and those
below it.
The menus will help you to choose the protocol to use and the file
to transfer.
2.6.5.2 File(s) reception menus <ALT-R>
The <ALT-R> key makes a window appear in which TPK asks you the
filename you want. When you have given the filename a menu appears
on the screen, giving a choice of file transfer mode according to
the file origin (TPK or BBS).
In the connected mode, if you type <CR> without having given the
filename, TPK will send a "/DIR" command to your correspondent,
putting the result into memory (ie. contents of the remote
directory) and will offer this list of files in a menu. Then you
can choose one or several files that you wish to receive.
Note: Be careful, this can ONLY work if your correspondent has TPK
and has not turned the "/DIR" command into "/DIRC".
(See command "MODEDIR" paragraph "4.1 Local commands." on page 59)
When you have made your choice , TPK will send the command which
corresponds to it towards the remote station.
These menus remain active in the disconnected mode but of course
they have no meaning in this mode ! (commands are interpreted by
TPK)
Two things can happen:
■ You have given a filename after <ALT-R>
TPK asks you for the origin of the file:
Description and use of TPK functions. 26
Terminal PacKet TPK v1.81
- TPK : the command will be "/SEND"
- BBS F6FBB : the command can either be "YD" or "YGET" for the
BINARY files, according to the level where you are located,
and "D" or "GET" for the ASCII files.
In the case of "D" and "GET", TPK open the file at CAPTURE
(as does <ALT-S>). The file is closed by receipt of a
<CTRL-Z> or manually with the <ALT-S> key.
- Other : in this case there is no generated command, the file
is simply opened in CAPTURE. This option is identical to the
opening of the CAPTURE using <ALT-S>.
■ You have not given the filename after <ALT-R>.
When you have chosen the file(s) to be received in your
correpondent's list, TPK immediately sends the command "/SEND"
for the first file chosen (this option can ONLY be used between
two TPK version 1.65 or higher).
2.6.5.3 File(s) transmission menus <ALT-E>
The <ALT-E> key makes a window appear in which TPK asks you the
filename of the file that you want to send. If the number of files
corresponding to the name you have given is greater than 1, TPK
displays the list in a menu allowing you to choose one or several
of them.
When you have made your chose two things can occur:
1.One file chosen:
You have only chosen one file or you have given a single
filename.
You can transfer it in several ways according to whether it is an
ASCII or BINARY file, and according to your correspondent's
method.
A menu offers you these various solutions:
■ Yapp/YappC : between two TPK 1.65 or higher, the protocol used
will be YappC which is an extension of Yapp (with a checksum).
If the destination software is Yapp then TPK will use the
normal Yapp, detection is done with the Yapp header.
■ ASCII : various options, see command "/SEND" paragraph "2.5.1
Internal commands." on page 14
If you have chosen Yapp or YappC it is a question of BINARY file
transfers, and TPK has to know the destination method to send, if
necessary, the right command before sending the file. That is
Description and use of TPK functions. 27
Terminal PacKet TPK v1.81
what the following menu offers you.
■ TPK (/SEND)
No need for extra information. The transfer can begin. The
protocol used will be YappC.
■ BBS FBB (YU)
■ BBS FBB (YPUT)
In both cases, the BBS needs the filename for the command.
This name can be different from the original name and TPK
opens a window asking you this. You must also give a
description of the file and TPK open another window for this.
An indicator on the ladder gives you the maximum number of
characters accepted by the BBS F6FBB or by the TPK "COMmente"
function.
2.ASCII : options in the ASCII mode correspond to the options of
the "/SEND" command in this mode. As is the case for BINARY
transfers, TPK needs to know the command being sent in order to
put the destination software into reception. The three possible
choices are "Send without command", in that case the text is sent
immediately and the two BBS F6FBB commands, ie. "U" and "PUT".
If your correspondent uses TPK, it is much simpler to guarantee
the transfer with the Yapp protocol.
3.Several files chosen:
If you have chosen several files, the ONLY protocol you can use
is YappC, therefore the protocol menu is not shown and TPK passes
immediately into BINARY file transmission.
Note: This possibility can ONLY therefore be used between two
TPKs.
2.6.5.4 Menu of file(s) choice in a list.
This menu will be used in TPK each time selection of one or more
files is necessary.
To select a file in the list:
■ With the keyboard:
You can move the selection bar onto the desired file with the up
and down arrows, then validate with <CR> or with the <S> key
which corresponds to the <Select> button.
When you have made your choice, validate it by key <O>
corresponding to the <Ok> button.
Description and use of TPK functions. 28
Terminal PacKet TPK v1.81
To cancel, press the <ESC> key or <A> which corresponds to the
<Cancel> button.
<HOME> takes the selection bar to the top of the menu.
<END> takes the selection bar to the bottom of the menu.
<PGDN> goes down on page in the list (one window height).
<PGUP> goes back one page in the list (one window height).
■ With the mouse:
Position the cursor with your mouse on the file you are choosing
and validate it by pressing the left button of the mouse. When
you have made your choice, validate it by positioning cursor on
the <Ok> button and by pressing the left button.
To cancel a selection press the right button of the mouse or
position the cursor on the <cancel> button and validate with the
left button.
The up and down arrows on the right side of the menu window act
in the same way as the corresponding keys on the keyboard.
Position the cusror upwards and validate with the left button.
2.7 PROGRAMMING FUNCTION.
2.7.1 General points.
TPK offers several methods allowing the creation of new commands.
The ability to create its own personal commands means TPK can adapt
to its own need, and furthermore, it's a great fun !
These commands can be called by using a combination of one of the
three special keys <ALT>, <CTRL> and <SHIFT> plus any of the ten
function keys <F1> to <F10>. You therefore have at your disposal
some 30 programmable commands.
Furtheremore, you can mix these commands with TPK or TNC commands:
these commands, made up of several commands are called
"macro-commands". The name of each macro-command will be chosen by
you.
Programmable commands and macro-commands can be integrated into one
text file (you get to baptize it !), thus enabling the creation of
quite complex programmes: these are programme-files.
Even possible combination must conform to a syntax which will be
explained in the following paragraphs.
Description and use of TPK functions. 29
Terminal PacKet TPK v1.81
2.7.2 Programming of function keys.
The <ALT-F1> to <ALT-F10>, <CTRL-F1> to <CTRL-F10> and <SHIFT-F1>
to <SHIFT-F10> keys are programmed by the "Touche" command
(Touche=Key) with the following syntax:
■ "Touche An Text_of_the_key" (A for ALT, n for key number)
■ "Touche Cn Text_of_the_key" (C ofr CTRL, n for key number)
■ "Touche Sn Text_of_the_key" (S for SHIFT, n for key number)
For example, to programme the <SHIFT-F1> key in order to connect
the F6ABJ-1 BBS, you write:
■ "T S1 ^6c f6abj-1^M" followed by <CR>
As this example shows, the "Text_of_the_key" can contain special
characters which enable simulation of control keys. The
carriage-return on your keyboard is nothing more than a key
containing <CTRL> and <M> (capital M, lower case m correspond to
another code !). Type <CTRL> and <M> on your keyboard and the
result will be a carraige-return. the control key corresponds to
the character "^" in the above example, the "M" corresponds to <CR>
which you must send after the BBS code, whilst the following <CR>
is manual; it validates and records the programmation.
The "^6" preceding the TNC connection command, simulates pressing
the <F6> key, which, on TPK, forces passage of the TNC into command
mode by sending a "break" on the serial link.
Now try: type <SHIFT> and <F1>, TPK must call up F6ABJ-1.
These explanations will have to suffice in the comprehension of
this example of <SHIFT-F1> programming.
Secial characters such as "^" are not always available from the
keyboard. Having the complete ASCII table at your disposal, it is
still possible to get these characters on the screen in the
following way:
Find the ASCII code expressed in DECIMAL (94 for "^"). Keep the
<ALT> key prssed while typing "94" on the number block. Release the
<ALT> key: the character "^" is displayed on the screen.
This is a general method and can be used outside of TPK as in TPK
to write any character, specific or otherwise.
In the case of function key programming, macro-commands or
programme files, TPK has a special writing which is used to
simulate a specific character via the "@" character.
The syntax is: @nnn@
Description and use of TPK functions. 30
Terminal PacKet TPK v1.81
Where "nnn" is the ASCII decimal code.
Eg, @27@ simulate the <ESC> key.
You can also simulate function key or key codes with two characters
by the special syntax: @0@nnn@
Eg: "@0@75@ will equal the left arrow or "@0@59@" will equal the
<F1> key.
Note: This is ONLY to be used in programming ! TPK ONLY interprets
them in this case.
The programmable keys not only need the "^" in order to simulate
the <CTRL> key, but also the character "@" (code ASCII 64) to
simulate the <ALT> key:
Eg: "@C" will simulate the <ALT-C> key which erase the screen.
It is therefore possible to enter several commands on the same key
thanks to the "^M" which, working like the <CR>, can line up the
commands in single file.
Eg: programming the <CTRL-F3> key as follow:
■ "T C3 sh copy a:*.* c:\tmp^M/dir c:\tmp\*.*^M"
Is equivalent to:
■ "sh copy a:*.* c:\tmp<CR>"
■ "/dir c:\tmp\*.*<CR>"
Typed on the keyboard.
The contents of a key must not exceed 255 characters (same rule for
the macro-commands described below).
The "Touche" command allow management of programmable keys:
■ When the "Text_of_the_key" is absent, TPK lists the contents of
the key.
■ If the n (key number) is also absent, TPK lists the contents of
all the keys in the category.
Examples:
■ "T S1" lists contents of <SHIFT-F1>
■ "T S" lists contents of <SHIFT-F1> to <SHIFT-F10> keys
■ <ALT-T> lists contents of all the function keys
Description and use of TPK functions. 31
Terminal PacKet TPK v1.81
The contents of the keys are saved in the TPK.KEY file at each
key's modification.
Some additional examples could prove useful:
■ "T S1 /DIR C:\TPK\*.*^M"
Affects the DIR command to the <SHIFT-F1> key and lists the
files in the TPK directory.
■ "T S2 ^7/SEND"
In the connected mode, preparation of a "/SEND" command: the
"^7" equivalent to key <F7> put TPK in the waiting for a command
mode (displaying "TPK>") and after hitting <SHIFT-F2>, you only
have to enter the filename.
■ "T S3 ^6MH^MK^M"
<SHIFT-F3> will put the TNC back in the command mode if it is
not there already , it will list the MHEARD and put the TNC in
the CONVERS mode (to be used in the connected mode).
■ "T S4 ^6@CMH^M"
Same thing but after the screen has been erased (by <ALT-C>.
2.7.3 Macro-commands.
A macro-command is a series of commands which can be triggered on
by a key word.
Note: The key word is CASE sensitve, so "bbs" is different from
"BBS".
Macro-commands are not limited in number.
Macro-commands are programmed in exactly the same way as function
keys (see paragraph "2.7 Programming function." on page 29). The
only difference is that carrying them out is not triggered on by
function keys but by a word key that you have chosen.
A macro-command can be a sequence of TPK or/and TNC commands.
2.7.3.1 Creating a macro-command.
The TPK command enabling creation of a macro-command and memorising
it on disc is "MEMorise":
■ "MEMorise Key Text" validated by a <CR>
Description and use of TPK functions. 32
Terminal PacKet TPK v1.81
With "Key" the name you have chosen and "Text" the programming
text.
Eg: "MEM bbs c f6abj-1^M" memorises the "bbs" macro-command which
requests a connection to F6ABJ-1.
2.7.3.2 Carrying out a macro-command.
Two ways:
■ The TPK "Macro" command followed by the key word.
Eg: "M bbs" carries out the "bbs" macro-command.
■ The <ESC> key followed by the key word.
Eg: "<ESC>bbs"
2.7.3.3 Managing macro-commands.
It is realised by two TPK commands:
■ "EMacro Key" edits the macro-command "Key". The content of the
macro-command is crossed back into the keyboard buffer, which
allow edition and modifications (see paragraph "2.10.2 Keyboard
management." on page 51).
Eg: "EM bbs" edits the macro-command "bbs"
The <ALT-M> key displays the macro-commands list.
Note: You can stockpile macro-command calls, function keys and
programmes up to a maximum level of 20.
2.7.4 Programme files.
TPK commands and macro-commands (paragraph "2.7.3 Macro-commands."
on page 32) can be reassembled in text files which then becomes
programme-files.
The programme-files must be placed in the TPK directory.
2.7.4.1 Creation of a programme-file.
Each line of a programme-file can contain one or several commands
according to the same principle as macro-commands.
A line which begins with a sharp (#) is considered as commentary
and is ignored by TPK.
Description and use of TPK functions. 33
Terminal PacKet TPK v1.81
The "ECHOTPK Text" command enables inclusion of commentaries in the
programme-files. When you are executing the file, "Text" will be
displayed in the traffic window.
2.7.4.2 Carrying out a programme-file.
The "EXecute" command launches the interpretation of commands
placed in the file whose name is passed into the parameter.
To interrupt a programme-file in progress, type the <ESC> key.
2.7.4.3 Example of a programme-file.
The command "EX lbbs" starts execution of the programme-file LBBS
whose listing is given below for analysis:
c fe6cnb-1
att 180 cnx
^7att 180 >
@S^H^H^H^H1
rm
^7att 600 >
b
Some explanation will not go amiss:
■ Line 1 : "c fe6cnb-1"
Connection onto the BBS. The request is sent to the TNC by TPK.
■ Line 2 : "att 180 cnx"
Wait 180 seconds for connection. If at the end of this time,
connection has not been established, the programme is
abandonned. (See command "ATTente" paragraph "2.7.5 Other
commands useful in programming." on page 35)
■ Line 3 : "^7att 180 >"
Wait for the BBS prompt ">" during 180 seconds. If the prompt
arrives eg. within 15 seconds, the following command is dealt
with without further delay, but if the prompt doesn't arrive in
180 seconds, the programme is interrupted.
You must not forget the "^7" which simulates the <F7> key for
passing into the command mode of TPK when you are connected, if
not, the command will be sent to the BBS !
The awaited text is everything located after the space to the
right of the duration (180) and the end of line <CR>.
■ Line 4 : "@S^H^H^H^H1"
Description and use of TPK functions. 34
Terminal PacKet TPK v1.81
<ALT-S> followed by 4 <CTRL-H> and an 1. Brought into service of
the CAPTURE on disc (See paragraph "2.4 CAPTURE mode." on page
14). The 4 <CTRL-H> erase the ".TPK" extension of the CAPTURE
filename TEMP.TPK. Therefore TEMP remains to which you can add a
1 to give new name TEMP1
■ Line 5 : "rm"
"rm" is sent to the BBS for reading personal messages. If there
are messages, they will be saved in TEMP1
■ Line 6 : "^7att 600 >"
Wait for the BBS prompt for 600 seconds. don't forget the "^7",
it's easy to forget !
■ Line 7 : "b"
The disconnection command "b" (for bye) is sent to the BBS.
CAPTURE will be automatically closed in disconnection. Of
course, it is possible to do it with an <ALT-S>: to put an "@S"
in the file is enough.
2.7.5 Other commands useful in programming.
TPK has at its disposal 3 predefined variables which are ONLY
usable in the programming of function keys, macro-commands and
programme-files.
2.7.5.1 Capture of the date and time.
■ "%DATE%" or "%DATE <format>%
Makes it possible to incorporate the present date in the key or
the macro-command.
Usable formats for the date:
- dd or d for the day with or without leading zeros.
- mm or m for the month with or without leading zeros.
- yy or yyyy for the year with 2 or 4 characters.
■ "%TIME%" or "%TIME <format>%"
Makes it possible to incorporate the time.
Usable formats for the time:
- hh or h for the hours with or without leading zeros.
Description and use of TPK functions. 35
Terminal PacKet TPK v1.81
- mm or m for the minutes with or without leading zeros.
- ss or s for the seconds with or without leading zeros.
- To display time with the 12H00 AM/PM format add AM/PM or
am/pm or A/P or a/p in the format string.
- To display UT time add a Z in the time format string and in
the date format string.
TPK uses the environment string TZ to set difference between
local and universal time.
Examples:
- %DATE d/mm/yy% = 1/12/92
- %DATE dd/mm/yyyy% = 01/12/92
- %DATE mm-dd-yy% = 12-01-92
- %TIME h:mm:ss% = 9:12:34
- %TIME hh:mm% = 09:12
- %TIME h:mm AM/PM% = 9:12 AM
- %DATE d-mm-yyy h:mm% = 1-12-92 9:12
Note: DATE and TIME can be mixed but be careful no other
texts in the middle of the format string.
- %TIME h:mmz% = 8:12 for TZ=FRA-1
- Creation of a macro-command for sinding DAYTIME to the TNC
with universal time.
DAYTIME %DATE yymmddhhmmssz%^M
You must enter this macro-command with the "MEMorise" command
(see paragraph "4.1 Local commands." on page 59)
2.7.5.2 Variable PATH.
TPK directory can be found with variable PATH. It can be used to
build a path from the TPK directory.
Eg: "T S5 @W^Y%PATH%capture.tpk^M"
Will write the TPK buffer into the TPK directory instead of the
BUFFER directory, with the name "CAPTURE.TPK"
Description and use of TPK functions. 36
Terminal PacKet TPK v1.81
2.7.5.3 Programming a waiting period.
Command "ATTente" (See also paragraph "4.1 Local commands." on page
59) whose syntax is:
■ "ATTente Duration [Event]"
With:
- "Duration" : a waiting time expressed in seconds.
- "Event" : several types of event are possible.
-- CNX : waiting for the connection.
-- DCNX : waiting for the disconnection.
-- Text : waiting for the receipt of the string Text at the
END of a line.
-- "Text" : waiting for the receipt of the string Text
ANYWHERE in a line.
Note: You cannot wait for a text in the disconnected mode.
-- PASSWORD : waiting for a password question.
(See paragraph "2.7.5.4 Password management." on page 38)
Examples:
■ "ATT 180 cnx"
Waits for a connection for 180 seconds. If the connection does
not take place before this time has elapsed, it is abandoned.
■ "ATT 60 >"
Waits for a BBS FBB prompt for 60 seconds. This text has to be
terminated by a <CR>.
■ "ATT 10"
Simply waits for for 10 seconds (pause).
Note: TPK functionning is not interrupted during this waiting
period.
Remember : a programme in progress can be cancelled at any time
by typing <ESC>.
Description and use of TPK functions. 37
Terminal PacKet TPK v1.81
2.7.5.4 Password management.
TPK can automatically send a reply to a password question from a
BBS or any other system.
The "ATTente" command is used with the following syntax:
■ ATTente <Duration> PASSWORD <Text_To_wait> <WordKey>
Where:
- Text_To_Wait : the text sent with the password numbers list.
- WordKey : a word key to find the password string in a TPK
file called PASSWD.TPK and which must be located in the TPK
directory.
When TPK receives the Text_To_Wait it looks for the word key in
PASSWD.TPK and if found, read the following line containing the
password string. Then with the numbers sent with the password
question takes the corresponding letters in the password string and
send them as reply.
Format of the PASSWD.TPK file:
■ One line for the word key.
■ One line for the password string.
You can put as many passwords as you want in this file. Just put
the two necessary lines for each password.
Example of PASSWD.TPK file:
Line 1 : EBNPASSWD
Line 2 : THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG
Example of command "ATTente" in this case:
■ "ATT 180 PASSWORD Password? EBNPASSWD"
TPK receives for example:
Password? 11 5 7 15 23
Its reply will be:
BQINM<CR>
This function can be used for the C_FILTER of VE2BLY or the SYS
command for F6FBB BBS for example.
Description and use of TPK functions. 38
Terminal PacKet TPK v1.81
2.7.5.5 Programming an event.
Command "At Time [Command]" (Do not confuse with "ATTente" !).
(See also paragraph "4.1 Local commands." on page 59).
Parameters:
■ Time : the time of command launch. The time parameter can be the
%TIME% variable and you can make an addition to it.
Eg: "a %TIME%+15 command"
■ Command : can be a macro-command or ANY TPK function. The
execution of this is ONLY valid in the disconnected mode,
otherwise commands are stockpiled and will be carried out after
disconnection.
Programming is carried out at the said time THEN IS ERASED. Waiting
time before the programme is carried out cannot exceed 24 hours.
You can programme a maximum of 10 different programmes which will
be erased in the space of 24 hours unless you programme more as
soon as the first ones are carried out.
Some examples:
■ "A 1000 <ESC>bbs"
Memorises a programme at 10 o'clock. When the TPK clock gets to
10 o'clock the "bbs" macro-command will be carried out.
■ "A 100 EX bbs1"
Programmes execution of "bbs1" at 1 o'clock.
■ "A 2355 EX bbs1"
Programmes execution of "bbs1" at 23H55.
2.7.5.6 Creation of a cycle.
Example: the macro-command BEACON.
"K^MBEACON TPK^M^6a %TIME%+15 macro BEACON^M
The first command launch (by typing "MACRO BEACON" or
"<ESC>BEACON") will write the "BEACON TPK" text then reprogramme
itself at the present time plus 15 minutes, creating thus a
continuous cycle.
Note: This ONLY works in macro-commands or function keys, because
the %TIME% variable is only known in these modes.
Description and use of TPK functions. 39
Terminal PacKet TPK v1.81
2.7.5.7 Management of events.
■ "A" without parameters lists the programmed events.
■ "A 1000" lists the events programmed at 10 o'clock.
■ EFAt 1000" erases the 10 o'clock event if it exists.
2.8 THE BROADCAST FUNCTION.
2.8.1 Installation of the BROADCAST manager.
Three commands are necessary for the correct operation of BROADCAST
mode.
Examples:
■ MYCALL FD1CDC
Advises both TPK and your TNC of your own callsign. Your
callsign MUST be initialized before using the BRoadcast
commands.
■ BR F6FBB-1 U F6FBB-1
Advises TPK the path used for the UNPROTO reply to F6FBB-1 (your
local BBS)
■ BR F6FBB-1 C F6FBB-1
Advises TPK the path used for connections to the local FBB BBS,
F6FBB-1
The following command enables automatic reception of your personal
mail:
■ BR RXMSG PRIV
Advises TPK to search for your personal mail.
All of these commands must be included in the file CONFIG.TPK
Note: You MUST call your local SysOp BEFORE validating these
functions as he must authorize you to use the BROADCAST option
prior to use. If you don't do this, TPK will send a beacon every
time it receives a message header frame from the BBS. This beacon
will be ignored by the BBS
When you have run TPKINST a directory will be created into which
will be placed two files after receiving the first BROADCAST from
your local BBS (that is provided this has been validated using the
Description and use of TPK functions. 40
Terminal PacKet TPK v1.81
above commands). The names of these files will be the CALLSIGN of
the BBS and the extensions will be .NUM and .LST
Examples: FC1EBN-1 uses the files FC1EBN-1.NUM and FC1EBN-1.LST
FC1EBN-12 uses the files FC1EBN12.NUM and FC1EBN12.LST
F6FBB-1 uses the files F6FBB-1.NUM and F6FBB-1.LST
F6FBB uses the files F6FBB.NUM and F6FBB.LST
These files <BBS>.NUM and <BBS>.LST contain very important
information so be sure that you DO NOT DELETE OR MODIFY them !
2.8.2 List of the BROADCAST function commands
All of these commands can be configured as macro-commands or
function keys.
For each command, you will find:
■ The syntax of the command.
■ A description of the command.
■ An example.
Command list:
■ BRoadcast <BBS> Connection <PATH>
Establish the packet path for automatic connection to <BBS>
Ex: BR F6FBB-1 C F6FBB-1 V FD1CDC-5
■ BRoadcast <BBS> Unproto <PATH>|AUTO
Specify the return path for the reply to the BROADCASTs of
<BBS>. This is the UNPROTO mode of the TNC. This is the command
which validates the BROADCAST receipt from this BBS.
Ex: BRoadcast F6FBB-1 U F6FBB-1 V FD1CDC-5
■ BRoadcast RXMSG Acceptpriv
Allows private messages to be included in the lists. You can't
read these messages if you are not a SysOp at the BBS. This
command is for co-sysops !
Ex: BRoadcast RXMSG Acceptpriv
■ BRoadcast <BBS> List
Use this command to directly access the message list of a BBS.
You can also use <ALT-L> which will open a menu with the BBS
list. The first character on each line is the message status
for TPK:
Description and use of TPK functions. 41
Terminal PacKet TPK v1.81
R : Message received
P : Private message received (in MSG_PRIV)
Y : Message read
* : Message ready to forward (in MSG_PRIV)
F : Message forwarded (in MSG_PRIV)
K : Message killed
+ : Message 7Plus (the 7plus files which have been extracted and/or
decoded are stored in the CAPTURE directory)
You MUST send the "BR RXMSG PRIV" command to TPK to request
automatic collection of your Personal mail.
In the BBS lists, if the message status is blank then the
message has not been received: if you select it with <ENTER> or
click-on with the mouse it will be marked to for collection.
When all selections are complete, confirm your request with <D>
(Delayed Reception) or with <I> (Immediate Reception) or by
clicking-on <RxDel> or <RxImm> with the mouse.
Incoming messages are received into sub-directories: the name of
the directory is the callsign of the BBS, the same as for the
.NUM and .LST files.
A typical directory tree for a user close to F6FBB-1 would look
like:-
C:\──TPK──┬──UPLOAD
│
├──PRIV_UP
│
├──DOWNLOAD
│
├──HELP
│
├──CAPTURE
│
├──BUFFER
│
├──DOC
│
└──LISTS───┬──F6FBB-1 Directory of the F6FBB-1 messages
│
└──MSG_PRIV Directory of your private mail
The directories F6FBB-1 and MSG_PRIV are created automatically
by TPK. The message names are the actual number of the
messages. For instance if you have a file with the name 123456,
then this will be message number 123456 at your local BBS.
To list messages from F6FBB-1 use: BR F6FBB-1 L
To list your own private mail use: BR MSG_PRIV L
■ BRoadcast <BBS> SYnchro
Description and use of TPK functions. 42
Terminal PacKet TPK v1.81
Send a beacon to <BBS> which contains the number of the last
message header TPK received. The beacon path is the one
configured in the BR <BBS> U <PATH> command. These messages are
sent every time TPK receives a header where the number is not
the one expected. If the TNC can't send the packets (on a busy
channel for instance) then it will respond with "too many
packets outstanding". That is not a problem, as the beacon will
be sent as and when the channel is clear.
Ex: BR F6FBB-1 SY
■ BRoadcast <BBS> Delete|Supprime
Delete the BBS <BBS> from the list. TPK will ignore any
BROADCASTs and will not FORWARD with this BBS.
Ex: BR F6FBB-1 DEL
■ BRoadcast <BBS> Erase|Efface nnn
Delete any old messages from the listing. nnn is the amount of
messages to keep in the list. Messages with status Y (read but
not killed) remain in the list. You MUST kill them before
erasing. You can't erase part of the list if some messages have
been selected but have not yet been received.
Ex: BR F6FBB-1 E 1500
To keep a total of 1500 messages in the list.
■ BRoadcast <BBS> Erase|Efface K
Delete all killed messages from the list.
Ex: BR F6FBB-1 E K
■ BRoadcast <BBS> Erase|Efface P
Delete your private messages from the list. (Don't attempt to
delete the actual files from the MSG_PRIV directory, you must
kill them from the listing of your personal mail !!!)
Ex: BR F6FBB-1 E P
■ BRoadcast <BBS> Erase|Efface Date <DATE>
Delete all messages older than <DATE>
Ex: BR F6FBB-1 E DATE 920714
■ BRoadcast <BBS> Erase|Efface Days|Jours <DD>
Delete all messages older than <DD> days
Description and use of TPK functions. 43
Terminal PacKet TPK v1.81
Ex: BR F6FBB-1 E Days 7
■ BRoadcast <BBS>
Send <BBS> management information from TPK.
Ex: BR F6FBB-1
■ BRoadcast
List the known BBSs. TPK can work with several BBSs. Enter the
command "BR <BBS> U <PATH>" and "BR <BBS> C <PATH>" for each
one.
Ex: BR
Note: Be careful: if you enter several BBSs, you will get your
personal mail from each, and the bulletins will be the same from
all of the BBSs ! Don't forget that you will also upset the
White Pages Database too. So the best choice is to enter ONLY
ONE BBS and all will be OK...
The following commands allow automatic reception of pre-selected
messages.
■ BRoadcast RXMSG PRIV
Requests receipt of your personnal mail from ALL BBSs declared.
You MUST have already entered your callsign to TPK using the
MYCALL command.
Ex: BR RXMSG PRIV
■ BRoadcast RXMSG TO <Destination Call>
Requests receipt of messages addressed TO <Destination Call>
Ex: BR RXMSG TO FBB
■ BRoadcast RXMSG BBS <@BBS>
Request receipt of messages routed to <@BBS>
Ex: BR RXMSG BBS GBR
■ BRoadcast RXMSG FROM <Call>
Request receipt of messages sent by <Call>
Ex: BR RXMSG FROM FC1EBN
■ BRoadcast RXMSG STRING <Text>
Request receipt of messages where TPK can find <Text> in the
subject field. Only ONE text_string can be searched for at any
Description and use of TPK functions. 44
Terminal PacKet TPK v1.81
one time.
Ex: BR RXMSG STRING TPK
■ BRoadcast RXMSG 7PLUS [DECODE]
Every incoming message is scanned for 7PLUS content. If it is a
7+ file, then the 7+ text is extracted and a file is created in
the CAPTURE directory. If you add the DECODE parameter to every
7+ message received TPK will execute the 7+ program and attempt
to decode the file. For correct operation the route to
7PLUS.EXE must be declared in your PATH statement or the file
must actually reside in the CAPTURE directory. You must ensure
that you have sufficient free memory available for 7PLUS to
execute whilst running TPK; a good test to check if this is
possible is to SHELL through to DOS (using the <F3> key) and
then run MEM.EXE from DOS5. It needs to report approx 100Kb of
free memory. (Also see BUFFER command.) Any 7+ reports
generated during execution are redirected to a file called
7PRESU. If you encounter problems then check this file to see
what happened during the last execution.
Ex: BR RXMSG 7PLUS
BR RXMSG 7PLUS DECODE
■ BRoadcast RXMSG BUffer
List those messages which are held in memory but have not yet
been saved to a file because there is a hole in the list.
Ex: BR RXMSG BU
2.8.3 Message transfers between TPK and the BBS.
■ FORward Timer|Intervalle <ttt>
Set the amount of time between each forwarding cycle (Default is
15 mins) in the range of 5 to 55 minutes. Once set then the
automatic exchange of messages will commence after each period
of n minutes.
Ex: FOR T 25
To set period to 25 min
FOR T
Shows the forwarding period and the value of the counter.
■ FORward Execute
Description and use of TPK functions. 45
Terminal PacKet TPK v1.81
Begin execution of reception and transmission of messages
to/from your local BBS.
Ex: FOR E
■ FORward List|Liste RX|TX
Lists those messages waiting to be received (RX) or transmitted
(TX)
Ex: FOR L RX
FOR L TX
2.8.4 Configuration examples of the "BROADCAST" functions.
Reception of the message headers from the local BBS F6ABJ-1
■ MYCALL <Your Call> (Ex: MYCALL FC1EBN)
■ BR F6ABJ-1 U F6ABJ-1
■ BR F6ABJ-1 C F6ABJ-1
If you want to receive your personal mail you must add:
■ BR RXMSG PRIV
Declaration of FF6PTT-1 BBS where you want to send messages using
forwarding, but without receiving message lists (in this case you
must NOT use the BR <BBS> U command)
■ BR FF6PTT-1 C FF6PTT-1 V F6PRA-4
If, for instance F2KL wants to receive a listing from the BBS
F6ABJ-1, receive his personal mail from this BBS, and also
forward his outgoing mail to both F6ABJ-1 and to FF6PTT-1; but
does not want to receive the message listing from FF6PTT-1, then
he would use the following commands (these can be entered into
the set-up file CONFIG.TPK):
■ MYCALL F2KL
■ BR F6ABJ-1 U F6ABJ-1
■ BR F6ABJ-1 C F6ABJ-1
■ BR RXMSG PRIV
■ BR FF6PTT-1 C FF6PTT-1
In this case FC1MVP is using his PMS to receive his mail and so
doesn't want TPK to undertake automatic reception from his local
Description and use of TPK functions. 46
Terminal PacKet TPK v1.81
BBS FC1GHV-1. The only commands used will be:
■ MYCALL FC1MVP
■ BR FC1GHV-1 U FC1GHV-1
■ BR FC1GHV-1 C FC1GHV-1
The command BR FC1GHV-1 C FC1GHV-1 allows him to use TPK for
writing his messages and forwarding them on to FC1GHV-1.
Connection to the BBS via a Thenet:
In fact the connection path is treated by the macro-commands
manager. It is possible to put several commands in this path,
macro-commands or programmes.
Example: connection to F6ABJ-1 via FF6KBS-5
■ BR F6ABJ-1 C FF6KBS-5^MATT 180 CNX^MC F6ABJ-1
Example: connection via several nodes.
■ BR F1AA C F6XYZ^MATT 180 CNX^MC F6ABC^MATT 180 ABC^MC F1AA
Simply add the waiting for the connection prompt for each node.
Connection to a BBS with a password.
First create a macro-command for sending the password:
"MEM PASSWD ATT 180 PASSWORD Password? PASSABJ"
Note: Be careful : the macro-command keyword MUST be in capital
because the BRoadcast command convert the connection path into
uppercase.
The connection path for the BRoadcast command will be:
"BR F6ABJ-1 C F6ABJ-1^MPASSWD"
(See paragraph "2.7.5.4 Password management." on page 38)
Examples of programmed keys for simplified operation of the
BROADCAST commands.
■ <CTRL-F1> Go to my personal mailbox:
T C1 BR MSG_PRIV L^M
■ <CTRL-F2> List the messages from my local BBS:
T C2 BR F6ABJ-1 L^M
■ <CTRL-F3> Send a resynchronization beacon to my local BBS:
Description and use of TPK functions. 47
Terminal PacKet TPK v1.81
T C3 BR F6ABJ-1 SY^M
2.9 THE LOGBOOK FUNCTION.
2.9.1 Contents of the LOGBBOK.
The LOGBOOK generated at every connection contain the following
informations, each field is a string in that order :
■ Current date at the moment of the connection : 8 characters.
Implicit format is dd-mm-yy
Modification of the date format with command "LOG Date"
■ Frequency of the QSO : 6 characters.
Implicit value : 144675
The command "FRE" modify this value.
■ Traffic mode : 4 characters.
Implicit value : PK
Modification with command "LOG Mode"
■ Power used : 4 characters.
Implicit value : 25W
Modification with command "LOG POWER"
■ QSO beginning time : 4 characters.
Implicit format : hhmm
Modification of the format with command "LOG Time"
■ Callsign of the station connected : 8 characters.
■ Report sent : 3 characters.
■ Report received : 3 characters.
Implicit value : 59
Modificaton with command "LOG Rst"
■ QSO end time : 4 characters.
Description and use of TPK functions. 48
Terminal PacKet TPK v1.81
Same format as the beginning time.
■ Commentaries : 40 characters.
2.9.2 Management commands of the LOGBOOK.
The "LOG" command associated to the "FRE" command allow the
management of the LOGBOOK.
Command "FREquence" see paragraph "4.1 Local commands." on page 59
and paragraph "5.2.4 Use of TPK with a KAM." on page 78
■ LOG
Display and edition of the LOGBOOK. The last QSOs are displayed
and you can move into the file, search calls, print it, etc.
See paragraph "5.3.1.9 The LOGBOOK screen." on page 88
■ LOG Date
Modification of the display format of the date in the LOGBOOK.
The format is the same as the %DATE% variable.
See paragraph "2.7.5.1 Capture of the date and time." on page 35
Example : "LOG DATE mm/dd/yy"
■ LOG Mode
Modification of the implicit traffic mode in the LOGBOOK.
Example : "LOG MODE Pack"
■ LOG Power
Modification of the value of the power used.
Example : "LOG POWER 100W"
■ LOG Time
Modification of the display format of the time in the LOGBOOK.
The format is the same as the %TIME% variable.
See paragraph "2.7.5.1 Capture of the date and time." on page 35
Example : "LOG TIME hhmm am/pm"
■ LOG Rst
Modification of the implicit report written in the LOGBOOK. This
value is used for the report sent and the report received.
Description and use of TPK functions. 49
Terminal PacKet TPK v1.81
Example : "LOG RST 55"
■ LOG Prn @xxx@yyy@zzz@
Modification of the printer initialisation string. This string
is sent at every printing of the LOGBOOK request. The printer
must print 124 characters on a line. So you must programme it to
do this.
The values must be given in decimal and separated by the "@"
character.
Example to set an EPSON printer in 15 cpi:
"LOG PRN @27@64@27@103@"
■ LOG ?
Displays the implicit values used for the LOGBOOK.
Example : "LOG ?"
2.10 OTHER FUNCTIONS.
2.10.1 Access to DOS function.
Access to DOS by remaining in TPK is possible.
■ Either by <F3> : it jumps to the DOS screen and to return back
to TPK type "EXIT"
■ Or by the "SHell" command : in this case, a DOS command and its
parameters can be passed.
Eg: "SH dir b:*.*"
Return to TPK occurs after execution of this command.
The receive buffer is offen a big memory consumer: it can be
temporarily saved on disc or in XMS/EMS memory before starting up a
programme which has no probleme using the now free memory.
(See command "BUFFER" paragraph "4.1 Local commands." on page 59)
Note: The "SHell" command without parameter is equal to the <F3>
key.
Description and use of TPK functions. 50
Terminal PacKet TPK v1.81
2.10.2 Keyboard management.
The keyboard management principle is very simple: TPK analyses what
has been entered after the <CR> validation. If it recognises a
command, it will carry out it, otherwise everything is sent to the
TNC.Certain commands are interpreted by TPK before being sent to
the TNC, eg: the "Connect" and "MYcall" commands. You will get the
reply from TPK and from the TNC !
The characters that you enter with the keyboard are displayed in
the "keyboard-entry" window at the bottom of the screen.
The line can then be edited and dealt with in several ways.
A circular buffer keeps the last 20 commands entered on TPK in
memory (including remote commands). This buffer is edited by the
<Up ARROW> which leeds back to the preceding command and by the
<Down ARROW> which moves on the following command in the buffer.
The keyboard-entry can then be corrected by using the classic
deletion, insertion keys. The presentation can be improved through
use of the text justification ("Justifie" command and <ALT-J> key)
and the word wrapping ("COUpure" command).
The "COUpure NbCol" command limits the current lenght to NbCol
maximum columns. The text is cut at the last space before this
column and the word in the process of being entered is sent on to
the following line. This mean a message can be entered on a BBS
without worrying about line returns. (NbCol=40 to 79)
The "Justifie NbCol" command justifies the text entered on NbCol
columns. When the text entered with the keyboard reaches the NbCol
column, the word currently being entered is sent to the following
line and the line in progress is centered on the NbCol columns. Its
use is the same as the "Coupure" command. (NbCol=40 to 79)
The <ALT-J> key is a command which autorises justification of the
text or not.(flip-flop)
2.10.3 Reconnection function.
A connection request is of course transmitted to the TNC, but is
also managed by TPK: the callsigns passed into the TNC are
memorised and if this connection does not result, it is possible to
relaunch it by typing <F8>.
However, when a station is connected to you, and a premature
disconnection takes place, you can simply hit <F8> to relaunch a
new connection.
Description and use of TPK functions. 51
Terminal PacKet TPK v1.81
2.10.4 QSO messages function.
You can prepare 10 "MESSAGEn.TPK" files which will be used during a
packet QSO. These files will be sent to your correspondent by the
<ALT-n> key where "n" is the number appearing in the message name
(<ALT-1> to <ALT-0>).
These files can be a welcome message or they will eg. describe the
station or any other text in current use. They can be created with
any text editor.
2.10.5 Printing function.
Printing can be put into service by the <ALT-I> or <F4> keys.
The receive buffer can be written on the printer by pressing the
<ALT-P> key. Be careful the buffer, if full, can be very long to
print. Hit <ESC> to stop !
2.10.6 Miscellaneous.
2.10.6.1 Warning bells.
■ "SOnnerie ON|OFF"
Ring on connection (telephone type bell !)
■ "ALArme F6XYZ" or "ALArme F6XYZ-n"
Bip-Bip each time the F6XYZ or F6XYZ-n (n is the SSID from 1 to
15) appears in the traffic window in the disconnected mode.
■ "ALArme F6XYZ-*"
Bip-Bip on the F6XYZ callsign whatever the SSID (F6XYZ, F6XYZ-1,
F6XYZ-2, etc).
■ "BELL ON|OFF" or <ALT-B> key.
Deletion or authorisation of the bip sent out by <CTRL-G>
inserted in the message text you receive on the screen. When the
command is active ("BELL ON"), the bells are replaced by the
ASCII character number 14 (musical note). This deos not concern
the connection bell, which is operated by the command
"SOnnerie". The <ALT-B> key does the same function in a
flip-flop mode. It's status is displayed a the bottom of the
screen (Bell led).
■ "/OPE"
Description and use of TPK functions. 52
Terminal PacKet TPK v1.81
This remote command is to be used by your correspondent during a
QSO to call you: a bell is triggered off on your PC to attract
your attention. An execution report is sent to your
correspondent.
2.10.6.2 Serial port management.
Here are the TPK commands which enable serial port configuration.
■ "FLux 0|1|2"
Flow control between the computer and the TNC by:
- 0 : DSR
- 1 : CTS
- 2 : DSR + CTS
Note: Identical to the parameter of TPK.CFG
■ "Vitesse 1200|4800|9600|19200|38400|57600|115200"
Modification of the serial port speed with the TNC.
■ "PORT n[?|address IRQ]
Change of serial port or addresses and IRQs of the serial
interface.
(See paragraph "5.1.2 Configuration of the serial port." on page
71)
■ <ALT-V>
Displays a little window (in the main screen only) giving the
status of the RS232 line (in the connected or disconnected
mode).
(See paragraph "5.1.1 Connection between TNC and PC." on page
70)
■ "TNCINI"
Unbalances a TNC in 8 bits without parity. TPK sends a <CR> in
every possible combination of bit numbers and parity, until the
"cmd:" prompt of the TNC is obtained. This command allows
putting back a TNC, whose configuration of the serial interface
is unknown, in a state of dialogue with TPK.
Note: The TNC command "XFLOW" must be "OFF" in order that the
hardware flow control will be used between the the computer and the
TNC.
Description and use of TPK functions. 53
Terminal PacKet TPK v1.81
(See paragraph "5.1.2 Configuration of the serial port." on page
71)
2.10.6.3 Use of external drivers.
■ "G8BPQ ON|OFF"
Validates the use of the G8BPQ driver. The serial port number in
TPK.CFG must correspond to the one you wish to use in the
driver.
(See paragraph "5.1.4 Use of an external driver." on page 73)
■ "INT14 ON|OFF"
Validates the use of an external bios INT14H driver like COMBIOS
of WA7MBL, MBBIOS of AA4RE or ESS (version 1.10 or higher) from
FC1EBN !
(See paragraph "5.1.4 Use of an external driver." on page 73)
2.10.6.4 Passage into direct terminal mode.
<ALT-A> key allow passage into a mode where TPK is almost
transparent. Everything typed on the keyboard is sent directly to
the TNC, including the programmable function keys and
macro-commands. This command enables trafficking in other modes
than packet, eg. in RTTY, AMTOR, etc, for the TNCs which
incorporate this possibility like the PK232 or the KAM.
Be careful using this possibility which can be interpreted in an
unforeseen way by TPK !
Description and use of TPK functions. 54
Terminal PacKet TPK v1.81
3.0 TPK FUNCTION KEYS.
3.1 FUNCTION KEYS <F1> TO <F10>
■ <F1> : help for ALT keys.
(See paragraph "5.3.1.2 The ALT keys help." on page 81 and
<ALT-H> paragraph "3.2 <ALT-A> to <ALT-Z> keys." on page 56)
■ <F2> : lists the stations heard and the last connections. Return
by typing any key or automatically after 30 seconds.
(See paragraph "2.2.1 MHEARD." on page 12)
■ <F3> : access to DOS while remaining in TPK. Return to the
programme by typing "EXIT<CR>"
(See paragraph "2.10.1 Access to DOS function." on page 50)
■ <F4> : starts or stops printing traffic. It's equivalent to
<ALT-I>.
(See paragraph "2.10.5 Printing function." on page 52)
■ <F5> : command allowing or not your correspondent access to your
disc (remote commands).
(See paragraph "2.5 Remote commands." on page 14 and paragraph
"6.1 The TPK.CFG file." on page 90)
■ <F6> : forces the TNC into the command mode by sending a "break"
onto the serial line. The "cmd:" prompt of TNC is displayed. you
can then pass a command to the TNC, which will be interpreted as
such and not as text to be sent. (To be used in connected mode)
(See paragraph "2.7.2 Programming of function keys." on page 30
example of the SHIFT-F3 key programming)
Note: Don't mix this up with the <F7> key.
■ <F7> : in the main screen and in the connected mode, <F7> allows
passage of a TPK command which will be interpreted as a command
and not a text to be sent. Eg. the TPK command "/SEND" can be
used to send a file.
The <F7> key displays the "TPK>" prompt in the keyboard-entry
window.
Don't mix this up with the <F6> key.
■ <F8> : the sending of a connection request with the preceding
connection parameters, memorised by TPK.
TPK function keys. 55
Terminal PacKet TPK v1.81
(See also paragraph "2.10.3 Reconnection function." on page 51)
■ <F9> : sending a disconnection request.
■ <F10> : the <F10> key send the contents of the keyboard-buffer
without the <CR>.
3.2 <ALT-A> TO <ALT-Z> KEYS.
■ <ALT-A> : allows using other modes than packet.
(See paragraph "2.10.6.4 Passage into direct terminal mode." on
page 54)
■ <ALT-B> : deletion/authorisation of bells brought about by
<CTRL-G> inserted into the text received on screen. This is a
flip-flop command and is equivalent to the "BELL" command.
(See paragraphs "2.10.6.1 Warning bells." on page 52 and "4.1
Local commands." on page 59)
■ <ALT-C> : erases the traffic window from the main screen in
connected or disconnected mode.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ <ALT-D> : sends the TNC command "DAytime" to the TNC. This
function is automatically carried out by TPK at the launch of
the programme.
(See also paragraph "2.7.5.1 Capture of the date and time." on
page 35 for an example of DAytime macro-command)
■ <ALT-E> : file(s) transmission menu.
(See paragraph "2.6.5.3 File(s) transmission menus <ALT-E>" on
page 27)
■ <ALT-F> : erases the monitor window on the main screen in
connected and disconnected mode.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ <ALT-G> : set the display in 8 or 7 bits.
■ <ALT-H> : TPK on-line help.
(See also <F1>, paragraph "3.1 Function keys <F1> to <F10>" on
page 55)
■ <ALT-I> : start/stop the printer. Identical to key <F4>.
TPK function keys. 56
Terminal PacKet TPK v1.81
(See paragraph "2.10.5 Printing function." on page 52)
■ <ALT-J> : activation/de-activation of the text justification.
Linked commands: "Justifie", "COUpure"
(See paragraph "2.10.2 Keyboard management." on page 51)
■ <ALT-L> : access to the messages listings.
(See paragraph "5.3.1.7 The message listing screen." on page 85)
■ <ALT-K> : enables quitting the KISS mode if it was active.
■ <ALT-M> : displays list of macro-commands.
(See paragraph "2.7.3 Macro-commands." on page 32)
■ <ALT-P> : print the receive buffer.
Associated keys: <ALT-W> and <ALT-Z>
(See paragraphs "2.3 BACKSCROLL." on page 13 and "2.10.5
Printing function." on page 52)
■ <ALT-R> : file(s) receiving menu.
(See paragraph "2.6.5.2 File(s) reception menus <ALT-R>" on page
26)
■ <ALT-S> : opening or closing the CAPTURE mode.
(See paragraph "2.4 CAPTURE mode." on page 14)
■ <ALT-T> : displays the list of programmable function keys.
(See paragraph "2.7.2 Programming of function keys." on page 30)
■ <ALT-V> : displays the status of the RS232 line in a small
window.
(See paragraph "5.1.1 Connection between TNC and PC." on page
70)
■ <ALT-W> : writing of the receive buffer in a file.
Associated keys: <ALT-P> and <ALT-Z>
(See paragraph "2.3 BACKSCROLL." on page 13)
■ <ALT-X> : to leave the TPK programme and return to DOS.
■ <ALT-Z> : erase the receive buffer.
TPK function keys. 57
Terminal PacKet TPK v1.81
Associated commands: <ALT-W> and <ALT-P>
(See paragraph "2.3 BACKSCROLL." on page 13)
■ <ALT-1> to <ALT-0> : send into the QSO the contents of the
messages of current useage. These files are called
"MESSAGEn.TPK" (n from 0 to 9) and are sent by pressing the
<ALT-n> key.
(See paragraph "2.10.4 QSO messages function." on page 52)
TPK function keys. 58
Terminal PacKet TPK v1.81
4.0 SYNTAX OF TPK COMMANDS.
4.1 LOCAL COMMANDS.
■ ALA F6XYZ[-n]|F6XYZ-*|F6XYZ
A bell sounds each time F6XYZ-n is received.
(See paragraph "2.10.6.1 Warning bells." on page 52)
■ At Time Command
Programmation of a command at a determined time. format of the
time is: hour and minutes placed side by side (eg: 1215=12H15).
Command is a command of TPK or a macro-command, etc.
■ At Time
This lists the programming at the stated time if it exists.
■ At
Lists all the programmings.
(See paragraph "2.7.5 Other commands useful in programming." on
page 35)
■ ATTente Duration Event
Awaits an event for a maximum of seconds "Duration". The command
ends as soon as "Event" happens.
"Event" can be:
- CNX for a connection.
- DCNX for a disconnection.
- A string ending a line of text received (Syntax: ATT Text).
- A string anywhere in a line of text received (Syntax: ATT
"Text").
- PASSWORD for a password question.
(See paragraph "2.7.5.4 Password management." on page 38)
If the time period runs out and the awaited event has not taken
place, the execution of the macro-command or the programme-file
is abandonned.
■ ATTente Duration
Syntax of TPK commands. 59
Terminal PacKet TPK v1.81
Pause for "Duration" seconds.
(See paragraph "2.7.5.3 Programming a waiting period." on page
37)
■ BELL ON|OFF
Deletion/Authorisation of the bip sent out by a <CTRL-G>
inserted in the text received. The <ALT-B> key can be used for
the same function).
(See paragraph "2.10.6.1 Warning bells." on page 52)
■ BUFFER [nnnn]
Receive buffer size.
You can change the number of lines in the receive buffer with
the command BUFFER.
nnnn is the number of lines you want.
TPK keeps a minimum of 50kb free to allow a SHELL to DOS. With
this value you can only execute DOS internal commands. To free
more memory you must reduce the number of lines or swap the
buffer to disk ..See command "SWAP".
Ex: BUFFER 1000
■ CHat NbLines
On the main screen, Nblines is the number of lines in the
traffic window measured from the top of the screen.NbLines mini
is the greatest value between FE and FC+3. NbLines maxi is the
number of lines on the screen minus 4.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ COMmente [x:\path\]FileName.Ext
Adds to the DIRC.TPK file a commentary about the file given in
the parameter. TPK asking you the commentary in a window.
(See paragraph "2.5.2 Commented directory." on page 16)
■ COUpure NbCol
Break in text entered with the keyboard from the number column
NbCol.Associated commands: <ALT-J> and Justifie
(See paragraph "2.10.2 Keyboard management." on page 51)
■ ECHOTpk Text
Syntax of TPK commands. 60
Terminal PacKet TPK v1.81
When a programme-file is being carried out, the Text is
displayed in the traffic window as a commentary.
(See paragraph "2.7.4 Programme files." on page 33)
■ EDITOR x:\path\editor.exe
Initialises the editor which can be called from the message
editor. You must give the full path to this programme, TPK will
test its presence.
Ex: EDITOR C:\UTIL\Q.EXE
(See paragraph "5.3.1.8 The message editor screen." on page 86)
■ EFAt Time
Cancellation of a programming. Associated command: At.
(See paragraph "2.7.5 Other commands useful in programming." on
page 35)
■ EFLogrx
Erases the list of stations heard.
(See paragraph "2.2.1 MHEARD." on page 12)
■ EFMacro Macro-Command-WordKey
Erases the macro-command WordKey. Associated commands: "EMacro",
"Macro", "MEMorise", "<ESC>WordKey"
(See paragraph "2.7.3 Macro-commands." on page 32)
■ EMacro Macro-Command-WordKey
Edition of a macro-command. Associated commands: "MEMorise",
"EFMacro", "Macro", "<ESC>WordKey"
(See paragraph "2.7.3 Macro-commands." on page 32)
■ EXecute Filename
Launches the execution of a programme-file.
(See paragraph "2.7.4 Programme files." on page 33)
■ EXIT
To leave the DOS window and return to TPK.
(See paragraph "2.10.1 Access to DOS function." on page 50)
■ FChat NbLines
Syntax of TPK commands. 61
Terminal PacKet TPK v1.81
Initialises the height of the monitoring window in the connected
mode if "RXblock" and "MCon" are ON. NbLines mini is 3 and
NbLines maxi is value of CHat minus 3.
Note: This mode is ONLY available with the TNC2.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ FEnetre F6XYZ-n
In the disconnected mode, sends all the F6XYZ-n packets in the
monitor window of the main screen (FENETRE=WINDOW).
(See paragraph "5.3.1.3 The main screen." on page 81)
■ FEnetre NbLines
Establishes the height of the main screen monitor window in the
disconnected mode. NbLines mini is 3 and NbLines maxi is the
value of CHat minus 3.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ FEnetre "Text"
In disconnected mode, this send all the packets whose the
callsign headers contain Text, into the monitor window. Text is
made visible in the division bar under this window.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ FEnetre
FEnetre without parameter disable the monitor window in
disconnected mode.
■ FIN
Return to DOS (end of programe) the same as <ALT-X> key
(FIN=END).
■ FLux 0|1|2
Flow control between the computer and the TNC:
- 0 : DSR
- 1 : CTS
- 2 : DSR + CTS
Values are the same as the corresponding parameter of TPK.CFG
(See paragraph "2.10.6.2 Serial port management." on page 53 and
paragraph "5.1.1 Connection between TNC and PC." on page 70)
Syntax of TPK commands. 62
Terminal PacKet TPK v1.81
■ FREquence xxxxxx
This modifies the frequency indicated in the LOGBOOK and on the
main screen bar under the traffic window.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ FREquence 1|2 xxxxxx
With a KAM or another KANTRONICS TNC, equipped with several
radio ports, there is validation of the use of 2 frequencys
balanced by the "STREAM SWITCH"
(See paragraph "5.2.4 Use of TPK with a KAM." on page 78)
■ G8BPQ ON|OFF
This validates the use of the G8BPQ driver. The serial port
number in TPK.CFG must correspond to the one you wish to use in
the driver.
(See paragraph "5.2.3 Starting." on page 76)
■ Init
Initialise TPK from the parameters of the CONFIG.TPK file. This
is also done at the launch of TPK.
■ Init n
Initialise TPK from the parameters of the file CONFIG-n.TPK
n between 0 and 9.
(See paragraph "5.2.3 Starting." on page 76)
■ Init Filename
Launches the execution of the contents of the file Filename.
(See paragraph "5.2.3 Starting." on page 76)
■ INT14 ON|OFF
Validates the use of an external serial driver like COMBIOS by
WA7MBL, MBBIOS by AA4RE or ESS by FC1EBN.
(See paragraph "5.1.4 Use of an external driver." on page 73)
■ Justifie NbCol
This provides justification of the text on NbCol columns. When
the text entered on the keybord reaches the column, the word in
the process of being entered is carried to the following line
and the line is centered on the columns (NbCol between 40 and
Syntax of TPK commands. 63
Terminal PacKet TPK v1.81
79).
Associated commands: <ALT-J>, COUpure
(See paragraph "2.10.2 Keyboard management." on page 51)
■ LANGuage [LANGUAGE]
Language change.
The command LANGuage allows you to change the language used by
TPK, where LANGUAGE is the name without extension of a .LNG
file.
You will find ENGLISH.LNG and FRANCAIS.LNG already included with
TPK.
Eg: LANG ENGLISH
■ LOG ON|OFF
Validation of the LOGBOOK.
(See paragraph "2.2.2 LOGBOOK." on page 12)
■ Macro WordKey
Launches the macro-command picked out by its WordKey. The
combination of <ESC>WordKey is equivalent to the Macro command.
Associated commands: "EMacro", "EFMacro", "MEMorise",
"<ESC>WordKey"
(See paragraph "2.7.3 Macro-commands." on page 32)
■ MCon ON|OFF
Activates or disactivates the main screen monitor window in the
connected mode. RXblock MUST also be ON.
Note: This mode is ONLY available with the TNC2.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ MEMorise WordKey Command
Stores in memory and on disc the macro-command WordKey with the
command which will be assiciated to it. Associated commands:
"EMacro", "Macro", "EFMacro", "<ESC>WordKey"
(See paragraph "2.7.3 Macro-commands." on page 32)
■ MODEDIR [1|2|3|4]
Display mode of the /DIR command.
Syntax of TPK commands. 64
Terminal PacKet TPK v1.81
┌───────────┬────────────┬─────────────┐
│ Parameter │ /DIR Local │ /DIR Remote │
├───────────┼────────────┼─────────────┤
│ 1 │ 1 column │ 1 column │
│ 2 │ 2 columns │ 2 columns │
│ 3 │ 1 column │ /DIRC │
│ 4 │ 2 columns │ /DIRC │
└───────────┴────────────┴─────────────┘
■ PATH
Gives the TPK directory.
■ PORT n [?|ADDRESS IRQ]
Change of serial port or addresses and IRQs of serial
interfaces. Associated commands: "Vitesse", "FLux"
(See paragraph "5.1.2 Configuration of the serial port." on page
71)
■ REPrise ON|OFF
Authorisation or deletion of the crash recovery of BINARY
transfers (ON by defalut).
(See paragraph "2.6.4 Recovery of an abandonned transfer." on
page 25)
■ RXblock ON|OFF
Validates the block mode of the TNC2. Allows the monitoring
window in the connected mode. Works ONLY with the TNC2.
Associated command: "MCon"
(See paragraph "5.3.1.3 The main screen." on page 81)
■ SHell [Command [Parameters]]
Access to DOS screen. return to TPK at the end of the command.
If there is no command this function is equivalent to the <F3>
key.
(See paragraph "2.10.1 Access to DOS function." on page 50)
■ SOnnerie ON|OFF
Validate the telephone type bell at each connection.
(See paragraph "2.10.6.1 Warning bells." on page 52)
■ SUpcr ON|OFF
In the main screen and in the disconnected mode, there is either
deletion or no deletion of a possible <CR> sent systematically
Syntax of TPK commands. 65
Terminal PacKet TPK v1.81
at the end of each information packet by the TNC2. This allow
correct display in the monitoring window.
(See paragraph "5.3.1.3 The main screen." on page 81)
■ SWap [<ON|OFF> [<PATH>|XMS|EMS]]
Swapping the receive buffer during a DOS SHELL.
Get more memory during a SHELL by swapping the receiving buffer
to disk or to extended/expanded memory.
Examples:
- SW ON E:\TMP
To swap the buffer into the TMP directory of disc E:
- SW ON XMS
To swap the buffer into extended memory.
- SW ON EMS
To swap the buffer into expanded memory.
- SW OFF
To disable swaping.
■ Touche Sn|Cn|An [Text_Of_The_Key]
Function keys (from 1 to 10) either associated with the <SHIFT>
key, the <CTRL> key or the <ALT> key. These 30 keys are
programmable.
Complete description paragraph "2.7.2 Programming of function
keys." on page 30
■ TNCIni
Put TNC in 8 bits mode without parity.
(See paragraph "2.10.6.2 Serial port management." on page 53) w
■ Vitesse [1200|4800|9600|19200|38400|57600|115200]
Modification of the serial port speed. Associated commands:
"PORT", "FLux"
(See paragraph "2.10.6.2 Serial port management." on page 53 et
paragraph "5.1.2 Configuration of the serial port." on page 71)
Syntax of TPK commands. 66
Terminal PacKet TPK v1.81
4.2 REMOTE COMMANDS.
When a correspondent is connected to you and is using one of these
commands, he RECEIVE in return some information or CARRIES OUT a
command.
(See paragraph "2.5 Remote commands." on page 14)
■ /BYE
Disconnect: TPK sends a disconnect request to the TNC which is
equivalent to the <F9> key in local.
■ /AIDE
Sends contents of the file AIDE (AIDE=HELP) which gives the
syntax of the remote commands. This file is a small text which
you can personalise as you wish, but TPK must find it in the TPK
directory at its launch, otherwise you will have an error
message.
■ /CHDIR or /CD
Change the current directory. If the system is closed, you
cannot get up into the tree above the directory for sending
files and your correspondent is limited to this directory or its
subdirectories. Associated command: <F5>
(See paragraph "3.1 Function keys <F1> to <F10>" on page 55)
■ /DIR [x:[\PATH\[FileName.Ext]]]
Lists the contents of a directory. If teh system is closed he
receives the contents of the directory where you are locked
into.
(See paragraph "2.5 Remote commands." on page 14)
The presentation of the directory list can be changed with the
"MODEDIR" command.
(Details paragraph "4.1 Local commands." on page 59)
■ /DIRC [Criterion]
Commented lists of files available on you discs. The criterion
lets you choose a field of interest. This command sends the
contents of the DIRC.TPK file.
(See paragraph "2.5.2 Commented directory." on page 16)
■ /DISK
He receives the name of the current disc.
Syntax of TPK commands. 67
Terminal PacKet TPK v1.81
■ /DISK x:
He changes the current disc of your computer unless the system
is closed in which case this command has no effect.
■ /EX
Enables closure of a message (equivalent to <CTRL-Z>).
■ /FREE
He receives the the number of free bytes on your disc.
■ /FREE x:
He receives the number of free bytes on your disc x: unless the
system is closed.
■ /HELP
The remote caller receives a help text reminding them of the
list of commands.
■ /LOG
He receives your list of stations heard.
■ /MSG
Allows your correspondent to leave a message.
(See paragraph "2.8 The BROADCAST function." on page 40)
■ /OPE
A bell is triggered off on your computer by your correspondent
in an attempt to lift you out of you lethargy !
(See paragraph "2.10.6.1 Warning bells." on page 52)
■ /SEND [x:]FileName[.Ext] [Y|A|T|E]
ASCII file or BINARY file transfer.
- Y : YAPP
- A : ASCII with the TNC in CONVERS mode
- T : ASCII with the TNC in TRANS mode
- E : ASCII without echo in the TPK traffic window.
- TE : ASCII without echo and with the TNC in TRANS mode.
Syntax of TPK commands. 68
Terminal PacKet TPK v1.81
In local, "/SEND" allows the sending of an ASCII file to the
TNC, eg. to configurate it. Eg: "/SEND TNC2.SET"
(See paragraphs "2.5 Remote commands." on page 14 and "2.6 File
transfers." on page 19)
The following commands can just as easily be carried out in local
(you can type them on your keyboard):
/DIR /DIRC /OPE /DISK /FREE /LOG /HELP /SEND /CHDIR /CD
Syntax of TPK commands. 69
Terminal PacKet TPK v1.81
5.0 CONFIGURATIONS AND SETTING UP OF TPK.
5.1 THE SERIAL PORT.
5.1.1 Connection between TNC and PC.
The RS232 connection must be pin to pin in the case of a TNC
equiped with a 25 pin plug. This wiring is valid for the TNC2 and
the PK232. In general, you can get away with using the wiring shown
as "complete wiring" in the TNC documentation and which is
recommended for the BBS type WA7MBL, etc.
PC TNC PC Tiny-2
GND 1 ───────────────── 1 1 and 7 ────────── 5
TXD 2 ─>─────────────>─ 2 2 ─>────────────>─ 3
RXD 3 ─<─────────────<─ 3 3 ─<────────────<─ 2
RTS 4 ─>─────────────>─ 4 4 ─>────────────>─ 7
CTS 5 ─<─────────────<─ 5 5 ─<────────────<─ 8
DSR 6 ─<─────────────<─ 6 6 ─<────────────<─ 6
GND 7 ───────────────── 7
DCD 8 ─<─────────────<─ 8 8 ─<────────────<─ 1
DTR 20 ─>────────────>─ 20
In the case of the TNC2, the DTR signal (pin 20) is used by the TNC
for the flow control with the computer, but generally, it is the
RTS signal which plays this role. TPK uses both signal: when its
reception buffers are full, or when it is out of time in dealing
with the received signals (in the case of SHell to DOS for
example), it puts these two lines to the zero logic level and the
TNC stops sending characters onto the RS232 line, if it is
correctly parametered, eg. by "Xflow OFF"
One of the TPK.CFG parameters is also concerned with the flow
control, but it concerns another sense of the RS232 link. CTS is
the signal used by the TNC to tell the computer to stop sending
datas on the line. TPK reads their value before sending characters
to the TNC. You can tell it also to keep an eye on the DSR signal:
that is the aim of the parameter in TPK.CFG.
In the main screen, by typing <ALT-V>, you can make these signals
visible so that they can be seen by TPK via the serial interface
UART registers.
The DCD signal of pin 8 is the one which will undoubletedly have
caused most difficulties to many OMs in starting up TPK. Indeed
this signal has been ignored on certain TNCs like the TINY-2.
Configurations and setting up of TPK. 70
Terminal PacKet TPK v1.81
However DCD is VERY important because it is this signal which
indicates whether the TNC is connected or not, from the AX25 point
of view, in the TNC2s equipped with the TAPR software or commercial
TNCs, just for TPK. According to the TNC, this signal is either
quite simply "empty", or pulled at the +5V through a resistance, or
is directly cabled together on the SIO of the TNC, ie. at a TTL
level instead of the RS232 level.
Generally, the DCD at the TTL level works perfectly well if your
serial card accpets this kind of level as opposed to RS232. This is
the case with cards of Asian origin ! Conversely, it doesn't work
with IBM cards, because they must have the right levels.
In the case where the DCD is not connected or linked up to +5V, you
can at first link it up directly to pin 25 of the SIO. This
modification will take you the same level as the TNC whose signal
is at the TTL level and will work in many cases.
The best thing to do is to make the substitution properly, so that
it will require mounting of a simple transistor on the TNC card, as
recommended by Paccomm for his TINY-2. This will result in proper
interfunctionning of TPK/TNC. You will find the diagram in the
CONNECT.TXT file.
<ALT-V> also gives the state of this DCD line. It must be at zero
when the TNC is not connected into AX25. This line reflects the
state of the CON LED, it is connected to the same place.
For a TNC2, programme either DSR+CTS or CTS with the help of the
FLux command or in TPK.CFG. For KANTRONICS TNCs use CTS.
TPK, from the moment it starts up, warns you through a message if
these signals are not valued and moves into the functionning mode
without access to the serial interface. The <ALT-V> key in the main
screen allows you to check the state of these signals thanks to the
UART register.
5.1.2 Configuration of the serial port.
The TNC can be linked up to the choice of COM1 to COM8
TPK implicit speed is fixed in TPK.CFG. The "Vitesse" command
allows you to change that speed from 1200 to 115200 bauds.
To get optimum file transfer functionning you must maintain a speed
higher than that of the radio link between the TNC and the
computer. A PC XT with a 4.77MHZ clock works weel at 9600 bauds
with TPK.
To change the serial port towards the TNC, type "PORT n" with n
from 1 to 8.
The serial port parameters begin by having the standard MSDOS
values, ie:
Configurations and setting up of TPK. 71
Terminal PacKet TPK v1.81
■ COM1 (and COM5) address=3F8 IRQ=4
■ COM2 (and COM6) address=2F8 IRQ=3
■ COM3 (and COM7) address=3E8 IRQ=4
■ COM4 (and COM8) address=2E8 IRQ=3
You can modify all these parameters with an editor in the TPK.CFG
file or in TPK with the "PORT" command:
■ PORT
Gives the port used by TPK.
■ PORT n
Allocates the n port in TPK.
■ PORT n ?
Gives the address and IRQ of n port:
Eg: "port 1 ?" must give "Address:3F8 IRQ4" (if it has not been
previously modified !!)
■ PORT n adr irq
Modifies the address and the IRQ on the n port (adr is in
hexadecimal and irq between 2 and 5)
Note: This command with these parameters does not modify the
port used by TPK, but ONLY its address and IRQ.
Eg: "PORT 4 370 4" moves the hexadecimal address 370 to port 4
and selects IRQ 4.
5.1.3 Configuration for IBM serial cards.
Parameters to use for TPK with an IBM serial card, equipped with
additional ports COM3 to COM8:
■ COM3 address 12832 (decimal) |
■ COM4 address 12840 (decimal) |
■ COM5 address 16928 (decimal) | COM3 to COM8 IRQ3
■ COM6 address 16936 (decimal) |
■ COM7 address 21024 (decimal) |
■ COM8 address 21032 (decimal) |
Configurations and setting up of TPK. 72
Terminal PacKet TPK v1.81
Information given by JEAN-CLAUDE FC1RZA.
5.1.4 Use of an external driver.
Two kinds of external drivers can be used in TPK: COMBIOS by WA7MBL
(COM1BIOS or COM2BIOS), MBBIOS by AA4RE, ESS by FC1EBN (TPK command
INT14) or the G8BPQ driver (TPK command G8BPQ).
Putting the INT14 or G8BPQ command in the TPK.CFG file is enough to
validate the chosen external driver.
Certain commands become ineffectual in the case of these drivers,
as for example the modification of addresses, serial port IRQs or
the speed in the case of the G8BPQ driver.
(See paragraph "2.10.6.3 Use of external drivers." on page 54)
The functionning must be correct with COMBIOS or MBBIOS but the
G8BPQ support is only in the test stage and many TPK functions
don't work with it.
5.2 SETTING UP TPK.
5.2.1 Decompression.
Originally, the TPK software is provided in compressed from: this
is a guarantee of receiving all the files, and not "bits and
pieces" !
You must have (nnn: version number):
■ TPKnnn-1.ZIP containing TPK.EXE and all configuration files.
■ TPKnnn-2.ZIP containing the french documentation files.
■ TPKnnn-3.ZIP containing the french on-line help files.
■ TPKnnn-4.ZIP containing the english documentation files.
■ TPKnnn-5.ZIP containing the english on-line help files.
■ TPKINST.EXE the installation and configuration programm.
■ TPKCRC List of the .ZIP files with CRC.
To decompress the files you must run TPKINST which will create all
the directories needed and modify the TPK.CFG file with the
informations you have given.
Configurations and setting up of TPK. 73
Terminal PacKet TPK v1.81
5.2.2 List of TPK files.
Here is the list of TPK files after decompression.
Contents of TPKnnn-1.ZIP:
■ AIDE File sent in response to /AIDE
■ CONFIG.TPK Commands to be carried out at the beginning of TPK.
■ CONFIG-1.TPK Other configurations which can be used
■ CONFIG-2.TPK with the "Init n" command.
■ CONFIG-X.TPK Commands to be carried out a the end of TPK.
■ DIRC.TPK Commented directory.
■ EXECAUTO.TPK Authorised DOS remote commands.
■ MESSAGE1.TPK Message to be sent with <ALT-1>
■ MESSAGE2.TPK Message to be sent with <ALT-2>
■ FRANCAIS.LNG The french texts.
■ ENGLISH.LNG The english texts.
■ TPK.CFG TPK configuration file.
■ TPK.DIR The macro-commands.
■ TPK.KEY The function keys.
■ TPK.EXE The programme itself.
■ TPK_COMP.EXE The (de)compression programme for FBB forward.
■ CVTDOC.COM The conversion programme for TPKDOC.IBM
■ LBBS Example of programme file (list of messages).
■ RBBS Example of programme file (read messages).
■ TNC2.SET Reference config for TNC2 with eprom 1.1.6
■ TNC2PMS.SET Reference config for TNC2 with eprom 1.1.6 with
PMS.
■ TNC2-117.SET Reference config for TNC2 with eprom 1.1.7b
■ TNC2118A.SET Reference config for TNC2 with eprom 1.1.8a
■ KAM.ZIP Configuration for KAM.
Configurations and setting up of TPK. 74
Terminal PacKet TPK v1.81
■ PK232.ZIP Configuration for PK232
■ PK232SP.ZIP Configuration for PK232 without batteries.
■ FV142.ZIP Compressed file verbose programme.
Contents of TPKnnn-2.ZIP:
■ COULEURS Type "COULEURS" to display the range of colours.
■ CONNECT.TXT DCD modification for TINY-2 by Paccomm (english)
■ TPKDOC.IBM The french documentation format IBM Graphics.
■ CVTDOC.COM The ESC characters conversion programme for
TPKDOC.IBM
■ CVTDOCTY.COM The IBM specific characters conversion programme.
■ TPKDCD.DOC Use of the DCD signal by TPK (french).
Contents of TPKnnn-3.ZIP:
■ TPK.HLP The on-line help (french).
■ FBB.HLP BBS F6FBB on-line help (french).
■ TNC2117.HLP TNC2 v 1.1.7 on-line help translated by F6BXM
(french).
■ CLUSTER.HLP The packet cluster on-line help (french).
Contents of TPKnnn-4.ZIP:
■ CONNECT.TXT DCD modification for TINY-2 by Paccomm (english)
■ TPKDOC.IBM The englich documentation format IBM Graphics.
■ CVTDOC.COM The ESC characters conversion programme for
TPKDOC.IBM
■ CVTDOCTY.COM The IBM specific characters conversion programme.
■ TPKDCD.DOC Use of the DCD signal by TPK (english).
Contents of TPKnnn-5.ZIP:
■ TPK.HLP The on-line help (english).
■ FBB.HLP BBS F6FBB on-line help (english).
■ TNC2117.HLP TNC2 v 1.1.7 on-line help (english).
■ CLUSTER.HLP The packet cluster on-line help (english).
Configurations and setting up of TPK. 75
Terminal PacKet TPK v1.81
5.2.3 Starting.
5.2.3.1 First attempts.
You can make your first attempt with TPK without the TNC, and even
without the serial interface.
Type TPK<CR> : you must first of all get a welcome screen while TPK
introduces all its parameters and reads its files, then an error
message informing you that it has not found the serial port or the
TNC. It's normal if the TNC is not on-line. As requested, type a
key to continue. If you don't type any key, the programme sequence
will continue after a temporisation of some seconds.
The error message which has been generated by the DSR and CTS
signals test corresponds to the flow control parameter of TPK.CFG.
You can now try to mess about with the commands and keys in such a
way a to see if everything is going as it should with your computer
and that there is no incompatibility (display, keyboard, etc).
5.2.3.2 First time starting.
Some advice: to get off to a good start, do not hesitate to go back
to a total erasure of the RAm of your TNC. To do this, cut off the
TNC supply, remove the RAM and put it on a piece of conducting moss
or on a piece of aluminium paper for a few minutes. Then put it
back in place.
It's amazing that this little trick can save you so much time. Also
think about it if your TNC musteriously lacks in later.
You must now check the TNC configuration which must be conducted
according to the instructions in paragraph "5.1.2 Configuration of
the serial port." on page 71
Rememeber: the programme startup is carried out from what is
located in TPK.CFG and CONFIG.TPK. Nevertheless, certain commands
such as "PORT", "INT14", "G8BPQ", "Vitesse" authorise a change on
the serial port without leaving TPK.
Eg: it is possible to pass from one TNC in the kiss mode associated
with G8BPQ to another TNC connected to another port without using
an external driver.
After these first attempts, the RS232 line having been established,
the right port having been specified and the TNC having been
supplied with power, get out of TPK (with <ALT-X>) and relaunch it.
If everything goes OK, you will once again find the main screen
with a text display which can be more or less coherent: you don't
have to have an error message ! Otherwise however you must find the
Configurations and setting up of TPK. 76
Terminal PacKet TPK v1.81
mistake, correct it and relaunch TPK.
There are two classic errors:
■ Error message concerning the serial line: see paragraph "5.2.3.3
Error messages."
■ Error message concerning a configuration error: check TPK.CFG or
CONFIG.TPK. Don't forget that you must not add or delete lines
to TPK.CFG !
When all problems have been solved, relaunch TPK and type the
command:
"TNCINI"
This command will send "AW 8", "PAR 0", and "RESTART" to the TNC to
set the correct number of bits and parity, after the cmd: prompt
has been received.
If you did not receive the copyright message from the TNC, retry
this command till you get it.
5.2.3.3 Error messages.
1.Error access TNC (missing DSR CTS)
This message is given out at the initialisation of the serial
port after the CTS and DSR signal tests and following the flow
control value given in TPK.CFG.
The signals used must be at the logic 1 level. This value can be
checked thanks to the <ALT-V> key.
Potential errors are:
■ You have forgotten to put the flow control parameter into
TPK.CFG or you have not chosen the right one.
■ The TNC is not powered.
■ The serial cable is not connected to the computer or to the
TNC.
■ The TNC is not connected onto the right serial port.
■ Your RS232 cable is not correct.
2.Error access UART serial port
A reading/writing test in the UART registers of the serial
interface is carried out at the set-up of the serial driver and
if this test is negative, the port is declared unavailable.
Configurations and setting up of TPK. 77
Terminal PacKet TPK v1.81
Potential mistakes are:
■ Adrressing the serial port according to the documentation of
your interface card.
■ You have used the command "PORT" with incorrect parameters.
3.ERROR DCD=1 logic (RS232) and TNC is not in the Connected status
!
The DCD signal from the RS232 line is at the logic 1 level and
TPK has detected that the TNC wasn't connected at the AX25 level.
You can control this state thanks to the <ALT-V> key.
(See paragraph "5.1.1 Connection between TNC and PC." on page 70)
5.2.3.4 Setting up commands.
The "Init" command sets up TPK from the configuration file
CONFIG.TPK parameters. It relaunches TPK set up programme from a
configuration file, as at the beginning of the programme.
The "Init n" command starts up TPK with one of the CONFIG-n.TPK
files (with n between 0 and 9).
The "Init FileName" command starts up the execution of the FileName
contents. Eg. to initialise the TNC with the parameters contained
in the TNC2.SET file (this is a reference file for configuration of
the TNC) type:
■ "I TNC2.SET"
Unlike "EXecute", where the characters are entered in the keyboard
buffer, the commands are directly sent to the TPK interpreter.
5.2.4 Use of TPK with a KAM.
5.2.4.1 Setting up.
The KAM.ZIP file contains some configuration files which can be
used with this TNC. To set them up, you only have to decompress
this file in your TPK directory:
Type: "PKUNZIP -O KAM"
You will get the following files:
■ CONFIG.TPK configuration file with commands specific to the KAM.
■ CONFIG-X.TPK configuration file sent at the end of TPK.
Configurations and setting up of TPK. 78
Terminal PacKet TPK v1.81
■ KAM.SET a configuration reference, which can be used for example
by comparing its contents with the state of your TNC through a
"DISPLAY" command, or it can be used to initialise your TNC
through the command: "/SEND KAM.SET"
5.2.4.2 Specific commands for the KAM.
The "FREquence 1|2 xxxxxx" command validate the use of two
frequencies with automatic change by the "STREAM SWITCH" which must
consequently be modified. This command is constructed for the KAM
or for other KANTRONICS type TNCs equipped with several radio
ports.
The following commands are found in the CONFIG.TPK file:
■ STR $F1/$F2
■ STREAMEV ON
■ FRE 1 14Mhz
■ FRE 2 144675
Furthermore, each "FRE" command change the TNC onto the
corresponding port. Validation of the "STREAM SWITCH" enables TPK
to change radio port and takes into account a connection arriving
on the port on which it is not at this time.
Eg. if you are on VHF and someone gets connected to you on HF, TPK
will switch the TNC onto HF, validate the connection and change the
frequency for the LOGBOOK. This possibility is only validated when
two frequencies exist and only works, of course, with a TNC
equipped with two radio ports. NOT TO BE USED WITH A TNC2 !
5.2.5 Use of TPK with a PK232.
The PK232.ZIP file contains configuration files. Just decompress it
by using the command: "PKUNZIP -O PK232"
You will get the following files:
■ CONFIG.TPK configuration file using commands specific to the
PK232.
■ CONFIG-X.TPK configuration file sent at the end of TPK.
■ PK232SP.ZIP compressed file of the "no batteries" version.
In the case of a "no battery" functionning, decompress this last
file by entering: "PKUNZIP -O PK232SP"
Configurations and setting up of TPK. 79
Terminal PacKet TPK v1.81
You get will new files:
■ CONFIG.TPK configuration file, in particular containing the
"/SEND PK232.SET" command to initialise the PK232 at each
launch.
■ PK232.SET which contains the total PK232 configuration commands.
It is used for reference, eg. by comparing its contents with the
state of your TNC with the "DISPLAY Z" command, or it can be
used to initialise your TNC by the "/SEND PK232.SET" command.
You can use TPK with a PK232 WITH or WITHOUT batteries. When the
latter is equipped with batteries, its use is the same as a
standard TNC: there are only a few parameters to initialise
again.
If your PK232 has no batteries, it loses its parameters at every
power out and you must restore the lot. The speed having been
lost, you must reinitialise it via the PK232 by sending the "*"
character. When it has been done, TPK immediately sends the
command "DCDCONN ON" to get a correct functionning of the DCD
signal. You then have to send all the PK232 configuration
commands. This is done by launching "CONFIG.TPK" which contains
the appropriate "/SEND PK232.SET" command.
To initialise a PK232 with no batteries, you must use the
special PK232 parameter of the TPK command:
- "TPK PK232"
5.3 THE DIFFERENT SCREENS.
This paragraph introduces the screens used by TPK:
The on-line help.
The ALT keys help.
The main screen.
The MHEARD screen.
The BACKSCROLL screen.
The DOS screen.
The message lists screen.
The message editor.
The LOGBOOK screen.
5.3.1 Description of screens.
Configurations and setting up of TPK. 80
Terminal PacKet TPK v1.81
5.3.1.1 On-line help.
These on line help screens are shown by using the <ALT-H> key: the
contents of the TPK.HLP file are displayed. You choose the command
by moving the menu bar onto the heading which interest you and by
validating with <CR> or <S> or by clicking your mouse on the
<Selection> button.
<ESC> or <A> or <Cancel> clicked by the mouse leaves the chosen
heading or on-line help.
<C> or <Change help file> button offers you the list of help files
available (files *.HLP).
The list of these files is given in the description of the contents
of the TPK compressed files paragraph "5.2.2 List of TPK files." on
page 74.
TPK can also read the help files provided by VK2DHU with its
excellent PAKET programme.
Return to TPK is automatic one minute after the keyboard has been
used, or immediately by <ESC>.
These help files are ASCII text files that you can modify with your
favorite editor (see details paragraph "6.5 The on-line help
files." on page 93).
5.3.1.2 The ALT keys help.
This on-line help screen is displayed by the <F1> key and gives you
the actions of the ALT keys.
Return to the main screen by hitting any key. Otherwise, return is
automatic one minute after the last keyboard use.
5.3.1.3 The main screen.
The main reception and transmission screen is the one which appears
at the end of the initialisation when TPK is launched.
It is made up of at least two windows, one dedicated to your
command or text entries (this is the keyboard-entry window which is
found at the bottom of the screen), and the other is dedicated to
the packet traffic. This traffic window is located in the upper
part of the screen. Indeed, the traffic window changes a little
according to whether or not you are in the connected or
disconnected mode.
In the disconnected mode, the traffic window receives:
■ The packet traffic if the TNC command "MOnitor" is ON.
Configurations and setting up of TPK. 81
Terminal PacKet TPK v1.81
■ The replies to the TPK or TNC commands.
In the connected mode, only the QSO packets are displayed, what is
going out and the stuff being received, just like the echo of you
have typed on the keyboard.
In both case, the keyboard-entry window enables the TNC or TPK
commands to be entered.
It is possible to open a third window which is optional and which
will install it at the top of the screen (to the detriment of the
traffic window which the number of lines will be reduced) and which
is called the MONITORING window. The traffic window will be
consequently at the middle of the screen, between the keyboard
entry window and the monitoring window.
The windows are separated by two or three lines according to the
number of active windows. They inform you of the state of the
system and of some function keys.
The monitoring window has two differents functions according to the
mode, connected or disconnected:
■ In the disconnected mode, you can receive the traffic of a
station in this window (See "FEnetre" command paragraph "4.1
Local commands." on page 59). The traffic will be reproducted
correctly in the case of the TNC2 as you can receive it if you
were connected, unless the repetitions that you will receive
each time. The packet path will be displayed on the line
underneath this window.
If you give a string instead of a callsign all the packets
containing this string in the path will be displayed in this
window and the line underneath will display the filter.
■ In the connected mode, the monitoring window receive the
traffic, except your packets. This window don't work in the Yapp
transfer mode because the TNC2 is in the TRANSPARENT mode. This
possibility is ONLY for the TNC2. Don't try it on other TNCs !!
Commands for the main screen management:
■ Command "CHat NbLines" defines the height of the traffic window
in connected or disconnected mode, measured from the top of the
screen.
NbLines mini = 4
NbLines maxi depends of the value of "FChat" and "FEnetre"
■ Command "FChat NbLines" defines the height of the monitoring
window in the connected mode, measured from the top of the
screen.
Configurations and setting up of TPK. 82
Terminal PacKet TPK v1.81
This mode is activated by:
- "RXblock ON" validation of the block mode of the TNC2
- "MCon ON" validation of the monitoring in the connected mode
for the TNC2.
If these two commands are activated the traffic will be
displayed in the monitoring window.
REMEMBER : this is ONLY valid for the TNC2 !
■ Command "FEnetre" has different functions:
- "FEnetre NbLines" defines the height of the monitoring window
in the disconnected mode.
NbLines between 3 and the number of lines on the screen minus
4.
- "FEnetre F6XYZ-n" sends all the packet coming from F6XYZ-n in
the monitoring window in the disconnected mode.
- "FEnetre "Text"" sends all the packets from which the
callsign path contains Text.
Example : with a KAM, "FE "/H"" sends all the HF traffic in
the monitoring window.
■ Command "SUpcr ON|OFF" allow supression of a <CR> added by the
TNC2 to each information packet in the disconnected mode. With
"SU ON", displaying in the monitoring window will be correct.
Put "SU OFF" on other TNCs (put it in your CONFIG.TPK file)
Summary of the main screen management:
Configurations and setting up of TPK. 83
Terminal PacKet TPK v1.81
Top of the screen
┌──┌───────────────────┬────────────────┐──┐
│ │ Disconnected mode │ Connected mode │ │
│ │ │ │ │
FEnetre──┤ │ "Fenetre" │ "FChat" │ │
or │ │ command │ command │ │
FChat │ │ │ │ │
value │ │ │ │ │
└──├───────────────────┴────────────────┤ ├── CHat
│ │ │ value
│ Traffic window │ │
│ │ │
│ "CHat" command │ │
│ │ │
│ │ │
├────────────────────────────────────┤──┘
│ Keyboard window │
└────────────────────────────────────┘
Bottom of the screen
Keys used in the main screen windows:
■ <ALT-C> will clear the traffic window.
■ <ALT-F> will clear the monitoring window.
5.3.1.4 The MHEARD screen.
The MHEARD screen is called by the <F2> key.
It is divided into two windows:
■ The upper window lists the stations heard.
(Details paragraph "2.2.1 MHEARD." on page 12)
■ The lower window lists the connections, disconnections and
remote commands received.
Return to the main screen by hitting any key. Return is automatic
after 30 seconds of keyboard inactivity.
5.3.1.5 The BACKSCROLL screen.
The BACKSCROLL screen is called by the keys:
<Home>, <End>, <PagUp>, <PagDown>
After which, you can explore the buffer with the arrow keys and the
<PGUP>/<PGDN> keys.
Configurations and setting up of TPK. 84
Terminal PacKet TPK v1.81
Return to the main screen with the <END> key or the <ESC> key.
(Details paragraph "2.3 BACKSCROLL." on page 13)
5.3.1.6 The DOS screen.
The DOS screen is obtained by the <F3> key. Return to the main
screen by the EXIT command, followed by any other key when TPK ask
it.
(See paragraph "2.10.1 Access to DOS function." on page 50)
5.3.1.7 The message listing screen.
5.3.1.7.1 Message listing window presentation.:
Key <ALT-L> to display a list of the known BBS.
■ You can select the BBS you want to consult. If there is no BBS
known, then TPK displays your personal mailbox (MSG_PRIV).
■ When you have selected the BBS, TPK displays the message list
from that BBS.
■ Remember, you can directly access the listings with the
BRoadcast command (BR <BBS> L)
5.3.1.7.2 Keys and MOUSE buttons used in the list window.:
■ <Cancel> (or <ESC> or <A>): returns you to the terminal mode of
TPK. The Last Listed message counter is NOT updated. You must
quit with <RxImm> or <RxDel> to update it.
■ <RxImm>: (or <I>) returns you to the terminal mode of TPK, and
IMMEDIATELY executes the reception of previously selected
messages.
■ <RxDel>: (or <D>) returns you to the terminal mode of TPK, and
the reception of previously selected messages will commence in
the next forward cycle. (RX delayed)
■ <CBbs>: (or <C>) changes the BBS list.
■ <Msg>: (or <M>) allows you to enter a message using the TPK
editor.
■ <RMsg>: (or <R>) reply to a message using the TPK editor. The
callsign fields are filled in by TPK and the text of the
original message is placed at the start of your reply, with each
line displayed beginning with a ">".
Configurations and setting up of TPK. 85
Terminal PacKet TPK v1.81
■ <EMsg>: (or <E>) edits a message with the TPK editor. The
callsign fields and the text is copied from the original message
into a new one which will be appended to your personal mail. The
original message still exists and must be killed otherwise it
will be forwarded.
■ <KMsg>: (or <K>) deletes a message. It will be marked as status
K and the file will be deleted from the disk. It cannot then be
recovered!
■ <PMsg>: (or <P>) copies a message to the printer.
■ <Bul>: (or <B>) command which toggles the listing of either
bulletins only, or both bulletins and private messages.
■ <File>: (or <F>) appends the message text to a file. The default
directory is the CAPTURE directory.
■ <Sel>: (or <S>) messages selection. You can select messages in
the list by the TO field and the FROM field and the @BBS field,
by a text in the subject or a text in ALL the header line, by a
DATE.
On the line below the mouse buttons you have:
■ The callsign of the BBS.
■ Last Received: the number of the last message header received
from this BBS
■ Last Listed: the number of the last message header consulted.
■ NbMes: the total number of message headers in the list.
5.3.1.8 The message editor screen.
Whilst in the Listing Window, any of the following 3 functions
automatically calls the TPK editor.
■ <Msg>
■ <RMsg>
■ <EMsg>
Four fields at the top of the screen show details of some of the
message parameters:
■ BBS: the local BBS where your message will be forwarded to.
The list of known BBSs is displayed in a menu. You MUST have at
least ONE BBS defined (by the BRoadcast command) or else an
error message will be displayed and the editor abandonned !
Configurations and setting up of TPK. 86
Terminal PacKet TPK v1.81
■ For: destination packet address
Ex: FD1CDC@F6FBB.FMLR.FRA.EU
■ Type: the type of the message, P for private, B for bulletins, T
for NTS.
■ Subject: the title of the message. If this is a reply the
original title is copied and preceeded by RE:
To modify any of these fields whilst you are in the text window,
position the cursor on the first line of text and hit the UP key.
Using editor keys.
■ <ESC>: abandons the current message and returns to the
(personal!) list. ALL text typed is lost!
■ <F2>: terminates the message. (like /EX on a BBS !!)
■ <CTRL-Y>: deletes a line. The deleted line is buffered and can
be restored using <CTRL-U>. This key also deletes text in all
the windows used for entering a filename <ALT-S> <ALT-W> in
terminal mode, <ALT-R> in the editor, <File> in the BBS listing.
■ <CTRL-U>: restores a line previously deleted with <CTRL-Y>
■ <ALT-E>: call your editor which must have been previously
initialised with the "EDITOR" command. The current text is
written in the temporary file TEMPMSG.TPK and the editor is
called with this filename as parameter.
(See command "EDITOR" paragraph "4.1 Local commands." on page
59)
■ <ALT-J>: toggles justification ON/OFF
■ <ALT-C>: toggles word wrap ON/OFF (Justification and word
wrapping are exclusive)
■ <ALT-R>: import (read) a file into the message. Text is appended
at the cursor position.
■ <F10>: save the current text in the TEMPEDIT.TPK file. You can
quit the editor and find again your text later with the key
<F9>.
■ <F9>: load the TEMPEDIT.TPK file in the editor window. This
function overwrite the current text. To append the text use
<ALT-R>.
Configurations and setting up of TPK. 87
Terminal PacKet TPK v1.81
5.3.1.9 The LOGBOOK screen.
Exploitation of the LOGBBOK screen.
When the LOGBOOK is displayed, you can edit it very simply by
moving the curseur into the field you want to modify, with the
keyboard arrows or by moving the mouse cursor into that field and
validating with the left button.
Functions of the keyboard:
■ <F1> : displays an help screen.
■ <F2> : enters the current date with the format defined by the
"LOG DATE" command into the field where the cursor is located.
■ <F3> : enters the current time with the format defined by the
"LOG TIME" command into the field where the cursor is located.
■ <F4> : change the LOGBOOK file. The list of all existing .LOG
files in the TPK directory is displayed if there is more than
one such file.
■ <F5> : search a callsign in the LOGBOOK file. Searching begin at
the beginning of the file.
■ <F6> : repeat callsign search from the cursor current position.
■ <F7> : LOGBOOK printing. It's possible to print one page,
several pages or all the LOGBOOK. Printing can take place in a
file or directly on the printer: To print give the name of the
printer for the filename : PRN or LPT1 or LPT2 or LPT3 according
to your printer configuration.
■ <F8> : add an element to the file. The implicit values are used.
You can after that enter a callsign, the times etc. You can use
this for manual use of the LOGBOOK.
■ <F10> : quit the LOGBOOK and return to the main screen.
■ <TAB> : go to next field.
■ <SHIFT-TAB> : go to the preceding field.
■ <ESC> : cancel the current modifications in the field where the
cursor is.
5.3.2 Configuration of a colour screen.
TPK supports CGA, EGA or VGA screens. The number of display lines
on the screen is specified in the following table:
■ CGA card : 25
Configurations and setting up of TPK. 88
Terminal PacKet TPK v1.81
■ EGA card : 25 or 43
■ VGA card : 25 or 43 or 50
The colours of the TPK screens are parametrable in the TPK.CFG
file.
Reminder of colour codes:
0 Black 8 Dark grey
1 Blue 9 Light blue
2 Green 10 Light green
3 Cyan 11 Light cyan
4 Red 12 Light red
5 Magenta 13 Light magenta
6 Brown 14 Yellow
7 Light grey 15 White
The colour parameters can be checked in the file COULEURS. The
command is "TYPE COULEURS". Make sure beforehand that the following
line exist in CONFIG.SYS: "DEVICE=[C:\PATH\]ANSI.SYS"
5.3.3 Configuration of a monochrome screen.
Monochrome modes (Hercule, MDA, etc) in principle are carried, but
have not been fully tried out. You must simply set the correct mode
with TPKINST. If they are not as you want, modify the parameters in
TPK.CFG, always with the COULEURS file.
Configurations and setting up of TPK. 89
Terminal PacKet TPK v1.81
6.0 TPK FILES.
These files must be situated in the TPK directory indicated in
TPK.CFG otherwise there will be a error message and abandonment of
the command.
Note: if this path is not specified in the configuration file, it
is the implicit disc and directory at the launch of the programme
which will be used by TPK. It is setted up by TPKINST.
6.1 THE TPK.CFG FILE.
The parameters in TPK.CFG are modified with TPKINST.EXE safe the
serial ports addresses and the colours.
This file is an ASCII text file and the parameters are commented.
The principle of the UPLOAD directory is explained in the paragraph
"2.5 Remote commands." on page 14 and its use can be modified by
<F5>. The DONWLOAD directory enables you to lock access to
reception into this sinlge directory, so you avoid writing files
anywhere.
You can modify and add commentaries but do not delete some
parameters. Furthermore, TPK loads its parameters in file order:
you must not modify this order !
6.2 THE CONFIG.TPK FILES.
The CONFIG.TPK files can be introduced as shown below:
FE 5
FE F6XYZ-1
ALARM F6ABC-1
MON ON
CONOK ON
CPACTIME ON
etc...
Certain command of TNC origin are therfore also managed by TPK and
take part of its functionning. "CPACTIME" command is an important
parameter allowing characters to be sent without <CR>, eg. in the
case of the TPK prompt ([TPK] >)
■ "RXblock" is used to validate the block mode in TPK.
■ "MCon" is used to validate the monitor window in the connect
mode. So that the window is active in the connected mode, you
must pass these commands to the TNC at each use of TPK, this
happens automatically by incorporating these two commands into
the CONFIG.TPK file carried out at the start of the programme.
Note: This mode is ONLY for the TNC2. Don't try to use it with
TPK files. 90
Terminal PacKet TPK v1.81
other TNCs !
■ "MYcall" is used by TPK for the personal mailer and for the
LOGBOOK.
For these commands you will get a reply from TPK AND from the TNC.
The "MOnitor" command in TPK must be abreviated as "MO" and not "M"
which stands for "Macro" !
6.3 THE DIRC.TPK FILE.
TPK files. 91
Terminal PacKet TPK v1.81
Structure of the DIRC.TPK file, commented directory.
&x:\path\ Criterion-1 Criterion-2 Criterion-N
FILENAME.EXT xxxxxx JJ/MM/AAAA HH:MM Commentaries (39 char maximum)
──────────────────────── Extra Commentaries ──────────────────────────
──────────────────────── Extra Commentaries ──────────────────────────
──────────────────────── Extra Commentaries ──────────────────────────
──────────────────────── Extra Commentaries ──────────────────────────
&x:\path\ Criterion-1 Criterion-2 Criterion-N
FILENAME.EXT xxxxxx JJ/MM/AAAA HH:MM Commentaries (39 char maximum)
& Recognition character ─┐
x:\chemin\ Access path to the file │
FILENAME.EXT Name of the file │
xxxxxx Lenght of the file ├── Created by the command
JJ/MM/AAAA Date of the file │ COMmente
HH:MM Time of the file. │
Commentaries Description of the file ─┘
Criterion-1...Criterion-N ─┐
Selection of a range of │
interest or a specific │
kind of file ├── To be added and modified
Extra commentaries │ with a text editor
If 39 characters are not │
enough ─┘
Example:
&C:\TPK\ENVOI\ PACKET TPK IBM
TPK165.ZIP 234567 10/09/1991 01:65 Programme TPK version 1.65
: New commands "/DIRC" "COMmente"
: "TNCIni" to swap a TNC in 8 bits without parity
: Menus for files transfers
: On-line help ..... etc .....
&C:\TPK\ENVOI\ TPK
TPKHELP.ZIP 87654 10/09/1991 01:00 TPK programme of outside help
: This is the help taken from TPK which can be used
: as on-line help in Desqview for example.
&C:\TPK\ENVOI\ SATELLITES
TRKSAT300.ZIP 321098 25/12/1991 03:00 TRAKSAT satellites pursuit.
In this example:
- /DIRC PACKET lists TPK165.ZIP
- /DIRC TPK lists TPK165.ZIP and TPKHELP.ZIP
- /DIRC SATELLITES lists TRKSAT300.ZIP
- /DIRC SAT also lists TRAKSAT300.ZIP
(See paragraph "2.5 Remote commands." on page 14 and "4.2 Remote
commands." on page 67)
TPK files. 92
Terminal PacKet TPK v1.81
6.4 THE EXECAUTO.TPK FILE.
File of authorised external remote commands.
If it does not exist, NOTHING is allowed.
Structure of the file for EACH authorised command:
■ Line 1 : Command
■ Line 2 : Exchange of the reception buffer on disc (Ok/No)
■ Line 3 : Number of parameters maximum (up to 18)
■ Line 4 : Authorisations for the 1st parameter
■ Line 5 : Interdictions for the 1st parameter
■ Line 6 : Authorisations for the 2nd parameter
■ Line 7 : Interdictions for the 2nd parameter
■ and so on up to the maximum number of parameters for this
command.
(See paragraphs "2.5 Remote commands." on page 14 and "4.2 Remote
commands." on page 67)
6.5 THE ON-LINE HELP FILES.
These files are ASCII text files and are therefore easily modified
with an editor. Just take into account the base structure enabling
the functionning of the on-line help.
The first line of the file contains the title of the screen
displayed at the bottom.
Eg: TPK.HLP : =[TPK commands]=
The second line contains the description of the heading of the
different sections. The heading has no particular format, except
its lenght which is limited to 74 characters. This description
enables therefore specification of it for the user.
Eg: TPK.HLP : = Command argument ==== Default ==== Description ==
Then come the different sections. Each section must begin with the
character "@" at the beginning of the line. TPK understands each
line beginning with this charcter to be a section. That which must
be displayed for the section is situated between two lines
beginning with the "@" character.
Eg. TPK.HLP:
TPK files. 93
Terminal PacKet TPK v1.81
@ALArme OFF/Call OFF ...Description
Parameters:
OFF Deletion of the alarm
Call Starts the alarm and TPK wil send out a beep on
receiving this call as the origin of a packet
@At [Time [Command]] .....2nd section.
The end of a section is therefore either the beginning of the
following one (line beginning with a "@"), or the end of the file.
(See paragraph "2.1 On-line help <ALT-H>." on page 10)
TPK files. 94
Terminal PacKet TPK v1.81
7.0 APPENDIX : EXTENSIONS TO THE YAPP PROTOCOL
These extensions are used in TPK 1.65a (and up) and FBB 5.14 and
up.
7.1 HEADER EXTENSION.
The header now carries the DATE and TIME of the file being
transmitted.
[SOH] [Len] [Filename] [NUL] [File Size] [NUL] [Date] [Time] [NUL]
The Date and Time are the values reported by DOS, coded in 4
hexadecimal characters and are sent in ASCII.
The receiver has the choice of using either extended Yapp with
checksum or normal Yapp.
■ The normal Yapp reply is RF, as before and the receiver can keep
the date and time information .
■ The extended Yapp reply is : RT Receive_TPK and is coded :
[ACK] [ACK]
If the receiver reply is RT the protocol used will be what I have
called YappC for Yapp with checksum. When the sender gets this
packet he MUST use YappC.
7.2 DATA PACKETS EXTENSION.
If the receivers reply is RT the protocol used will be YappC. The
checksum allows detection of packets corrupted along the link,
particularly on the RS232 lines where there is no error control or
correction (or it's very poor!)
Data packets : [STX] [Len] [Datas] [Checksum]
Checksum is the sum of all datas bytes in 8 bits like Xmodem. If
the checksum is bad then the receiver must send a Cancel and enters
CW state.
7.3 CRASH RECOVERY.
A new field has been added to the resume reply to tell the sender
if the receiver can use YappC or not.
Resume reply for Yapp: (as used before by TPK and FBB)
Appendix : Extensions to the Yapp protocol 95
Terminal PacKet TPK v1.81
[NAK] [Len] [R] [NUL] [Received Length] [NUL]
│ │ │
│ │ └── in ASCII as in the header
│ └── as Resume !
│
└─────── len of the following bytes
Resume reply for YappC:
[NAK] [Len] [R] [NUL] [Received Length] [NUL] [C] [NUL]
│
Tells sender I can use YappC ─────┘
When the sender gets this packet then he must also use YappC.
Appendix : Extensions to the Yapp protocol 96
Terminal PacKet TPK v1.81
INDEX
C
CONFIG.TPK 40, 46, 63, 74, 76,
77, 78, 79, 80, 83, 90
D
DCD 70, 71, 75, 78, 80
K
KAM 54, 63, 74, 78, 79, 83
P
PK232 12, 54, 70, 74, 79, 80
T
TNC2 7, 8, 12, 20, 62, 64, 65,
70, 71, 74, 75, 79, 82, 83,
90
TPK.CFG 7, 10, 53, 54, 62, 63,
70, 71, 72, 73, 76, 77, 89,
90
TPKINST 7, 10, 15, 40, 73, 89,
90
Y
YAPP 3, 19, 20, 22, 23, 24, 27,
28, 68, 82, 94, 95
YAPPC 27, 28, 95, 96
Index 97