DP Tool Club 17/CD_ASCQ_17_101194.iso/vrac/tictac13.zip/TICTAC.DOC

Text File | 1994-08-18 | 10KB | 211 lines

This is TICTAC version 1.3 and is copyright 1994 by Stephen B. Henry.

This version adds more error checking, detects matching files already
in the Wildcat! database or associated directories and moves them
to an "oldfiles" directory while updating the database with the newer
file and information.

See the new line in TICTAC.CFG which specifies this directory. The
directory must exist as no checking is done for it nor will it be
created by TICTAC. See also the notes appended to the TICTAC.CFG
file regarding setting up that file for your system.

Note also that in this version I have standardized the trailing
backslash on _all_ drive/path entries in TICTAC.CFG. This was causing
problems in the previous versions when someone put a trailing backslash
on the paths for the batch files.

Problems with recognizing multiple drives across multiple networked
machines has been corrected. TICTAC should now work just fine on any
peer-to-peer network or any system configuration which supports Wildcat!
If you can run Wildcat! you should be able to run TICTAC. :)

Version 1.2 added more useful detail to the TICTAC.LOG and deletes
.TICs for files that are successfully added to Wildcat!'s filebase.

It also added two batch file hooks, TICTAC1.BAT and TICTAC2.BAT which
are optional and may be used for a variety of things.

TICTAC1.BAT is called (see TICTAC.CFG below) just after the program
starts but before any .TIC files are read or processed. It could be
used, for example, to move files to a processing directory and/or
unzip the ALLTICS.XXX file that comes on the Planet Connect feed.

TICTAC2.BAT is called (see TICTAC.CFG below) just after the program
completes all TIC/FILE processing and just before it would other-
wise return to Wildcat! This batch file could be used to clean up
processing directories, move un-tossed files and resulting .TAC
files to a holding directory, etc. This is ideal if you are going
to be away and need the system to process automatically without
stumbling over dregs from previous runs.

Whether or not these batch files are called and the paths to where
they are located is entered in the TICTAC.CFG file. (see below)

Version 1.1 corrected a bug that was forcing files to the default
directory regardless of area where they were supposed to go.

TICTAC is a wcCODE utility designed to run from the SysOp Menu or any
other menu hook or door or as an event. It will only work on Wildcat!
version 4.x.

This package contains the following files:

TICTAC.DOC -- this documentation file.
TICTAC.WCX -- the compiled wcCODE file.
TICTAC.LST -- the area list file (needs to be edited to your system!)
TICTAC.CFG -- the configuration file (needs to be edited to your system!)

All files should be placed in your main Wildcat! directory. Delete the
.DOC file if you don't want to waste the space.

TICTAC is a down and dirty program I wrote because I couldn't wait for
the "other guys" to get theirs finished and anything else I found was
too slow or too disk intensive, or just plain too expensive! When wcCODE
arrived it seemed like the logical way to go. Here are the results.

This file is distributed as shareware which means you are supposed to
register it if you decide to keep using it. It's fully functional, won't
expire and won't intentionally do anything nasty to your system. There
is no warranty of any kind however so if you use it you are on your own.
I will not acknowledge any responsibilty for any use to which this program
is put -- intended or otherwise.

If you like it (ie: you use it more than 30 days!) send your $10
registration fee (US or CDN is fine) to:

Stephen B. Henry
329 Simon Street
Shelburne, Ont. Canada L0N 1S4

You can get support _if you registered_ by calling AMBASSADOR BOARD at
[phone] for a full access free GUEST account at 9600 bps, or
[phone] for a PREVIEW account (you can write messages!) at 14,400
bps. For the PREVIEW account use login name: NEW USER and password: ACCESS.
You can also reach me in the MSI SupportNET as Steve Henry or by Internet
as [e-mail]. I will accept voice phone calls (at reasonable
times - eastern) but I would prefer your register first. [phone]

Those who do register will be sent the next version when it is released.
Bug fixes are free if you download them from the usual sources.
Proposed additions include message to SysOp and/or Callers re new imports.
Unlimited file areas (to the limits of your system's memory). Notification
of orphaned files. File dates or current date will be optional. And a few
other goodies.

Setup is easy. (I'm a SysOp, remember!)

1) edit the sample TICTAC.CFG file to suit your system. It is ASCII and
   has TEN lines:

   1 - drive and path to inbound files (the ones you are going to toss).
   2 - drive and path to .TIC files (can be same as 1).
   3 - drive and path for default destination directory (where to put
       files not found in TICTAC.LST).
   4 - Wildcat! file area _number_ for default area.
   5 - Description of default area.
   6 - drive and path for "oldfiles" directory (where to put files already
       in Wildcat! database that are the same as one to be processed).
   7 - Y or N - run TICTAC1.BAT or not.
   8 - drive and path to TICTAC1.BAT or "none".
   9 - Y or N - run TICTAC2.BAT or not.
  10 - drive and path to TICTAC2.BAT or "none".

Line 1 is so the program can find the files to import (it moves them to
the correct Wildcat! area)

Line 2 is where the program will look for the .TIC files. TICs with no
associated file or for which the file cannot be imported for one reason
or another (TICTAC does limited error checking) are renamed to a .TAC
extension. At this point it's up to the SysOp what they do with them
after a TICTAC run. TICs for successfully processed files are deleted.

Line 3, 4 and 5 define the default file area (such as "New Files" or
"Miscellaneous Files") which is where TICTAC will put any processable
files that do not match an area listed in the TICTAC.LST file. The Fido
area name from the TIC file is now written to the TICTAC.LOG file for
reference.

Line 6 is the drive and path to the "oldfiles" directory.

Line 7, 8, 9 and 10 set up the processing for TICTAC1.BAT and/or TICTAC2.BAT
and must contain the appropriate choice of information. There must be ten
lines in TICTAC.CFG.

A TICTAC.LST file is also needed. It is also ASCII and has one line
for each Fido area with four elements on each line. The elements are:

   1 - Wildcat! file area number as per MAKEWILD
   2 - Fido file area name as per the .TIC file (use FILEBONE.NA for
       complete list)
   3 - Wildcat! file area description as per MAKEWILD or similar
   4 - Drive and path to associated file area directory

See details in the sample TICTAC.LST file provided. Elements on each line
must start at the column numbers indicated, be no longer than the indicated
lenght and there must be four elements per line or unpredictable results
will occur. DO NOT use TABs to separate the functions, use the SPACEBAR!

TICTAC will use this information to match and process files. TICs without
associated files will be renamed with a .TAC extension. Files with no
associated .TIC file will be ignored. TICs/files that cannot be processed
will be renamed with a .TAC extension and the file left alone. TICs for
files that are successfully processed will now be deleted. Files that
match existing files in the Wildcat! database will cause the database to
be updated with the new information and the "old" file will be copied
to the "oldfiles" directory as specified in TICTAC.CFG. The associated
.TIC file will then be deleted.

Add the file to a menu (SysOp or other controlled menu is recommended!)
or as an event. To do this use MAKEMENU. A SysOp Menu item with an
unusual command choice like [@] is suggested. Remember to select "RUN
WCX FILE" as the command type and set the parameter to "TICTAC.WCX".

If no TICs are present TICTAC will cycle through it's configuration and
exit cleanly back to the BBS. It works well in unattended events. If the
process is aborted for some reason you can just start over and TICTAC
will pick up where it left off. Only in the rarest circumstances will
a file be overlooked and in that case it will remain in the "inbound"
directory.

How it works:

TICTAC starts be reading it's .CFG and .LST files and preparing the
information in those files for use.

Next TICTAC checks to see if batch file #1 was configured for use. If
so it shells to DOS and runs it.

It then looks for TICs in the indicated directory and processes them
one at a time making use of information from the .CFG, .LST, .TIC and
other system files. Files are moved to their proper directories and the
Wildcat! file database is updated with the filename, size, current date,
uploader (TICTAC) and descripton in the indicated area.

A rudimentary log file (TICTAC.LOG) is produced with enough detail to
help you track files and determine which files were not available to be
processed by orphaned TICs (renamed .TAC)

Finally TICTAC checks to see if batch file #2 was configured for use. If
so it shells to DOS and runs it.

It then returns to Wildcat!

This file has been well tested and works flawlessly on my system. It is
fast enough to make it an acceptable tool for my use. Maybe you will like
it too. The price is certainly right and I intend to upgrade and support it.
It's not flashy... I've gone Spartan in favour of speed. I hope to improve
on that in the next release too. It will never have a glitzy ANSI screen
interface. It just gets the job done.

If you have any ideas, suggestions or bug reports, please send them along
to me. The source code is not available at this time, so please don't ask.

Thanks to Ron Goodchild, SysOp of BAY AREA TECHNICAL SERVICES, Tampa Fl,
for his patience during the early stages of the development of TICTAC.

Steve Henry
August 18/94.