Date:		May 20, 1994
From:		Lloyd Hubbard
Subject:	OS/2 2.1 Service Pak XR06200
		Update from CD ROM

Updating OS/2 2.1 wasn't without complications.  There are several READ.ME files and they are very long, sometimes with duplicate, conflicting, or wrong information.  The upgrade must be started from two diskettes and both 3.5" and 5.25" sizes are provided.  Interestingly, they don't both contain the same files because of space limitations on the 5.25"

The main problem was getting the UPDATE process to find my CD ROM, a SONY 31A.  The SONY worked fine under my OS/2 2.1 installation so I knew it could be recognized.

It turns out that there is a CONFIG.SYS file on DISK 2 of 2 of the update and it must be modified to add the lines calling for the CD ROM drivers.  Simple!  Just copy the appropriate lines from the operative CONFIG.SYS onto the diskette.  Wrong!  The installation program can't find things on the HARD DRIVE so, in installation Disk 2 of 2's CONFIG.SYS file one must first remove the path from the driver location.  Try again.  No luck; the right drivers aren't on the diskette and there's no room for them.  Answer: Remove some of the unnecessary files from a COPY (be sure to make a copy) of the install diskette (Disk 2 of 2) and copy the required drivers from the HARD DRIVE.  After that, a piece of cake.  The installation proceeds smoothly, and excpet when there is a CD ROM file older than one on your HARD DRIVE, requires no operator intervention.

Although my CD ROM controller is part of my Sound Blaster 16 card, it was not necessary to have the Sound Blaster drivers on the installation floppy (Disk 2 of 2), in spite of what the IBM support service said.

Additional notes:  The IBM help line was not much help, they seemed as confused as I was.  Also, I set the resolution to VGA prior to installing the SERVICE PAK, as suggested, using the disks provided.  This worked fine.  The new, S3 32 bit driver for my Diamond Stealth video card was installed after the update and is simple to do by following the installation instructions in one of the READ.ME files.