home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
z
/
zl2b0103.zip
/
BETA.HST
< prev
next >
Wrap
Text File
|
1993-01-03
|
11KB
|
257 lines
ZipLab Plus 2.ß (BETA)
Beta version history file
IF THIS IS THE FIRST VERSION OF ZIPLAB 2.0 BETA WHICH YOU ARE TRYING, DON'T
EVEN BOTHER WITH THIS FILE. JUST READ AND FOLLOW THE DIRECTIONS IN THE
FILE "ZIPLAB.DOC".
2.ß.4 - January 3, 1992
*************************
Just a documentation change so far today. I wanted to add some stuff
about GIFTEST - These additions have been added to ZIPLAB.DOC.
IV. Using GIFTEST with ZipLab
ZipLab does not pass any default parameters at all to Giftest.Exe. You
will need to do that by specifing the parameters on the line in
ZLAB000.CFG which is for this purpose. If all you want to do is test .GIF
files for integrity, and make sure they pass some standard of resolution
and colors that you set, This is all pretty easy. Just use:
/M:640X480X256 (replace the resolution and colors with yours)
Giftest will work just fine with a simple parameter line like this. If you
want to insert the resolution/colors into the PCBoard description, it gets
a bit tricky... The first thing you have to tell Giftest is what board
type you are running, so follow the parms above (no spaces) with:
/B:x (Where "x" is a "1" for ProDoor or a "2" for PCBoard)
Now we need to tell Giftest where the description file is for the node you
are on. This is the tricky part... To do this, you are GOING TO HAVE TO
HAVE A DIFFERENT ZLAB000.CFG FILE FOR EACH NODE. Follow the parms above
(no spaces) with:
/F:drive:\path\description.file
Now in PCBoard, that is going to be the drive and directory which is
specified on line 179 of PCBoard.Dat, and then the filename of UPDESC.x
where "x" is replaced with the node number for the current node. (just
use UPDESC without an extension if you are not running nodes)
In Prodoor, the path will be your PCB home directory FOR THAT NODE, and
the filename will be $DOOR.NAM.
Please do not use the "/E" parameter on the Giftest parameter line. ZipLab
will take care of the file if it fails, there is no need to have Giftest
erase the file, and it will only confuse ZipLab.
You will then have to do this for each node you have, and they will have
to be in different directories. I recommend that you use something like
C:\ZIPLAB\NODE1 as a directory to hold your node 1 .CFG files. All the
other files for ZipLab with the exception of the ZLABxxx.CFG files can
still be shared and can reside in C:\ZIPLAB or wherever you have specified
in the .CFG files.
Pg14
Then change your ZLAB command line in PCBTEST.BAT to something this for
node 1:
PCBoard:
ZLAB %1 %PCBDRIVE%%PCBDIR% C:\ZIPLAB\NODE1 %2
ProDoor:
ZLAB %TARGET% %pcbdrive%%pcbdir% C:\ZIPLAB\NODE1
The other option is to put the ZLABxxx.CFG files in the home PCB directory
for each node, and then the command line is simple:
PCBoard:
ZLAB %1 %PCBDRIVE%%PCBDIR% %PCBDRIVE%%PCBDIR% %2
ProDoor:
ZLAB %TARGET% %pcbdrive%%pcbdir% %pcbdrive%%pcbdir%
2.ß.3 - January 2, 1992
*************************
Just a quick fix for the .GIF testing routines, which were going off
into a "loop" if the .GIF failed testing on some systems. No changes
required to any .CFG or other files. Just drop in the .EXE
2.ß.2 - January 1, 1992
*************************
1) The configuration files have changed. I have included a small utility
called CFGCVT.EXE in the archive, which can be used to convert your
ZLABxxx.CFG files from the December 28 version to this one. Just
run:
CFGCVT [drive:][\path\]ZLABxxx.CFG
In about a heartbeat, it will come back and tell you that it has
converted the file. You may NOT run CFGCVT.EXE on a single .CFG
more than once, and once you have converted all your .CFG file you
may safely just erase CFGCVT.EXE. A new version will ship with any
future beta's which require .CFG modifications.
All of your modifications will survive the change, with 4 new lines
being added to the .CFG file:
2
The Interconnect Bulletin Board System
C:\FAIL
C:\ZIPLAB\ZLAB000.TCN
199001
Y
Y
Y
1 >> Y
2 >> Y
3 >> C:\ZIPLAB\
C:\ZIPLAB\ZLAB000.CMT
4 >> Y
NONE
C:\UTILITY\PKZIP.EXE
C:\UTILITY\PKUNZIP.EXE
C:\UTILITY\LHA.EXE
C:\UTILITY\ARJ.EXE
C:\UTILITY\TDCHECK.EXE
C:\UTILITY\SCAN.EXE
C:\UTILITY\RECOM.EXE
C:\UTILITY\DELF.COM
C:\UTILITY\GIFTEST.EXE
/B:2 /F:UPDESC.2
GIF;EXE;PCX
C:\ZIPLAB\CRC.ADS
C:\ZIPLAB\LST.ADS
1 - A "Y" if you wish ZipLab to send a mail message to the user
when a file fails testing. A "N" if not.
DEFAULT = Y
2 - A "Y" if you wish the sysop to also receive a mail message in
the instance of a virus detection. A "N" if you do not.
DEFAULT = Y
3 - The DRIVE\PATH\ to the directory which will hold the .MSG files.
These are the mail messages sent to the user/sysop on failure.
Please put a "\" at the end of the path.
DEFAULT = C:\ZIPLAB\
4 - A "Y" if ZipLab should add the contents of FILE_ID.DIZ (if
found) to the bottom of the zip comment. "N" to disable.
DEFAULT = Y
2) I have finished the routines to send mail messages in PCBoard/Prodoor
to the user/sysop if a file fails. This is an optional item, with the
enable/disable of the feature set in ZLABxxx.CFG in 2 of the new lines.
There are sample text files included in the archive. These files are
the ones which will be sent as a PCB/Prodoor mail message to the
user (and Sysop as well in the case of a virus).
The files (and failure reasons) that ZipLab Plus uses are:
NAME OF FILE REASON FOR FAILURE
------------ ------------------
OLDDATE.MSG Failed date limit checking
FILECRC.MSG Failed CRC or -AV checking
IMBEDCRC.MSG An imbedded archive failed CRC or -AV checking
TRASHCAN.MSG .TCN (Trashcan) text was found in the description
BADTD0.MSG A Teledisk format (.TD0) file failed TDCHECK
USRVIRUS.MSG Message sent to USER on virus detection
SYSVIRUS.MSG Message sent to SYSOP on virus detection
UNACCEPT.MSG An unaccepted file format was uploaded
GIFFAIL.MSG A .GIF file failed GIFTEST
These files may NOT be renamed from the sample ones I sent in the
archive, but may be modified to contain any text you want. You
may also use the @ZCODES (see ZIPLAB.DOC) in the text, including
one new @ZCODE described below.
You must also tell ZipLab where the files are located, in the line
which is indicated with a "3 -" above. Only the path please, and
follow the path with the "\" character. I strongly suggest that you
just put these in your C:\ZIPLAB\ directory along with the .TCN,
.CMT, ADS.CRC and LST.CRC.
A sample message file, OLDDATE.MSG:
// MESSAGE FROM ZIPLAB PLUS @V_N@
On @D_T@ at @T_T@ you uploaded:
@F_N@
This file failed ZipLab Plus upload testing.
The reason for failure was:
Date limit failure - Files are older than acceptable limit.
This BBS only accepts programs and files created on @D_L@ or later.
The newest file in this upload was dated @N_F@. Please check the
dates of the files inside an archive before uploading.
// AUTOMATED MESSAGE FROM ZIPLAB PLUS
// PLEASE DO NOT REPLY TO THIS MESSAGE
If you want to send messages for some types of failures and not
for others, just rename or delete the appropriate file. If
ZipLab doesn't find a .MSG file for the failure reason in question,
it will just go on without sending anything.
3) As requested, I have allowed a "Y" or "N" toggle in the .CFG file
to tell ZipLab whether or not to append the contents of FILE_ID.DIZ
(if found) to the bottom of the Zip "comment". A "Y" will enable
the append, a "N" will disable it.
4) The word ONLINE will no longer appear after the user name on the
local screen. This was a bit obvious and cluttered up the
screen for no good reason. The OFFLINE and OFFLINE-OFFHOOK
messages will still appear to let you know the user has hung up,
and that ZipLab has taken the phone line offhook (busy) during
testing.
5) I have added a new @ZCODE: @T_C_T@ This is "Trash Can Text" and
will contain the keyword or phrase which was matched on a file
reject due to .TCN match. This can be used in both the .CMT and
the new .MSG files, along with the original @ZCODES.
6) Several minor cosmetic or technical fixes, with no impact on you.
7) Full ZIPLAB.DOC documentation updated to reflect the changes in
this beta.
OUTSTANDING CURRENT ITEMS:
* FOSSIL driver routines
* Don't check "bbs ads" on date limit validation (it does now...)
* ANSI autodetect
* Allow other virus check programs than just SCAN
* LST.ADS processing WAAAAY too slow
* A version of ZCRC.EXE which accepts DOS "wildcards"
OUTSTANDING FUTURE ITEMS:
* WildCat! version
* Generic version
2.ß.1 - December 28, 1992
*************************
First beta version - Missing the feature of sending a mail message to
the user and sysop on virus detection. This feature in development.