ZipLab V - I was a Teenage ZipLab
(C)Copyright 1991 by Jeffrey S. Morley
April 20th, 1991
PCBTest.Bat enhancer for PCBoard 14.5
ZipLab V is a alternative/replacement for the normal PCBTEST.BAT file which
is run by PCBoard after a user uploads file(s). In the past, we have all
run maybe PKUNZIP -T on each file, and if there were no CRC erorrs, all
was considered well. There is a lot more we can do to protect ourselves and
our users from unwanted files! ZipLab will do the following:
* Test for CRC errors in the .ZIP file.
* Test for imbedded .ZIP files and if found, CRC check those too.
* Test for imbedded .TD0 (Teledisk) files and if found, test with TDCHECK.
* Virus SCAN imbedded EXE and COM files, using SCAN.EXE from McAffey.
* Remove all .ZIP comments from the file.
* Replace .ZIP comments with your own. (Optional)
* Delete unwanted BBS ads and/or other unwanted ZIP members as you define.
* Reject programs older than a date (year) which you specify.
* NEW IN THIS VERSION!!! ******************************************************
ZipLab V - PTEST.CFG FILE HAS CHANGED!!! YOU MUST RUN SETUP.EXE AGAIN TO
CREATE THE CONFIG FILE. DON'T FORGET THIS STEP, OR NOTHING
WILL WORK!
This version now supports users in NON-COLOR mode. ZipLab will
detect these users, and will not display any colors. The user
MUST STILL HAVE ANSI.SYS LOADED! ANSI codes are used for moving
the cursor. If you have lots of users calling in with non-DOS
machines which can't support ANSI, don't use ZipLab.
Somewhat against my better judgement, you may now ADD a zip
comment to the file while testing. There is an additional
line added to PTEST.CFG. If you can resist the urge to mess
with the .ZIP, please put "NONE" in this field.
Fixed some problems with TestAge, including a bad compile which
was mistakenly sent out in some ZipLab IV packages.
Added the /NOMEM command to the call to SCAN.EXE, so your local
RAM memory won't be tested every time. This will speed things
up quite a bit.
ZipLab IV - This version of ZipLab is now an EXE file, instead of a series
of batch commands. This was done to speed the process up. The
batch file method, while effective and flexible, was very slow.
Many users were becoming discouraged waiting on large,
multi-file uploads to be tested.
*******************************************************************************
REQUIRED:
You must already have the following programs:
PKZIP.EXE - Phil Katz archive create program (version 1.01)
PKUNZIP.EXE - Phil Katz archive extract program (version 1.01)
TDCHECK.EXE - .TD0 (Teledisk) checker from SyDex (any version)
SCAN.EXE - McAffey's virus detection program (any version)
There are other small utility programs which I have bundled with this .ZIP.
Those which were not written by me may require registration for continued
use. PLEASE SUPPORT SHAREWARE AND DO SO!
RECOM.EXE - Mike Loewen's ZIP file comment remover and date stamper.
Quick Start ---
* NOTE! Since PCBoard is SHELLING out to run PCBTEST.BAT, there is limited
memory available for PTEST.EXE. If you are running in a multitasking
or other memory constrained situation, PTEST may not work! You should
have at least 210k free memory when shelled out of PCBoard. If this is
a problem, you may want to consider the VAROOM (overlay) version of
PCBoard, which runs in considerably less memory than the standard PCB.EXE.
The other option is to run PCBoard with the SET PCB = /SWAP environment
variable. This will cause PCBoard to "swap" its code to the best available
storage (EMS, DISK) whenever a SHELL function (external protocol, viewfile,
and even DOORs if you have the SHELL column in DOORS.DAT(LST) set to "Y")
is called. This method will cause a slight delay when SHELLing, but will
provide the largest amount of available DOS memory for your external code.
* Place the PTEST.EXE and SETUP.EXE files into a directory which is in your
DOS PATH.
* UnZIP the enclosed supplemental utilities into directories in your DOS PATH.
Make note of where you put them, you will need this information later.
* Change to your PCBoard HOME directory (C:\PCB for many) and run SETUP.EXE.
The resulting PTEST.CFG must reside in your PCBoard home directory.
* Fill in the following information when prompted by SETUP.EXE:
- The type of modem HANDSHAKE you desire. This can be
0, 1, 2 or 3. 0=none, 1=XON/XOFF, 2=CTS, 3=CTS & XON/XOFF
(Use 2 or 3 with an error correcting modem...)
- The name of your BBS system. 43 characters maximum.
- The DRIVE and PATH to the directory where rejects will be
placed pending manual sysop inspection.
- The date (yyyy) which will be the minimum acepted year. ZIPs
containing files older than this will be rejected.
NEW!!! - The fully qualified filename of the zip comment to add, or
type "NONE" if you don't want to add a comment.
- Full DRIVE:\PATH to PKZIP.EXE.
- Full DRIVE:\PATH to PKUNZIP.EXE.
- Full DRIVE:\PATH to TDCHECK.EXE.
- Full DRIVE:\PATH to SCAN.EXE.
- Full DRIVE:\PATH to RECOM.EXE.
- Full DRIVE:\PATH to TESTAGE.EXE.
(I need these spelled out becuase the method I am using
to get ERRORLEVELS returned to the program requires it.)
- A list, each on one line, of any extensions (.GIF, .TXT etc)
Which will be passed without normal ZIP testing. Any
extensions other than .ZIP which do not appear in this .CFG
file will be rejected by the process. The "." is optional.
- A list, each on one line, of files which you wish deleted
from .ZIP's before posting. This could include the famous
"READMEOR.DIE", "BBS.AD", or other unwanted advertising.
Sample PTEST.CFG file:
2
The Interconnect BBS
M:\HOLD
1990
NEW!!! C:\EXE\COMMENT.CMT
C:\ZIP\PKZIP.EXE
C:\ZIP\PKUNZIP.EXE
C:\ZIP\TDCHECK.EXE
C:\DIAGS\SCAN.EXE
C:\EXE\RECOM.EXE
C:\EXE\TESTAGE.EXE
.ROM
.GIF
ANNOYING.BBS
README.TOO
* Edit your existing PCBTEST.BAT file, and delete the whole thing except
for two lines:
Sample PCBTEST.BAT file:
@ECHO OFF
PTEST %1
* That's it... Now when PCBTEST.BAT is run by PCBoard, it will pass
command over to PTEST.EXE with the parameter containing the path
and name of the file to be tested. PTEST will check out the file,
placing any rejects in the holding directory you specified in the
SETUP process above.
This program was written in QuickBasic 4.5, with some help from Hammerly
Computing's ProBas 4.01. I have also included a few utilities which PTEST
will use in the course of testing. These utilities are the property of the
authors, and you are strongly requested to register them if you continue to
use PTEST.EXE. There is no registration required for PTEST itself, nor for
any of the little utilities included which were written by me.
Jeffrey S. Morley
The Interconnect BBS
(703)425-2505
* PTEST.EXE, SETUP.EXE, DELF.COM and TESTAGE.EXE are my own creations,
and no registration is required. They are all:
(C)Copyright 1989-1991 by Jeffrey S. Morley