CREATE AN OS/2 2.0 BOOTABLE DISKETTE
                             BY MIKE MANTEI
                              MAY 23, 1992

I need to credit Daryl Caudill and Morton Kaplon for most of the information 
that I needed to create these CMD files.  I have taken the information that 
they gathered, put in my own changes and setup the CMD files to do all of the 
work.

I created these files on a 486-25 PC and have tested them as much as I could.  
If you have problems, I will do what I can to help if you leave a message in 
the OS/2 Conference on EXEC-PC.  I make no promises that these will work for 
you, but they do work for me.  

My intention was to be able to create boot disks for the various machines that 
I run OS/2 on.  I wanted these disks to contain the minimum number of files, 
and contain the maximum amount of power and have partially succeded.  These 
CMD files will create 1 or 2 diskettes that can be used to boot your computer 
to an OS/2 command prompt and give you the ability to run CHKDSK.

These procedures assume that you will be using diskette drive A: and that you 
have OS/2 installed in directory C:\OS2.  The files I have created should be 
copied to an empty subdirectory and run from there.  They will copy some of 
the required files from your A: drive to this directory, copy the necessary 
files to your blank floppy(s), and then clean up. 

These files can be used to create an OS/2 bootdisk for your system.  I have 
tried many different options, and have provided 6 different CMD files for this 
purpose.  The file that you use, depends on your system configuration.  Use 
the appropriate files for your system.
 
     BOOTDSK1.CMD - All partitions are FAT and no math coprocessor is
                    present.  CHKDSK.COM will be on the boot disk.

     BOOTDSK2.CMD - All partitions are FAT and a math coprocessor is
                    present.  CHKDSK.COM will be on the boot disk.

     BOOTDSK3.CMD - Partitions can be FAT or HPFS.  No math coprocessor
                    is present.  CHKDSK.COM will only work on FAT
                    partitions.

     BOOTDSK4.CMD - Partitions can be FAT or HPFS.  A math coprocessor
                    is present.  CHKDSK.COM will only work on FAT
                    partitions.

     BOOTDSK5.CMD - Partitions can be FAT or HPFS. No math coprocessor
                    is present.  CHKDSK.COM and HPFS support will be
                    installed on a second floppy.

     BOOTDSK6.CMD - Partitions can be FAT or HPFS. A math coprocessor
                    is present.  CHKDSK.COM and HPFS support will be
                    installed on a second floppy.

These procedures will all require that you have the IBM OS/2 2.0 installation 
diskette and disk #1 and that OS/2 2.0 be installed on your system in the
C:\OS2 directory.  Procedures 1-4 require one blank formatted high density 
3-1/2" diskette and procedures 5-6 require two blank formatted high density 
3-1/2" diskettes.  Just follow the instructions on the screen.

If you look in the CONFIG.SYS file on the original disk 1, you'll
see the system loads the floppy and hard disk drivers for both the
PS/2 and non-PS/2 machines.  Depending on which machine you have, you
do NOT need the other machines drivers loaded.  If you look in the final
CONFIG.SYS file located on your hard disk, you'll see it only loads
the files needed for your machine.

These are the floppy disk drivers included on disk 1:

    IBM1FLPY.ADD  24026    Floppy disk controller driver
    IBM2FLPY.ADD  12997    IBM floppy disk controller driver

These are the hard disk drivers included on disk 1:

    IBMINT13.I13   9564    Generic ISA disk controller driver
    IBM1S506.ADD  12908    ST-506 compatible disk controller driver
    IBM2SCSI.ADD  15780    IBM Generic SCSI disk controller driver
    IBM2ADSK.ADD  10724    IBM ABIOS DASD Device Driver

I'm assuming the IBM1S506 file is faster/better than the generic file, but for 
a boot disk I used the generic driver because its a smaller file.  Obviously, 
whatever your hard disk CONFIG.SYS file ends up with, you should leave alone! 
(unless of course a problem requires you to change it).