home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR4
/
WTICK982.ZIP
/
WILDTICK.DOC
< prev
next >
Wrap
Text File
|
1994-01-03
|
15KB
|
411 lines
Wildtick - The Simple TIC processor for Wildcat 3.x
v.982 Open Beta Test
Copyright (C) 1993
Lawrence Gordon
All Rights Reserved
I. What is Wildtick?
Wildtick is a simple to use TIC-processing system for Wildcat BBS
version 3 and higher. It is very fast, it is very small, and it
is very easy to set up and use. It integrates with software you
already have: Tomcat and WCFile.
Wildtick is designed specifically for "end nodes"; there is no
"hatching" or file forwarding ability. For the majority of Wildcat
sysops, however, it should do the job - moving files from your mailer's
inbound directory to Wildcat and updating your Wildcat file databases.
Wildtick also has a couple of other features that make it a great
tool for the Wildcat sysop: the ability to create a message for
upload to your bbs about your new files, and to create or update
a "runlater.txt" for your virus scanner.
II. How does Wildtick work?
Wildtick can run "stand-alone" or can be called from a batch file.
Quite simply, all you have to do is type "Wildtick". It takes no
arguments. Pretty simple, eh? Of course, there are two configuration
files you have to set up first, Wildtick.cfg and Wildtick.bbs,
otherwise Wildtick won't do very much. A simple batch file to
call Wildtick might look like this:
@echo off
bnu /l:1=38400,8N1 /F
:loop
c:
cd\fd
fd /nounpack
if errorlevel 250 goto mail_in
if errorlevel 245 goto call_bbs
if errorlevel 240 goto mail_out
if errorlevel 10 goto user_break
if errorlevel 0 goto stop_bat
:mail_in
c:
cd\fd
wm toss netmail
if exist c:\fd\file\*.tic goto tic_in
goto loop
:call_bbs
call DOBBS.BAT
goto loop
:mail_out
c:
cd\fd
wm scan netmail
goto loop
:tic_in
c:
cd\fd
wildtick
goto loop
:user_break
goto stop_bat
:stop_bat
bnu /u
exit
This batch file assumes that Wildtick.exe is in your C:\FD directory
and that the configuration files, Wildtick.cfg and Wildtick.bbs are
there, too. In fact, Wildtick won't run unless they are in the same
directory.
III. Configuring Wildtick - Part 1 - Wildtick.cfg
You have to have Wildtick.cfg, or Wildtick won't work. It is nothing
but a simple text file, but it _must be set up correctly_. A
sample .cfg file is included. Edit it to reflect your setup and name
it Wildtick.cfg. Pay attention to what you're doing! The sample.cfg
file is included here in its entirety. Memorize it like your life
depends on it!
; Wildtick Configuration File - Wildtick.cfg
;
; All statements must begin at Column 1.
; Leave no blank spaces after the "=" sign and the variable
; Maximum variable lengths are indicated by the dotted lines
; between "[" and "]" and "Maximum Length = x"
; All comments must begin with ";"
; Some directories must be terminated with the "\" character
; and some should not. Pay careful attention to the instructions
; in the file.
;
;The correct format is STATEMENT=VARIABLE
;The STATEMENT must be capitalized!!!!!!!
;
;All STATEMENTs must have a variable
;
;STATEMENTs used by Wildtick are REPNAME, REPFROM, REPTO,
;REPSUBJECT, REPCONF, REPHEADER, REPCLOSER, REPTAG, REPPACKER,
;REPTIC, REPDIR, REPFILES, and REPLATER
;
;REPNAME is the name you give to the .REP file created by Wildtick
;Wildtick will create a QWK-style .REP packet for upload to your
;BBS. In the example, the reply-packet will be named "TOAST.REP".
;This field is required.
;Maximum Length = 8
; [--------]
REPNAME=TOAST
;
;REPFROM is the name you wish to use as the message poster in your
;REP file. This should be your name and should be capitalized.
;If REPFROM is not specified, the default "SYSOP" will be used.
;Maximum Length = 25
; [-------------------------]
REPFROM=LAWRENCE GORDON
;
;REPTO is whom you wish to post your message to.
;If REPTO is not specified, the default "ALL" will be used.
;Maximum Length = 25
; [-------------------------]
REPTO=ALL
;
;REPSUBJECT is the information you want in the .REP subject line.
;If REPSUBJECT is not specified, the default "New Files!" will be used.
;Maximum Length = 25
; [-------------------------]
REPSUBJECT=New Files!
;
;REPCONF is the message area on your board to post the .REP to.
;This field is required.
;Maximum Length = 7
; [-------]
REPCONF=2
;
;REPHEADER can be used for information to your callers.
;If REPHEADER is not specified, the default "The following files
;have been received:" will be used.
;Maximum Length = 65
; [-----------------------------------------------------------------]
REPHEADER=The following files have been received:
;
;REPCLOSER can be used for additional information to your callers.
;If REPCLOSER is not specified, the default "Now available for download."
;will be used.
;Maximum Length = 65
; [-----------------------------------------------------------------]
REPCLOSER=Now available for download or file request.
;
;REPTAG is any tagline you want to give your message.
;If REPTAG is not specified, the default "The simple TIC processor
;for Wildcat!" will be used.
;Maximum Length = 60
; [------------------------------------------------------------]
REPTAG=The simple TIC processor for Wildcat!
;
;REPPACKER is the archiver you want to use to bundle your .REP
;Uncomment the archiver of choice and make sure that it is in
;your path. Note well that LHA must have the -m argument!
;If REPPACKER is not specified, the default "PKZIP" will be used.
;Maximum Length = 64
; [----------------------------------------------------------------]
REPPACKER=PKZIP
;REPPACKER=ARJ a
;REPPACKER=PKPAK
;REPPACKER=LHA a -m
;
;REPTIC is the directory in which your .TIC files can be found.
;No trailing backslash!
;This field is required.
;Maximum Length = 64
; [----------------------------------------------------------------]
REPTIC=C:\FD\FILE
;
;REPDIR is the directory to move your .REP file for upload to Wildcat
;through the Tomcat mail door as defined in TCMAINT.
;Requires termination of the directory name with the trailing
;backslash "\".
;This field is required.
;Maximum Length = 64
; [----------------------------------------------------------------]
REPDIR=C:\LOADS\
;
;REPFILES is the location of your WC30 directory. Wildtick must be
;able to find both WCFILE.EXE and TOMCAT.EXE in this directory.
;No trailing backslash!
;This field is required.
;Maximum Length = 64
; [----------------------------------------------------------------]
REPFILES=C:\WC30
;
;REPLATER is a text file to write to have your virus scanner run on the
;received files. Include full path and file name.
;If REPLATER is not specified, the default "RUNLATER.TXT" will be used.
;Maximum Length = 64
; [----------------------------------------------------------------]
REPLATER=C:\WC30\TS.LST
;
;That's all folks!
There, that wasn't too bad, was it?
IV. Configuring Wildtick - Part 2 - Wildtick.bbs
You have to have Wildtick.bbs, or Wildtick won't work. It is nothing
but a simple text file, but it _must be set up correctly_. A
sample .bbs file is included. Edit it to reflect your setup and name
it Wildtick.bbs. Pay attention to what you're doing! The sample.bbs
file is included here in its entirety. Memorize it like your life
depends on it! (I know this is repetitious, but it bears repeating!)
; Wildtick BBS File - Wildtick.bbs
;
; All statements must begin at Column 1.
; All comments must begin with ";"
;
;Each line may contain 3 or 4 arguments. The fourth argument
;is the "default uploader" and is optional.
;Arguments 1, 2 and 3 are required.
;
;Argument 1: The TIC area name. This can be no more than 8 characters.
;Argument 2: The directory to move the files to. This must be terminated
; with the backslash "\".
;Argument 3: The file area number as found in MAKEWILD
;
;Argument 4: Name of the default uploader. If there is no argument 4,
; the default uploader is the person named in the REPFROM field in
; WILDTICK.CFG. If you choose to have a different default uploader,
; then any spaces between words in argument 4 MUST be delineated by
; the underscore "_" character. (See the TOADNET entry below for
; an example.)
;
;Each argument must have only one blank space between it and the
;next argument.
;
;All directories must be terminated with the backslash "\".
;
;The file area number must be included.
;
PDNBASIC C:\WC30\PROGBAS\ 16
OLR_BETA C:\WC30\OLRBETA\ 25
OLR_DEV C:\WC30\OLRDEV\ 26
OLR_MSGB C:\WC30\OLRMSGB\ 27
OLR_MISC C:\WC30\OLRMISC\ 28
OLR_PNT C:\WC30\OLRPNT\ 29
OLR_QNET C:\WC30\OLRQNET\ 30
OLR_READ C:\WC30\OLRREAD\ 31
OLR_UTIL C:\WC30\OLRUTIL\ 32
SOFTDIST C:\WC30\SOFTDIST\ 33
UTILNET C:\WC30\UTILNET\ 34
TOADNET C:\WC30\TOADNET\ 37 Toast_Master
WDN_DOOR C:\WC30\WDNDOOR\ 35
WDN_WC3 C:\WC30\WDNWC3\ 36
;
;That's all folks!
Set up all your TIC file areas and you'll be fine. If you
omit a line listing, Wildtick will create an AREANAME.BBS (for
example, TOADNET.BBS) file in your inbound directory and not move
the files to your Wildcat file areas. But if you enter information
incorrectly in the Wildtick.bbs file, your program will crash.
Are you still with me?
V. Output files.
Wildtick produces a number of output files.
A. BBS_ID.REP file.
BBS_ID.REP, where BBS_ID is the name for your bbs QWK-style
reply file. If your REPNAME is TOAST, then TOAST.REP
will be created. After execution of Wildtick, the REP
packet will be uploaded to Wildcat through Tomcat. It's
all done automatically through Wildtick.
B. WILDTICK.LOG
A log file, called Wildtick.log, is kept of all the TICs
processed by Wildtick and is found in your Wildtick directory.
Review it at your leisure, delete it at your peril!
C. WILDTICK.ERR
A log file, called Wildtick.err, is kept anytime Wildtick
exits prematurely. It contains the date, time and
description of the condition causing the premature exit.
This will help you figure out where you are going wrong,
and help me figure out where I'm going wrong.
(It won't help you figure out where I am going wrong, though.)
D. RUNLATER.TXT
This is a list of all files processed by Wildtick. You can
name this file whatever you want (e.g. TS.LST for TranScan)
and then call your virus-scanner to test them and rearchive
them as necessary.
E. XXXXXXXX.WTC
Wildtick saves all TIC files during processing with the
.WTC extension. If your program aborts for some reason,
your TIC files may be restored by renaming all *.WTC
files to *.TIC. Under normal operation, these files will
be erased.
F. *.MSG
Wildtick creates several files with the .MSG extension
during processing. Under normal operation, these will
be erased. However, program aborts may leave them in
your directory. It is safe to erase them. The particular
.MSG files are TEST.MSG, TEMP.MSG, REPLY.MSG and BBS_ID.MSG
where BBS_ID is the name of your REP file.
G. *.BBS
Wildtick creates several messages with the .BBS extension
during processing. Under normal operation, these will be
moved to your Wildcat file directories for processing by
WCFILE. Some .BBS files may remain in your directory
because a TIC file could not be associated with a Wildcat
file area. Examine the content of the .BBS to see the
associated files and descriptions and manually add them
to Wildcat using WCFILE with the name of the .BBS. Be
sure to add this area, file directory and number to your
Wildtick.bbs.
VI. The Whole Shebang
This is the sequence of events:
A. User runs Wildtick
B. Wildtick checks for TIC files.
C. If it finds any, it reads them and moves the associated files
to the proper Wildcat directories.
D. Wildtick creates a REP file and calls TOMCAT to upload it
to your bbs in the proper conference.
E. Wildtick calls WCFILE to add the new files to Wildcat.
F. Wildtick is done.
VII. Beta Testing
This version of Wildtick, and all other versions under 1.00, are
open beta tests, and are free for personal use. Wildcat sysops are
encouraged to use and abuse Wildtick to track down those nasty bugs
and quirks that I couldn't find, report them to me, and to ask for
refinements to the program (that I may or may not add when the
final program is released.)
This program has been tested on single-node, multitasking,
networked, and Desqview systems, and appears to work on all, but
I cannot guarantee that it will work on yours, no matter what your
configuration is.
Be that as it may, I still want to know if you are using it,
what your configuration is, your results and problems you might
be having with it. That is my only requirement for this beta test.
Beta Testers are also asked to do the following:
1. Send me a netmail message at FidoNet 1:100/560 to let me know
you are testing Wildtick.
2. Report all problems to me via netmail. All reports should tell
me the version number of Wildtick, your directory information,
and your system configuration, and a copy of your WILDTICK.ERR
file.
3. Read the FidoNet WILDCAT echo for messages and announcements
concerning Wildtick. I monitor the WILDCAT echo and I am
available there to answer questions and to take your heat when
the program flops on you.
4. Run Wildtick stand-alone a few times before you set it up as
an event or call it from your batch file so you can see what
it is doing and report any problems with it to me. Report
all error messages you might get, such as
"Error 76 at program line 5614".
VIII. Final Release
Those sysops that have been particularly helpful to me in the beta
test cycle will be entitled to a free copy of Wildtick when then
initial non-beta version is released.
IX. Trademarks, Copyrights, etc.
Wildcat, WCFile and Tomcat are copyrighted by Mustang Software, Inc.
PKZIP is copyrighted by Phil Katz.
Wildtick is copyrighted by Lawrence Gordon.
Lawrence Gordon
4 Waverton
St. Louis, MO 63124
BBS Phone (314) 994-0312
FidoNet 1:100/560
ToadNet 86:8012/11
Revised 01/03/1994