home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
UPCHECK
/
EXZT223K.ZIP
/
EXZTEST.NEW
< prev
next >
Wrap
Text File
|
1993-09-18
|
12KB
|
253 lines
┌───────────────────────────┐
│ What is new in ExZTest? │
└───────────────────────────┘
ExZTest v2.23 ß11 September 18, 1993 01:00
─────────────────────────────────────────────────────────────────────────────
o Added EXZCLEAN.EXE to the job stream (used by EXZTEST for
a long time now). Seems that some braindead sysops are
now on a new kick - that is to insert their file
description into ZIP files as FILE_ID.DIZ if one does not
exist there. Not to even mention the probable reliability
of such a description, the new file will have the sysop's
then current system date, regardless of the rest of the
files in the archive which may well be antiques - thus
effectively defeating any age checking the code might do
later. ExZClean will reset the date of any FILE_ID.DIZ or
DESC.SDI file to the most recent date found in the archive
(excluding these two files). It will also remove any
files which contain the ASCII character 255 in their name
- a favorite of some pirate boards to make deletion of the
file difficult.
ExZTest v2.23 ß10 July 30, 1993 Not a wide beta release
─────────────────────────────────────────────────────────────────────────────
o I think I finally got the freezing problem nailed in this
one. Seems the code was inadvertantly compiled with only
100h bytes of stack space which can create some mean
prooblems. Fixed.
ExZTest v2.23 ß9 July 29, 1993 Not a wide beta release
─────────────────────────────────────────────────────────────────────────────
o I had a report of ExZTest hanging on return from the last
update. While the debug session it was put through did
show up a small problem, the hangs did not come from
ExZTest. The problem turned out to be in some versions of
FWKCS.EXE which ended up stepping on QEMM (this problem
was only evident on a machine with QEMM loaded). I don't
know which specific versions of FWKCS may have had this
problem beyond 1.19, however, version 1.21 (the current
release at the time of this writing) works flawlessly.
Upgrading to it, at least as far as ExZTest is concerned,
is transparent.
ExZTest v2.23 ß8 July 24, 1993 23:00
─────────────────────────────────────────────────────────────────────────────
ExZTest support, as some of you well know, was handed over
to someone else quite some time ago. It was hoped that
modifications and improvements would be forthcoming on it,
things which I knew all too well I would not have time for
in view of then pending software projects. As best as I
can establish, there has been no new development on
ExZTest, in any shape or form, with the possible exception
of one, interim release. But, things do change and
admittedly I am used to running this code, although there
may well be others out there today which perform like
functions. Beta 8 brings back an old tradition - it
brings ExZTest back to its roots. :) You need to
understand that this is a minor update only, thus the beta
designation has not been removed at all. I am still in
the midst of a major project (come and check out CMS if
you haven't yet heard about it!) and still do not have the
time for serious work on it. Nonetheless, some ideas are
now going on the drawing boards for ExZTest 2.5 which will
be a near complete re-write! Look out! With all that
said....
o Unlike beta versions of the past, this one is a public or
wide beta release.
o Minor internal changes to accomodate toolkits I am
currently using.
o ExZTest was having significant problems with the new SCAN
due to SCAN's increased memory requirements. ExZTest will
now swap itself out of memory leaving behind only about
3000 bytes of resident code. It will look for XMSmemory,
EMS memory and disk, in that order, to accomplish this.
This does not mean you should not have PCB set to swap any
longer!! YOU SHOULD! :)
o ExZTest no longer looks for the PCBoard /SWAP environment
variable! Since version 15 no longer uses this, it is up
to you to insure that in fact, you are swapping from PCB!
o ExZTest no longer supports ZDCS. It has been a long time
since I have worked with either program (ZDCS or ExZTest)
and a lot of changes have been made to ZDCS as I
understand it. ZDCS is working well with other duplicate
checker(s).
o ExZTest continues to work with FWKCS. It will work fine
with recent versions although FWKCS now has some
additional features which are not currently used by
ExZTest.
o The ExZUtil companion to ExZTest has been re-written.
This program continues to have 2 functions: a) to
establish if an EXE is a self-extractor and b) to place
the most recent file date contained within the archive on
the ZIP file. If you have ExZUtil.Com in a search path,
ExZTest will automatically find and use it. ExZUtil is
now nearly "bullet-proof" in accuracy! I have yet to be
able to fool it. Although ExZTest does not currently
address this, ExZUtil now also correctly identifies ARJ
and LHA archives and self-extractors!
ExZTest v2.23 ß5-ß7
─────────────────────────────────────────────────────────────────────────────
o Not released.
ExZTest v2.23 ß4 August 23, 1991 22:30
─────────────────────────────────────────────────────────────────────────────
o Modified handling of PCBOARD.SYS to handle files created
by /X versions (greater than 99 nodes).
ExZTest v2.23 ß3 August 23, 1991
─────────────────────────────────────────────────────────────────────────────
o Yet another problem identified with ZIPs containing
directory information. This one, unfortunately, made
ExZTest go into an endless loop (sigh). Fixed.
o I had a report that SENDCOM locked up a Hayes Ultra. Since
I could not test this (I have no Hayes modems) I have
added the ability to also interface the code with Sam
Smith's Proecho program. This was tested with Proecho
v3.2 beta only. To trigger the interface for Proecho
simply change the "/SN" command line parameter to "/SP".
You can use either of these 2 programs depending on this
command line switch.
-> Due to the lockup problem corrected above I will make this
beta available from conference 168 (Ex-Support) on ExecNet
and from the Ex-Support conference of Hacker Central (the
support system for ZDCS). PLEASE, DO NOT POST THIS CODE
FOR DOWNLOADING ANYWHERE ELSE AT THIS TIME!!!
ExZTest v2.23 ß2 August 12, 1991
─────────────────────────────────────────────────────────────────────────────
o Well, I'll be! I have no idea how this sucker worked
here, perhaps SENDCOM defaults to COM1, I dunno.. In any
event, Reggie was right - I was pulling the port number
info from PCBOARD.SYS 2 bytes too early! Yuk! Beta 2
corrects this and will now correctly send the COM port
number to SENDCOM (sigh).
o I found yet another odd one (so much for beta testers,
heh!). If you uploaded a file which was, in fact, a text
file (small) but you called it .ZIP the preliminary ZIP
checks would not find an error. Since there woul dnothing
to log to the duplicate databases no batch file was being
built for it BUT the SHELL to the (non-existant) batch
file was done, never the less. End result? You'll be
sitting at a DOS prompt same as if you'd have typed
COMMAND.COM (sigh). No security breach since the caller
would have no means of accessing the system but the node
would be hung. Fixed.
ExZTest v2.23 ß1 August 10, 1991
─────────────────────────────────────────────────────────────────────────────
o Rather than re-invent the wheel (so to speak) I have added
limited support toward displaying text through the COM
port while ExZTest is working. In order to use this
feature you need to accomplish a few tasks. Please read
this one carefully if you intend to use this feature! The
obvious pupose here is to keep the caller informed
(somewhat) while we do all the darned testing in hopes
that they will not drop carrier after a minute or two..
1. I have supplied a file called EXZSEND in this ZIP as a
sample. It contains 8 lines of text which will be
used. The name CANNOT be changed and the file MUST be
placed either in the default directory (when ExZTest is
running) or in a DOS search path. More on this in a
minute..
2. Optional interface has been added to ExZTest to use
SENDCOM, a free offering available from numerous
systems (included in this ZIP for you). This program
should be placed in a DOS search path so that is
accessible from all nodes.
3. ExZTest will fetch the content of EXZSEND and insert
send instructions to the work file it uses in the
appropriate places, according to your setup options. In
order to trigger this you must add "/SN" to the ExZTest
command line (your PCBTEST.BAT file).
4. If you look at EXZSEND you will readily see how the text
is used. You can change the text to your liking as long
as you observe a few rules:
a) Each message must be only 1 line;
b) A line CANNOT exceed 100 characters (and I'd
recommend less!);
c) No control characters (e.g. TAB) can be used. If
you want to indent the display use any number of
spaces to accomplish this at the start of a line.
ExZTest will look for leading spaces and replace
them with ASCII 255 to make sure they correctly get
through the com port;
d) Each line must be CR/LF delimited - standard ASCII
text file;
e) Line feeds, if deemed necessary, can be inserted on
a line by adding the characters " CR " (without the
quotes) any place. The characters "CR" must be in
caps. Note that there is an automatic CR at the end
of a line already, and there are two additional CRs
inserted before the first line is used and after the
last line is used.
f) No color codes should be added! ALL charcters will
be sent as they exist in the file. No checking is
done for the caller's graphics mode to strip ANSI,
if it exists!
5. If the /SN option was used *and* PCB color codes are
not turned off, ExZTest will also insert a @cls@ into
the PCBPASS/PCBFAIL file automatically.
6. If /SN was not on the command line all the above will
be totally ignored and bypassed.
Have fun! BTW, this is a small change. Even though this
one is marked beta (I am tired of all these releases, heh)
it does NOT require registration.