Obtain new drivers

The new drivers are in a self extracting zip file on the IBM Device Driver Web site. Download ftp://ftp.software.ibm.com/ps/products/os2/os2ddpak/idedasd.exe to a temporary directory and unzip it. You should get the following files

• ibm1s506.add - the disk device driver (needed even if you use SCSI)
• os2dasd.dmd - the DASD manager
• ibmidecd.flt - the filter for IDE CD drives
• ibmatapi.flt - the filter for ATAPI devices
• os2cdrom.dmd - the CDROM device manager
• ibm1s506.sym - ignore, idedasd.ddp - for the GUI installer, readme.txt.

Diskette Preparation

Create new installation diskettes (watch out for diskette naming - the boot sequence is INSTALL diskette, diskette 1, then diskette 2 for Warp 4). To do this run CDINST.BAT which is in the root directory of the CD. This is a DOS program.

Copy the new disk drivers ibm1s506.add, os2dasd.dmd and ibmidecd.flt to diskette 1.

Using a text editor, open the file on diskette 1 called CONFIG.SYS. Add a line at the bottom SET COPYFROMFLOPPY=1. This will cause the install to copy the new drivers to the hard disk.

Boot from the install diskette and follow the instructions.

Drive partitioning

With todays big disks some partitioning can be very useful. You can have many OS's on your system and control booting using the Boot Manager supplied with OS/2's FDISK. You get an opportunity to partition a disk early in the first install phase. A typical partition arrangement is

• Boot Manager - minimum size (one cylinder)
• C: - Primary - Windows
• C: - Primary - Another Windows or DOS
• D: - Logical - A common FAT drive
• E: - Logical - OS /2 HPFS (say 500MB)
• F: - Logical - whatever

Many people put two OS/2's in, on separate disks. Keep your bootable operating systems in partitions which are entirely below 1024 cylinders on the disk.

Utilities

You can run OS/2 from a command line using the boot diskettes. It is sometimes handy to have a diskette with utilities on it. This diskette will also need some DLL's. A typical list of files is

• FDISK.COM (type FDISK for a panel, FDISK /QUERY for a listing or FDISK /HELP)
• FORMAT.COM (FORMAT C: /FS:FAT, FORMAT E: /FS:HPFS)
• The CHKDSK files are fixpack sensitive, ask for details.
• TEDIT.EXE and TEDIT.HLP
• XCOPY.EXE
• UHPFS.DLL (HPFS utility support)
• VIOCALLS.DLL, KBDCALLS.DLL and NLS.DLL

Warp 3

Because of the state of CD development when Warp 3 was released, Warp 3 has trouble installing IDE CD drives. You will need to manually add to the config.sys on diskette 1 BASEDEV=IBMIDECD.FLT.

You will also need to change the CD selected during the install to IDE, or manually intervene after phase 1 and update the config.sys on the hard drive.

Warp 3 does not have Plug and Play functions. In Warp 4 these are implemented in the *.snp files.

Removeable drives

For the like of Zip and Jazz drives you will need the statement BASEDEV=IBMATAPI.FLT in the config.sys.

SCSI

The SCSI support with Warp 4 will generally work, but you still need to make the above changes. For newer cards you may need to get drivers from the Device Driver Web site.

Remember if you install another IDE drive later on, it takes a drive letter which is early in the sequence which bumps all the SCSI drives up one letter, thus rendering any OS on a SCSI drive unusable. Consider using small placeholder partitions for the drive letters that the IDE drives will use.

Display drivers

Don't install display drivers during the install. Just let OS/2 install its basic VGA drivers. Get the latest drivers for your card and install them afterward.

The Scitech Display driver will save you a lot of hassles and is compatible with most video cards. You may need some advice regarding appropriate cards and drivers.

Problems