DMCFIG
             COPYRIGHT 1987 BY ONTRACK COMPUTER SYSTEMS, INC.
                       ALL RIGHTS RESERVED WORLDWIDE

              DISK MANAGER CONFIGURATION MAINTENANCE UTILITY



This file contains the instructions for using the DMCFIG program.




USE CTRL-S TO STOP AND START THE SCROLLING PROCESS AS YOU READ THIS FILE.




You may print this file by using either PRINT.COM (a DOS utility), your
text processor, or us the DOS COPY command as follows:


              A>COPY DMCFIG.REF PRN <ENTER>


******************************************************************************


This program is intended to ensure the integrity of the system built by
DISK MANAGER.  Specifically, DISK MANAGER requires two things in order to
properly operate in the system of your computer.  If these two prerequisites
are not met, you will experience an error SIMILAR to the following when
attempting to access a partition which DISK MANAGER has placed on your disk:

                 INVALID DRIVE SPECIFICATION

If you do not experience this type of error message, DMCFIG will not be
helpful to you.

DISK MANAGER allows the use of large and nonstandard disk drives through a
device driver.  This device driver makes the partitions that DISK MANAGER
creates as types "WRITE-READ" and "READ-ONLY" useable to your system as
individual DRIVE-LETTERS (C:, D:, etc.).

Our device driver is named "DMDRVR.BIN". The following rules MUST be
satisfied to see that it gets installed when your system boots:

          1) The file "DMDRVR.BIN" must be on the boot device
          2) A file "CONFIG.SYS" must be on the boot device, and
             it MUST reference the DMDRVR.BIN file.

              a)  As a minimum, we require a statement to read

                        "device = dmdrvr.bin"

                  to appear in CONFIG.SYS.

              b)  Other "device =" statements may also appear if desired.

              c)  For more detailed information on CONFIG.SYS, see your DOS
                  manual.

                                    PAGE 1






Normally, when DISK MANAGER creates a BOOTABLE DOS PARTITION on the disk,
it automatically sets that partition up in such a fashion as to cause the
device driver to load properly.  There are, however, several circumstances
which could cause the device driver to become "configured-out" of the system:


          1) Installation of some applications will alter the CONFIG.SYS file
             and delete the reference to our driver.

          2) Use of the DOS "format" command on the DOS partition will clear
             our driver file and the config.sys file.

          3) Use of the DOS (or other backup means) RESTORE process which
             changes the contents of CONFIG.SYS.

          4) Inadvertently deleting or erasing either CONFIG.SYS or our
             driver file.

          5) Installing a second physical disk, when the first was already
             installed, but NOT by DISK MANAGER.

Fortunately, DATA IS NEVER LOST from the driven partitions when these
situations occur.  The data is temporarily inaccessible, but it remains
intact.


DMCFIG can be invoked from the "A>" prompt with the DISK MANAGER diskette
in the A: drive.  By default, it assumes you will be booting off of the C:
drive, which is normally the first NON-FLOPPY drive in the system.

Invoke DMCFIG as follows:

A>DMCFIG<ENTER>          to maintain the C: drive

      or, alternatively,

A>DMCFIG D:<ENTER>       to maintain the D: drive (substitute any
                               valid drive-letter)


DMCFIG will perform the following actions:


1) Verify the existence of CONFIG.SYS on the given drive-letter.

   If it is not found, it will be created with an appropriate reference
   to our device driver.

   If it is found, it will be examined for the presence of a line which
   invokes our device driver.  If it does not find one, an appropriate
   line WILL BE ADDED at the beginning of CONFIG.SYS.

   DMCFIG will notify the operator of any action it takes.






                                    PAGE 2






2) Verify the existence of DMDRVR.BIN on the given drive-letter.

   If it is not found, a message is issued which indicates it was not
   present, and instructions are displayed on how to get it out there.
   Specifically, you must COPY it from the DISK MANAGER diskette.

   Example:    A>COPY DMDRVR.BIN C:

          This example assumes the DISK MANAGER diskette is in A:, and
          that your target boot disk is C:.

   If it is found, you will be notified accordingly.


3) DMCFIG will then terminate.



Please note that you are free to modify CONFIG.SYS to perform this or
other functions with your favorite word processor, or EDLIN, or COPY CON,
etc.  We believe DISK MANAGER to be fully compatible with all other
well-behaved device drivers and applications.

As long as the appropriate CONFIG.SYS and DMDRVR.BIN files exist on
your boot device, you should see the DISK MANAGER sign-on banner when you
boot the system, and the driven partitions should be valid drive-letters.

If this still does not occur, there are probably NO "WRITE-READ" or "READ-ONLY"
DISK MANAGER partitions on your disk.  You may use "DM /M" (DISK MANAGER in
MANUAL MODE) to inspect the PARTITION TABLE to see if this is the case.




























                                    PAGE 3