▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄
█ █ █▄█ █ █▄█ █▄ █ █▄▀ The Premium Upload Scanner
█▄█ █ █▄▄ █ █ █▄▄ █▄▄ █ █ Version 4.0
Copyrighted Pete Rocca & Multiboard Communications Centre, 1994
╓───────────────────────────────────────────────────────────────────────────╖
║ UpCheck 4.0 - 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 archives
however in all my years of being a sysop, I have never seen more than
three. 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 another
process for more than 40 seconds. First of all, no other programs should
be accessing the UpCheck data files, and secondly, most programs that
lock a file, 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.
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, the look of the screen and the current situation that the
program was under and I will get back to you with a solution.
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 anoth 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 to rename 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
removed), 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!
Thanks, Pete Rocca
1:2401/123 -=- 519-660-8981 (14400)