

                                   
                                   
                                   
                                   
                                   
                                  T4
                                   
                                   
                                   
                                   
                                   
                                Manual
                                for the
                    Packet Radio Terminal Software
                             version 1.4G
                                   
                                   
                                   

                           Manual version 1.2


   Preface

   This  is version 1.2 of the manual for the version 1.4G of  the
   Packet Radio Terminal software T4.

   I   will   keep   updating  this  manual  during  the   ongoing
   development  of  T4  in order to provide  the  users  of  T4  a
   reliable handbook for the installation and usage of T4.
   In  this  document  it is assumed that the reader  is  familiar
   with  the  usage  of DOS and normal PC computers.  It  is  also
   assumed that packet radio as a part of the Amateur Radio  hobby
   is known.

   The  reader  is asked to inform the writer about found  defects
   and lacks of this document. The best way to do so is to send  a
   packet  message through the international Packet Radio Network.
   Wishes  and ideas on the improvement of this document are  also
   welcomed.
   
   
   
   
   Arsi Moilanen, OH2KME @ OH2RBT.FIN.EU
   Helsinki  the 28 th of February 1995
   
   
   
   
   
   
   
                           T4 is created by
                      Mikko Koskenniemi, OH2MKP.
                                   
                       The manual is written by
                         Arsi Moilanen, OH2KME,
                            with the aid of
                      Mikko Koskenniemi, OH2MKP.
                                   
                  Translation from Finnish is done by
                       Timo Sivula OH6KK/OH2LVZ
                                   




1 Presentation of the software

2 Installing T4
       2.1 Preparations for the installing
       2.2 Hardware
               2.2.1 The computer
               2.2.2 Required TNC
       2.3 The required files and directories
               2.3.1 T4.EXE
               2.3.2 EPURT4.EXE
               2.3.3 FlXLST.EXE
               2.3.4 SEND.EXE
               2.3.5 TEXTATTR.EXE
               2.3.6 T4-INIT.ZIP
               2.3.7 T4.INI
               2.3.8 EPURT4.INI
               2.3.9 READ.INI
               2.3.10 T4.CLR
               2.3.11 Connect scripts (.AC files)
       2.4 Using T4 without the message maintenance facility
       2.5 Memory requirements
       2.6 Startup
       2.7 TFxxx -drivers

3 The functions and commands of T4
       3.1 Keyboard commands
       3.2 Aborting commands
       3.3 Esc
       3.4 Alt-A Password solving function
       3.5 Alt-B screen blank
       3.6 Alt-C AutoConnect
       3.7 Alt-D DOS -shell
       3.8 Alt-O Options
       3.9 Alt-R Receive
       3.10 Alt-S Send
       3.11 Alt-X
       3.12 F1-F5
       3.13 F10
       3.14 Ctrl-F1 - Ctrl-F10
       3.15 Scrolling if the screen and QSO windows.
       3.16 TNC -commands
       3.17 Remote Commands
       3.18 Remote control of file commands
       3.19 T4-Editor (Alt-E)
       3.20 Connect texts

4 Message maintenance
       4.1 What unproto?
       4.2 The unproto traffic
               4.2.1 Automatic request of messagelist
               4.2.2 Manual transmission of an unproto request
       4.3 Starting the unprototraffic
       4.4 Fetching the messagelist with ALT-L
       4.5 Using the message lists
       4.6 Reading messages from the BBS (ALT-M and CTRL-M)
       4.7 Viewing the messages
       4.8 Writing messages
       4.9 Writing replys to messages
       4.10 Sending a message to the local BBS
       4.11 Marking messages to be removed
       4.12 Editing the header information of messages
       4.13 Moving messages from a list to another.

5 File transfer functions

6 Automatic functions

7 Description of the files used by T4
       7.1 *.AC files
       7.2 Epurt4.Ini
       7.3 Epurt4.Exe
       7.4 *.Lst
               7.4.1 *.Bak
       7.5 *.Num
       7.6 Read.Ini
       7.7 T4.Ini
       7.8 T4.Exe
       7.9 T4.Par
       7.10 T4.Pwd
       7.11 T4.Scr




1  Presentation of the software

   T4  is  a  Packet  Radio  terminal program developed  for  the  DOS
   operating  system. The software is compatible with the FBB  mailbox
   software  and  provides an interface for all  of  the  applications
   provided by FBB for terminal usage.

   The  T4 philosophy is to make the use of Packet Radio as a tool for
   communications easy and partly automatic. T4 can collect  both  the
   subject  lists of the messages at the users local mailbox  and  the
   messages that interest the user automatically from the local BBS.
   T4  saves  the automatically received messages on the  users  hard-
   disk.  The interactions between the mailbox and the user  are  thus
   done   automatically.  The  messages  are,  when  so   is   wished,
   transferred  in compressed form saving precious bandwidth.  As  the
   messages  are  present  on  the  HDD  of  the  user,  the  reading,
   answering  and all handling of the messages becomes very  fast  and
   simple.

   The  T4  user  can choose to have the received lists  and  messages
   distributed  in different lists according to various criteria,  ex.
   according  to who the message is sent to or from. This way,  as  an
   example, the latest DX or AMSAT bulletins can be put in own  lists.
   This way the finding of the latest bulletin becomes very simple.
   T4  provides an inbuilt editor with which messages and  replys  are
   written.  the  same  editor is also used for reading  the  incoming
   messages.

   T4  provides the possibility of 5 simultaneous connects on the same
   frequency.  There is also a monitor channel where  the  traffic  of
   the frequency in use is monitored.
   T4  programming enables through software multitasking the  listing,
   reading  and editing of messages at the same time as the  reception
   or  sending of messages is happening automatically with  the  local
   BBS.
   The  sending and reception of text and binary files is possible  on
   all  of  the  six  channels  (5 + the  monitor  channel).  If  both
   stations  are  using  T4, or the other end is a  FBB  mailbox,  the
   transfer  of  binary  files  can be done  easy  using  the  AutoBin
   protocol.



2  Installing T4

 2.1 Preparations for the installing

       Before  you  start using T4 you should know which  mailbox  you
       will  primarily  be  using  as your home  BBS  (Bulletin  Board
       System  =  Mail  Box)  .  Because of the configuration  of  the
       Packet  Mailboxes one user can only have one home BBS.  A  home
       BBS  is  the  mailbox where you regularly read  your  mail  and
       whose   callsign   is  part  of  your  Packet   Radio   address
       (@OH2RBT.FIN.EU). When visiting other mailboxes it is of  great
       importance  to  keep the home BBS information correct.  Because
       of  the  White  Pages (WP) server of the F6FBB wrong  addresses
       can spread fast thus leading to that your mail will be lost.

       If  you  have  the  possibility to choose your  Home  BBS  from
       several  mailboxes it is recommended that you  choose  the  one
       that  is  the most reliable, that you cane hear well  and  that
       hears  you  well. It is also important that the SysOp  provides
       the services and servers that you are interested of.

       It   is  also possible to use T4 without the message management
       it provides, see 2.3.


 2.2  Hardware

      2.2.1 The computer
            an  IBM PC/AT compatible computer. A couple of hundreds of
            KB  space is needed for the program files, a big amount of
            messages  can increase this need into tens of Mb.  XMS  is
            recommended. Almost any kind of display works  OK,  but  a
            colour display is nicer to look at. A VGA screen makes  it
            possible to use 50 lines screens.

      2.2.2 Required TNC
            -WA8DED compatible, as an example OHTNC V2 or other TNC2 clone
             equipped with the WA8DED Firmware EEPROM
            -Any TNC that can be used in KISS mode. In this case a TFPCR WA8DED
             emulator is used in the PC
            -BayCom (DG3RBU) modem with the help of either the TFX or the TFPCR
             TNC emulator
            
            We  recommend  the  use  of a WA8DED  compatible  TNC.  In
            Finland  the  OHTNC  V2 with a 5 MHz or faster  clock  has
            been found being reliable. The use of some kind of an  DCD
            solution  that enables the opening of the TRX  squelch  is
            also recommended.

            More   information  about  using  T4  without   a   WA8DED
            compatible TNC can be found in chapter 2.7 "Tfxx drivers"


 2.3 The required files and directories
       -Create a directory called C:\T4. Copy T4.ZIP into this directory.
       -UNZIP T4.ZIP, (PKZIP V2.0 has been used)

       More information about the files can be found inn chapter 7,
       File descriptions
       Now you ought to have the following files:
       -T4.EXE  (Possibly named according to processor  version,  like
        T4_286.EXE)
       -EPURT4.EXE
       -FIXLST.EXE
       -SEND.EXE
       -TEXTATTR.EXE
       -T4-INIT.ZIP
       
      2.3.1 T4.EXE

            T4.EXE is the actual program file that starts T4.

            The  obligatory  file is T4.INI. In order  to  enable  the
            message  maintenance the file EPURT4.INI  is  needed.  The
            colours are set in the file T4.CLR

            Different  versions  of  T4.EXE  that  are  optimised  for
            different   processors  (80xxx),   like   T4_286.EXE   are
            available.  In case you have got one of these .EXE  files,
            please  note  that your processor should be  at  least  as
            big as the name suggests. If a T4_386.EXE is started  in
            a  80286 computer the results can be unexpected halts  and
            fault situations without any warnings.

            It  has  been  noted  in practise that the  386  optimised
            T4.EXE  runs somewhat faster in 386 and 486 machines  than
            the 8088 code.

      2.3.2 EPURT4.EXE

            EPURT4.EXE   is  an  accessory  program  with   what   the
            unnecessary and old messages are removed and deleted  from
            the T4 system. The message header is removed from the .LST
            files  and  the message file itself is removed. EPURT4.EXE
            is  configured in the file EPURT4.INI. Close T4 before you
            run  EPURT4.  In some cases there have been problems  when
            using  the Windows 3.11 32-bit disk access using T4  in  a
            windows  DOS  session. On the other hand, there  are  also
            many cases when there have been no problems.

      2.3.3 FlXLST.EXE

            If  you manage to destroy or in some way spoil a .LST file
            you  need FIXLST.EXE. If the .LST files get corrupted  the
            message  maintenance facility will not work properly.  The
            probability of such a situation is very small, but as  the
            problems encountered when the LST files get corrupted  are
            quite  difficult,  this  program has  been  created.  This
            accessory  program can correct faults in the message  list
            files (.LST). Start it without parameters and you will get
            a short description on its usage.

      2.3.4 SEND.EXE

            SEND.EXE is an accessory program to help sending 7+  coded
            messages   with  T4  utilising  the  message   maintenance
            functions  of  T4.  SEND.EXE  makes  new,  unsent  N  type
            messages of  the 7+ parts. These messages are then sent to
            the mailbox automatically in normal order.
            SEND.EXE has to be started in the T4 directory. It can  be
            done either when T4 is closed or when in the T4 DOS-SHELL.
            Start  it  first without any parameters to get  the  short
            info  text  in the screen. When used for sending  SEND.EXE
            requires the following command line parameters:
            1. Callsign of the recipient (to CALL)
            2. His/her BBSs callsign (@ BBS)

3. Callsign of sender (Mycall)

4. The callsign of the mailbox you use for sending messages

            5. The name of the 7+ files ex.

      2.3.5 TEXTATTR.EXE

            TEXTATTR.EXE  is  an  accessory program  that  prints  the
            colours   and   their   combinations   and   the   numbers
            representing  each of those, on the screen. These  numbers
            are  used in T4 for defining the text colours. By  editing
            these numbers in the first column in T4.CLR you can select
            what colours T4 is to use.

      2.3.6 T4-INIT.ZIP

            If  you  are installing T4 for the first time, unzip  this
            file which holds the configuration files of T4. If you are
            updating T4 from an older version, dont unzip this  file,
            as  you  dont  want to loose the settings you  previously
            have made.

            In T4-INIT.ZIP you will find:
            -T4.INI
            -READ.INI
            -EPURT4.INI
            -T4.INI
            -T4.CLR

            Edit  T4.INI,  EPURT4.INI and READ.INI according  to  your
            personal preferences.

            Create  a connect-script for the BBS you use as home  BBS.
            (see 2.3.10)

      2.3.7 T4.INI

            This  is the main configuration file for T4. In this  file
            you will find a short description on how to edit the file.
            In  T4.INI  you define the callsign of your  station,  the
            parameters of the TNC etc.

            This file is essential when starting T4, T4 will not start
            without this file.

      2.3.8 EPURT4.INI

            In  EPURT4.INI two things are defined: The  order  of  the
            lists in the CTRL-L window and the time how long different
            types of messages are kept until they are marked old. Also
            this file contains a short description on how to edit  the
            file.  This  file  is  essential when  using  the  message
            maintenance facility of T4.
            The message lists that are intended to be used have to  be
            mentioned in EPURT4.INI in the order they are to appear in
            the  CTRL-L window. There has to be at least two  separate
            lists:

            -One with the callsign of the own station, OH2KME.LST.
             Here all the personal message that are sent to you or by
             you will appear.
            -One with the callsign of your home BBS, OH2RBT.LST, in
             this list all other messages will appear, if you don't have
             more that two lists.

            See chapter 4 for further information.

            You  can move message between selected lists, but it is  a
            lot  easier  to manage the lists if you edit  READ.INI  as
            close  as  possible  to  the final selection  as  soon  as
            possible. The parameters set in READ.INI define  how  much
            will be done automatically by T4 for you!

      2.3.9 READ.INI

            In  READ.INI you define how the message subjects  will  be
            divided  in  the many message lists of T4.  This  file  is
            essential when the message maintenance facility of  T4  is
            utilised. In this file you can exclude specified types  of
            messages  from  your  lists, and  mark  certain  types  of
            messages to be read automatically by T4, when they  appear
            at your home BBS. More about this later.

      2.3.10 T4.CLR

            This  file  defines the colours used  by  T4.  T4  is  not
            essential, without this file T4 uses the default  colours.
            If  the file exists it will be used for definition of  the
            screen  colours. If you want to find or what numbers  give
            what  colours,  try  TEXTATTR.EXE. By adding  128  to  the
            colours you will get a blinking colour.

      2.3.11 Connect scripts (.AC files)

            If  you intend to use the message maintenance facility you
            need to create a connect script for your home BBS. T4 uses
            AutoConnect  (.AC) files for this purpose.  You  create  a
            separate  file  for each station you want to  be  able  to
            reach automatically. If your home BBS is OH2RBT, the  name
            of  the file for this station will be OH2RBT.AC. The  file
            contains the route to your BBS without any C letters  like
            in  the  FBB  connect scripts. The AutoConnect  files  are
            saved in the T4 directory.

            An  example: If your home BBS is OH2RBT and it is  reached
            through  the OH2RDT-2 node, the OH2RBT.AC file would  look
            like following:

            OH2RDT-2
            OH2RBT

            If you have to use more than one node for reaching the BBS
            there  are  simply more lines in the file,  one  for  each
            node.  If the connect is direct, no nodes whatsoever  just
            one line is enough:

            OH2RBT

            When using BPQ nodes the port number has to be defined:

            OH2RDT-2
            2 OH2RBT

            Remember  that  there must be no empty  lines  and  spaces
            after  the  callsigns in the .AC files! You can check  the
            spaces by pressing HOME and END in the T4 editor and  note
            how far the cursor goes, if there are spaces simply remove
            them with backspace.

 2.4 Using T4 without the message maintenance facility

       If  you  dont want to employ the message maintenance  facility
       of  T4,  as  an  example if you just want to  test  T4,  do  as
       follows.  When  T4  is  used without  the  message  maintenance
       facility,  it  works  just like any other  terminal  programme,
       offering   5   simultaneous    channels   and   file   transfer
       facilities.

       1. Copy T4.EXE and T4.INI into the C:\T4 directory. In this case you
          must have neither the file EPURT4.INI nor the file READ.INI in the
          same directory.

       2. Edit the TNC parameter in the end of T4.INI where the monitoring
          is set. Replace MUIS or MUISC by MIS or MISC. This setting prevents T4
          from seeing the unproto traffic sent by your local BBS.

       3. Edit all details in T4.INI that have to do with unprotos and your
          home BBS. Ex make your home BBS call sign AAAAA etc.

       4. Set the Auto Unproto facility OFF in the options window (ALT-O)

       5. Do not use the ALT-U command.

 2.5 Memory requirements

       T4  has  a  so called "scrollback buffer". This can be scrolled
       by  the  user in order to read text that has been sent or  read
       previously.  There are separate buffers for each channel,  i.e.
       there  are 6 buffers. Because T4 uses colours in order to  make
       the  understanding of the screen easier one character  needs  2
       bytes.  One  line takes 160 characters, 100 lines  takes  11600
       bytes etc. The size of the text buffers are set in T4.INI

       If   XMS   memory  is  available,  T4  will  take  it  in   use
       automatically. In this case the maximum size of the buffers  is
       65  000  lines / channel. This means that the amount of  memory
       needed  is  about  10 Mb. If XMS memory is not  available,  the
       text  buffers  will be stored in conventional DOS  memory.  The
       maximum  size of the text buffer is then 400 lines  /  channel.

       Note  that the amount of free memory may decrease too much  and
       cause  problems. T4 needs about 300 KB of memory but  the  size
       is  dependent on the size of the buffers and the  size  of  the
       files  that are edited with the T4 editor. At least  50  KB  of
       free  memory must be available when t4 is being used. This  can
       be  checked out on the lower statusline the second number  from
       the left.

       The  use  of XMS memory can cause problems with the  TFPCX  and
       TFX  drivers.  If  needed,  the  use  of  XMS  memory  can   be
       prohibited but the /NOXMS parameter at start-up.

 2.6 Startup

       When  starting T4 even for the first time some of the following
       have to be connected to the COM port defined in T4.INI

       -A TNC equipped with a WA8DED EEPROM

       -A TNC in KISS mode and the TFPCR loaded in the computers memory

       -A BayCom (DG3RBU) type of modem using a TFX or TFPCR emulator.

       If  you  have to use an emulator, it has to be loaded into  the
       computers  memory  before  you start  T4.  T4  will  not  start
       without  a TNC or an emulator that emulates a TNC. See 2.7  for
       more details on the Tfxxx emulators

       T4 is started by starting T4.EXE in the C:\T4 directory

       At  first T4 empties the TNC buffers, the start-up phase can be
       a  bit  faster if the receiver is switched of during the start-
       up phase.

       Below  you  see  an example of what the C:\T4 tree  looks  like
       after you have started T4. In your case your call will be  used
       instead  of  OH2KME and the other directories will  be  created
       according  to  what  you  have  specified  in  EPURT4.INI.   T4
       performs the creation of the directories at the first  time  it
       is  started,  and  every  time when a  new  list  is  found  in
       EPURT4.INI and READ.INI.
       
       C:\
          T4\       The T4 directory, .LST, .NUM,.EXE,.AC etc.
          DECODE    The received 7+ files will be put here
             PUB    File   transfer   remote   commands   use   this
                    directory.
          OH2KME    The personal mail of the stations owner
          OH2RBT    The "general" list of your home BBS
          OH        An example of a list created in EPURT4.INI
          AUTO_TXT  The connect and macro texts
       
       The  AUTO_TXT directory has to be made by the user if he  wants
       to define his own macros and connect texts.
       In  the  normal  case,  when T4 uses  the  message  maintenance
       facility,   many   automatic  measures  are   done   in   these
       directories. More about this in Ch. 6.

 2.7 TFxxx -drivers

       TFPCR.EXE lets you use a TNC without the WA8DED EEPROM.  Do  as
       follows:

       -Set the TNC into KISS mode. Youll have to look in the manual of
        your TNC in order to find out how this is done. Use a normal terminal
        software in order to give the commands to your TNC.

       -Start TFPCR.EXE with the correct parameters (COM port etc.)

       -Start T4.EXE

       It  is  recommended that you use a batch file (.BAT) fro  daily
       use.

       If  you have a TNC without the WA8DED EEPROM the author of this
       document  (OH2KME) can provide the WA8DED TNC program  fro  the
       following TNCs: OHTNC, TNC2 clones, PK 88 and both the new  and
       old versions of PK232

       TFX.EXE  and TFPCX.EXE are used with the BayCom (DG3RBU)  modem
       and they use the processor of the PC to emulate a TNC.  TFX  is
       recommended  as  it is a lot more effective and reliable,  both
       CNAX  and  BELL work OK with it in contrary what they  do  with
       TFPCX.

       All  these  drivers  write at start a  message  on  the  screen
       informing  the user about different parameters that  they  use.
       Note  that  the  software interrupt  has  to  be  the  same  as
       specified in T4.INI

       Note  that  the  TFX and TFPCX  drivers used  with  the  BayCom
       modem have problems when working with:
       -Smartdrv
       -EMM386.EXE and QEMM386.SYS; memory management in general
       -Microsoft Mouse.Com. Possibly other mouse drivers, too.

       The  use of XMS memory can make reception very bad, when  using
       the  BayCom modem. This phenomenon is especially bad when using
       the  TFPCX  driver. Try starting T4 without having any  XMS  in
       use  with  the  /NOXMS  parameter if needed.  Dont  use  TFPCX
       unless you have to, use TFX!

       TFX  or  TFPCX will not work in the DOS session of  Windows  or
       OS/2
       

3  The functions and commands of T4

 3.1 Keyboard commands

       The following is a list of the keyboard commands.
       The commands can be used when in T4 is in normal mode.
       The commands of the editor (ALT-E) can be found in chapter 3.19.
       The commands marked with an asterisk are explained more
              exactly in Ch 4.
       
       Esc     Returns T4 towards normal mode from Editor mode, List
               mode etc.,

       Alt-A   Sends password. This function requires the file T4.PWD.

       Alt-B   Screen Blank. The screen will be back if repeating
               the command. Move  the lower status line down first.

       Alt-C   AutoConnect, choose station from the window.

       Alt-D   DOS-shell, return with EXIT.

       Alt-E   Starts the T4 editor. se Ch 3.19.

       Alt-H   Brings up a popup help, exit with Esc.

       Alt-I   Inserts an empty line in the transmit window.

       Alt-L * Fetches the subject list from the local BBS using the
               L command.

       Alt-M * Initiates message receive of marked messages to all
               lists.

       Alt-O   Options

       Alt-R   File Receive.

       Alt-S   File Send or when in editor Save File.

       Alt-T * Prints the unproto buffer status on screen in the
               format:  # / 100.

       Alt-U * Unproto request transmission to the local BBS.

       Alt-W * Initiates message writing.

       Alt-X   Closes T4.

       F1-F5   Chooses QSO channel .

       F3    * Moves messages between lists.

       F7    * Searches for messages / creates new message list.

       F10     Chooses the monitor channel.

       Ctrl-E  Echo of transmitted text to the middle window.

       Ctrl-Enter Sends command to TNC See Ch 3.16 TNC -commands.

       Ctrl-L* Listing of message lists.

       Ctrl-M* Like Alt-M, but the fetching is done only on messages
              in the chosen  list.

       Ctrl-W* Initiates transmission of messages to the BBS. This
              command must be  given on a free QSO channel of T4.

       Ctrl-F1 -
       Ctrl-F10  Include macro text in edited file or transmit macro text.


 3.2 Aborting commands

       Some  of the functions of T4 can be cancelled by repeating  the
       command  and answering the question in the opening  window.  In
       such  a window there are different alternatives to choose from.
       By  now pressing Enter the function that is labelled in CAPITAL
       letters  is chosen. Pressing ESC or any other key that  is  not
       mentioned in the window aborts the cancelling procedure.

       An  example.  You  have decided to use the AutoConnect  (ALT-C)
       function,  but  then you decide that you dont want  to  do  it
       anyway  and  want to cancel the function (before a  connect  is
       established).  To cancel the function simply press  ALT-C  once
       again  and you will see "Stop AutoConnect? (y/N)". By  pressing
       ENTER,  or  any other key except "y", you choose No,  i.e.  the
       ALT-C  function  will NOT be cancelled, if you really  want  to
       abort the function you press y.

 3.3 Esc

       When  you  are using the different facilities of T4  you  might
       notice  that  there  are  in  some  cases  several  levels   of
       facilities.  E.g. if you use the list function  (CTRL-L  )  you
       have  to  choose the list after choosing CTRL-L, this  way  you
       have  entered a second level of the facility. ESC  returns  you
       stepwise  backward towards the normal QSO mode of T4.  Thus  in
       some  cases  you will have to press ESC a couple  of  times  in
       order to get back to QSO mode.

       When  you are using the T4-editor for writing messages pressing
       ESC  brings up a windows asking if you want to save the message
       or not. More about this in Ch. 5.

       EXCEPTION!:  When  you  are scrolling trough  a  list  (CTRL-L)
       pressing  ESC  will get you out of the list, but  it  will  not
       change  the status of the new, just scrolled part of the  list.
       Using Q at this point exits the list and changes the status  of
       seen messages to seen messages. More about this in chapter 5.

 3.4 Alt-A Password solving function

       When  in connect, a SysOp can solve the password for his remote
       operated  BBS  or  Node with this function  automatically.  You
       need  to  create  a file named T4.PWD where the  passwords  are
       specified like the following:

       OH2RBT-0> ThisistheBBSpassword
       RUSA2:OH2RBT-2} Andthisisthekeytothe_TheNet_node

       As  you see, there can be passwords for several systems in  the
       same  file.  Simply  press ALT A, when you  want  to  give  the
       password for the system you are connected to.

 3.5 Alt-B screen blank

       this  function blanks the QSO screen. The function is  not  yet
       ready,  youll have to move the lower statusline  all  the  way
       down  first, in order to blank the whole screen. Pressing ALT-B
       again returns the screen.

 3.6 Alt-C AutoConnect

       This  command,  when  given on a free QSO channel,  pops  up  a
       window where the stations for which you have created .AC  files
       are  listed.  Just  choose one of these and T4  will  make  the
       connect  for you. More information about the .AC files  can  be
       found in Ch. 7.1.

            An  example: If your home BBS is OH2RBT and it is  reached
            through  the OH2RDT-2 node, the OH2RBT.AC file would  look
            like following:
            
            OH2RDT-2
            OH2RBT

            If you have to use more than one node for reaching the BBS
            there  are  simply more lines in the file,  one  for  each
            node.  If the connect is direct, no nodes whatsoever  just
            one line is enough:

            OH2RBT

            When using BPQ nodes the port number has to be defined:

            OH2RDT-2
            2 OH2RBT

            Remember  that  there must be no empty  lines  and  spaces
            after  the  callsigns in the .AC files! You can check  the
            spaces by pressing HOME and END in the T4 editor and  note
            how far the cursor goes, if there are spaces simply remove
            them with backspace.

 3.7 Alt-D DOS -shell

       Pressing  ALT-D Opens the DOS shell for you. Back you get  with
       EXIT.

       Please  note: You need at least 50 KB of free RAM in  order  to
       get  the  DOS shell functioning. If you are using NDOS or  4DOS
       you  need about 150 KB of  free RAM. Remember that when in  the
       DOS-shell  T4  is at sleep and the TNC buffers can  get  filled
       up.

 3.8 Alt-O Options

       When  you  are in some of the QSO channels (F1..F5 or F10)  you
       can  set  the  different  T4 options  by  pressing  ALT-O.  The
       settings are saved in T4.PAR and are in use also the next  time
       you  start  T4.  All  the  options are  of  on/off  type.  More
       information on the remote commands can be found in Ch. 3.17.

       -Cbell, connect bell bleeps when somebody connects you.

       -Cnax, gives a sound every time a packet is decoded.

       -Remote cmd's,  on/off. See Ch. 3.17 for more details on these.

       -Remote file cmds, permits or prohibits remote file upload or
        download.

       -Block_RX, prints the received data as packets on the screen in stead
        of printing each line separately. This function saves the resources of
        a slow computer.

       -BinRead, set compressed message reading on or off.

       -BinSend, set compressed message sending on or off.

       -ScrolLock Blink, blinks the scroll lock led when you have unread
          personal messages in your message list. Might be wise to switch of
          with TFPCX, TFX is OK with this function. The inactive time is set in
          T4.INI.

       -Auto Unproto, sends a unproto request automatically every time T4 is
        started.
       -7bit convers, makes a send-only conversion of the Scandinavian
        letters, does not affect the received text.

       Note:  When  TFPCX  is  in use CNAX and CBELL  dont  work  and
       ScrolLockBlink can cause a hang-up.

       Don't use TFPCX, use TFX with which there is no problems !

 3.9Alt-R Receive

       This  is  the  File reception facility of T4. Press  ALT-R  and
       choose  what  protocol you want to use. The  reception  can  be
       aborted by pressing ALT-R again. The default directory  to  put
       the  received  files in, is T4\PUB. If you  want  to  put  file
       somewhere else, just type the right path in the address field.

       The different options of ALT-R:

       1. Text file -saves the file as ASCII text. If you give a name that
          is already being in use, T4 will add the incoming text to the end of
          the file. The file is closed by pressing ALT-R once again.

       2. Bin file, manual reception of binary files. The reception starts
          when you press ALT-R and give the file name. The reception is ended
          when you press ALT-R once again and answer y to the upcoming question.

       3.  AutoBin. AutoBin receives and saves the binary file in  the
           semiautomatic AutoBin protocol.

           -press ALT-R, choose AutoBin and fill in the name of the file you
            are about to receive

           -send the other station the command to start sending the file you
            want to have

           -the other station answers with #BIN#1234 where 1234 is the file
            size in KB.

           -send the sending station the sign for starting the transmission:
            #OK#

           -when the file is completely transmitted the sending station adds a
            #OK# to the end of the file. T4 closes the file upon this sign
            automatically.

       4. AutoBin (FBB)  downloads completely automatically a file from FBB.
          Note that the file name has to be the name of the file in the BBS. If
          you don't want to have the file in your PUB directory put your path
          in the beginning of the filename: C:\TRANSF\T4.Zip.

       5. AutoBin (T4) -asks an other T4 station to send a file in his PUB
          directory to your station using the AutoBin protocol. If you dont
          want to have the file in your PUB directory, put the right path in
          the beginning of the filename, like previously. This function
          assumes that the other station has enabled the remote file commands
          in the ALT-O window.

 3.10 Alt-S Send

       With  this  function you can send files in the same  manner  as
       you  can receive them with ALT-R, the drive can be changed with
       F3. The transmission is aborted by pressing ALT-S again.

 3.11 Alt-X

       Closes  T4 and saves the text buffers in T4.SCR and the options
       settings in T4.PAR.

 3.12 F1-F5

       Chooses the QSO channel

 3.13 F10

       Chooses the monitor channel

 3.14 Ctrl-F1 - Ctrl-F10

       Pressing  the CTRL key and some function key lets you insert  a
       macro text at the cursor position, either into a file that  you
       are  editing  or  into  the text you are sending  in  a  live
       connect.  The  macro  texts  are  put  in  a  directory  called
       AUTO_TXT  that  is  situated under the C:\T4  directory.  These
       files can be used as headings or footer in messages etc.

       Create a directory named AUTO_TXT under the T4 directory.  Edit
       files  named C_F1.TXT, C_F2.TXT etc. The text written in  these
       files  is  then inserted at the cursors position when  pressing
       CTRL-F1, CTRL-F etc.

 3.15 Scrolling if the screen and QSO windows.

       1. F1 - F5 chooses the QSO channel-

       2. F10   Monitor channel, is also called the monitorchannel

       3. ScrolLock prohibits new incoming text from being printed on the
          screen of the chosen channel. In order not to fill the TNC buffers,
          this function has to be put off after use!.

       The  so  called 101/102 button keyboards extra keys are  used
       as follows:

       -PgUp - PgDn move the lower info line that separates the QSO window
        from the monitor window
       -Home - End Moves the cursor to the beginning or end of line.

       -Insert sets Insert mode on or off.

       -The cursor keys move the cursor on the screen.

       The  number keys function as follows in the middle window  when
       NumLock is on:

       -PgUp - PgDn scrolls the screen one page at a time

       -Cursor up or down scrolls the window

       -Home - End moves the screen either to the begin or end of the
        scrollbak buffer.

       Note  that if NumLock is not on, the number keys will  function
       as  the  extra keys in the 101/102 keyboards mentioned earlier.
       Pressing SHIFT puts the keyboard temporarily in the mode  where
       NumLock  is  on. If your keyboard is not of the 101/102  models
       try the SHIFT/NumLock function!

 3.16 TNC -commands

       T4  controls  a  TNC that is equipped with the  WA8DED  EEPROM.
       This  results in that the TNC commands are not quite  the  same
       as  those usually used. In the following there is a short  list
       of the commands. The complete list can be found as appendix.
       The  commands are given on an empty line ending with CTRL-ENTER
       pressed simultaneously.

       C Creates a Connect, ex: C OH2RBT-2

       D Disconnect,

       I Mycall, sets the callsign used by the TNC.

       T Txdelay

       O Maxframe, the maximum amount of packets sent in one burst

       The length of the packets (PACLEN) is set as follows:
       1. choose one of the QSO channels (1-5)
       2. type PACLEN 230 and press Ctrl-Enter
       3. now the selected QSO channel uses a packet length of 230.

       The  setting  of the PACLEN is individual for the separate  QSO
       channels.  The  settings are saved in T4.PAR.  Default  is  128
       characters. If your QSO is good, you can set the value to  250,
       but  if you are using nodes the length should not be more  than
       230, as the TheNet protocol uses some 10 bytes in the frame.

 3.17 Remote Commands

       Note:  These can be disabled by setting the Remote Cmds  of  in
       the ALT-O window.

       /BELL   Rings a bell.

       /BYE    Cuts the qso=disconnect.

       /CLR    Sends coloured and blinking text to the other T4 end. Try
               TEXTATTR.EXE, use the number for the combination of colours you
               want to use in the command parameter, like: /CLR 14 and follow
               this command with the text you want to send ,on the same line.
               If you add 128 to the colour code the text will blink.

       /KEY    Types the time gone since last keyboard input. Lets you
               check when the operator was there last.

       /STR     This  command lets you use the same text  colours  in
                transmission until you wish to switch back to normal text.
                This way you don't have to put the /CLR command in front of
                every line. Instead T4 now puts "/CLR" automatically in front
                of every line. The command has to be set separately for each
                and one of the QSO channels, i.e. you can use different colours
                on different channels. Please note that this and the /CLR
                command can only be used when both stations are  using a T4
                terminal.
                The command is enabled in the following manner: write the
                commands /STR /CLR14 and press CTRL and ENTER at the same
                time. Now your T4 will add a /CLR 14 in front of every line you
                transmit, you can verify this in the monitor window. This
                colour mode is disabled when you press ESC and /STR.

       /SHW2, /SHW3, /SHW4 and /SHW5 are different bells to make the other
                end alert, they work both in video and audio. Try these!

 3.18 Remote control of file commands

       /BGET FILENAME Switches the file receive (download) mode ON.

       /BPUT FILENAME Starts the sending (upload) of a file. The file will
                      be put in the PUB directory

       /DIR    Lists the contents of the PUB directory.

 3.19 T4-Editor (Alt-E)

       This  command  (ALT-E) starts the T4-editor. Please  note  that
       this same editor in different modes is in use in all of the  T4
       file view and edit functions:

       -reading of messages

       -writing of messages

       -replying messages

       -editing of normal ASCII files

       The  maximum  size  of the file to be edited is  determined  by
       either  the  maximum amount of lines (1000) or  the  amount  of
       free  memory  (at  least 50 KB). The criterion  that  first  is
       fulfilled determines the maximum file size.

       Pressing  ALT-E, when the editor is on, opens a new  window  in
       which it can be chosen whether a new file is to be edited  (L
       or  any  other  key  except i) or if a  new  file  is  to  be
       inserted  in  the  file that is currently being  edited  ("i").
       Insert starts at the line where the cursor is at the moment.

       The  file is chosen from the list in the window with the cursor
       keys  and  by  pressing enter. T4 puts the files in  alphabetic
       order. The drive can be changed by pressing F3

       The  editor commands in edit mode are as follows. (Other editor
       commands,  such  as those in use when viewing messages  can  be
       found in Ch 4.)

       -Insert switches between insert an replace mode

       -Ctrl-Backspace or Ctrl-Y deletes the line that the cursor is on

       -Home / End moves the cursor to the beginning or end of line

       -CTRL home moves the cursor to the beginning of the file

       -CTRL end moves the cursor to the end of the file

       -Page Up / Dn scrolls the file one page at a time

       -the cursor keys function as normally

       -Alt-C deletes all text in the editor, asking permission first

       -Alt-E opens a window where you can choose to either start to edit a
              completely new file (L) or insert a new file into the file
              presently  being edited (I).

       -Alt-S saves the file This files overwrites an old file with the same
              name, if there is such a file

       1. Note! T4 uses the one and same editor for viewing messages also.
          The contents of the editor is not cleared in any phase (except for
          ALT-C) so you can bring up the last edited file anytime. If you choose
          to edit a new file, this one will replace the file in the editor.

 3.20 Connect texts

       You  can  create several different texts that are sent  to  the
       stations  making a connect to your station. The text  specified
       in  T4.INI  is  sent every time to the connecting station.  The
       ones  specified  later  are sent in addition  to  the  text  in
       T4.INI.

       Create  a file named DEFAULT in the T4\AUTO_TXT directory.  The
       contents  of this file is then sent to every station connecting
       you.  If  you  wish  to  create  personal  greeting  texts   to
       different  callsigns, this is done by creating files that  have
       the  same  name  as  the  callsign of the  recipient  i.e.  the
       contents  of  the  file N5VGC will be sent  to  N5VGC  when  he
       connects your station


4 Message maintenance

 4.1What unproto?

       In  the  AX.25  protocol frames that are not addressed  to  any
       specific station are called unproto (un-protocol) frames.
       The  fabulous FBB mailbox programme uses the unproto  procedure
       to  send  information of the new messages arriving to the  BBS.
       Every  time  a  new  message is received at  FBB,  the  mailbox
       beacons it out in the following format:
       
       fm OH2RBT to FBB ctl UI pid F0
       175462 P   3 OH2LLW OH2RBT OH2KME 950206 Moikka !
       
       Here  OH2RBT  is  the FBB mailbox and it has  just  received  a
       message  from  OH2KME to OH2LLW. The line  contains  the  vital
       information  that T4 needs for the maintenance of  the  message
       lists.  These lines are either sent one at a time, at the  same
       instant  when the message arrives at the mailbox, or, they  are
       sent  in a row when this is asked for. The point is, that while
       the  frames  arent addressed to any specific  station,  anyone
       can gather a message list from these lines.

 4.2 The unproto traffic

       T4  listens  constantly  for  these  unproto  beacons.  When  a
       unproto  beacon transmission is heard, T4 checks if the message
       is  already in some of the T4 lists, if not, the message header
       is  added  to the list. If T4 finds out that there are messages
       lacking  between  the one that is in the beacon  text  and  the
       last  one that is registered in the T4 lists, T4 asks  for  the
       BBS  to list the lacking subject headers. This way there is  no
       need  for  using  the L command of FBB as the message  list  is
       kept automatically up to date.

       The  number of the last received unproto message beacon can  be
       seen  in the lower statusline as the 7th number from the  left.
       If  there  are  messages lacking in between the latest  unproto
       and  the  one received by T4, T4 uses a buffer of 100  unprotos
       to  fill in the gap. This way it is not necessary to repeat all
       the  messages since the last one listed if the gap  is  only  a
       few messages long.

      4.2.1 Automatic request of messagelist

            If  such a situation occurs, when some message headers are
            missing  from the list, it is necessary for T4 to ask  for
            repetition of these from the BBS. The message headers  are
            asked to be repeated from the first one missing onwards
            An example of such an update request:

            Unproto Update 175466
            fm OH2KME to OH2RBT ctl UI^ pid F0
            ? 0002AD6A19

            On  the  first line T4 announces to the user  that  T4  is
            about  to  request for an update of the header  list.  The
            update  request is sent as an unproto frame. In this  case
            OH2KME  asks for the headers from 175466 onwards. The  FBB
            will  reply with the asked headers, sent as unprotos.  The
            unproto  transmission starts after  a  short  while.  This
            happens,  if the SysOp has enabled this function  for  the
            user in the BBS.

      4.2.2 Manual transmission of an unproto request

            The  update request can be started also manually with  the
            command ALT-U when T4 is in QSO mode, i.e. one of the  QSO
            channels  or the monitor channel is active. As a reply  to
            the  request  the  BBS starts sending the  message  header
            information  as  unproto frames.  Please  note,  that  the
            frames are not coming as fast as in a normal AX.25 QSO, as
            the idea is not to congest the channel.

            If  T4  is  up  to  date when asking for  an  update,  the
            reaction from the BBS looks like:

            fm OH2RBT to FBB ctl UI pid F0
            175466 !!

            This tells T4 that there are no new messages, and thus  no
            need fro further update transmissions. T4 listens also for
            these  unprotos if somebody else asks for them and  checks
            whether its own lists are up to date or not

 4.3 Starting the unprototraffic

       If  you  start  a  completely new T4. whose message  lists  are
       totally  empty,  T4  will ask for ALL of the  messages  in  the
       local mailbox. The lowest message number accepted in T4 is  10,
       so  all  the  message headers from number 10  onwards  will  be
       requested  immediately when T4 sees a unproto beacon  from  the
       BBS with a header number greater than 10.

       Usually  the latest message number in the BBS is a lot  greater
       than  10, ex 175450. The maximum amount of sent unproto updates
       from the BBS is also usually set somewhere between 300 and  500
       newest  headers. This leads to that you cannot get the complete
       list  of  175440 message headers. In such a case the  BBS  will
       send  out  a unproto with a notice of this situation, in  order
       to  prohibit T4 from keeping asking for the older messages. The
       notice can look like the following:

       fm OH2RBT to FBB ctl UI pid F0
       175466 ! OH2KME

       When  T4  receives this notice, it saves the headers  that  are
       available, and skips the older ones.

       If  your  local  BBS doesnt react in any way to  the  requests
       sent  by  your  T4, you ought to contact your local  SysOp.  It
       might  be  that  you  need  to  send  the  requests  trough   a
       digipeater or the unproto facility of the BBS is not enabled.

       If  your BBS does not support the unproto system, you can still
       list  the  messages semi-automatically with the command  ALT-L.
       If  T4 is empty it can be worth considering when the time  is
       right   fro  listing  of  the  3000  latest  messages  in   the
       BBS...More about this in chapter 4.4

       The  last  message number of the T4 lists can be found  in  the
       lower  statusline as the 7th number from the left, to the right
       of the UA notation.

 4.4 Fetching the messagelist with ALT-L

       If  there is no possibility for a direct QSO to the BBS, or the
       BBS  doesnt support the unproto sending of headers, or the QSO
       is  simply  bad, the message list can be fetched by the  manual
       listing command ALT-L on a free T4 QSO channel.

       This function is also good to use when you havent had your  T4
       on  for  a  while and there are more than 300 messages  lacking
       from  your  message lists. ALT-L gets all the missing  headers,
       as the unproto system send only the 300 newest ones.

       If  you  want to prohibit T4 from starting the unproto  listing
       when  you  are using the ALT-L listing, start ALT-L on  channel 5.

       Pressing  ALT-L brings up a window with a list of stations  you
       have  created a AutoConnect (.AC) file for (see Ch 7.1). Choose
       the  BBS  you  want to take the list from with the cursor  keys
       and  pressing  enter. T4 makes a connect to the chosen  station
       and  gives  it the command LR XYZ, where XYZ is the  number  of
       the  first message you are missing. Note that this command  can
       be  seen  only  in  the  monitor  channel.  When  the  list  is
       completely received, T4 disconnects.

       Note  !  Using ALT-L requires that you have specified the  list
       format  used  by the language you use in your BBS correctly  in
       T4.INI

       The  message list is then coloured at reception. The  different
       colours have the following meaning:

       -Grey: marked as deleted in READ.INI, will not be listed in any list.
       -Green: no criterion listed in READ.INI suits to this message, it is
        thus listed in your general list.
       -Blinking green: A personal mail for your callsign.
       -Red, will be moved to some special list, specified in READ.INI OR
        will be marked with r

 4.5 Using the message lists

       Access  to the message list of T4 is gained by pressing CTRL-L.
       This opens a window where all lists that you have specified  in
       EPURT4.INI are viewed. If there are more lists that fit in  the
       window,  the  ones outside the window can be reached  with  the
       cursor keys.

       Move the cursor to the list you want to see, and press enter.
       You can exit the CTRL-L window by pressing either Q or ESC
       There  are several columns in the list. Starting from the left,
       the  first one is the type and status of the message. The  type
       is  either  personal:  P  or bulletin:  B.  There  are  several
       statuss fro the messages, more about this later.

       Note! There are two ways to exit the lists:

       1. Q: verifies that you have seen all lists, and marks the messages
          as seen.

       2. ESC does not change the status of the messages.

       The   headers   that  you  have  yet  not  seen  are   coloured
       differently  in the list and the total amount of these  can  be
       found in the New column of the CTRL-L window.

       When  you are scrolling through a message list, you can  choose
       a  specific  message  to  be read by pressing  ENTER  when  the
       cursor is on a message that has no status, i.e. the message  is
       marked  either P or B. After choosing this message with  ENTER,
       the   status  changes  to  either  Pr  or  Br.  The  status   r
       denominates,  that the message is marked for  reading,  but  it
       has  not  yet been fetched from the BBS. A personal message  is
       marked  P  before you choose to have it read, and it is  marked
       Pr after the marking.

       You  can search for a specific message by pressing F7. Fill  in
       the  search criterion and press enter. The search stops at  the
       first message that fulfils the search criterion.

 4.6 Reading messages from the BBS (ALT-M and CTRL-M)

       Enable the compressed download procedure from the options  menu
       (ALT-O).

       There are two ways to start the reading of messages marked  fro
       reading (Pr Br) from the BBS:

       1. Alt-M: First exit the list and the CTRL-L window (press q twice).
          Choose a free QSO channel and press ALT-M. This will start a download
          of all messages in all lists that are marked for reading (Pr Br)

       2. Ctrl-M: Choose the list you want to perform the fetching to and
          press enter.

       T4  fetches all messages marked for reading automatically after
       the  time set in T4.INI. This way there is usually no need  for
       manual  start  of this procedure. This function is  similar  to
       pressing ALT-M on channel 5.

       Use  channel  5  when  you use ALT-M, this  way  the  automatic
       message fetching is not started during the manual fetch.
       Both  the manually and automatically started downloads  can  be
       aborted  with the command ALT-M and answering Y to the upcoming
       question.

 4.7 Viewing the messages

       The  messages  can be viewed when T4 has downloaded  them  from
       the  BBS. Start the list (CTRL-L) and go to the list where  you
       have marked messages to be read. Now the status has changed  to
       PR  or  BR,  this  means  that the massage  can  be  viewed  by
       pressing  enter  when  the  cursor is  on  the  header  of  the
       message.  You can get back to the list by pressing enter  again
       or ESC.
       After this the status of the message changes to Y.

 4.8 Writing messages

       When  T4  is in QSO mode, i.e. one of the QSO channels  or  the
       monitor channel is active you can start writing a message  with
       ALT-W.

       Fill  in  the  missing parts in the upcoming window  and  check
       that  the pre-filled parts are OK. Pressing enter at any  point
       of  this  window starts the editor. Note that you  cannot  exit
       the  window  before all fields are filled. Write your  message.
       You  can  insert a prepared file by pressing ALT-E and choosing
       I,  as insert. The insertion will be done at the line where the
       cursor  is. When you have finished the message, press  ESC  and
       then  enter.  Here you can cancel the message if you  want,  by
       choosing the alternative you want in the window.

       Now  the  message can be found in the list with your  callsign,
       and  the status will be N. The message will then be sent either
       by  pressing CTRL-W in QSO mode or triggered by the  T4  timer,
       automatically.

 4.9 Writing replys to messages

       If  you want to write a reply to a message you can choose  from
       two ways of doing it:

       1. press r, when you are reading the message to which you want to
          reply

       2. press r when the cursor is on the header of the message you want
          to reply to, in the list.

       Fill  in  the  missing parts in the upcoming window  and  check
       that  the pre-filled parts are OK. You can move the cursor with
       the  cursor  keys. Pressing enter at any point of  this  window
       starts  the editor. Note that you cannot exit the window before
       all  fields are filled. The message header edit can be  aborted
       by pressing ESC.

       T4  copies the content of the message you want to reply to into
       the  editor  and inserts a > sign in front of every line.  This
       way  the  reader  knows  what is a comment  and  what  you  are
       commenting on. Unnecessary lines can be removed with CTRL-Y  or
       CTRL-backspace.  See more on the editor in Ch  3.19.  When  the
       reply  is  finished, press ESC and then ENTER in  the  upcoming
       window.

 4.10 Sending a message to the local BBS

       The  messages can be sent either by pressing CTRL-W in QSO mode
       on a free channel or triggered by the T4 timer, automatically.
       The  BBS to which the message is supposed to uploaded is chosen
       in  the message writing phase. The upload BBS is typed into the
       FWD  field. You can choose any BBS that you have created a  .AC
       file  for,  to be this upload BBS. Please note, that there  can
       be  messages to be uploaded to one BBS only at one  time.  When
       the message has been sent, its status becomes Y.

 4.11 Marking messages to be removed

       If  a  message  becomes unnecessary it can be  removed  in  two
       ways:

       1. When you are reading it, press k.

       2. When you are listing messages, press k when the cursor is on the
          header of the message you want to remove

       The  status of messages marked for removal is K. You can change
       the  status back to Y by pressing K once again. If there  is  a
       message  for  that  number  its  status  will  then  become  Y,
       otherwise it will be marked without any status at all.
       The  deleting of the messages is done by starting  the  program
       EPURT4.EXE  either in the DOS-shell or in DOS. In lifetimes  of
       the messages is set in EPURT4.INI.

 4.12 Editing the header information of messages

       Pressing  e  when  the  cursor is on the  header  you  want  to
       change, enables the edit of the header information.
       As  and  example: you can edit the type or status of a  message
       into  something  that hasnt been mentioned in EPURT4.INI,  and
       thus prohibit the deleting of that specific message.
       If  you  want  to temporarily prohibit the message  from  being
       deleted, you can put it on hold by changing the status to H.
       Note!  There are other FBB used message types used than  P  and
       B.  An  ACK  message has the type A, and it will  thus  not  be
       removed by EPURT4. Edit the type of this file to either B or  P
       in order to get rid of it.

 4.13 Moving messages from a list to another.

       You  can  open a window that lets you move a message  from  one
       list  to  another  by pressing F3 when the  cursor  is  on  the
       header  of  the message you want to move. Choose the  list  you
       want  to have the message moved to and press enter. If you want
       to  create a completely new list, press F7 and give the name of
       the  new  list, WITHOUT extension (.LST). The messages are  not
       sorted  in any specific order, yet. A sorting procedure  is  to
       come in later versions.

       You  can  return to the CTRL-L window by pressing ESC,  if  you
       dont  want to change the status of the messages you have seen.
       If  you  want to update the list, press q, and the messages  in
       the  list  up to the point where the cursor is, will be  marked
       as seen.


5 File transfer functions

6 Automatic functions

7 Description of the files used by T4

 7.1*.AC files

       If  you intend to use the message maintenance facility you need
       to  create a connect script at least for your home BBS. T4 uses
       AutoConnect  (.AC)  files  for  this  purpose.  You  create   a
       separate  file  for each station you want to be able  to  reach
       automatically.  If your home BBS is OH2RBT,  the  name  of  the
       connect  script  file for this station will be  OH2RBT.AC.  The
       file  contains  the  route to your BBS without  any  C  letters
       unlike  the  FBB  connect scripts. The  AutoConnect  files  are
       saved  in  the T4 directory. You need to create separate  files
       for every station you want to connect automatically.

            An  example:  If your home BBS is OH2RBT  and  it  can  be
            reached  through  the OH2RDT-2 node,  the  OH2RBT.AC  file
            would look like following:
            
            OH2RDT-2
            OH2RBT

       If  you  have  to use more than one node for reaching  the  BBS
       there are simply more lines in the file, one for each node.  If
       the  connect is direct, no nodes whatsoever, just one  line  is
       enough:
            
            OH2RBT

       When using BPQ nodes, the port number has to be defined in  the
       .AC file:
            
            OH2RDT-2
            2 OH2RBT

       Remember  that  there must be no empty lines and  spaces  after
       the  callsigns  in the .AC files! You can check the  spaces  by
       pressing  HOME and END in the T4 editor and note  how  far  the
       cursor  goes,  if  there  are spaces simply  remove  them  with
       backspace.
            
 7.2Epurt4.Ini

 7.3Epurt4.Exe

 7.4*.Lst

       The  messageheaders are stored in the files with the  extension
       .LST.  The  mesage header data is presented according  to   the
       following C- language format:
       
       #include<stdio.h>
       #include<time.h>
       
       typedef struct {
          char type         ;  /* 1   Type of message (A,B,P,T)
       */
          char status       ;  /* 1   Status of message ($,A,F,K,N,Y)
       */
          long numero       ;  /* 4   Number of the message
       */
          long size         ;  /* 4   Size of message in characters
       */
          char from[7]      ;  /* 7   Adjacent BBS giving the message
       */
          char via[41]      ;  /* 41  Route
       */
          char to[7]        ;  /* 7   To field
       */
          char title[81]    ;  /* 81  Title of message
       */
          time_t time       ;  /* 5   Date of last status change
       */
          char fwd_bbs[20]  ;  /* 20  BBS to fwd
       */
          long nro          ;  /* 4   Place in .LST file
       */
          char bid[20]      ;  /* 20  Bulletin ID   (BID)
       */
       } meslist;
       
       int main()
       {
       FILE *f;
       meslist viesti;
       
       printf("The space required by one messageheader = %d \n ",
                         sizeof(meslist));
       f = fopen("OH2MKP.LST","rb");
       if(f == NULL) return 1;
       
       while(fread(&viesti,sizeof(meslist),1,f)!=NULL)
               {printf("%10ld ",viesti.numero);
                printf("%s\n",viesti.title);
                }
       
       fclose(f);
       return 0;
       }
       
      7.4.1*.Bak

 7.5*.Num

 7.6Read.Ini

7.7T4.Ini

7.8T4.Exe

7.9T4.Par

7.10 T4.Pwd

7.11 T4.Scr

