▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄
█ █ █▄█ █ █▄█ █▄ █ █▄▀ The Premium Upload Scanner
█▄█ █ █▄▄ █ █ █▄▄ █▄▄ █ █ Version 5.01
Copyrighted Pete Rocca & Multiboard Communications Centre, 1994
All rights reserved
TABLE OF CONTENTS
═════════════════
Section Line
─────────────────────────────────────────────────────
FORWARD ········································ 46
What is it? ································· 50
Quick note ··································· 56
Overview ····································· 66
CONFIGURATION ·································· 98
System Information ··························· 108
Files Configuration ························· 135
Limits Setup ································· 193
Control Setup ······························· 258
Archiver Setup ······························· 366
Extended Options ····························· 391
RUNNING ········································ 511
Command line parameters ····················· 537
Running under RemoteAccess 2.0 ··············· 560
The log file ································· 612
UTILITIES ······································ 669
Command line parameters ····················· 682
Advanced user tools ························· 768
INFORMATION ···································· 788
Licence and disclaimer ······················· 788
Registration ································· 824
Support ····································· 920
Errors ······································· 981
Acknowledgements ····························· 1061
╓───────────────────────────────────────────────────────────────────────────╖
║ What is it? ║
╙───────────────────────────────────────────────────────────────────────────╜
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, and/or to the Sysop with a warning or message
receipt. Fast and easy to use!
╓───────────────────────────────────────────────────────────────────────────╖
║ Quick Note ║
╙───────────────────────────────────────────────────────────────────────────╜
Although the docs aren't the shortest ones, I suggest you at least
skim through them in order to get your system set up correctly... If
you are confident that you can set up the program and you are really
impatient, then at least read the QUICK.DOC file for a quick guide.
╓───────────────────────────────────────────────────────────────────────────╖
║ 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.0, then you also have the ability to
quickly insert the FILE_ID.DIZ,DESC.SDI or DESC.SDN description into
the file base description. You can also send online messages to the
user to detail why a file failed while still online.
If you are using a BBS package that supports Hudson or JAM messages
then you can set UpCheck to send a message to the user if a file
should fail, as well as the option to send yourself a receipt of the
failure.
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. It also can
quickly comment all of your ZIP files in your current hard drive
collection, in order to bring them all up to date. UpUtils can also
set and return errorlevels depending on the type of archive is being
processed.
╓───────────────────────────────────────────────────────────────────────────╖
║ UpSetup - Configuration program ║
╙───────────────────────────────────────────────────────────────────────────╜
UpCheck is very easy to install. The configuration file and the
UPCHECK.PAC file must be in the same directory as the EXE and OVR
files. All of the other files can be anywhere you like, which allows
for some pretty sophisticated setups.
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.
═══ Serial number
Here you enter your serial 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".
═══ Comment file
This is the name of the file that you want
as your ZIP file comment, if you do not want
ZIP file commenting, then either leave this
blank or turn it off in the Control Menu.
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 that
rarely will you get a duplicate file passed,
nor fail an original one.
═══ Minimum size to record
Any files smaller that this size are not to
be included in any of the check or the data
base of signatures. If this value is 1000,
then any files that smaller than 1000 bytes
will be skipped during processing. This is
used for people who have a large file system
and would rather save the space and time of
a smaller duplicate database then to concern
themselves with watching for small duplicate
files. This can also be set to a value near
2000 if you find that a lot of BBS ads get
passed you, and you don't want them to
effect the users chances of failing uploads.
In other words, play with this number as you
see fit. Leaving it at '0' has the same
effect as versions of UpCheck prior to 5.00
Control Setup
──────────────────────────────────────────────────────────────────
═══ 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 this 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.
═══ Swapping method
Here you can specify what type of media and
which order you want to use for swapping to
when loading external programs. This is to
increase the amount of conventional memory
that will be available to the virus scanner
and the archivers. XMS/EMS and your HDD are
all valid media types. If swapping to disk,
UpCheck will look for a TMP or TEMP enviro-
ment varible and use that path for its swap
file, otherwise the current path will be
used.
═══ Insert ZIP file comment
If you choose, UpCheck will insert a file
comment into the headers of all processed
ZIP files.
═══ Minimum graphics resolution {+}
You can specify the minimum resolution that
an uploaded graphic can be. If the GIF/JPG
is not within the specified range, it will
fail.
═══ Maximum graphics resolution {+}
This is the same as above, but the maximum
resolution that will be execepted.
═══ Security to force pass {+}
If this is not set to Off, zero, then any
user who has this security level or higher
will always get credited for the file. If
for instance, your co-sysop and registered
users upload you something, even if it
fails the test, it will say "Thank you for
the upload" and let the BBS give them the
credit. If you specify, UpCheck will send
you a message, informing you of the fail.
═══ Flag to force pass {+}
This is simular to the security to force a
pass, but it uses the user's flag settings
instead. Remember that currently the only
supported drop file that supports the flag
settings is EXITINFO.BBS
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.
═══ Scanning (Option 3)
This is the full path and file name as well
as the parameters for your scanning program.
If you specify "OFF" without the quotes and
in uppercase, then UpCheck will bypass virus
scanning.
Extended Options
──────────────────────────────────────────────────────────────────
═══ File base format
This is the type of file base that you wish
to use for inserting descriptions.
═══ Update file base
If you don't want UpCheck to write the files
information and description to the database
then select No.
═══ Configuration path
This is the path to your FILES.RA or other
file configuration file. This is required to
locate the correct file database area to use
for the file being processed.
═══ 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 (when using RemoteAccess 2.0)
═══ 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.
═══ Message format {+}
This is the format of the message that you
want created. UpCheck supports both JAM and
Hudson currently.
═══ Message base path {+}
This is the full path to your message base.
If you are using Hudson, then this should be
the path to the "MSGTXT.BBS", "MSGTOIDX.BBS"
"MSGIDX.BBS" and "MSGHDR.BBS" files, which
is normally "C:\RA\MSGBASE\". If using JAM
then it is the path to the JAM message files
(do not include the message area name)
═══ Message board {+}
This is the message board that the message
should be posted to. When using Hudson,
this should be a number in the range of 1 -
200. If using JAM, this should be the name
of the JAM area. (For example, if your JAM
area was "C:\RA\JAM\SYSOP" then "SYSOP" is
the board name and "C:\RA\JAM" is your path
to the message base.
═══ 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.
═══ User notify-online {+}
This when set to to other than No will send
the user an online message to the user that
explains why the file failed.
═══ 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.
═══ Personal reply {+}
This when set to Yes will use the Sysop/User
names for the sender name in messages rather
of "UpCheck 5.01". This allows for ease of
making a reply that gets directed to the
correct person.
═══ 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"
╓───────────────────────────────────────────────────────────────────────────╖
║ 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.0, 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 450k conventional memory free to run this program. (The
actual overhead of the program is only 5k when swapped out, but a
lot of scanners eat almost 450k up all on their own) This program
will run with McAfee Scanner 9.21 V113 in about 450k of memory with
no problems.
Running UpCheck 5.0
──────────────────────────────────────────────────────────────────
═══ Command line parameters
The program takes from one to three command
line parameters.
UPCHECK <filename> <------ LOCAL ONLY
UPCHECK <dropfile> <filename>
UPCHECK <dropfile> <filename> <node>
Remember to call this program after the
user has uploaded a file. <filename> cannot
contain wildcards (*,?)
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.0
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\EXITINFO.BBS @ *N *M
Or if you are running a multinode system:
C:\UPCHECK\UPCHECK.EXE \RA\NODE*N\EXITINFO.SYS @ *N *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.
Here's an example below...
═══════════════════════════════════════════════════════════════════════════
Scan online Yes
Failed scan /move to 58
Scan utility \RA\DOORS\UPCHECK\UPCHECK.EXE \ra\node*N\EXITINFO.BBS @ *M
═══════════════════════════════════════════════════════════════════════════
UpCheck doesn't care about the Failed Scan
action, as RemoteAccess will handle it when
it gets the Pass or Fail sign from UpCheck.
UpCheck doesn't care about the Scan Online
either. If the dropfile is missing, it will
assume that there is no user online and
will surpress any output to the modem. Note
though, that if a dropfile cannot be found,
UpCheck can't figure out who is uploading
the file, therefore will not send mail to
the user, should a file fail.
Also remember to turn on upload scanning in
the area(s) that you permit uploads and set
the LongDesc option to "Yes"
╓───────────────────────────────────────────────────────────────────────────╖
║ UpCheck - The log file ║
╙───────────────────────────────────────────────────────────────────────────╜
The log file contains information about who uploaded what, and what
happened to the file. It has four possible entry types...
1) User: This is the user's name
2) File: This is the file that was processed
3) Code: This is a reference code to explain the error
4) Stat: This is the status of the file
Below is a table that gives a reference to many of the possible
values that "Code" may return.
═════╤════════════════════════════════════════════════════════
Code │ Section = Program return codes
═════╪════════════════════════════════════════════════════════
0-x │ Every program has its own return code setup, consult
│ its documentation regarding the (x) return code
═════╤════════════════════════════════════════════════════════
Code │ Section = Swapping routines
═════╪════════════════════════════════════════════════════════
1-1 │ No space for swapping
1-2 │ Program is too low in memory
4-0 │ Error allocating enviroment
5-0 │ Error calling swap
5-1 │ Could not return from swap
5-2 │ Could not swap out
6-x │ Error caused during redirection
═════╤════════════════════════════════════════════════════════
Code │ Section = Program being called
═════╪════════════════════════════════════════════════════════
2-0 │ Not found
2-1 │ Invalid drive
2-2 │ Invalid path
2-3 │ Invalid name
2-4 │ Invalid drive letter
2-5 │ Path too long
2-6 │ Drive not ready
═════╤════════════════════════════════════════════════════════
Code │ Section = Dos error codes
═════╪════════════════════════════════════════════════════════
3-2 │ File not found
3-3 │ Path not found
3-5 │ Access denied
3-6 │ Invalid handle
3-8 │ Not enough memory
╓───────────────────────────────────────────────────────────────────────────╖
║ UpUtils - System Utilities ║
╙───────────────────────────────────────────────────────────────────────────╜
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, as well as add support for third
party utilities. Wildcards are valid for UpUtils.
Running UpUtils
──────────────────────────────────────────────────────────────────
═══ Command line parameters
/A = Add the files signature into the bad
files listing. This is good for files
that stay the same except their name,
like randomly named BBS ads.
/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) {+}
/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. {+}
/P = This is the same as the /K switch but
will prompt you for a decision before
deleting the file. {+}
/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.
/C = Comment ZIP files. This switch will
comment the ZIP files it comes in
contact with, with the ZIP comment
file as specified in UpSetup.
/Z = Purge the duplicate files database.
This command will remove signatures
of files that are smaller than the
'minimum size to store' setting. The
benifits of a smaller database is
mainly speed while checking for any
duplicate files. The drawback is the
chance of smaller files passing the
dupe check when they are duplicates.
(*This command will rarely be used*)
/E = Returns an errorlevel as specified.
This is only good when creating an
advanced batch file setup. Refer to
the next section for more info.
/R = Returns an errorlevel associated to
the type of file processed. Again,
this is for the advanced batch file
setups.
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.
If you require each file to be processed
fully, use Upcheck in local mode instead
of UpUtils.
╓───────────────────────────────────────────────────────────────────────────╖
║ Advanced User Tools ║
╙───────────────────────────────────────────────────────────────────────────╜
With the UpUtils utility you can build your own advanced batch file.
With a great batch file, you can make just about anything happen with
your archives.
The two functions /REPORT and /ERRORLEVEL allow for some great ways
to handle certain conditions.
The easiest way to show how you can use these is to look at the file
ADVANCED.BAT that is included in this archive.
Remember that UpCheck does not require that you make such a batch
file system and will run just fine in 99.99% of all situations. These
functions are to provide additional ways for you to implement third
party utilities.
╓───────────────────────────────────────────────────────────────────────────╖
║ Licence 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,
UpUtils and the companion utilities 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 distribute a registration key without the express
written consent of Pete Rocca of Multiboard Communications Centre.
You may not use a registration key that is not licensed by Pete
Rocca for use on your system.
It is illegal to edit, alter, hack, reverse engineer and / or modify
any components of the UpCheck archive in any manner.
If you agree to all of the above, then you may use these programs.
By the way, the startup PASSWORD is "ACCEPTED".
╓───────────────────────────────────────────────────────────────────────────╖
║ Registration ║
╙───────────────────────────────────────────────────────────────────────────╜
Commerical Systems
~~~~~~~~~~~~~~~~~~
If you are making or attempting to make a profit by providing services
including but not limited to the transfering of files or messages, and
will be using UpCheck in this enviroment, then you are subject to the
"Commercial Licence".
If registering a commercial system with 3 lines or less, then the cost
for registration is $15. If registering a commercial system with 4 to
20 lines, then the registration cost is $25. For systems running more
than 20 lines, please inquire about a special pricing for your system.
Non-Commercial Systems
~~~~~~~~~~~~~~~~~~~~~~
If you do not fall into the the above "Commercial System" definition
then the cost for registration is $10.
Canada: If registering in Canada then please send the registration
fee in Canadian funds via cheque or money order payable to
"Multiboard Communications Centre" to: 150 Mill Street,
London, Ontario, Canada, M9P1T4.
Outside
Canada: If registering outside of Canada then please send the fee
in US funds via check or money order payable to "Multiboard
Communications Centre" to 150 Mill Street, London, Ontario,
Canada, M9P1T4.
--- Clip Here ---
UPCHECK REGISTRATION 5.01
~~~~~~~~~~~~~~~~~~~~~~~~~
Name: ______________________________________________________
Address: ______________________________________________________
______________________________________________________
City: ________________________ Province/State: ____________
Country: ________________________ Postal/Zipcode: ____________
BBS Name: ______________________________________________________
BBS Phone: ________________, ________________, ________________
Software: _______________________ OS: ________________________
Other relevent information, suggestions or comments
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
I am running a: Non-Commercial System [ ] $10
Small Commercial (upto 3 nodes) [ ] $15
Large Commercial [ ] $25
I have enclosed my fee of ________ [ ] Cheque [ ] Money Order
I am registering within Canada. My fee is in CDN funds. [ ]
I am not registering within Canada. My fee is is US funds. [ ]
Send my registration code via [ ] Mail [ ] Fidonet @ __________
* PLEASE DO NOT USE THESE BOXES *
+--------+ +----+ +-----------+ +--------------------------+ +----+
| / / | | | | x| | | |5010|
+--------+ +----+ +-----------+ +--------------------------+ +----+
--- Clip Here ---
╓───────────────────────────────────────────────────────────────────────────╖
║ Support ║
╙───────────────────────────────────────────────────────────────────────────╜
If you wish to join the support conference for UpCheck, then please
leave me, Pete Rocca, a message @ 1:2401/123 telling me so, and be
sure to include your FidoNet address. The tag name is "UPCHECK". I
will include you in my export list, and you will be able to poll my
system for the mail.
I am also looking for sites that would allow other local sites to
"freq" the newest version of UpCheck from you. In exchange for this
service, you would be listed in the support documentation and would
always be the first to know when a new version of UpCheck is released
Current Support Sites
────────────────────────────────────────────────────────────────────
CANADA
Southern Ontario
Pete Rocca RemoteAccess 2.01
Multiboard Communications DESQview 2.62
London, ON PCL 14,400
(519)660-8981
Fidonet 1:2401/123
Northern Ontario
Rod Aubertin RemoteAccess 2.01
Mostly Country BBS DESQview 2.60
Sault Ste Marie GVC 14,400
(705)777-0114
Fidonet 1:222/30
UNITED STATES
Alaska
Gary Hammer RemoteAccess 2.01
Nothern Exchange BBS OS/2 2.11 (SP)
Fairbanks, AK Hayes 28,800
(907)479-3292
Fidonet 1:355/24
Missouri
Tom Stoltz RemoteAccess 2.01/Pro
Happy Hour RA HST DualStandard
Raymore, MO
(816)322-1133
Fidonet 1:280/301
╓───────────────────────────────────────────────────────────────────────────╖
║ Errors ║
╙───────────────────────────────────────────────────────────────────────────╜
If you ever get a runtime error, chances are pretty good that you have
incorrectly specified a path or file name, or you that the UPCHECK.CFG
or UPCHECK.DAT file is corrupted.
One other possible runtime error you could possibly get would be if a
user uploaded a file that had more then ten levels of embedded files
however in all my years of being a sysop, I have never seen more than
four. If anyone uploads a file that contains more than 10 levels of
embedded archives, chances are that they are real idiots! When I say
levels, I don't mean files. UpCheck can handle an infinate number of
embedded archives, but a level is when a file is archived, then the
archive is rearchived (see below)
ORIGINAL.ZIP (uploaded)
LEVEL2.ZIP is located in ORIGINAL.ZIP
LEVEL3.ZIP is located in LEVEL2.ZIP
LEVEL4.ZIP is located in LEVEL3.ZIP
LEVEL5.ZIP is located in LEVEL4.ZIP
... etc ...
Anyone who does this should be shot quickly. If you feel that this may
be of a problem, you can always disable embedded archive searching.
The last possbility of a runtime error is if a file is locked by some
other process for more than 40 seconds. No other programs should be
accessing the UpCheck data files anyways, and secondly, most programs
that do lock files, do it for very short periods of time (less than a
second) so this shouldn't be a problem.
In any case, if you ever get a runtime error, the only thing that will
most likely happen is that the file will report failed. A runtime
error will NOT cause your system to 'hang'.
Any logical errors or runtime errors that you cannot seem to resolve
should be reported to 1:2401/123 for my evaluation, please include the
error number and location, the look of the screen and the current task
that the program was under and I will get back to you with a solution.
Example : Runtime error 103 at 05C3:3029
\ \
Number Location
Other neat stuff:
UpCheck avoids a large number of problems that other scanners seemed
to have over looked. The classic one is this:
a) a file called TEST.ARJ gets uploaded and rearchived to ZIP
format so now a file called TEST.ZIP exists
b) a different program called TEST.LZH gets uploaded and
rearchived to ZIP, the bbs allowed the upload because the
file TEST.LZH did not exist, but the scanner failed to
realize that another program already existed in the same
directory with the same name. The scanner would either
delete the first file, or add all of TEST.LZH's files into
the first file. Yuck!
UpCheck would have renamed the second file TEST.ZI0 and updated the
filebase accordingly. UpCheck will continue renaming from ZI0 to ZI9
to ZIA to ZIZ as files are duplicated.(Although the rarity of any of
this happening is so far fetched, it shows the detail and concern
that UpCheck exhibits)
Many other scanners will also not update the filebase with the new
size or type of the file once rearchived (and/or the garbage killed)
but UpCheck will always update the base.
Also, many scanners either abort or 'freeze' the system if a caller
hangs up during scanning.... not UpCheck.
If you find a problem, PLEASE let me know as soon as possible so I
can fix it and get you rolling again in no time flat!
╓───────────────────────────────────────────────────────────────────────────╖
║ Acknowledgments ║
╙───────────────────────────────────────────────────────────────────────────╜
This program has been tested on Dos 3.3 through Dos 6.2, DESQView
2.40 through 2.62, DESQView/X 1.2, Windows 3.1 and OS/2 2.0 through
OS/2 2.11, other operatiing enviroments should work fine, but they
have not been fully tested yet.
Requires at least Dos 3.3 and about 450k free conventional memory.
(Can't do much about the memory problem, only 5k of that is mine,
the rest you can blame on McAfee and the author of SQZ.)
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.
The JAM message base format is used in UpCheck and this is the JAM
license header... "JAM(mbp) - Copyright 1993 Joaquim Homrighausen,
Andrew Milner, Mats Birch, Mats Wallin. ALL RIGHTS RESERVED."
The RemoteAccess filebase format is (C) Copyright Andrew Milner &
Wantree Development, 1993. All rights reserved.
Thanks to the public domain swapping utilites that required very
little in the way of tweaking, by Thomas Wagner.
Thanks to a major beta tester, David Gee, who does every possible
thing to crash my program :) 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.
Also thanks to Tom Stoltz and Gary Hammer for their suggestions and
also for becoming the first two support boards for UpCheck.
Also, a BIG 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, and remember, please register, it's cheap!