This is a suggested procedure for setting up your first DOS+
system disk.

Once you have created a bootable DOS+ system (see -INSTALL.DOS)
put the system tracks on a freshly formatted (i.e. empty) disk.
Then copy CCPXTEND.SYS as the first file.  This will place it
near the directory and minimize head movement in loading (it 
will be used frequently).

Next, do "save 16 subspace".  This will later be erased, but
reserves space for $$$.SUB files created by JOB.  This will
speed up execution of batch jobs.  This space will handle jobs
with up to 32 lines.

On a separate disk, make a COPY of the distributed DOS+24.LBR by

    FCOPY -v dos+24.lbr command.lbr

(or equivalent PIP command.  FCOPY has DU addressing).

Use LU or NULU to strip and re-organize this COPY by deleting
all files except the .COM files.  You can use:

    NULU -o command.lbr -d *.?z? *.rel *.sys --read.me -k -x
or
    LU -o command.lbr -d *.?z? *.rel *.sys --read.me -r -x

(each will ask how many directory entries to assign.  I suggest
 you allow for 40 or more - you will be adding to this library).

(you might as well delete MOVDOS+.COM unless you are using a
 1983 Kaypro IV.)

If you are using LU 3.0 or up, or NULU 1.51 or up, the file 
dates will be preserved during the re-organization.

Now copy this new COMMAND.LBR to your new system disk

    FCOPY -v command.lbr d0:       (d is where your new disk is)

(You may add your favorite utilities to COMMAND.LBR.  STAT and
 NULU will be useful.  DO NOT INSTALL WordStar there if you ever
 use the R)un command.  Never install overlay files.  There is
 no point to installing files that are an exact multiple of the
 disk allocation size, such as LT version 1.5, unless you need
 more directory space.)

When you have finished adding the other files you want (your
own) to the system disk, do "ERA SUBSPACE".  Create it again
before adding new files to the disk or to COMMAND.LBR.  This
will optimize JOB performance.

You can reboot from the new disk now if you wish.

Create LRUN.COM on drive d: (your new disk) by:

    ALIAS d:ccpxtend.sys lrun.com        (takes no added room)

Set all files to be $SYS files with

    STAT *.* $sys

(this last will make them accessible to all user numbers)

To prepare for future date-stamping, do

    INITDIR d:               (d is the drive for your new disk)

DISK.DIR (.DZR) is a listing of my own system disk.  It may be
helpful in organizing your own.

CCPXTEND.SYS bytes 109h thru 110h (as viewed in DDTZ) contains
the name of the program to run when a command is not found on
the path or in COMMAND.LBR. (8 chars, including blank padding).
If set to all blanks no extra try is done.  If you wish to
automatically access your MBASIC interpreter, for example,
change this to "MBASIC  " by

    STAT ccpxtend.sys $dir
    STAT ccpxtend.sys $r/w

    DDTZ ccpxtend.sys
    .... signon etc.
    -s109
    0109 52 'M'
    010A 55 'B'
    010B 4E 'A'       (note use of quoted characters)
    010C 50 'S'
    010D 43 'I'
    010E 44 'C'
    010f 20 .         (exit mode, got to terminating blank)
    -w                (write it back)
    -^C               (exit DDTZ)

    STAT ccpxtend.sys $r/o
    STAT ccpxtend.sys $sys

and now MBASIC will be automatically loaded and passed your
command line.  For this you should put MBASIC on your disk,
possibly in COMMAND.LBR.  Now, instead of "MBASIC xxx" you
will simply enter "xxx" (but "MBASIC xxx" is still valid).

Another possibility is "JOB     ", which will try to run 
a submit file (of type .JOB) on disk or in JOBS.LBR if all
else fails.

There are two more customization points in CCPXTEND.SYS.

Adr.   Default   Use
0103H    'A'     '@' thru 'P', alternate drive to search for
                 commands.  Normally '@' for DOS+ to disable
                 and allow DOS+ paths to control.
0104h    0ffh    0ffh (disable), 0 thru 15=0fh for alternate
                 user to search for commands. 

                 cbf
–æ