Contents of the READ.ME file
A couple of new things to know before getting started with this copy
of DAZL. First, DAZL (again) requires an environment variable before
starting up. You can get around this by starting DAZL up in your
current directory. See the DOCS for more info (SETUP).
Secondly, the command line syntax has changed somewhat. The earlier
versions used a plus key '+' to prefix the drive list. Beginning with
this version the new prefix key is the colon key ':'. The change is
to facilitate some new code.
Starting with this version of DAZL we are trying to determine
'automatically' if a file with .EXE extension is a ZIP or simply an
other type of executable. This is all transparent to the user, as a
quick check is made before running the executable file. If the file
returns a ZIP code then the file is opened in the ZIP window. The
tradeoff of course is that you cannot extract from this type of file
as a self executing program while running DAZL. You can however TAG
ALL files and extract them yourself, or SHELL to DOS and run the .EXE
There is a problem with this. At least one other program (NARC.EXE (c)
Gary Conway, Infinity Designs) uses an internal string that resembles
the headers used by ZIP files. While alot of programs will do this, the
only ones that will cause problems contain the header type in the last
2048 bytes. Undexpected results occur from program (DAZL) crashes to
unusual ZIP file displays. If you a get an .EXE file that opens in the
ZIP mode showing a single file containing 40 zillion bytes then you
have found an incompatible file.
This copy of DAZL has a limited amount of tamper detection. Without
going into any detail, DAZL reads portions of itself during each
session. If certain information is changed then DAZL will display
an error message and refuse to load. More sophisticated measures
may be introduced but at this time hacked copies of DAZL are not a
problem. More work is being done in this area.
Those wishing to download a fresh copy of DAZL may call the EXCHANGE
BBS. The number is prominantly displayed in the main screen.
Registration to the BBS is required, but you will be able to download
the software on your first visit.
Registered owners will receive the latest version via U.S. Post. If,
as was the case this past two weeks, a new version is forthcoming you
will be notified of such and be given the opportunity to receive the
current version or wait for the new release.
The problem discussed below is also true of PKZIP 1.01. The simple way
out is to not tag files that have the '-' character in them. Try to
discourage others from doing this as it is a character often used to
delimit command options with many programs, PKZIP included.
PKUNZIP uses the dash (-) to recognize command line parameters.
The parameters are supposed to be placed prior to the filename
(and DAZL passes them that way) however PKUNZIP appearantly
recognizes the dash(-) as a parameter identifier irregardless
of the location. This in turn causes DAZL to decompress all files in
the ZIP. If you have selected an output path you they will be
directed into that directory.
A note for owners of large systems. DAZL may encounter a problem if
too many drives/directories are scanned. In testing, DAZL has
functioned properly with up to 12 drives (a total of 242 directories),
however larger drives allow greater trees. Attempts are underway to
increase this limitation.
We regret this inconvenience.