TECHNICAL INFORMATION DOCUMENT TITLE: PTF615 - "IDE Disk Driver Update" DOCUMENT ID: TID300042 DOCUMENT REVISION: B DATE: 25JAN95 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: PTF615 PRODUCT and VERSION: UnixWare 1.1 ABSTRACT: The ptf615 file contains PTF615 - "IDE Disk Driver Update". This PTF also requires a replacement boot floppy #1 diskette available separately in the file boot1.tar. SYMPTOM Cannot install UnixWare v1.1 on machines with IDE drives. A symptom of the original problem was a warning from the disk driver that a disk driver request had timed out. This was most common with IBM controllers. SOLUTION Download the ptf615.dd.Z, ptf615.txt and the boot1.tar file to the /tmp directory on your machine. Create a replacement IHV HBA diskette using the ptf615.dd.Z files. Install your system using the replacement for boot floppy #1 (boot1.tar), the orginial #2 and #3 diskettes from the red box. When prompted for the IHV HBA diskette use the replacement created from the ptf61d.dd.Z image files. Installation Instructions: DATATYPE: compressedimage To create a diskette from an IHV HBA disk image file included in this PTF, become superuser and format a 3.5 inch 1.44MB diskette using: $ su provide root password at Password: prompt place a 3.5 inch high density disk in the floppy drive # format -v /dev/rdsk/f03ht ( f13ht if it's the b: drive ) # uncompress the image using: uncompress ptf615.dd.Z Now dd the image onto the disk using: # dd if=/tmp/ptf615.dd of=/dev/dsk/f03ht bs=1024k note path to dd image may be different use f13ht of it's the b: drive Solution Specifics General Description. These release notes acquaint you with the information for UnixWare PTF615 - "IDE Disk Driver Update". This update requires a replacement for the original boot floppy number one for your product (available separately as boot1.tar) and an HBA boot image floppy created from this PTF. After booting the system using the 3 UnixWare boot floppies, including boot floppy #1 (replace the boot floppy #1 from the original product with the replacement created from the image in boot1.tar), the system will prompt you for the HBA floppy, use the one created from the disk image provided in this PTF. The 3 boot images and the additional HBA boot floppy provide a new disk driver for booting and installing a UnixWare system from an IDE hard disk drive. The booting problem persists when using an IBM WDA-L42 IDE hard disk drive. New Features PTF615 a new HBA boot floppy containing an updated driver for IDE hard drive. Software Notes and Recommendations. PTF615 updates a system file to support IDE hard drives. The only file that gets updated is /etc/conf/pack.d/athd/disk.cfg. This update is for UnixWare version 1.1. Hardware Notes and Recommendations. The PTF is targeted for the i386 and i486 CPU's. Installation Instructions. The PTF consists of two 3.5 boot floppies. The first one contains the UnixWare boot floppy #1. It replaces one of the original boot floppies (the one labeled "1 of 3"). The second floppy is an HBA boot floppy. To install PTF615, place boot floppy #1 (the one which was created using the boot1.tar file, replacing the original one) into the boot floppy drive (drive 0, or drive "A") and reboot the machine. You may now follow the installation instructions stated by UnixWare as the process continues, using the original boot floppies #2 and #3. After processing boot floppy #1, UnixWare will prompt you to insert the HBA floppy into the floppy drive. UnixWare will then continue to prompt you for boot floppies 2 and 3. After processing the 3rd floppy, UnixWare will prompt you for the media with which you want to install the various system packages, such as the base package and the graphics package. After the installation of these packages (usually from cartridge tape or CD-ROM) is complete, UnixWare will again prompt you for the same HBA floppy which you used after floppy #1. Troubleshooting. PTF615 is successful if you succeed in installing Unixware onto your IDE hard drive, and booting from the drive. A symptom of the original problem was a warning from the disk driver that a disk driver request had timed out. This was most common with IBM controllers.