Installing SCO UNIX on an HP Netserver

NOTE: For OpenServer 5.0.0 you must type “ahslink” instead of “link”.
OpenServer 5.0.2 (and later) use “link”.
A. If your CD-ROM or tape, and boot disk are connected to the internal
embedded SCSI controller on NetServer models that use either the alad or
arad driver (see table earlier in this document), press Enter or type “restart”.
OpenServer release 5.0.x automatically detects the controller.
Restart
B. If your boot disk is connected to the internal embedded SCSI controller on a
NetServer LH 3, LH 4, or LPr then you need to replace the slha driver that ships
with OpenServer 5.0.x. At the “Boot:”” prompt type:
restart link=slha Sdsk=slha(0,0,0,0) Srom=wd(0,0,0,0)
Note that you use slha in the link part, and “slha” in the Sdsk part. While
loading the driver from the driver diskette you will be prompted to replace the
existing driver by entering the table entry numbers that are listed (typically 28
and 2).
If you are not using the Symbios SCSI controller on these systems you should
enter “disable=slha” at the “Boot:” prompt.
C. To install OpenServer 5.0.0 or 5.0.2 to the HP NetServer LXr Pro you will
need to use a new N1 diskette for SCO SLS OSS444 (or later). The NetServer
LXr Pro has the CD-ROM connected to SCSI A and the boot disk connected
to SCSI B. The OSS444 N1 diskette contains multiple instances of the “alad”
driver built in. At the “Boot:” prompt type:
restart Sdsk=alad(1,0,0,0) Srom=alad(0,0,5,0)
If you then install SCO Advanced Hardware Supplement (AHS) 5.2.0 after
the system is installed you will have to manually edit the file
“/etc/conf/cf,d/mscsi” to change the “number” field for the “Sdsk” line from
“1” to “0”, and the “Srom” line from “0” to “1” since the “alad” drivers in
OSS444 and AHS 5.2.0 use a different scheme to number controllers. After
editing the “mscsi” file you must relink the kernel:
cd /etc/conf/cf.d
./link_unix -y
Then reboot your system.
If you rebooted your system after installing AHS 5.2.0 but before editing the
“mscsi” file your system will not boot. You must reboot your system using an
old kernel by typi ng “unix.old” at the “Boot:” prompt. You will then be able