CREATING AN OS/2 2.1 EMERGENCY BOOT AND UTILITIES DISK SET

Date:  3/10/94

In order to backup, restore, or perform any maintenance on an
OS/2 volume, all files on the volume need to be completely
available (not in use, so that the disk can be either read from
or written to).  IBM recommends that this be done by booting from
the OS/2 "Installation Diskette" and "Diskette 1" floppy disks,
and pressing the ESC key at the installation screen, which exits
to the OS/2 command prompt.  As shipped from IBM, these disks do
not have enough free space to include additional device drivers
that might be necessary for OS/2 to recognize non IBM supported
mass storage devices.  The Iomega Bernoulli disks are one such
item that requires special drivers in order to be recognized by
OS/2.  If a Transportable MultiDisk 150 meg Bernoulli driver were
used to backup an OS/2 system and the OS/2 system crashed, there
would be no way to access the MultiDisk 150 in order to restore
the system. Outlined below are instructions that will allow the
creation of a three diskette OS/2 emergency boot loader with the
necessary drivers to recognize your non IBM supported mass
storage devices.

1)   Copy the IBM OS/2 "Installation diskette" and for our
purposes label it "OS/2  Emergency Boot Disk".  This disk
requires no changes and is the first stage of booting OS/2.  From
now on, this disk will be referred to as "Boot Disk." 

2)   Copy the IBM OS/2 "Diskette 1" and label it "OS/2 Emergency
Boot Diskette 
1."This disk will be modified to allow the installation of OS/2
driver files.  From now on, this disk will be referred to as
"Disk 1".

3) Delete FDISK.COM, SYSINST1.EXE, and SYSINST2.EXE from "Disk
1". These files are not needed to beet OS/2, and take up
approximately 250K of space. We now have enough space on the
floppy disk to install the driver software.

4) Copy the necessary driver software to "Disk 1."  A call to
Iomega's technical support staff revealed that in the case of the
MultiDisk 150 connected via the Iomega Parallel Port Adapter
(PPA), after the driver is configured, only 9 files  totalling
approximately 50K are required for this configuration to be
recognized by OS/2.  These files are listed below and need to
reside in the "\OAD" subdirectory on "Disk 1."

        a)   BETA-MD.DEV  (supports the MultiDisk 150)

        b)   BETA-MD.OPT  (supports the MultiDisk 150)

        c)   PPA.ADP  (supports the PPA)

        d)   PPA.OPT  (supports the PPA)

        e)   CONFIG.DEV  (needed by OS2.SYS)

        f)   CONFIG.OAD   (needed by OS2.SYS)

        g)   IOM$ERR.DAT   (needed by OS2.SYS)

        h)   IOM$MSG.DAT  (needed by OS2.SYS)

        i)   OS2.SYS  (the actual OS/2 driver file) 

5)   Edit the CONFIG.SYS file on "Disk 1" with the following
changes (case is
irrelevant):

        a)Change "protshell = sysinst1.exe" to 
          "protshell = cmd.exe".

        b) Change "set os2_shell = sysinst2.exe" to
           "set os2_shell = cmd.exe".

        c) Change "libpath = .;\;\os2\dil;" to 
           "libpath = a:\".

        d) Change "set path = \;\os2;\os2\system;\os2\install" to
           "set path = a:\".

        e) Change "set dpath = \;\os2;\os2\system;\os2\install"   
           to |set dpath = a:\".

        f) Add the new driver activation command(s) for your non  
           IBM supported device.  

        The command that supports the MultiDisk 150 is, "device = 
        a:\oad\os1.sys a:\oad\config.oad".

6)   Format a third floppy disk, give it the volume label of
"UTILS" and physically label it  "OS/2 Emergency Boot Utilities." 
This disk will contain common OS/2 utilities, and  from now on
will be referred to as "Utils." 


7)   Copy the following files from the hard disk (with OS/2
installed on it) to the "Utils" diskette:

        a)   C:\OS2\CMD.EXE

        b)   C:\OS2\CHKDSK.COM

        c)   C:\OS2\XCOPY.EXE

        d)   C:\OS2\ATTRIB.EXE

        e)   C:\OS2\FDISK.COM

        f)   C:\OS2\FORMAT.COM

        g)   C:\OS2\LABEL.COM

        h)   C:\OS2\BACKUP.EXE

         i)   C:\OS2\RESTORE.EXE

        j)   C:\OS2\SYSTEM\OS0001.MSG 


The above files take up approximately 700K of disk space.  This
should leave plenty of room for additional utilities, or the
backing up of critical OS/2 configuration files.


8) Follow the steps below to start OS/2 from these diskettes:

      a) Boot or restart the computer with the "Boot Disk" in     
         drive A:.

      b) When prompted to insert "Diskette 1" insert our "Disk 1" 
         and press return.

      c) When the OS/2 command prompt appears, remove our "Disk   
         12" and insert  our "Utils" diskette.

      d) OS/2 is now running in a single session mode with the    
         utilitiesthat you need on line to backup, restore, or    
         perform maintenance on you OS/2 volumes.