home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
SFCHKUP.ZIP
/
SFCHKUP.DOC
< prev
next >
Wrap
Text File
|
1992-01-02
|
11KB
|
214 lines
SFCHKUP
Version 1.0
Copyright (C) by Mike Woltz, 1991
Buffalo Creek Software
A Member Of
The Association Of Shareware Professionals
INTRODUCTION
------------
SFCHKUP is a utility which is designed to evaluate the integrity
of files uploaded by callers to a SPITFIRE BBS. It is utilized at
the beginning of the SFINIT.BAT file which is run immediately after
a caller logs off the BBS. Due to the fact that SFCHKUP is written
in Assembler, it takes up very little disk space and runs quickly.
REQUIRED FILES
--------------
SFCHKUP.EXE is provided along with a sample batch file that is
used during processing. This file MUST be named CHKUP.BAT. A sample
SFCHKUP.MSG file is also provided which must reside in the SPITFIRE
Home Directory (if used). The use of this optional file is described
below. In addition, several other files are utilized during SFCHKUP
processing. These normally include MUV and DELXCEPT which are
available via Buffalo Creek's BBS (515-225-8496). Other files may
be used at the Sysop's discretion and depend upon the way their
CHKUP.BAT is set up.
CONFIGURATION OF SFCHKUP
------------------------
SFCHKUP.EXE and CHKUP.BAT must be placed in the SPITFIRE Home
Directory (which is where SPITFIRE.EXE is located.) To configure
SFCHKUP, just run it with no parameters. You will then be prompted
for the Upload File Path which is where uploads are stored once the
caller sends them. For this example, we will use C:\CHKUP1 as the
Upload File Path for Node 1. Each Node MUST have its own CHKUP
directory, normally named \CHKUP1, \CHKUP2, etc. This makes it
possible for SFCHKUP to run on a SPITFIRE BBS that has the maximum
number of nodes possible which is 255.
You will also be prompted for the File Area Path which is the
destination path of all files which successfully complete SFCHKUP's
evaluation. We will call this path C:\UPLOADS for our example.
Once these paths are provided, SFCHKUP will search the drives
configured to see if they exist. If not, SFCHKUP will create them.
You will then be prompted as to whether you wish to save changes.
Then, you're prompted as to whether you would like SFFAREA.DAT to be
refreshed. A [Y]es response will change the Upload File Path in ALL
areas of the node being configured to the CHKUP directory. A file
called SFCHKUP.DAT will store this information in the SPITFIRE Home
directory. Each node will have a unique SFCHKUP.DAT file.
If ever these paths need to be changed, run SFCHKUP /CONFIG and
you will once again be able to configure them.
CONFIGURATION OF CHKUP.BAT
--------------------------
CHKUP.BAT contains a set of instructions that are carried out
during the proceedings of the use of SFCHKUP. It can run many other
programs and other batch files which will process uploaded files in
various ways. Since there is no way to know which ones will be used
by Sysops, they will not be discussed in detail here. Buffalo Creek
Software will not be responsible for their use or support.
A sample CHKUP.BAT is provided for you to use as an example when
you are setting up SFCHKUP.EXE. Examination of this batch file
reveals the use of other utilities during processing of uploads,
ways that certain uploads can avoid processing and the means to
dispose of particular uploads which do not evaluate properly.
It is necessary to edit CHKUP.BAT to your specifications. You
will need to configure the paths that it references for your system.
If you utilize any or all of the other programs referenced therein,
you will need to obtain them, configure them if necessary, and place
them in a subdirectory located in the path.
CHKUP.BAT normally creates a work directory (C:\CHKUP1\CHKWORK
for example) during processing and deletes it when its work is
complete. Uploaded files are moved there for evaluation, processed
there and then moved to another location afterwards.
RUNNING SFCHKUP
---------------
SFCHKUP is written to honor file sharing, and as such, may be
run on more than node of a multinode SPITFIRE BBS simultaneously.
Each node will require its own CHKUP path and its own CHKUP.BAT.
SFCHKUP is designed to be run at the BEGINNING of SFINIT.BAT,
especially on multinode SPITFIRE BBSs. This is because the first
thing that SFCHKUP does is check to see who the last caller was. If
SFCHKUP is run later on in SFINIT.BAT, and another node is running
it as well, it is possible that the information on last caller could
be incorrect. Take care to make sure to run SFCHKUP first!
It is entirely up to you, the Sysop, how you utilize SFCHKUP
and its associated CHKUP.BAT file. You can make it as simple or as
elaborate as you please. Sysops who devise a unique methodology are
encouraged to share it with the rest of the SPITFIRE BBS community
by posting it in a message or uploading it to Buffalo Creek's BBS!
A short discussion of suggested ways that files may be processed
follows. You are not required to process your files in the ways
described and you are free to run other tests in addition to or in
place of the ones described.
EVALUATING FILES WITH CHKUP.BAT
-------------------------------
In most cases, all files uploaded will be evaluated by SFCHKUP.
The phase of evaluation can be configured to be skipped if you'd
rather NOT process a file. You might want to post say *.TXT files
as is and feel that there is no need to perform any tests on them.
If this is the case, the example CHKUP.BAT file demonstrates how you
can check for this type file's existence (IF EXIST *.TXT...) and
then skip the processing entirely (...GOTO TXTFILE). The file would
then be posted exactly as it was uploaded to the BBS. Similarly, you
could elect not to process *.BBS/*.CLR files, etc.
You could configure CHKUP.BAT to check for files that you would
rather not be contained within the file such as known BBS ads,
PKUNZIP.EXE/PKZIP.EXE, COMMAND.COM, etc. By using a statement such
as IF EXIST <filename.ext> DEL <filename.ext>, these files can be
eliminated from the file. When SFCHKUP's work is done, it will
correctly update the SFFILES.BBS in the configured Upload File Path
with the file's FINAL size.
A utility designed to check for so-called Computer Viruses can
be run as part of the evaluation. In our example, McAfee's VIRUSCAN
is used. SCAN.EXE and similar utilities exit with a DOS ERRORLEVEL
based upon the results of the evaluation. Our CHKUP.BAT shows that
an errorlevel of 0 indicates a file with good integrity while a file
with an errorlevel of 1 indicates a questionable file. Questionable
files can be sent to a holding directory (ex. C:\BADCHKUP) for later
scrutiny (accomplished by two IF ERRORLEVEL...GOTO... statements)
or deleted entirely.
Another utility can be used to check uploaded *.GIF files. For
example, GIFTEST.EXE can be used. Since GIFTEST also exits with a
DOS ERRORLEVEL, careful editing of the CHKUP.BAT file can allow you
to delete the file if it has poor integrity or is at a resolution
that you do not support on your BBS or save it in the holding
directory. Here, we accept .GIF files of no less than 321x201x16
resolution.
ZIP Comments found in uploaded files can be removed and replaced
with that of your BBS after they have completed evaluation. There
are quite a number of recommenting utilities (ex. RECOM.EXE) that
can be used to accomplish this.
Files that have been compressed with schemes other than the one
you are using on your BBS can be converted (to PKZIP with a utility
such as TOZIP.EXE.) Remember that SPITFIRE will ONLY support online
viewing of the contents of files compressed with PKZIP, though!
The above overview is brief by design. It is STRONGLY
recommended that you thoroughly read through the documentation of
each and every utility used in conjunction with SFCHKUP.
AFTER RUNNING SFCHKUP
---------------------
If files are not posted as a result of failing one of SFCHKUP's
integrity evaluation procedures, SFCHKUP will adjust the caller's
upload credits and K of upload credits accordingly subsequent to
completing evaluation of all files. In addition, SFCHKUP.MSG (which
must reside in the SPITFIRE HOME directory if used) will be copied
to XXX.BBS where XXX is the number of the caller who uploaded the
questionable file as contained in the SPITFIRE users database. The
filename will be appended to SFCHKUP.MSG. If there already exists a
XXX.BBS for that caller, SFCHKUP will append its data to it. In
addition, a notation is made to HEYSYSOP.LOG to notify the Sysop
that a questionable file has been received, its name and the name of
the caller who uploaded it.
All uploaded files with good integrity will then be moved to the
Upload File Area Path that you have configured. The SFFILES.BBS in
that area will be appended to with the final names, file sizes and
descriptions of all acceptable files. Finally, the work directory
will be removed and control will be returned to SFINIT.BAT.
DISTRIBUTION
------------
SFCHKUP is distributed under the shareware concept. You are
free to distribute the SFCHKUP program as long as it remains
unmodified and no fee is charged. If you continue to use this
program after an adequate evaluation period, a fee is required.
A $1.00 registration fee is required to register SFCHKUP. This
can be sent to:
Buffalo Creek Software
ATTN: Mike Woltz
913 39th Street
West Des Moines, Iowa 50265
DISCLAIMER
----------
Mike Woltz and/or Buffalo Creek Software shall in no way be
held responsible for any damage incurred while operating SFCHKUP.
All other programs used in conjunction with SFCHKUP are Copyright by
their respective authors and may not be products of Buffalo Creek
Software. All responsibility lies with the user of the software.
The shareware version of SPITFIRE and other SPITFIRE utilities
are available for download from:
Buffalo Creek's BBS
Mike Woltz, Sysop
(515) 225-8496
38400/19200/9600/2400/1200 Baud