John,
 
Check back about a week to where I described my problems with getting ZCPR
to work with the Z80DOS BDOS replacement.  I had a problem with the ENV and
PATH getting installed at the wrong addresses since I forgot to install
LDR.COM.  Could this possibly be your problem?
 
INSTALL ALL Z3UTILITIES with Z3INS.  You will not have a problem if you try
to install a non-ZCPR program, since the string 'Z3ENV' will not be present
in the first sixteen bytes at the proper address.  Z3INS will just report that
the program is not a ZCPR program.
 
You are right about there must be a table of addresses for the packages.  It is
in the SYS.ENV.  Look back at SYSENV.LIB and you will see equates which were
satisfied by Z3BASE.LIB at assembly.  THEREFORE, LDR should FIRST load SYS.ENV
and the rest of the packages.  Also, Z3INS must be told where to put the ENV
and then lookup any additional addresses needed.  You do this by installing
LDR.COM with Z3INS.COM or patching the address in at 0109h using DDT or some 
other utility.
 
By the way, I just ordered the WIN89 twenty meg hard disk package for my 
machine.  I'm also considering the purchase of ZCPR3.4 to run on that hardware.
Some of the later features make it appealing.
 
You're doing good with getting the system up.  I made many more mistakes and 
burned a lot of that 'midnight oil' doing the same.  I did it without anyone to
talk to but myself and spend untold hours pouring over the documentation which
you have now for installation.	I know you are getting excited since you're 
so close, but take a little time to go back over the process up to here.  Keep
the printout of the memory map handy.  Reread the descriptions of the packages
and build a diagram of how they interrelate with each other and with the bios,
ccp, and bdos.	This will really help you use ZCPR to its fullest.
 
In brief, the ENV describes your ZCPR system.  It has the addresses of the 
packages implemented in your system, the terminal capabilites and such.  
This address is patched into all ZCPR programs so they can use the included
data to take advantage of the various features of your system or determine 
that they can't run in your system (ex. NO IOP).
 
The RCP allows you to first replace some of the standard CCP commands with
programs which do the same thing, but better.  For instance, I use a program
for directories which alphabetizes, sorts on filename or ext, allows vertical
or horizontal presentation, can dir any user area or all, can also list the 
files in the *.LBR files, and more.  So I don't use the CCP dir command.  The 
RCP can be programed to call this program if someone types the dir command, or
I could just rename the program to DIR.COM.  The RCP method has advantages 
over the latter.  For instance, I can have several directory utilities.  If
a certain dir program called with appropriate switches works best for a 
particular kind of work, I can set up the system to load a different RCP 
before beginning work and have the perfect configuration.
 
The FCP allows you to run ALIAS commands which will handle iterative tasks.
An example might be compiling a program in C to ASM and, then, if no errors
were generated, assemble the code with your favorite assembler along with 
your usual switch parameters, and then, if still no errors, load the program
using the correct program and switches.....,etc.  If there is an error, it 
can abort the process on that code and continue with the next program in the 
list by restarting itself or shut down for your input.
 
The CmdLine allows you to execute multiple commands by typing a single line.
For instance, A0>DIR;ERA *.BAK;DIR would run a directory before and after
the deletion so your can see how much space you reclaimed.
 
I incorportated the WHEEL as well.  I'm looking to set up a machine for Julia,
my wife, to use in a business venture that she and her sister are just getting
into.  This way, I can make the system totally menu driven, allow them access
to the system functions they need, and at the same time, password protect 
certain user areas and prohibit certain functions such as file delete.	I can
still perform ALL of the functions by setting the wheel byte which will now
allow me to leave the menu program, or get to additional menu screens to 
perform the housekeeping functions and do repairs.
 
I hope this improves the picture of what ZCPR can do, a bit about how, and
gives some hope that the work to this point has not been in vain.
 
Later, -- ken
f what ZCPR can do, a bit a