boot(1M)

boot -- UnixWare system boot program

Description

The boot program loads and executes SCO^® UnixWare^® kernels and other stand-alone programs. Stand-alone programs execute before the operating system is up and running, so they cannot depend on operating system services. In normal operation, UnixWare kernels are the only stand-alone programs ever used.

During installation of the UnixWare system, the boot program is placed on the hard disk starting at logical block 0 of the active partition. See fdisk(1M) for a description of the partition table and active partions.

The system invokes the boot program each time the computer is started. It tries to locate the boot program on the floppy disk drive first; if the floppy disk drive is empty, the system invokes the hard disk boot procedure. The boot procedure depends on whether you are booting from a floppy disk or hard disk, as described below.

The floppy disk boot procedure has two stages:

The boot block in sector 0 of the filesystem loads boot.
boot loads and executes the UnixWare kernel.

The hard disk boot procedure has three stages:

The system firmware loads the masterboot from absolute sector 0 on the hard disk.
The masterboot then loads the partition boot program from the active partition.
The remainder of boot is loaded from /stand, a bfs filesystem.

When first invoked, boot displays the following status message:

   Starting UnixWare...

At this point you can press any key to interrupt boot and initiate the Boot Command Processor (BCP). The prompt [boot] indicates that you are in the BCP. In this interactive mode you can make entries in the following syntax:

   PARAMETER=value

which is the same syntax as that used in the /stand/boot file. You can change the values of parameters on the existing parameter/value list, add new ones to the list, or remove system parameters. (See boot(4) for a complete list of valid parameters.)

NOTE: The parameters you add, change, or remove interactively apply only to the kernel that you are in the process of booting, except in the following circumstance: If you are installing UnixWare for the first time (Initial System Load), parameters added using the BCP will be automatically added to /stand/boot. Following all other uses of the BCP you must also edit the /stand/boot file and add, change, or remove them there for the effect to be permanent.

The Boot Command Processor commands can be abbreviated to a unique substring, and are case-insensitive. When param is used as an argument to show, however, it is case-sensitive. The following commands are available:

? or help

Displays this list of commands.

boot [filename]

Loads and runs specified program; default is BOOTPROG.

dir [dev]

Lists all files in /stand directory; default device is BOOTDEV.

logo

Displays the logo image until a key is pressed.

logo off

Turns off display of the logo image for the duration of this boot session.

show [-a | param]

Shows boot parameter values:

-a: Shows all boot parameters, even messages.
param: Shows only boot parameters and messages starting with param.

param=value

Sets the value of a boot parameter.

param+=value

Appends the value to a boot parameter, inserting a comma.

If the TIMEOUT parameter is non-zero (default is 0) and you have not typed anything, boot times out and resumes loading the default program.

For example, you can use the BOOTPROG parameter to change the name of the kernel file to boot from the /stand directory. As delivered, the default is unix. If you change the value of BOOTPROG to unix.old or unix.good, for example, the boot program will load that alternate kernel from the boot filesystem.

If you specify a file that does not exist or cannot be loaded for some reason, you will be warned and will re-enter the BCP.

Files

/stand/boot
/stand/bootmsgs

Diagnostics

The masterboot and boot programs have different error messages.

masterboot diagnostics

The masterboot program displays an error message and locks the system. The following is a list of the most common masterboot messages and their meanings:

Error loading operating system: Disk I/O error occurred when trying to read in the partition boot of the active operating system.
Missing operating system: The sector loaded from the active partition is not marked as a valid partition boot block. (The last two bytes of the 512-byte sector must be ``0x55, 0xAA''.)
Cannot determine disk geometry: The masterboot was unable to determine the logical geometry (cylinders, heads, etc.) of the disk.
No active partition: No partition in the partition table is marked active.

References

boot(4), disksetup(1M), fd(7), fdisk(1M), sd01(7), vtoc(7)

Notices

The computer always tries to boot from any diskette in the floppy diskette drive first. If the diskette does not contain a valid bootstrap program, errors occur.

The boot program cannot be used to load programs that have not been linked for standalone execution. To create stand-alone programs, use the option of the UnixWare system linker ld(1) and special stand-alone libraries.

Although stand-alone programs can operate in real or protected mode, they must not be large or huge model programs. Programs in real mode can use the input/output routines of the computer's startup ROM.