Technical article 105937

SCO OpenServer installation bootstring options.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

SCO OpenServer 5.0.4, 5.0.5 or 5.0.6, 5.0.7 is not installing properly.

Cause

Some systems require the use of a bootstring for a successful
installation.  Also, some systems require additional drivers
not supplied on the SCO installation media.  For example,
Compaq servers may require the use of the Compaq Extended
Feature Supplement (EFS) in order to install the operating
system.

Solution

The following optional bootstrings can be used while installing. To use them at the "boot:" prompt, the term "defbootstr" or "restart" (the terms are equivalent) needs to be part of the syntax and is placed before the bootstring(s) to be used. For example:

boot: defbootstr scsi.noscan
or:
boot: restart scsi.noscan

The above example is not meant to be used for all scenarios. It is used as an example of the syntax for the acceptance of the bootstring(s) into the installation default bootstring.

Many times when an installation fails there will be a clue as to why it failed. For example, an error relating to a specific driver that is not being used for installation can be disabled.

Following are some of the common bootstrings available. (All of these are to be entered at the "boot:" prompt. The syntax "defbootstr" would be typed in one time after boot: as in the example above.)

To disable machine architecture checking, type:
mcheck.disable

To prevent the installation from attempting to retrieve information about hardware in the system on the PCI bus, type:

pci.bios32

To prevent the bus from being scanned for additional hard drives, type:

scsi.noscan

To prevent the ATAPI interface on the IDE bus from being scanned for hard drives, type:

wd.noscan

To disable a particular driver from loading during installation (making sure that the driver being disabled isn't one that is needed to install the operating system), type:

disable=<driver>

For example, on some Compaq systems you may need to enter the string:

boot: defbootstr disable=ida
or
boot: restart disable=ida

Also, multiple drivers can be disabled in the same string, as seen in this example:

boot: defbootstr disable="ida,wdha"
or
boot: restart disable="ida,wdha"
The above will prevent the IDA and wdha drivers from being
loaded.  However, if you are using the Compaq Integrated Disk
Array controller, you would not want to disable the IDA driver
from loading.

To limit the amount of RAM available during the installation, type:

mem=1m-16m

To link in a particular driver that is not part of the installation media, type:

link=<driver>

Note: If you need to link in an additional driver(s) you will need to have the driver on a floppy that is in a Boot Time Loadable Driver (BTLD) format.

To link in multiple drivers:
link="driver driver"
For example:
boot: defbootstr link="alad ida"
or:
boot: restart link="alad ida"

To specify a location of a SCSI hard drive (OpenServer 5.x.x):

Sdsk=<driver>(0,0,0,0)

where "driver" is the name of the host adapter driver, and "(0,0,0,0)" is (adapter number, bus number, SCSI ID, lun).

Adapter number is "0" for the first adapter using this driver, "1" for the second, etc...

To specify a location of an EIDE (IDE) CD-ROM (OpenServer 5.x.x):

Srom=wd(n,n,n,n)    Srom is for a CDROM.

In this case the (n,n,n,n) stands for the following:

(IDE Controller, Master/Slave, LUN, BUS)

The valid options for "n" are "0 or 1".

In the above examples:
IDE Controller:  0 = Primary    1 = Secondary
Master/Slave:    0 = Master     1 = Slave
LUN:             0  (LUN for an EIDE/IDE device is always 0)
BUS:             0  (BUS for an EIDE/IDE device is always 0)
Example:  To specify a CD-ROM that is on the Secondary IDE
controller in the Master position, the following bootstring
could be used:
boot: defbootstr Srom=wd(1,0,0,0)
or:
boot: restart Srom=wd(1,0,0,0)

Note: In many cases if the CD-ROM is the only device on an IDE interface it must be "Master" to be found during installation.

Note: You cannot specify the location of the installation
IDE hard disk in the same manner.  For instance, you cannot
point the installation at the Secondary/Master disk with
the bootstring "Sdsk=wd(1,0,0,0)".  Simply put, if IDE
disks are present, there must be a Primary/Master drive
configured in order for the installation to proceed, and
the installation will use that disk as the root drive.  No
other IDE disk configuration will work, and hence, the
bootstring "Sdsk=wd(......)" has no effect in _any_ case.

This problem is overcome with the latest "wd" driver available from:

http://www.sco.com/support/update/download/release.php?rid=22
Posted 18-AUG-2004
This will permit an IDE disk to boot as a Secondary Master and will
be detected automatically at Initial System Load (ISL).  Note, though
that OpenServer must be installed within the first 4GB of this disk.

If you have a SCSI disk attached and wish to boot from this then the bootstring to use would be:

defbootstr hd=Sdsk

This will recognize the SCSI drive as the primary.

NOTES:    For OpenServer 5.0.6 there is also a "disable=uhci" for USB support.
          This is relevant should USB support conflict with an already used
          interrupt when SMP is installed.
NOTES:    Certain computers may require a bootstring that others may not.

In the examples where the characters "< >" are used, these symbols are not entered; they were used to denote a general term.

See also

TA105826 "SCO OpenServer 5.0.4 installation hangs during hard disk initialization."

TA105741 "My 5.0.4 install fails with "Warning no controller response on SCSI adapter..."

TA105732 "Installation of SCO OpenServer 5.0.4 on Compaq Deskpro 4000."

TA105644 "How do I install OpenServer 5.0.4 on the Compaq ProLiant 2500 or 800 using the integrated SCSI controller for my hard drive(s) and an IDE CD-ROM?"

TA105675 "What version of the Compaq EFS should I install with SCO OpenServer Enterprise 5.0.4?"

man bootstring(HW)

From the Xinuos technical article database, record 105937. Reproduced with permission. The original is at www.sco.com/ta/105937, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.