home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
WILDCAT
/
WTICK103.ZIP
/
WILDTICK.DOC
< prev
next >
Wrap
Text File
|
1994-02-24
|
17KB
|
442 lines
Wildtick - The Simple TIC processor for Wildcat 3.x
v1.00 Official Release
Copyright (C) 1994
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 many 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 option to create a message for
upload to your bbs about your new files, to create or update
a "runlater.txt" for your virus scanner, the option to "passthrough"
files to other directories without creating a message or updating
your Wildcat file database, and the option to create a bullx.bbs/
hellox.bbs to announce your new files to your users.
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. There are two configuration files you have to set up
first, Wildtick.cfg and Wildtick.bbs, otherwise Wildtick won't do
very much, and they must exist in the same directory as the directory
from which Wildtick.exe is called. 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
Wildtick.cfg is a simple text file that tells Wildtick about your
system. The format of Wildtick.cfg is simply
STATEMENT=VARIABLE
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 and all the Statements and Variables
are explained.
; 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 BBSID, UPLOADER, REPLY,
;SUBJECT, CONF, HEADER, CLOSER, TAGLINE, PACKER,
;INBOUND, WCDIR, QWKDIR, SCANLIST, REPORT and BULL
;
;BBSID 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".
;If you do not want to create a message for your BBS, leave this
;field blank.
;Maximum Length = 8
; [--------]
BBSID=TOAST
;If you don't want a message to be uploaded, use
;BBSID=
;
;UPLOADER 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 UPLOADER is not specified, the default "SYSOP" will be used.
;Maximum Length = 25
; [-------------------------]
UPLOADER=LAWRENCE GORDON
;
;REPLY is to whom you wish to post your message.
;If REPLY is not specified, the default "ALL" will be used.
;Maximum Length = 25
; [-------------------------]
REPLY=ALL
;
;SUBJECT is the information you want in the .REP subject line.
;If SUBJECT is not specified, the default "New Files!" will be used.
;Maximum Length = 25
; [-------------------------]
SUBJECT=New Files!
;
;CONF is the message area on your board to post the .REP to.
;We don't advise using 0 as your upload conference area.
;This field is required only if you direct Wildtick to create
;a message for uploading to your BBS.
;Maximum Length = 7
; [-------]
CONF=2
;
;HEADER can be used for information to your callers.
;If HEADER is not specified, the default "The following files
;have been received:" will be used.
;Maximum Length = 65
; [-----------------------------------------------------------------]
HEADER=The following files have been received:
;
;CLOSER can be used for additional information to your callers.
;If CLOSER is not specified, the default "Now available for download."
;will be used.
;Maximum Length = 65
; [-----------------------------------------------------------------]
CLOSER=Now available for download or file request.
;
;TAGLINE is any tagline you want to give your message.
;If TAGLINE is not specified, the default "The simple TIC processor
;for Wildcat!" will be used.
;Maximum Length = 60
; [------------------------------------------------------------]
TAGLINE=The simple TIC processor for Wildcat!
;
;PACKER 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 PACKER is not specified, the default "PKZIP" will be used.
;Maximum Length = 64
; [----------------------------------------------------------------]
PACKER=PKZIP
;PACKER=ARJ a
;PACKER=PKPAK
;PACKER=LHA a -m
;
;INBOUND is the directory in which your .TIC files can be found.
;Do not use a trailing backslash in your directory name.
;This field is required.
;Maximum Length = 64
; [----------------------------------------------------------------]
INBOUND=C:\FD\FILE
;
;QWKDIR 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
; [----------------------------------------------------------------]
QWKDIR=C:\LOADS\
;
;WCDIR is the location of your WC30 directory. Wildtick must be
;able to find both WCFILE.EXE and TOMCAT.EXE in this directory.
;Do not use a trailing backslash in your directory name.
;This field is required.
;Maximum Length = 64
; [----------------------------------------------------------------]
WCDIR=C:\WC30
;
;SCANLIST is a text file to write to have your virus scanner run on the
;received files. Include full path and file name.
;If SCANLIST is not specified, the default "RUNLATER.TXT" will be used.
;Maximum Length = 64
; [----------------------------------------------------------------]
SCANLIST=C:\WC30\TS.LST
;
;REPORT is the Wildtick Log file. You can now specify a name and
;directory for your log file.
;Maximum Length = 64
; [----------------------------------------------------------------]
REPORT=C:\FD\WILDTICK.LOG
;
;BULL is the name of the bulletin or hello .bbs to create for advising
;your callers of your new incoming files. It is not required if you
;don't wish to create a bulletin. Use a full path and file name of
;your choice.
;Wildtick will only create 1 bulletin/hello file.
BULL=C:\WC30\BULL\BULL13.BBS
;BULL=C:\WC30\DISP\HELLO4.BBS
;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 must contain 4 arguments.
;
;Argument 1: The TIC area name. This can be no more than 8 characters.
;Argument 2: File Area Description for your callers.
;Argument 3: The Wildcat file directory to move the files to. This must be
;terminated with the backslash "\".
;Argument 4: The file area number as found in MAKEWILD or P for a
;"passsthrough" file area.
;
;The File Area Description is new. Separate all words in the description
;with the underscore "_" character.
;
;All directories must be terminated with the backslash "\".
;
;The file area number must be included.
;
;If you only want Wildtick to move incoming files to a new directory
;without creating a message and updating your Wildcat file database,
;use P for the Makewild Number.
;
;There is no longer any requirement for separating the arguments
;by one space.
;
;TIC Area File Area Description Wildcat Directory Makewild No.
NODEDIFF Fidonet_Nodediff C:\IM\NODELIST\ P
TOADNET Toadnet_Files C:\IM\NODELIST\ P
; note that the Makewild Nos. above are P for Passthrough
PDNBASIC Programming_-_BASIC C:\WC30\PROGBAS\ 15
; ^ ^ note the underscores
OLR_BETA OLRNET_Beta_Test C:\WC30\OLRBETA\ 24
OLR_DEV OLRNET_Development_Programs C:\WC30\OLRDEV\ 25
OLR_MSGB OLRNET_Messagebase_Tools C:\WC30\OLRMSGB\ 26
OLR_MISC OLRNET_Miscellaneous_Files C:\WC30\OLRMISC\ 27
OLR_PNT OLRNET_Point_Related_Files C:\WC30\OLRPNT\ 28
OLR_QNET OLRNET_QWK_Networking_Files C:\WC30\OLRQNET\ 29
OLR_READ OLRNET_Readers C:\WC30\OLRREAD\ 30
OLR_UTIL OLRNET_Utilities C:\WC30\OLRUTIL\ 31
SOFTDIST SDS_Files C:\WC30\SOFTDIST\ 32
UTILNET UTILNET_Files C:\WC30\UTILNET\ 33
WDN_DOOR WDNET_Wildcat_Door_Programs C:\WC30\WDNDOOR\ 34
WDN_WC3 WDNET_Wildcat_Utilities C:\WC30\WDNWC3\ 35
IM_BETA IMNET_InterMail_Beta_Versions C:\WC30\IMBETA\ 36
IM_DEMO IMNET_InterMail_Demos C:\WC30\IMDEMO\ 37
IM_UTIL IMNET_InterMail_Utilities C:\WC30\IMUTIL\ 39
;
;That's all folks!
Set up all your TIC file areas and you'll be fine. If you
omit a TIC area, Wildtick will create a TIC_AREA.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 INBOUND directory. It is safe to erase them. The particular
.MSG files are TEST.MSG, TEMP.MSG, REPLY.MSG, PASS.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.
H. WTICXYZ.BAT
In order to circumvent the out of memory error generated
with some configurations, WILDTICK now creates this file
in Wildcat's home directory. It may be erased after a
call to Wildtick, or it can be left alone.
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 or passthrough directories.
D. Wildtick optionally creates a REP file and calls TOMCAT to
upload it to your bbs in the proper conference.
E. Wildtick optionally creates a bullx.bbs or hellox.bbs
announcing your new files.
F. Wildtick calls WCFILE to add the new files to Wildcat.
G. Wildtick is done.
VII. Operating Tips/Support
This program has been tested on single-node, multitasking,
networked, and Desqview platforms, and it appears to work on all,
but I cannot guarantee that it will work on yours, no matter what
your configuration is. All Wildtick is guaranteed to do is take
up space on your harddrive.
Users with problems may obtain support by following these rules:
1. Report all problems to me via netmail at Fidonet 1:100/560.
All reports should tell me the version number of Wildtick, your
directory information, your system configuration, and a copies
of your WILDTICK.ERR, WILDTICK.CFG and WILDTICK.BBS files.
Please archive this files and name them something like
USER.ZIP where USER is your name.
2. 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.
3. 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.
VIII. Registration
Wildtick is distributed under the Shareware concept: fully functional,
no "nag screens" and non-crippled in any way. It does not require
a key file and will not stop running after a particular length of
time. Be that as it may, if you use it please register it. A
registration form is included with the archive.
IX. Trademarks, Copyrights, etc.
Wildcat, WCFile and Tomcat are copyrighted by Mustang Software, Inc.
PKZIP is copyrighted by Phil Katz and PKWARE.
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 02/09/1994