Here is a sample of my TIC.CFG and I have pulled out the bet parts of
the TIC doc to make it a bit easyer on you. Dont forget to set the TZ
enviroment variable in your autoexec.bat file if you need any more help
on this please feel free to call or send net mail. I hope this helps and
good luck.

Bruce Odum
LifeQuest BBS
Telegard State Center
(603)432-2904 HST Duel STD
1:326/104 fido
85:857/100 ustgnet


-----------------------------------------------------------------------------

IN      E:\FD\NEWFILES             ;Sample tic.cfg setup
ZONE 1  E:\FD\OUTBOUND
ZONE 85 E:\FD\OUTBOUND
FIDO
MAIL    E:\FD\MAIL
NET  326
NODE 104
HOLD    E:\FD\TICKHOLD
QDIR    E:\FD\TICKQDIR
LISTNAME FILES.BBS
AKA 85:857/0             (aka flag A0)
AKA 85:857/1             (aka flag A1)
AKA 85:857/100           (AKA flag A2)
STOPDUP E:\FD\TICKDUPE
TEMP    E:\FD\TICKTEMP
REPLACE E:\FD\TICKOLD
QUIET
FLEA
          /-------------------dir and path of where you want the files
AREA D:\WIN_DRVR WIN_DRVR<-------tic name that you receive
     1:326/102 PASSWORD *&<--flags
          \------\-----name and password that you will be receiving or
                       sending to.

     (ONLY ONE SPACE BETWEEN AREA'S)
AREA D:\WIN_GAME WIN_GAME
     1:326/102 PASSWORD *&

AREA E:\TGUTI TGUTI
     85:857/101 PASSWORD CA2* <--Note use of AKA flag
     1:132/177 PASSWORD C
     1:326/105 PASSWORD C

------------------------------------------------------------------------------

           The format of the configuration file follows:

      IN c:\file\inbound     (This specifies the inbound area)

      ZONE 1 c:\opus\outbound  (This specifies the Outbound area)
                               (The FIRST Zone is the DEFAULT Zone)

      ZONE 2 c:\opus\outbound.002

      ZONE 3 c:\opus\out3       (Zones need not follow Binkley style)

      NET 266                          (Your Net)

      NODE 12                          (Your Node)

      HOLD c:\holddir\          (Where outbound TICs and FLEs are kept)

      QDIR c:\qdir              (MUST be defined - not yet used)


      [ListFmt %3:-13 %1]       (Alters the default format of the FILES.BBS)

      [ListName Files.Bbs]      (Alters name and/or location of FILES.BBS)

      [AKA 1:1/313]             (Adds your AKA addresses to the Seenby lines)
      [AKA 5:678/90]


      [STOPDUP [c:\tickdir]] (Optional parameter, turns on Stopdup
                               feature - Specifies where DUP files
                               are to be kept)

      [QUIET]          (Optional - Stops beeping on fatal error)

      AREA c:\file\ticktest TICKTEST
           Local ListName c:\files\RBBS.LST
           1:266/1 Passwrd1 [FLAGS]       (Where flags = [*][&][F][C|H][An])
           2:512/26 Pass2p

      [TEMP c:\ramdisk]  (Optional directory for temporary files)


      [FIDO]          (Send files as MSG attaches instead of FLO attaches)

      [MAIL c:\netmail] ( Location of Netmail - Required if FIDO specified)

      [FLEA]          (If present, tells the program to also process
                        inbound FLE files)

      [LOGPATH]       (If present, log the PATH lines to the logfile)

      [LOGSEEN]       (If present, log SEENBY lines to the logfile)

      [CRC]           (Enable CRC testing)

      [LogCRC]        (Place copy of CRC in the log)

      [Crc2Dup]       (Place copy of CRC in the DUP file)

      [NoWait]   (Prevent HATCH's re-prompt for bad FILEname or AREAname)


           The  brackets indicate optional items,  and should NOT be entered
      in the real configuration file.


                                  ( config detail )

      IN c:\netfile   This entry should point to  the  inbound  files  area.
           Directory  entries  in  the TIC configuration file may be entered
           with or without trailing backslashes,  and must reference an  ex-
           isting directory.

      ZONE  1 c:\opus\outbound  This specifies the Outbound area for zone 1.
           TIC allows multiple zones in  multiple  outbound  areas  (Binkley
           style).    The ZONE line may be repeated for as many zones as you
           are communicating with.   THE FIRST ZONE STATEMENT MUST REFERENCE
           YOUR  OWN  ZONE,  and  is used as the default zone when a control
           file (TIC or FLE) does not contain a specified zone.  The control
           file must have at least one ZONE line.

      ZONE 2 c:\opus\outbound.002  This tells the system where to place  FLO
           files  for  zone  2.   Note that a directory must be declared for
           each zone you plan to address,  even if you  run  FIDO  mode  and
           don't create FLO files.

      ZONE  3  c:\opus\out3   The directory must be specified for each zone.
           Tick does NOT assume that zones other than your own are named the
           way they are done in Binkley.

      NET 266   This line must contain your primary net number,  and is  re-
           quired.

      NODE  12      This line must contain your primary node number,  and is
           also required.  (In a future release, I'll change this so you can
           just specify your address as NET/NODE on the same line).

      HOLD c:\holddir\   This specifies the location of the "HOLDing" direc-
           tory.   This is where the outbound TIC and FLE control files  are
           stored until your mailer sends them.  It also will be used by fu-
           ture  TICK  versions  to  hold  other information as well.   This
           directory is maintained by TICK,  and should  not  contain  other
           files.   Know what you are doing before changing anything in this
           directory.

      QDIR c:\qdir  This directory should be a separate directory and should
           contain nothing.  It is not yet used,  but MUST be declared.   It
           will have a use in a future version of TICK.

      [ListFmt  %3:-13  %1]    This  optional  entry allows you to alter the
           default format of the  "Files.BBS"  file  that  TICK  has  always
           created.    The  format  may be compatible with TBBS,  RBBS,  and
           nearly any other BBS that uses an ASCII file  as  a  files  list.
           Additional  description is below.   The numbers shown in this ex-
           ample are the default parameters used if you  do  NOT  declare  a
           ListFmt.


      [ListName Files.Bbs]  Just as TICK may give you a different format for
           the FILES.BBS,  it is not restricted to the name "FILES.BBS".  It
           is possible to have it called by any legal dos filename.  You may
           locate the file in any directory,  rather than the same directory
           that  the files go to,  and you may specify that ALL descriptions
           go to the SAME file is  that's  what  you  require.    (See  more
           below).

      [AKA 1:1/313]
      [AKA  5:678/90]    These entries direct TICK to add these nodes to the
           Seenby list.   It is now possible to establish a link with chosen
           nodes  using the AKA address instead of your main address.   (See
           more below.)

      [STOPDUP c:\tickdir]    This optional line,  if present,  activates  a
           function  similar  to  the  STOPDUP program I had written to help
           limit duplicate files from being passed by Flea.  What it does is
           to keep a list of all filenames  processed  in  each  echo  area.
           Whenever a new file is received in an echo area,  the filename is
           compared to all names in the list.   If that name has  previously
           been seen, the incoming TIC or FLE file has its extension renamed
           to  BAD,  and the received file is ignored.   If you later decide
           that the file should be passed anyway,  you may  rename  the  BAD
           file  back  to  TIC or FLE,  and delete the filename from the ap-
           propriate ECHONAME.DUP file.  The next time TICK is run, the file
           will be passed.   As implied above,  when STOPDUP  is  specified,
           TICK  keeps  a  file  in  the  specified (or default,  if none is
           specified) directory for each echo area you have set up.   If the
           echotag is "NODELIST", then the file name is "NODELIST.DUP".

      [QUIET]      If this is not present,  TICK will beep should it need to
           abort with a fatal error.  Non-fatal errors will not cause a beep
           in any case.

      AREA c:\file\ticktest TICKTEST
           Local ListName c:\files\RBBS.LST
           1:266/1 Passwrd1 [*][F][&][[H][An] or [C]]
           2:512/26 Pass2p


                This structure is used to define the  echo  areas.    It  is
           analogous to the AREAS.BBS used by confmail.   For each echo, you
           use the keyword AREA, followed by the directory,  followed by the
           echotag.  The following lines are in the format shown above, con-
           sisting  of ZONE:NET/NODE PASSWORD FLAGs.   There may be up to 40
           such addresses lines present in each AREA.   An AREA ends at  the
           first  line  NOT in the ADDRESS PASSWORD format,  such as a blank
           line.   The exception is that lines beginning  with  the  keyword
           "LOCAL"  do  not  end an area if they immediately follow the AREA
           line.   These LOCAL lines are used to establish special treatment
           specific to that area only.

FLAGS---->      The  password is the password used for that particular node,
           and may be up to 8 characters.   It is  case  insensitive.    The
           other  node  must  specify the same password for your node in his
           TIC.CFG file.  The "*",  if present,  specifies that you will ac-
           cept files coming from that node.   If not present,  you may send
           files to that node, but will not accept them from him/her.

                The "&",  if present,  tells TICK and HATCH to  ignore  that
           node  when  sending files.   Files are never sent to a node which
           has the "&" flag.   If combined with the "*" flag,  that node be-
           comes  a  "receive-only" node.   You will accept file coming from
           the node,  but will NOT echo files TO it.   If the  "&"  flag  is
           present  but  the  "*" flag is NOT present,  the node may neither
           send nor receive from  you,  and  is  effectively  commented  out
           without ending the area.

                It  is  possible  to tell TICK to generate CLO and HLO files
           directly, or to generate FLO files as the default.   The way this
           is  done  is  to  append a "C" for crash or a "H" for hold as the
           last token in the system you are connecting to.   The "C" and "H"
           are  mutually exclusive.   If you attempt to use them both in the
           same line,  TICK will issue a warning,  and will treat the system
           as a HOLD.  If you are running in the FIDO mode, the MSG produced
           should  have  the Crash or Hold bits set as appropriate.   In the
           Non-Fido mode, FLOs, CLOs, or HLOs are produced.  The Address and
           password are separated by whitespace,  as are  the  password  and
           flag fields.  The FCH*& flags are in any order, but are contained
           in  a single "word".   They must NOT be separated from each other
           by spaces.

                The "F",  if present,  may be upper or lower case (as may be
           the  C  or  H),  and specifies that you will send Flea compatible
           files (FLE extension)  to  that  node  (instead  of  sending  TIC
           files).  The format of the received file is irrelevant.

                The "An" flag takes the form of the letter "A", followed im-
           mediately  by a single hex number ranging from "0" to "F".   This
           is used to designate that an AKA address is to  be  used  in  the
           link  to the node declared on this line.   Further description is
           below.

                The AREA statement,  as mentioned,  may have up to 40  nodes
           listed  for each echo.   You may repeat the AREA statement for as
           many echos as you carry.   The statement is considered to end  at
           the  first line which is not in ZZ:NET/NODE PASSWORD form.   (The
           LOCAL lines are a partial exception to this rule).

      [FLEA]   This statement tells the program that it is also  to  process
           any  inbound  FLE files as well as TIC files.   The default is to
           process only TIC format.   (Again,  you may  SEND  either  format
           regardless).


      [TEMP]    c:\ramdisk  This allows you to specify where TICK will write
           its temporary files.   Choosing a ramdisk here will speed up  the
           processing.   If this is not included in your CFG file, TICK will
           use the default directory for your temporary files.

      [FIDO]   What this will do is to have TICK create MSG attaches  rather
           than  FLO  files.    (See WARNING below!)  This should then force
           TICK to handle attaches to  messages  rather  than  creating  FLO
           files.    The  TIC's  and FLE's are still placed in the outbound.
           The code will try to put both file attaches in the  same  message
           if  there  is  room.    If  the  combined length of the paths and
           filenames exceed the 72 byte field allowed,  two messages will be
           created  instead.    The  created messages will have the killsent
           flag set,  so that your mailer may kill the message once it is no
           longer needed.  I am assuming that whatever software you are run-
           ning  will  respect  the  "killsent" flag and delete the MSG file
           which "points to" the TIC of FLE in the outbound.  What TICK does
           is to find all MSG files which are file attaches, local, private,
           have the killsent flag set, and are from "TICK .....".   It takes
           the  subject lines from MSG's meeting these criteria,  and writes
           them to a temp file.  It then looks at all TIC's and FLE's in the
           outbound(s).  Any which do not have an active MSG attach are con-
           sidered "orphans" and are deleted.

      WARNING:  DO NOT RUN TICK IN THE FIDO MODE IF YOU HAVE  ANY  TIC'S  OR
           FLE'S IN THE OUTBOUND WHICH ARE "POINTED TO" BY FLO FILES.

           TICK  will find no MSG attach,  assume that the TIC/FLE's are or-
           phans, and delete them!

      [MAIL c:\netmail]  This entry is REQUIRED if you are  running  in  the
           FIDO  mode.    It  allows TICK to find your netmail directory for
           MSG's.   If you do NOT use the  FIDO  mode,  this  entry  is  not
           needed.



      [LOGPATH]   If  present,  path  information  (present in the TIC format
           files) will be sent to your log file for future reference.   This
           is useful in determining topology.  Also, since the time and date
           that each system processed the file is included in the PATH, this
           allows  you  to see how much delay was encountered on each leg of
           the trip.

      [LOGSEEN]   If present,  all seenby lines in the received TICs or  FLEs
           are  also  logged  to  the LOG file.   This results in very large
           logs, and is only intended for debugging and finding problems.


      [CRC]  Tick generates a CRC-32 on all files that it processes.  If you
           include CRC in your CFG file,  the CRC in the  inbound  TIC  file
           will be compared to the one calculated.  If they don't match, the
           file will be failed.

      [LogCRC]    If  this is in your CFG,  the CRC-32 will be logged to the
           logfile.

      [Crc2Dup]  This will cause the CRC-32 to be stored in  the  DUP  file.
           It doesn't do anything now, but might be useful in the future.

      [NoWait]  This prevents HATCH from looping back for new input when you
           enter an incorrect FILEname or AREAname.

                              (HOW TO USE AKA'S)

           For each alternate address you are known by,  add a line  to  the
      CFG  file  beginning with the keyword "AKA",  and followed by your ad-
      dress in [zone:]net/node format.   If the  zone  is  not  present,  it
      defaults  to  the  default  zone  (the first ZONE statement in the CFG
      file).  For example:

           AKA 1:1/313

           When I place this in my CFG file, I will add both my main address
      of 1:266/12,  and 1:1/313 to the seenby list in my outbound TIC's  and
      Fle's.

           You  may specify for each node you send to,  what address you are
      sending from.  All addresses still appear in the seenbys.

           Here's how it works:  There is an additional flag for the  node's
      flag  field  (the  field  where  you  specify if that node is <C>rash,
      <H>old, <*>, etc).   If you want that node to receive from you as your
      primary address, you need make no change.  If you want to send to that
      node as an AKA, the new flag is "A", followed by the number of the AKA
      to use (from 0 to F in Hex).  The number corresponds to the order that
      you have defined AKA's in your CFG file ...  The first AKA is "0", the
      second is "1", etc.

           NOTE THAT THE NUMBERING STARTS AT '0', NOT AT '1'.

           For example,  to send to node 2:512/26  using  my  first  AKA  of
      1:1/313, I would set the node up like this:

           2:512/26 Password HA0*

           This  will  instruct TICK to communicate with that node as 1/313,
      send it HOLD, and accept files from him as well.   Since I will be now
      sending  to  512/26  as 1/313,  he must set up my node as 1/313 in his
      TIC.CFG,  and need NOT set up the dummy 266/12 as was  previously  re-
      quired.

           The number after the "A" must be a single character, and must not
      be separated from the "A" by a space

                     (SET UP OF THE TZ ENVIROMENT VARIABLE)

           In addition to the CFG file,  you should set the TZ environmental
      variable  to  the difference between local time and GMT.   This is the
      same variable used by Opus and many other bbs-related programs.    For
      the Eastern time zone,  it would be set to TZ=EST5EDT.   In your batch
      file, have the line:

           SET TZ=EST5EDT  <--THIS MUST BE IN YOUR AUTOEXEC.BAT

           This variable is not needed for TICK to run;  but  if  the  time-
      stamps  in the PATH statement are to be meaningful,  it should be set.
      If it is NOT set, it defaults to the Pacific time zone.   This was not
      MY  decision,  but rather was the decision made by Microsoft when they
      coded their comilper.   When time-released  versions  of  TICK  become
      available,  it  will  be  necessary  to  set this variable so that the
      release time will be proper.   WARNING: Bob Germer pointed out  to  me
      that  this form of TZ variable can cause problems for Opus,  depending
      on what version of DOS you run.  If you experience problems with other
      programs using this TZ string, you could use the form:

           SET TZ=EST5

           This will work for both TICK and Opus.   Its disadvantage is that
      you  will  need to change the "5" to "4" during daylight savings time.
      The first format will give the correct results within TICK in standard
      and in daylight time zones without the  need  to  manually  alter  the
      string.    An  alternative  would be to set the EST5EDT format in your
      batch file that calls TICK, and reset it to the EST5 format after TICK
      has been run.


