;
                                 MYLOAD.COM                                   

             Size (recs) CRC   Version    Author/Latest Issue      Disk
               4k (25)   962E  1.0a       Hal Bower 12/90          Z3COM7

  1- Syntax  2- Configuration                                                 


   MYLOAD is an Intel HEX file loader/overlayer.   It is written as a Z-System
Tool, and relies heavily on Version 4 of  The Libraries for  proper operation.
As a Z-System tool,  it accepts DU: or DIR: specifications for re-direction of
file input.   It  also contains  an extensive  parser to  alleviate  excessive
typing.   File Types may  be  specified or default,  but  the  file  format is
somewhat restricted by the basic function of overlaying/loading Intel-standard
HEX files to produce a standard COM file.

   While MYLOAD is primarily intended to apply HEX overlays onto COM files, it
also functions like the old CP/M LOAD.COM.
:1
    Syntax    MYLOAD file

   Myload will load FILE.HEX from and  write FILE.COM to the current Drive and
User areas.  If operating in  the Verbose mode (See Configuration),  a message
will be displayed that FILE.COM cannot be located (assuming none exists),  and
that the program is switching to FILE.HEX.   If FILE.COM already exists in the
current user area,  it will be loaded,  then FILE.HEX loaded over it.   Before
writing the new file to  disk,  a check is made for the presence of the output
file,  and you have the option of replacing the existing file, or aborting the
write.   To load  FILE.HEX to  a  COM file in another User area, or on another
drive, use the syntax:

	MYLOAD DU:=file   or   MYLOAD DIR:=file   (on a Z-System)
 Syntax - 2/4 

   Multiple HEX files may also be loaded  and combined into  a single COM file
by simply listing their names separated by spaces,  commas or other recognized
delimiters as:

        MYLOAD file1,file2, file3,...

   As in the simple load case,  this example  will  produce  FILE1.COM  from a
successive load  of FILE1.HEX  (assuming FILE1.COM does not exist), FILE2.HEX,
FILE3.HEX, etc.   If FILE1.COM already  exists,  it  will  be overlayed by the
following HEX files.  Explicit DU: or DIR: specifications are accepted for all
file entries.  An example of multiple file overlaying is:

	MYLOAD A15:newfile=b3:oldfile work:ovrlay1 newpatch.hx

   In this example, the file NEWFILE.COM would be written to Drive A, User 15.
It would be  comprised  of OLDFILE.COM  (or OLDFILE.HEX if  no COM found) from 
User Area  3  on  Drive B,  overlayed  with  OVRLAY1.HEX in  the  WORK:  Named 
Directory and NEWPATCH.HX (which  must be  a standard HEX file) in the current
Drive and User area.
 Syntax - 3/4  

   Likewise, Named Directories will be printed in a  Z-System where a Name has
been defined for a Drive/User.   If no Name is located, then status lines will
use the DU: form.  When operating in  a "vanilla" CP/M system, the DU: form is
always used for input and output.

   MYLOAD also senses specified  File  Types,  and will not override any which
are so entered with the default COM or HEX.   It is therefore possible to make
an OBJ or other user-specified type for output,  or overlay an input file with
types other than HEX.  The contents of the overlay files will,  however,  have
to follow the  required  Intel-standard  Hex  file  formats.   There  are  two
constraints imposed  by  this.   The first is that no  writes are permitted to
page 0, or any address less than 100H;  and the  second is that the first file
in the argument string,  if no  assignment of an output name is made (no equal
sign), or the first name after the equal sign MUST be EITHER .COM or .HEX.
 Syntax - 4/4 

   The contents of the  overlay  files  will,  however,  have  to  follow  the
required Intel-standard Hex file formats.   There are two  constraints imposed
by this.   The first is that no writes are permitted to page 0, or any address
less than 100H;  and the second is that the first file in the argument string,
if no assignment of an output name is made (no equal sign),  or the first name
after the equal sign MUST be EITHER .COM or .HEX.
:2
 Configuration 

   Two options may be specified by  configuration  bytes in the MYLOAD header.
The first of these  bytes,  located at  115H,  causes  Verbose output with all
status messages to be  displayed.   Setting  this  byte to  a binary Zero will
reduce output to the terminal to only essential  messages,  and errors.   On a
system operating under ZCPR 3.x, this local flag is combined with the Z-System
Quiet flag, so a  "Quiet"  mode will only be  selected when both the local and
ZCPR flag bytes are Zero.

   The second byte controls whether a  BELL  character is sent to the terminal
when errors are detected.   If this beeping creates  an annoyance,  it  may be
disabled by setting the configuration byte  at 116H to  a  binary Zero.   

   Both configuration bytes may be changed by overlaying with a HEX file using
MYLOAD, or with  Al Hawley's  excellent  ZCNFG tool  via  the  MYLOAD.CFG file
contained in the release package.
