TIC2TAG.DOC

6.2 KB ea310d8c767a8c6f…
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
            T2T v2.0α (Alpha) Copyright 1993, All Rights Reserved
          (c) MurSoft Inc -- Jonathan G. Murray @FidoNet (1:345/28)
                     Jon's LateNite BBS (808) 834 - 1261
  T.A.G. Structures Provided Courtesy Of "Those Awesome Guys", Thanks Guys!
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*

First Beta Release, 19 Apr, 1992
First Public Release, 18 Jan, 1993
(Been a long time coming, eh?)

Disclaimer:
  This program is guaranteed to do nothing more than take up a bit of your
  precious drive space, and maybe some of your time as well.  I run it on my
  system, and that's the best assurance I can offer that it is not harmful or
  malicious.  If it breaks (or breaks something), you get to keep the pieces.

Registration:
  I ask for nothing except your undying gratitude and your everlasting
  admiration and respect for my omnipotent foresight and knowledge. Lacking
  that, a few bucks and/or a letter of thanks would be more than enough. My
  address is listed at the end of this document if you are feeling generous
  (winning lottery tickets are always happily accepted as well!)

Explanation:
  TIC2TAG is designed to read your *.TIC and *.FLE files from your inbound
  files directory, and add the descriptions to your T.A.G. BBS *.DIR files.
  TIC2TAG also generates a file named TEMP.OUT that can be imported into your
  message base for a handy little notice of what's been received.

Note:
  TIC-2-TAG, TIC2TAG, and T2T may be used synonymously within this document.
  (They all refer to the same thing)

Quick Installation:
  Read and edit the TIC2TAG.CFG file, and run TIC2TAG!

Normal Installation:
  1) UnZIP T2T*.ZIP into any directory (I recommend a directory on your path,
     but if you have one place you like to put all your T.A.G. utilities,
     that directory will be fine)

  2) Edit TIC2TAG.CFG to match your system information

  3) Add "[d:\pathname\]TIC2TAG" to your regular maintenance BEFORE you process
     your *.TIC/*.FLE files (T2T reads the *.TIC/*.FLE files and takes it's info
     from those files)

  4) Add a routine to convert the TEMP.OUT file to a message (I use
     "File2Msg", a public domain program by Jack Decker), but you could also
     use "MBUTIL POST TEMP.OUT", or whatever.

  5) Sit back and watch it work!

Sample Batch File:
===========================================
  @Echo off
  Echo Processing Inbound Files
  TIC2TAG
  TICK
  File2Msg TEMP.OUT
===========================================

Sample Configuration File (TIC2TAG.CFG)
===============================================================================
; TIC2TAG.CFG
; Tick-To-TAG Configuration File
;
IN c:\binkley\inbound\   ; { Inbound Files Directory }
;
; One default option may be selected, this will be used for all areas
; where the *.DIR file is not individually defined.  If neither option
; is selected, each 'AREA' _must_ have the *.DIR defined! ( If more than
; one default is selected, only the first will be used )
;
; DEFAULT FILES.DIR        ; Default *.DIR ( Files.Dir )
DEFAULT AREANAME.DIR       ; DEfault *.DIR ( Same as TIC AreaName )
;
LOG c:\logs\TIC2TAG.LOG ; If no LOG defined, none produced
;
; AREA definition must be the LAST item in the configuration file!
; No options listed after the 'AREA' lines will be recognized.
;
;AREA Path[filename.dir]   AREATAG    [ Uploader_Name, or ORIGIN ]
;                                              1         2         3     3
;                         [----+--8] [----+----0----+----0----+----0----+6]
;AREA f:\files1\files.dir  FILES1     ORIGIN ; Owner is Origin Address
;
; AREA lines with no *.DIR defined will assume the default.
;
 AREA d:\tag               TAGDIST    T.A.G._Distribution
 AREA d:\tagutil           TAGUTIL    ORIGIN
 AREA d:\sds\files.dir     SOFTDIST   Software Distribution
===============================================================================
Configuration File Notes:
  - TIC2TAG assumes it's configuration file name will be TIC2TAG.CFG.  If
    TIC2TAG finds TIC2TAG.CFG in the current directory, it will use that file.
    If TIC2TAG doesn't find TIC2TAG.CFG in the current directory, it will look
    in the directory TIC2TAG.EXE is located in. As an alternative, you may
    specify the configuration file on the command line, ie: "TIC2TAG
    c:\config\T2T.CFG".

  - Anything on a line after a semicolon (;) in the configuration file is
    ignored.

  - Spaces are used as dividers on a single line, extra spaces are ignored.

  - TIC2TAG can either default to "FILES.DIR", or the TIC AreaName (.DIR) for
    the TAG *.DIR file.  Only one may be used, and only the first default
    option defined will be used.

  - The TIC2TAG.LOG is optional, and if not defined, will not be produced.

  - The trailing backslash (\) on any path statement is optional, and will be
    added if left out

  - All configuration options must be placed before the 'AREA' statements.
    Any options defined after the 'AREA' statements will be happily ignored.

  - Each are that you receive files in should be defined.  TIC2TAG will simply
    not process any files for undefined areas (You will be notified in your
    log, if the 'LOG' option is defined).

  - If the word "ORIGIN" is used as 'Uploader Name', the origin address of the
    file will be placed in the *.DIR file as the Owner.

Contacting the Author:
  For the next few years (at least until summer '95 when the Marine Corps is
  scheduled to send me elsewhere) I can be reached via FidoNet Netmail at
  1:345/28, or via Jon's LateNite BBS (808)834-1261.

  If you prefer the old-fashioned kind of mail, send it to:

                Jonathan Murray
                1660-E Hilo Holly Place
                Honolulu, HI  96818-1336

Final Notes:
  All comments/suggestions/bitches/gripes/complaints (and even thanks!) are
  welcome any time.  I am of the belief that a program is never "finished", so
  if something doesn't work right, or you think a new feature would enhance
  this program, let me know!

Thanks, and any experienced "Doc-Writers" are welcome to fix this up for me!
<g>