home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 1
/
crawlyvol1.bin
/
bbs
/
tic_talk
/
tic_talk.doc
< prev
next >
Wrap
Text File
|
1994-02-15
|
4KB
|
87 lines
TIC_TALK documentation
Version 2.20, 15 February 1994
Copyright (c) 1993 byt GRUNT Software and Rich Tietjens
All Rights Reserved
TIC_TALK is Freeware! It is copyrighted, so you aren't allowed to alter
the program in any way, nor sell it for profit (on-line services and PD
libraries may charge a small access fee; "membership" BBSes may _NOT_
distribute this software if a fee is charged for access).
"Wot's it for, then?"
TIC_TALK is for Express BBS and ST-Keep sysops who would like to have file
descriptions automatically generated from TIC files. It is completely
automatic, and so far bug-free (Ha! We'll see how long that lasts!).
*** Version 2.20 changes the way that TIC_TALK looks for the file
area and description in the TIC files, hopefully eliminating the
spurious filenames generated by previous versions.
Setup:
Look at the sample file TIC_TALK.CTL provided in this archive.
It should look like this:
F:\BT\INB\
F:\BT\KNOWN\
F:\BT\PROT\
ST-Keep
K:\BT\STICK.CTL
F:\LOGS\TIC_TALK.LOG
YES
5
Each line means something important to TIC-TALK, and if any of them is
missing, TIC_TALK will simply exit without doing anything.
Line 1: Path for normal inbound files (as in Binkley.Cfg)
Line 2: Path for "known" inbound files (as in Binkley.Cfg)
Line 3: Path for "protected" inbound files (as in Binkley.Cfg)
Line 4: ST-Keep or Express
Line 5: Full path and filename of your STick Control File
Line 6: Full path and name of your Tic-Talk Log. May be the same as your
Binkley log; Tic-Talk does NOT limit file size on the log file, so
you need to do so either manually or by letting Binkley handle it.
Line 5: Fix CRC lines in the TIC file; YES or NO expected.
Line 7: Log Level: Level 1 reports the least amount of info;
Level 5 reports every little detail.
All paths _MUST_ end with a backslash. If you leave one out, TIC-TALK will
probably exit without doing anything. You certainly won't get the expected
results.
The BBS type (ST-Keep or Express) is case-independent, which means that
Uppercase, lowercase, or mixed cases are OK. TIC_TALK uses this line to
determine where to put your file descriptions.
IMPORTANT: You MUST create a FILES or DESC folder in each path listed in
your STICK or AUTOFILE control file, or TIC_TALK won't know where to put the
descriptions it creates when an area is not found. Don't put the names in
the control file, just create the folders. If you are running ST-Keep, just
create a room for each of the indicated paths; then create a file
description for any file in the room (put one there, if need be) and ST-Keep
will create the FILES folder for you.
Fixing CRC lines: AUTOFILE is case-sensitive; a CRC line in a TIC file
must start with an all-uppercase "CRC" or AUTOFILE won't recognize it. In
order to fix this, TIC_TALK will rewrite the TIC file with a mixed-case or
all-lowercase CRC line, putting it into uppercase. If you don't want
TIC_TALK to do that (or you don't need it), just put NO on Line 6 of the
TIC_TALK control file.
Running TIC-TALK:
TIC-TALK may be run from the desktop, from Semper's Function or Execute
dialogue, or from a command line interpreter such as Pcommand or Tomshell.
It requires the full path and filename of the setup file that you decide to
use. Here's my command line:
TIC_TALK k:\bt\tic_talk.ctl
This tells TIC-TALK where to find the setup file, which in turn tells it
where to work.
Enjoy!
- Rich Tietjens aka "Captain Blade" aka "Guido the Torpedo"