Dear SCO Customer, The enclosed Support Level Supplement (SLS) UOD453A, the Hard Disk Controller BTLD Supplement with support for additional HD BTLDs, contains a replacement wd driver for: SCO UNIX System V/386 Operating System Release 3.2 Version 4.2 SCO Open Server Enterprise System Release 3.0 SCO Open Server Network System Release 3.0 SCO Open Desktop Release 3.0 SCO Open Desktop Lite Release 3.0 SLS UOD453A supplies an enhanced wd driver which provides support for ATAPI (IDE) CD-ROM drives and for large EIDE (Enhanced IDE) hard drives. It also corrects installation errors such as "WARNING: hd: no root device" and "/initscript: /dev/hd00: cannot open." This support is available at installation time or after installation. IMPORTANT: Do NOT use SLS UOD453A with SLS UOD429A. Both SLSs supply ATAPI CD-ROM and EIDE support, however the support is provided for different instances. Use SLS UOD453A when your installation requires a SCSI Host Adaptor BTLD. SLS UOD429A does not support the use of a BTLD. If you are currently using SLS UOD429A successfully, there is no reason to use SLS UOD453A. These two SLSs should not be used on the same system. INSTRUCTIONS AT INSTALLATION TIME 1. Boot the system from the SCO supplied standard N1 boot floppy. 2a. At the Boot: prompt, type the following, if the boot disk device is attached to a SCSI host adapter: defbootstr link=" xwd" hd= Srom=wd(,,) where is replaced by the actual SCSI BTLD name, is replaced by Sdsk for SCSI, or ida0 for Compaq IDA, and , , and are replaced by 0 or 1 as follows: HA# is 0 or 1 and refers to the number of the ATAPI controller; ID is 0 or 1 and 0 refers to the CD-ROM as master and 1 as slave; LUN is 0 or 1 and is the LUN of the ATAPI CD-ROM drive (always 0). NOTE: " xwd" must be entered in that order and enclosed in quotation marks. For example, a common bootstring for a system with the boot disk device attached to a Compaq integrated SCSI host adapter and the CD-ROM drive attached to the primary IDE controller as master device, would be: defbootstr link="CUCHA xwd" hd=Sdsk Srom=wd(0,0,0) 2b. At the Boot: prompt, type the following, if the boot disk device is attached to an IDE controller: defbootstr link=xwd Srom=wd(,,) where , , and are replaced by 0 or 1 as described in 2a above. For example, a common bootstring for a system with the boot disk device attached to an IDE controller and the CD-ROM drive attached to the secondary IDE controller as master device, would be: defbootstr link=xwd Srom=wd(1,0,0) 3. Follow all on-screen prompts. You will see the message, "Characteristic h not supported, ignore." You can safely ignore this message. 4. Step 4 applies _only_ if you are installing on a disk larger than 2Gb. If you are not installing on a disk larger than 2Gb, then you can skip Step 4 and answer the questions covered in Step 4 normally. In the "Hardware Setup" screen, you will see the choices "Preserve" or "Overwrite". If you _are_ installing on a disk larger than 2Gb, then you need to make the choices below respectively for SCO Open Desktop 3.0 and SCO UNIX Version 4.2: - SCO Open Desktop 3.0, you must choose the "Preserve" option during installation. You cannot use the "Overwrite" option. - SCO UNIX Version 4.2, you must choose the "Fully Configurable Initialization" option. You cannot use "Automatic Initialization." For both SCO Open Desktop 3.0 and SCO UNIX Operating System Version 4.2, the following section is relevant. Do NOT Scan for bad tracks. If you have already attempted to scan for bad tracks, and the hard drive is greater than two gigabytes (2Gb) you will need to delete the entries in the Current Bad Track using the procedure below. To delete the badtrk entries: - Select option six (6). - Delete all entries from Current Bad Track Table. - Enter 'q' to quit and press to accept the default value for the bad track space allocation. - When prompted: "Do you wish to update this device with the new table? (y/n)", enter 'y' to update device with the new table. - When prompted: "Do you want to attempt to salvage ...(y/n)", enter 'n'. 5. In the "Hardware Setup" screen, when prompted for installation media, press for additional choices. You will see the choice "SCSI Tape." Press again for more choices. Now highlight and select "SCSI CD-ROM." You will be in the "Installation Media Setup" screen. The only value that can be changed in this screen is the "SCSI ID" value. Press for choices and highlight and select the value 0, if the ATAPI CD-ROM is configured as a master device or 1, if configured as slave. Continue the installation as instructed in the standard SCO documentation and on-screen prompts. 6. In the screen "Filesystem Setup", adjust filesystem sizes if necessary to assure that no filesystem is greater than 2 Gigabytes (2048 MB). When you exit this screen, you may see these messages: "WARNING: Multiple SCSI host adapters detected WARNING: Using SCSI host adapter for installation" where is the BTLD driver name used in step 1 above. You can safely ignore these messages. 7. Next, you will be prompted to boot from the N1 floppy a second time. At the Boot: prompt, enter the identical bootstring as in step 2a or 2b above, instead of pressing , as the on-screen message indicates. Continue to follow the on-screen prompts. When prompted "Do you want to replace the existing wd driver?", answer "yes". 8. To use the CD-ROM after installation, run "mkdev cdrom" to configure your CD-ROM drive. Select wd as the adapter name. Edit the file /etc/default/boot to change the line defining DEFBOOTSTR so that it does not contain any "hd" or "Srom" references. INSTRUCTIONS FOR INSTALLING ON AN INSTALLED SYSTEM 1. Insert the SLS UOD453A floppy in the floppy drive. 2. Type "/usr/bin/installpkg" and follow the on-screen instructions. 3. Type "cd /etc/conf/cf.d". 4. Type "./link_unix -y". 5. To use the CD-ROM after installation, run "mkdev cdrom" to configure your CD-ROM drive. Select wd as the adapter name. Edit the file /etc/default/boot to change the line defining DEFBOOTSTR so that it does not contain any "hd" or "Srom" references. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier. We appreciate your business. SCO Support Services