home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-387-Vol-3of3.iso
/
t
/
tscan695.zip
/
TSCAN695.DOC
< prev
next >
Wrap
Text File
|
1992-08-29
|
32KB
|
826 lines
┌─────────────┐ ───────────── ▀▀▀▀▀▀▀▀▀▀▀▀ ───── █▀▀▀▀█
│ ┌─────────┐ │ ───────────────── █ ─────────── █
│ │ ┬ ─┐┌─┐ │ │ ───────────────── █ ▄▄▄▄▄ ▄▄▄▄▄ █▄▄▄▄▄ ▄▄▄▄▄ ▄▄▄▄▄ ▄
│ │ │ │┘ │ │ │ ───────────────── █ █ ▄ █ █ ─ █───── █ █───── █ ▄ █ █▀▀▀█
│ │ ┴ ─┘└─┘ │ │ ───────────────── █ █ ─ █ █▄▄▄█─█▄▄▄▄█ █▄▄▄▄▄ █ ─ █ █ ─ █
│ └─────────┘ │ ────────────────────────────── █
└─────────────┘ ────────────────────────── ▄▄▄▄█ Version 6.95 Standard
───────────────────────────────────────────────────────────────────────────
Copyright(C) 1990, 1991, 1992 - IBD Software, All right reserved.
Written by: Bill VanWezenbeeck and Tony Mann for TAG v2.6c1
Unauthorized Duplicate is prohibited.
───────────────────────────────────────────────────────────────────────────
.
Table of contents:
------------------
Chapter description Page
___________________________________________________________
Packing List .......................................... 1
What is TagScan ....................................... 1
The History of TagScan ................................ 1-2
Warranty .............................................. 2
Technical Support ..................................... 2
License Agreement and Copyright ....................... 2
Dos Versions and System requirements .................. 2
TagScan and Multi-Taskers ............................. 3
Setup Instructions .................................... 3
TagScan Companion Utilities ........................... 3
Converting Uploads to ZIP, ARJ or LZH format........... 3
Change Users SL/DSL ................................... 3
Adding Color to the LOG ............................... 4
Sending BEEPS to the local console .................... 4
Setting TagScan up on Multi-Node Boards ............... 4
Virus Bulletin ........................................ 4
User#.Msg ............................................. 4
Auto Ansi Detect & Carrier Monitoring ................. 4
GIF file compression .................................. 4
Adding files to the TRASHCAN.FIL ...................... 5
Work Directories ...................................... 5
Bad File "Storage" Directories ........................ 5
TagScanExitCodes ...................................... 6
Special Thanks ........................................ 6
External Programs and Utilities ....................... 7
TagScan support files ................................. 8-9
Registration Information .............................. 10
TagScan Alpha & Beta-Sites ............................ 10
Contacting the Authors ................................ 10
.
-1-
Packing List:
-------------
The following files should be included in this archive.
If not, please don't use them, instead contact me at the
address listed at the end of this DOC file...
------------------------------------------------------------------------
TSCAN695 DOC 32285 08-29-92 WHATSNEW 695 10762 08-29-92
SETUP695 EXE 55024 08-29-92 TSCAN695 EXE 86064 08-29-92
TS_NOREG TXT 1931 08-29-92 TS_REG EXE 13616 08-29-92
NOCNVRT FIL 882 08-29-92 SCREENS ZIP 4389 08-29-92
TS-TRASH CAN 1164 08-29-92 TS-TRASH DEL 1699 08-29-92
QINSTALL DOC 2534 08-29-92
------------------------------------------------------------------------
What is TagScan?
----------------
TagScan is a program that, with the use of some external programs
and some unique features of its own, allows a TAG SysOp to process
UPLOADS to their fullest... It is a complete UPLOAD manager for
TAG v2.6c1 and should now work with Mutli-node versions as well
thanks to some assistance from Victor Capton, thank you Victor.
The History of TagScan
----------------------
TagScan originated as a simple batch file that I wrote strictly to be
used on my own BBS. As people noticed it they would ask me if they
could have a copy for their own BBS, and I would give one to them. It
then became clear to me that I needed to release it so that anyone
could just download it without asking me first, thus TagScan was born.
As more people downloaded it and tried to get it to work with their BBS
it became clear that I needed to try and make it as generic as possible.
At this point I worked on the batch file for what seemed like months and
was able to improve it a little but still was not satisfied. That's when
Tony came into the picture. The two of us spent about 30-35 hours
straight (about 15lbs of coffee worth) and finally had PostUl33 ready.
The best thing was, it worked for 95% of the people that wanted to run
it.
Ever since my release of Postul version 3.03 I searched for a way to
speed-up the processing of the batch file so Tony and I decided that it
was time to learn a programming language, we chose Turbo Pascal and
began to learn. Tony approached a friend, Michael Arnette, who was just
getting started with Pascal but was a little more familiar than we were
and he offered to help. With the help of Mike we were able to get past
the rough start to of learning the new language, if fact he wrote the
first Pascal release of TagScan for us, which became a template for our
first Official Release. In a matter of a few weeks we had TagScan
(PostUl33) completely rewritten in Pascal.
After releasing v4.01 we started on the updates and advanced functions
for TagScan. To assist with some of the functions that were unclear to us
Tony approached Mitch Urquhart while, at the same time I had conversations
with a friend of mine, Mike Griffin.
.
-2-
With their help we were able to get past the next 3 speed bumps in our
quest to learn Pascal. After viewing our source code from v4.01 Mitch made
several suggestions on how to enhance the code, our function to determine
the file extension of the UPLOAD worked, but was slow so Mitch rewrote some
new functions for us. They worked great! In fact we haven't changed a thing
with them yet. Mitch also showed us the best way to determine DosErrors and
how to Trap them in Pascal. Knowing this was critical, because of the 3rd
party programs that are executed from TagScan. With all the help that Mike
and Mitch gave us we released TagScan v4.10 which was, not only better, but
faster as well...
The story continues with each new release...
Warranty
--------
No warranty is given or implied. Use this software at your own risk.
The authors of TagScan can NOT be held responsible for the use or misuse
of this software. Please read the documentation carefully before setting
this program up on your BBS. Because of the range of OPTIMIZATION that
is available to computer users these days certain software may react
differently from one system to another. Please read the Dos Versions and
system requirements paragraph later in this documentation.
Technical Support
-----------------
Technical support is provided at the either of the numbers listed at the
end of this DOC file. We what to know if you are having a problem so that
it can be addressed and hopefully fixed.
License Agreement and Copyright
-------------------------------
You may freely evaluate this product for as long as you like although
some of the features will not be available in unregistered versions.
This software may be freely distributed so long as:
> All the original files are left unmodified.
> No files have been added to or removed from the original archive
for any reason whatsoever.
> Other than postage no FEE may be charged.
TagScan is not public domain, it is copyrighted 1990,1991,1992 by
Bill VanWezenbeeck and Tony Mann.
Dos Versions and System requirements
------------------------------------
Version 6.94 has been tested under MS-DOS 3.30 - 5.00 only. There has
been no testing under any versions of DR-DOS. I see no problems with
running TagScan under DR-DOS but if you are having problems with this
software and are running DR-DOS v#.## please let us know so that we can
make some attempt to locate the possible reasons.
Also BETA testing has been done with XT class machines as well as AT/286's
386's and 486's.
.
-3-
=======================================================================
TagScan and Multi-Taskers
=======================================================================
We look for the presence of a Multi-Tasking Program such as DESQview
or WINDOWS. If a Multi-Tasker is detected TagScan will NOT write
directly to the screen. This will allow TagScan to be "Well Behaved"
in a multi-tasking environment.
=======================================================================
Setting TagScan up on your BBS
=======================================================================
Installing TagScan is very easy, just follow the instructions.
1-Create a Sub\Directory off of your BBS directory called TAGSCAN
and move all the files in this package to that directory.
2-Run the SETUP694.EXE program. This will create the TSCAN694.DAT file
which will configure TagScan for your BBS. Answer all the questions.
3-Edit/Update your POSTUL.BAT file as follows:
Echo off
C: <--- Drive letter your BBS is on.
Cd\BBS\TagScan <--- Change to your TagScan directory.
Tscan### %1 %2 %3 %4 %5 %6 <--- Execute TagScan. (###=Version#)
4-If you say YES to the question "Use the NoScan Feature" then edit
your NOSCAN.LST file and be sure that it includes your \BBS, \GFILES,
\ROOT directories and any directory that should NEVER be TagSCANed. I
considered "Hard Coding" these into TagScan but decided that it should
be the choice of the SysOp rather than TagScan.
5.> Finish reading this DOC file to be sure that you have a full
understanding of ALL the features. There may be some that your
not using that you be better used.
=======================================================================
Converting Uploads to ZIP, ARJ or LZH Formats
=======================================================================
This is a feature available to registered users only. With conversion
turned on TagScan will convert ALL uploads to one of the 3 archive
formats that the SysOp specifies in the setup. Some areas on the BBS
can still be left as NO CONVERT areas if you choose. If there are
some areas on your BBS that you don't want to convert then you will
simply add the full path to that directory to the NOCNVRT.LST file.
Please include only (1) directory per line. Here is an example:
D:\BBS\FILES\SYSOP\ <---- Must end with a \
D:\BBS\FILES\TEXT\
The NOCNVRT.LST must reside in the \TagScan directory to be of any
use to TagScan.
NOTE: If you are having problems converting or processing .ARJ files
please be sure to tell TAG to swap to DISK rather than MEMORY
when shelling to the POSTUL.BAT file. This is necessary because
of the large memory requirements that ARJ.EXE has.
=======================================================================
Changing Users SL and DSL
=======================================================================
The SysOp has an option available which will change the users SL and
DSL if they should upload a Virused File to the BBS. This is a nice
feature because you can lower the access to where the user will be
locked out of the BBS until the SysOp can evaluate the situation on
a one to one basis.
=======================================================================
Adding color to the LOG file
=======================================================================
By default TagScan will write ^P color codes to the logfile but you can
toggle this "OFF" when running the SETUP690.EXE program. Most SysOps
choose to make the LOG file their SYSOP.LOG but some don't and find the
^P color codes to be slightly distracting and sometimes confusing when
viewing the LOG with an ASCII editor.
=======================================================================
Sending BEEPS to the local console
=======================================================================
By default TagScan will BEEP in certain situations. One of these would
be when a file was found to contain a VIRUS. If you would prefer that
TagScan not BEEP simple toggle the beeps to "OFF" using SETUP690.EXE.
=======================================================================
Setting TagScan up on Multi-Node Boards
=======================================================================
At this time there nothing that needs to be done. TagScan will look in
your \Gfiles directory for the USER.LST first, if it is not found then
it will look in your \MULTI directory. So if you share your USER.LST
between nodes there should be no problem. Also if you load SHARE it
will be detected and file handling will be toggled accordingly.
.
-4-
=======================================================================
Optional Virus Bulletin
=======================================================================
A bulletin may now be created if a Virused File is detected by
TagScan. In this bulletin will be found ALL of the users important
info such as Name, Handle, Password, Phone, Address, Total times on
your BBS, Total Posts, Total Uploads, Total Downloads and the file
description along with the date and time of the upload.
=======================================================================
Creating the USER#.MSG file.
=======================================================================
Because Tony and I both have "File Area Co-SysOps" we thought it
would be nice to allow them to see the TagScan Logs without having
to give them access to the TAG LOG FILES. I order to do this we
decided to allow TagScan to create a USER#.MSG file which is created
in the \GFILES directory. In the config generator you will have the
option of choosing which user, if any, you want this log to go to.
TagScan will only append information to the file, so if another
program has already create a USER#.MSG TagScan will simple add to it
without disrupting any other information.
=======================================================================
Auto ANSI Detect & Carrier Monitoring
=======================================================================
There is no longer a need to run ANSICK1 in your Logon.Bat because
TagScan now checks the comport and determines whether or not the
remote user has ANSI or not. Also we now monitor the comport for a
carrier and if lost, TagScan will busy the line out until it has
finished. We chose to busy out the line in case the SysOp is
running a comport monitor that reboots after X number of rings. The
worst thing that could happen is for TagScan to reboot in the middle
of the processing.
=======================================================================
GIF file compression.
=======================================================================
TagScan will allow the SysOp to compress GIF uploads as they come into
the BBS although it will need to use an external utility to do the actual
work. Two currently being used by our Beta Sites are "GifLite.Exe" and
"Gif2Jpg.Exe". When you are configuring TagScan you will be asked about
this feature and if you choose to use it you will need to enter the FULL
Path and EXE name as well as the necessary switches that will be used. The
default is GifLite.Exe. If you use Gif2Jpg.exe the output file will be
changed to .JPG (The DIR file will be updated as well).
.
-5-
=======================================================================
Adding files to the TRASHCAN.FIL
=======================================================================
There is an option in TagScan to allow the SysOp to add all uploads
to TAG's TrashCan.Fil file located in your \GFILES or \ALTERNATE TEXT
directory. This can be toggled on or off from the TSCFG###.EXE program
that you will be or have already used to setup TagScan for your BBS.
To add color to the TextString that will be added just after the
filename you will simply have to use a ~ which tells TagScan to
insert a ^P in place of that ^. Immediately after the ^ should be a
# from 0-9 which TAG will use to determine the ANSI color to use( See
the TAG docs if you need to know more about the ^P colors). The use of
the ^# will be a little clearer to you once you run the TSCFG program.
Here is an example to help you understand it a little better.
Example String could be: ^7Match Found^3! ^9Please try another^3!
^ ^ ^ ^
| | | |
Red | Dark Blue Light Blue
|
Light Blue
A BEEP can also be added by entering a ~(Tilde) symbol. So ~^7 would be
BEEP+RED.
If you are unsure what the TRASHCAN.FIL is or does please refer to
your TAG documentation.
=======================================================================
Work Directories
=======================================================================
TagScan will automatically create the necessary work directories off
of the current upload directory but as of v6.80 you have the option
of specifying your own. There are currently 2 work directories that
are required, one for SCANNING the file and one for CONVERTING archive
formats. Cliff Morrison, our Canadian Alpha test site uses RAM Disks,
so if you desire you can now do the same. If you decide to use them
as well please be sure that it is at least 1meg so that TagScan has
some room to work. The size of the RAM disk should also reflect the
size of your average upload. If average uploads are 500k "compressed"
then you will surely run out of space if your RAM Disk is only 1meg in
size. A more practical size in this case would be 2meg.
=======================================================================
Bad File "Storage" Directories
=======================================================================
There are 2 directories that TagScan will create to store "BAD-CRC" files
and or "VIRUSED" files. By default TagScan will create "C:\VIRUS" for
storing any VIRUSED uploads and "C:\BAD-CRC" for storing any uploads that
fail the CRC check. These directories can be defined by the SysOp from
the SETUP690.EXE program. If your C-Drive is simply a SMALL boot-drive
you will want to change these defaults to another drive.
.
-6-
=======================================================================
TagScanExitCodes
=======================================================================
TagScan will write all errorlevels and error messages to the file
TAGSCAN.ERR which will be located in your \TagScan directory. All
errors written will be the actual error that a program returned to
TagScan. You will need to refer to that particular program to see
what the error was.
=======================================================================
Special Thanks
=======================================================================
I would first like to thank "The TAG Team" for giving us a
great piece of software to work with, as well as some great
structure files.
Thanks also to "McAfee & Associates" for their SCAN utility
that helps make it possible to keep our BBS's virus-free...
Thanks to CSI Online for the many hours of Alpha testing and
Cliff Morrison at The Bears Den for the GREAT bug reports, they
helped get this release out on time.
And Thank You to all our Beta-Sites for their time, effort and
input. They helped make the coding process easier than we ever
expected it to be.
.
-7-
=======================================================================
External utilities and Programs...
=======================================================================
TagScan calls to several external programs to do the uncompressing
and scanning. If these programs aren't in your path then TagScan
will not run correctly. All the following programs can be downloaded
or Freq'd from "The BatModem" or "The Ice Palace" or can be found on
most BBS's in your local area.
Compression Utilities
---------------------
Zoo.exe version 2.01 [Public Domain - Written by: Rahul Dhesi]
(ZOO201.ZIP) - (Magic-filename is ZOO)
PKxarc.com version 3.5 [Copyright (C) PKWARE 1986-87]
(PKX35A35.EXE - Self Extracting) - (Magic-filename is PKXARC)
PKunpak.exe version 3.61 [Copyright (C) PKWARE 1986-88]
(PKPAK361.EXE - Self Extracting) - (Magic-filename is PKUNPAK)
Pak.exe version 2.51 [Copyright (C) 1988-90 NoGate Consulting]
(PAK251.EXE - Self Extracting) - (Magic-filename is PAK)
PKunzip.exe version 1.1 [Copyright (C) PKWARE Inc. 1989-1990]
(PKZ110.EXE - Self Extracting) - (Magic-filename is PKZ110)
Arj.exe version 2.30 [Copyright (C) 1990,91,92 Robert k. Jung]
(ARJ230.EXE - Self Extracting - Magic-filename is ARJ)
Lha.Exe Version 2.12 [Copyright (C) 1988,91 Haruyasu Yoshivaki]
(LHA212.EXE - Self Extracting - Magic-filename is LHA)
Scan Utilities
--------------
Scan.exe version 8.6v93 [Copyright (C) 1989-92 by McAfee Associates]
(SCAN93.ZIP) - (Magic-filename SCAN)
GIF Compression Programs
------------------------
GifLite.Exe version 1.31 [Copyright (C) 1991 by Tsung Hu, Canada]
(GIFLT131.ARJ) - (Magic-filename GIFLITE)
ZipLogo Utilities
-----------------
Zn.exe version 2.0 [Copyright (C) 1989, Matthew J. Palcic]
(ZN_20.ARJ) - (Magic-filename ZIPNOTE)
.
-8-
=======================================================================
TagScan Support Files
=======================================================================
There are several files that can exist in your \TagScan directory but
they are not needed. TagScan will use them if they exist but run fine
without them.
COMNTDIR.LST - In this ASCII file should be listed ALL of the
upload directories that you desire ZIP or ARJ
to add comments to. If you said YES to ZIP or ARJ
comments then this file will be considered REQUIRED
and if not found comments will NOT be added to the
uploads. Please be sure that ALL path statements
listed in this file have '\' trailing backslashes.
Example: E:\BBS\FILES\UPLOADS\ <-- Correct
E:\BBS\FILES\UPLOADS <-- Incorrect
NOSCAN.LST - (Not required but we HIGHLY recommend using this file)
If a directory that is listed in this ASCII file
matches the CURRENT upload directory then TagScan
will abort without processing the Upload. Useful
for SysOps that have AMIGA or APPLE file on their
BBS's. If you decide to use this file please be sure
to toggle "Use NOSCAN Feature" to Yes from the TSCFG
generator as well as having the file in your \TAGSCAN
directory.Please be sure that ALL path statements
listed in this file have '\' trailing backslashes.
Example: E:\BBS\FILES\UPLOADS\ <-- Correct
E:\BBS\FILES\UPLOADS <-- Incorrect
NOCNVRT.LST - This ASCII file should contain all the directories that
you wish to SCAN but not CONVERT. This is useful if you
want to have file areas on your BBS that "Validated
Archives" can be uploaded to. This will allow the
"Authentication Records" of the file(s) to remain intact.
Please be sure that ALL path statements listed in this
file have '\' trailing backslashes.
Example: E:\BBS\FILES\UPLOADS\ <-- Correct
E:\BBS\FILES\UPLOADS <-- Incorrect
.
-9-
NOCNVRT.FIL - This ASCII text file should contain any filenames that
should not be converted, such as known AUTHENTICATED
distribution files (Eg:McAfee's Virus Utilities). More
information about this can be found in the file itself
which is released with this version.
Briefly:
A Carot (^) placed in front of a partial file name
will cause the file name to be treated as a wildcard.
A Semi-Colon (;) as the first character on a line will
cause the whole line to be ignored.
Anything else will be considered as a valid file name
and will be treated as such without wildcards.
Example:
^Scanv - on a blank line would be read as Scanv*.* and
accordingly would not be converted.
Scanv - on a blank line would be read as Scanv.* and
if, for instance, Scanv86.Zip was uploaded the file WOULD
be converted since Scanv.* and Scanv86.Zip do not match.
NOVIRI.??? - This file will be sent to the remote user after the
upload is found to be Virus-Free. NOVIRI.CLR for
ANSI users and NOVIRI.MSG for Non-ANSI users.
(Note - All ANSI files SHOULD be saved to 79 lines)
YESVIRI.??? - This file will be sent to the remote user after a
Virus is detected in the upload, and just before
the user is logged off and your system is rebooted.
Again, .MSG for Non ANSI users and .CLR for ANSI users.
(Note - All ANSI files SHOULD be saved to 79 lines)
BAD-CRC.??? - This file will be sent to the remote user if the upload
fails the CRC checking.
Again, .MSG for Non ANSI users and .CLR for ANSI users.
(Note - All ANSI files SHOULD be saved to 79 lines)
.
-10-
=======================================================================
Registration Information
=======================================================================
Registration is only $10.00.
When you are ready to register your copy of TagScan simply
execute the program TS_REG.EXE and then edit the form that
it will create for you (TS_REG.LTR). Please do NOT edit the
BBS Name that is added to this file, the BBS name is a critical
component in generating the correct registration number for
your BBS.
=======================================================================
TagScan Alpha & Beta-Sites
=======================================================================
Alpha Sites
--------------------------------------------
CSI Online - SysOps: Gary and Lisa Jackson
Conroe, Tx / 409-321-3198 / 1:106/3198
--------------------------------------------
The Bear's Den - SysOp: Cliff Morrison
Smith Falls, ON / 613-283-0759 / 1:163/412
--------------------------------------------
Beta Sites
--------------------------------------------
Griffs Tavern BBS - SysOp: Mike Griffin
Houston, Tx / 713-550-5999 / 1:106/5999
--------------------------------------------
The Bovine Bar BBS - SysOp: Scott Williams
Houston, Tx / 713-947-7264 / 1:106/77
--------------------------------------------
Isle of View - SysOp: Stephen VanHecke
Houston, Tx / 713-771-1460 / 1:106/2261
--------------------------------------------
BG's Bar & Grill - SysOp: Greg Mears
Jackson, MI / 517-783-4005 / 1:2330/2002
--------------------------------------------
Whispers BBS - SysOp: Wade Fallin
Jacksonville, Fl / 904-744-5624 / 1:112/90
--------------------------------------------
The Razor's Edge - SysOp: Steve Goldbeck
Auburn Hills, MI / 313-377-3326 / 1:120/358
--------------------------------------------
That's about it... If you have any Bugs to report please
contact Tony or I at our respective BBS addresses or for
Local support you can contact one of the above Alpha or
Beta Sites.
-*- The Ice Palace -*- | -*- The BatModem -*-
---------------------------------------------------------------
SysOp: Tony Mann | SysOp: Bill VanWezenbeeck
Houston, Tx - (713) 591-7939 | Houston, Tx - (713) 876-0767
US Robotics DS - v32bis/v42bis | US Robotics HST - v32/v42bis
1200-38400 bps - 24hrs 7days | 1200-38400 bps - 24yrs 7days
FidoNet Address - 1:106/821 | FidoNet Address - 1:106/1525
|
Sincerely,
Bill VanWezenbeeck