▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄
█ █ █▄█ █ █▄█ █▄ █ █▄▀ The Premium Upload Scanner
█▄█ █ █▄▄ █ █ █▄▄ █▄▄ █ █ Version 4.0
Copyrighted Pete Rocca & Multiboard Communications Centre, 1994
╓───────────────────────────────────────────────────────────────────────────╖
║ UpCheck 4.0 ║
╙───────────────────────────────────────────────────────────────────────────╜
A premium upload scanner, description handler and true duplicate CRC
detection built in. Also can write a message to the user, explaining
why the file failed (Hudsonbase), and/or to the Sysop with a warning
or message receipt. Fast and easy to use!
╓───────────────────────────────────────────────────────────────────────────╖
║ Quick Note ║
╙───────────────────────────────────────────────────────────────────────────╜
The docs are fairly short, and if you don't read them, you probably
won't get guess the password to run the configuration program, so
give them a quick read, it'll save you hours of manually inserting
descriptions and sorting through archives...
╓───────────────────────────────────────────────────────────────────────────╖
║ Overview ║
╙───────────────────────────────────────────────────────────────────────────╜
UpCheck and it's companion utilities are more than any Sysop could
require in an upload file processing system...
UpCheck is a small and quick program that is capable of scanning an
upload for file integrity, duplications, as well as being able to
remove unwanted files, add files and then recompress the archive in
maximum compression mode. If you are using RemoteAccess 2, then
you also have the ability to quickly insert the FILE_ID.DIZ,DESC.SDI
or DESC.SDN description into the file base description and if the
file shoud fail, create a message to the user telling them why.
UpCheck comes with a program called UpUtils. This program can
perform such database features as creating duplicate file signatures
from your existing collection of files, and insert the descriptions
of these files into the RemoteAccess 2 file database.
╓───────────────────────────────────────────────────────────────────────────╖
║ UpSetup - Configuration program ║
╙───────────────────────────────────────────────────────────────────────────╜
UpCheck is very easy to install. The configuration file must be in
the same directory as the executable programs. All the executables
should be in the same directory, as the same configuration file is
used by all the programs. Also, the UPCHECK.PAC file should be in
this directory or you will get a "Security violation" message.
System Information
──────────────────────────────────────────────────────────────────
═══ System Name
Here you enter your BBS name. Make sure that
if you are registered, that this is appears
EXACTLY the way shown in your key file. It's
case sensitive.
═══ Sysop Name
Here you enter your name. It is also case
sensitive to your registration number.
═══ Registration Number
Here you enter your registration number,
when you receive your key. You have three
chances to enter it properly.
Files Configuration
──────────────────────────────────────────────────────────────────
═══ Duplicate Database
This is the file that contains all of the
file signatures that are required for
duplicate file detection. You should never
attempt to edit or alter this file.
═══ Badfiles Database
This is the text file that contains the
names of all the files you want removed from
the uploaded file. For example the BBS
advertising files from other systems. You
can edit this file with any standard text
editor. Be sure that each file is on it's
own line and does not contain wildcards.(*?)
═══ Statistics File
This file contains a record of the number of
passing archives, failed archives and total
bytes read and written. To reset the totals
you can simply delete this file.
═══ Log File
This file is written to every time a file is
uploaded. It contains a list of the person
who uploaded the file, the file name and the
status of the file.
═══ Advertising File
This is the file that you want copied into a
passing archive. For example an advertisment
or such. If you do not wish a file added,
simply leave this field blank.
═══ Copy to {+}
This is the name that you want your added
file to be called in the archive. An example
would be that you wanted the file copied
from "C:\BBS\TEXT\BBS.AD" into the archive
and call it "CALLHERE.TXT".
Limits Setup
──────────────────────────────────────────────────────────────────
═══ Maximum age of files in days
This is the maximum number of days old that
a file within an archive can be before being
considered too old.
═══ Maximum percent of old files
This is the percentage of files that can be
old and the archive still pass.
═══ Maximum percent of duplicate files
This is the percentage of files that can be
duplicates before the whole archive gets
failed. This is good at about 80% usually
as it allows room for advertising files that
you may not have marked in your bad files
file, and the next feature will usually do
the better test.
═══ Maximum percent of duplicate bytes
This is the percentage of bytes that can be
duplicate before the whole archive gets the
fail flag. This is good at a value around
25%. This is different over the other one
as it work like this...
JUNKY!.BBS 1000 bytes - dup junk file
README.HA 1000 bytes - dup junk file
MISSED.IT 1000 bytes - dup junk file
VALUED.EXE 70000 bytes - real program
If this had been the contents of the archive
the percentage of files duped would have
been 75%, but the duped bytes only about 5%.
Has you can see, that with good setting for
both files and bytes, you can be sure never
to get a duplicate file passed, nor fail an
original one.
Control Setup
──────────────────────────────────────────────────────────────────
═══ Allow Avatar Emulation
When set to yes, UpCheck will display Avatar
graphics to a user that has the Avatar flag
turned on.
═══ Allow RIP Emulation
When set to yes, UpCheck will auto-detect if
a user has RIP capabilities and display RIP
graphics to them.
═══ Scan Embedded
When set to yes, UpCheck will extract the
embedded archives found within and process
them with date, duplicate and virus scanning
for each level found.
═══ Pass Unsupported File Types
When set to yes, any files that cannont be
determined as being an ARC/ARJ/LHA/LZH/PAK/
ZOO/ZIP/UC2/SQZ/GIF/JPG type file will be
passed, otherwise it will be failed.
═══ Recompression Type
When this is not set to "Same", UpCheck will
recompress the file into a new type.
═══ Keep Original Name
When set to yes, UpCheck will not rename the
archive with the proper extension if the
original one is invalid (Example: a ZIP file
with the extension ZZZ would not be renamed
back to ZIP) Obviously this cannot be "yes"
when "Recompression Type" is not "Same" and
the UpSetup program will correct this.
═══ Define Bad Extensions
Here you can specify extensions that you do
not want to be able to be uploaded. If a
file uploaded consists of nothing but these
types of files the archive will be failed,
however if a file contains a fair amount of
these files, it will be passed, but you can
specify in the "RemoteAccess Options" to
warn you of such a file. For example, if
you didn't want graphics to be able to be
uploaded, you could set the extensions to
BMP/RLE/GIF/PCX/JPG/PIC and even if a user
uploaded these files archived, it would
detect them and take action accordingly.
Archiver Setup
──────────────────────────────────────────────────────────────────
═══ Decompression (Option 1)
Options A thru L are the full paths, files
and parameters to be executed for the
decompression of the related file type.
═══ Recompression (Option 2)
Options A thru L are the full paths, files
and parameters to be executed for the
recompression of the related file type.
═══ Integrity (Option 3)
This is the full path and file name as well
as the parameters for your scanning programs
for GIF/JPG/EXE and virus scanning.
RemoteAccess Options
──────────────────────────────────────────────────────────────────
═══ RemoteAccess Mode
This when set to Yes allows the RemoteAccess
options to be used.
═══ Configuration Path
This is the path to your FILES.RA file. This
is required for locating the correct path of
the file in relation to the file description
database.
═══ File Base Path
This is the path that points to the filebase
subdirectories. For example, usually set to
"C:\RA\FILEBASE\" as the "TXT", "HDR" and
"IDX" subdirectories are usually in this
path.
═══ Message Base Path {+}
This is the full path to your "MSGTXT.BBS",
"MSGTOIDX.BBS","MSGIDX.BBS" and "MSGHDR.BBS"
files. Normally set to "C:\RA\MSGBASE\"
═══ User Notify-Fail {+}
This when set to Yes will generate a message
to the user if an upload failed. The message
will explain the reason for the failure.
═══ Sysop Notify-Fail {+}
This when set to Yes will generate a message
to the sysop, saying what file failed, why
and who uploaded it.
═══ Sysop Notify-Warn {+}
This when set to Yes will generate a message
to the sysop if a file triggers a warning
but still passes. Examples would be a file
that contains a great number of retricted
extensions, or if it was of an unsupported
type.
═══ Holding Message {+}
This should be set to Yes if you want the
message to include a statement along the
lines of: "The file is being held for Sysop
Review"
═══ Message Board {+}
This is the message board that the message
should be posted to. Please remember that
UpCheck supports ONLY Hudson style message
bases.
═══ Add Uploader Name {+}
This when set to Yes will append the users
name to the file description in the file
database.
═══ Add Archive Info {+}
This when set to Yes will put the number of
files within the archive and the range of
dates in the archive into the file database
description.
═══ Add Graphics Info {+}
This when set to Yes will put the dimension
info from GIF and JPG files into the file
database description.
╓───────────────────────────────────────────────────────────────────────────╖
║ UpCheck - Upload scanning program ║
╙───────────────────────────────────────────────────────────────────────────╜
UpCheck, the executable itself, is the actual scanning program for
when a user uploads a file. It is run from your bulletin board in
a numerous number of ways. I suggest that you consult your software
documentation for info on installation of an upload scanner. If you
are running RemoteAccess 2, then great, it's easy.
Two things to keep in mind before running UpCheck. First, UpCheck
requires a fossil driver to display it's screens over the modem. If
you are running RemoteAccess, no worries, you're using one, if not,
my suggestion would be to try BNU or X00. (two very good fossil
drivers) The second thing you should remember is that due to the
memory hogging programs this program must execute, you should have
at least 500k conventional memory free to run this program. (The
actual overhead of the program is only 74k but a lot of scanners eat
almost 400k up all on their own) This program will run with McAfee
Scanner 9.21 V112 in about 485k of memory without any problems.
Running UpCheck 4.0
──────────────────────────────────────────────────────────────────
═══ Command line parameters
The program requires two parameters.
Remember to call this program after the
user has uploaded a file.
1) The path and name of the dropfile. Such
files are EXITINFO.BBS, DORINFO1.DEF and
DOOR.SYS. For example, if your dropfile
was located in C:\BBS then you would put
C:\BBS\DOOR.SYS for your parameter.
2) The path and name of the uploaded file.
If you wanted to scan a file called
"GAME.ZIP" that was in your "C:\UPLOADS"
directory, you would put the parameter
"C:\UPLOADS\GAME.ZIP"
═══ Running under RemoteAccess 2
When running under RemoteAccess, the line
that you should enter in the...
Options -> Files -> Upload scan
...field should look something like this:
C:\UPCHECK\UPCHECK.EXE \RA\DOOR.SYS @ *M
Or if you are running a multinode system:
C:\UPCHECK\UPCHECK.EXE \RA\NODE*N\DOOR.SYS @ *M
Recall from your RemoteAccess documentation
that the *N is replaced with the node # and
the @ is replaced with the path/name of the
uploaded file, and that the *M means to use
the MemorySwap function of RemoteAccess.
Also remember to turn on upload scanning in
the area(s) that you permit uploads.
╓───────────────────────────────────────────────────────────────────────────╖
║ UpUtils - Database building utilites ║
╙───────────────────────────────────────────────────────────────────────────╜
UpUtils is a supplementry program that is designed to simplify the
job of creating duplicate databases and making sure that all the
file descriptions are correct.
Running UpUtils
──────────────────────────────────────────────────────────────────
═══ Command line parameters
There are are six command line parameters
/D = Enable duplicate checking & building.
This allows you to build a dupe list
of all your files that are presently
on your system.
/I = Enable the insertion of descriptions
that are included inside some of the
files. This allows you to quickly
put your descriptions into the data
base. (RemoteAccess Only) {+}
/P = This is the same as the /K switch but
will prompt you for a decision before
deleting the file. {+}
/K = Kill duplicate files. This switch
will cause all the files that are
checked and duplicates to be deleted.
**USE THIS WITH EXTREME CAUTION** You
could lose all your files if you do
not use this one properly. {+}
/S = Scan subdirectories. This switch is
useful when doing all your files as
it allows the program to search the
current directory and all it's lower
subdirectories also.
/Q = Query the database. This switch will
return the current statistics of the
database holding the information on
number of files processed, failed and
passed, etc.
The UpUtils program also requires a file
specification for files to process. Wild
cards are valid. For example, if you want
to process all ZIP files, you would put
"*.ZIP" for your file specification.
Although UpCheck will handle multi-level
embedded archives, UpUtils only will seek
into the original archive. The reason for
this is that any other way would make the
building of your database too incredibly
time consuming, and that the first level
is usually more then enough for testing.
╓───────────────────────────────────────────────────────────────────────────╖
║ UpBadCrc - Unwanted files removal by Crc updater ║
╙───────────────────────────────────────────────────────────────────────────╜
UpBadCrc is a simple program that takes a file name and stores its
personal signature in the bad files list (UPCHECK.BAD) To avoid you
from accidentally adding massive amounts of files to the bad list,
UpBadCrc does not accept wildcards. When you notice a file that is
changing its name but staying the same otherwise. (for example a
random file name BBS ad) you should extract the unwanted file from
the archive and type "UPBADCRC filename". This program will then
take the signature and put it into the bad files list and mark it as
a CRC instead of a filename by placing a '∞' character in front of
the signature, so don't be alarmed if you see this in your bad files
list.
╓───────────────────────────────────────────────────────────────────────────╖
║ License and Disclaimer ║
╙───────────────────────────────────────────────────────────────────────────╜
UpCheck is not free, it is being marketed under the "try before you
buy" or shareware concept. You are entitled to use UpCheck, UpSetup
and UpUtils for a period up to thirty (30) days, after which you
MUST register it.
Registration entitles you to use UpCheck and its companion programs
as well as any future versions of the programs that may or may not
be released. Registration will also unlock all of the features that
UpCheck is capable of. (In other words, the {+} features)
By running any of the executable programs included, you agree that
Pete Rocca, nor any affiliates of Pete Rocca are responsible for
any damage ever experienced, however so created. If you cannot agree
to this, then your privilege to use any of these programs is revoked
and it becomes illegal for you to execute any programs included with
this documentation.
You may freely copy and distribute the shareware version of UpCheck
as long as its original archived contents are not modified in any
way. You may not use nor distribute a registration key without the
written consent of Pete Rocca of Multiboard Communications Centre.
It is illegal to hack, reverse engineer and/or modify any components
of the UpCheck archive.
If you agree to all of the above, then you may use these programs.
By the way, the startup PASSWORD is "ACCEPTED".
╓───────────────────────────────────────────────────────────────────────────╖
║ Registration ║
╙───────────────────────────────────────────────────────────────────────────╜
Earlybird Special (BEFORE May 1st, 1994)
Canada: If registering in Canada then please send $10 (CDN funds) via
cheque or money order payable to "Multiboard Communications"
to 150 Mill Street, London, Ontario, Canada, N6A1P6
Outside
Canada: If registering outside of Canada then please send $10 (US
funds) via check or money order payable to "Multiboard
Communications" to 150 Mill Street, London, Ontario, Canada,
N6A1P6
Regular Registration (AFTER April 30th, 1994)
Canada: If registering in Canada then please send $15 (CDN funds) via
cheque or money order payable to "Multiboard Communications"
to 11 Alma Drive, Etobicoke, Ontario, Canada, M9P1T4.
Outside
Canada: If registering outside of Canada then please send $15 (US
funds) via check or money order payable to "Multiboard
Communications" to 11 Alma Drive, Etobicoke, Ontario, Canada
M9P1T4.
Send your payment along with the following form, completed to the
address specified above.
UPCHECK REGISTRATION
~~~~~~~~~~~~~~~~~~~~
Name: _____________________________________________________
Address: _____________________________________________________
_____________________________________________________
City: ________________________ Province/State: ___________
Country: ________________________ Postal/Zipcode: ___________
BBS Name: _____________________________________________________
BBS Phone: ________________, ________________, _______________
Software: _____________________________________________________
FidoNet: ___________________ (if applicable)
Operating System Info, and any other information
_____________________________________________________
_____________________________________________________
Any suggestions, or comments
_____________________________________________________
_____________________________________________________
Send my registered version: On 3.5" 720k Disk [ ] - $5 Extra
On 5.25" 360k Disk [ ] - $5 Extra
To my FidoNet Node [ ]
╓───────────────────────────────────────────────────────────────────────────╖
║ Support, Comments ║
╙───────────────────────────────────────────────────────────────────────────╜
If you have any questions or comments, you can Netmail me at the
FidoNet (1:2401/123) XA,CM,V32,V42. Registered users will get their
replies sent out, however, unregistered users will have to poll my
system for responses. (Sorry, but I have to keep costs down) You can
also find me in the RemoteAccess Utilities FidoNet area. The latest
version can be FREQ'd with the magic name "UPCHECK".
╓───────────────────────────────────────────────────────────────────────────╖
║ Acknowledgments ║
╙───────────────────────────────────────────────────────────────────────────╜
This program has been tested on Dos 3.3 through Dos 6.2, DESQView
2.40 through 2.62, DESQView/X 1.2 and Windows 3.1, other operatiing
enviroments should work fine, but they have not been fully tested
yet. (Although Os/2 2.1 seems to be fine also)
Requires at least Dos 3.3 and almost 500k free conventional memory.
(Can't do much about the memory problem, only 74k of that is mine,
the rest you can blame on McAfee and the author of SQZ.) UpCheck
will run fine with 74k of memory, but when it shells to run the
other programs for extracting, scanning and repacking, it will
fail.)
RemoteAccess, ZOO, SQZ, UC2, PKZIP, ARJ, ARC, LHA, BNU, X00 and/or
McAfee Software are all reserved trademarks and / or copyrighted
software by their respective authors.
Thanks to my beta tester, David Gee, who did everything possible to
try and make sense of a 'mysterous bug' that wouldn't go away at
2am, that turned out to be a wrong configuration parameter. I'd
also like to thank him for all the suggestions on improving UpCheck
and lastly for being the first registered user of the program.
Thanks to my wife Laurie, who hates me being on 'this damn machine',
but still finds the way to support me. Thank you.
Thanks to you, the user, for actually reading to the end of the
documentation, congratulations, and remember, please register.
---
Documentation End / March 23th, 1994