User`s manual

NBO - Network Boot Operating System

3-144

Note that certain arguments are passed (through MPU registers) to

the loaded program. The following is a list of the MPU registers and

their contents:

Invoke the NIOT command with the H option to see which LUNs

are available. Refer to Appendix G for a list of LUNs.

NBO uses primarily the BOOTP and TFTP protocols to load the

boot file. Refer to the DARPA Internet Request for Comments RFC-

951 and RFC-783, respectively, for the description of these

protocols. You may skip the BOOTP phase (address determination

and bootfile selection) by specifying the IP addresses (server and

client) and the boot filename; the booting process would then start

with the TFTP phase (file transfer) of the boot sequence.

You may invoke NBO without any arguments. Depending on the

interface's configuration parameters, the display of various IP

addresses and the boot file name signifies that the BOOTP phase

was successful. The booting process halts and waits about 5

seconds for you to abort (by pressing the BREAK key).

If you do not abort, a <CR><LF> sequence is printed to signify the

entrance into the TFTP phase of the boot process. Once this phase is

started, you cannot abort unless a time-out condition arises. When

R3 Controller Logical Unit Number (CLUN) of the boot

R4 Device Logical Unit Number (DLUN) of the boot

R5 System Call Support available

R6 Base address of Network Controller Device

R7 Execution Address of Load Program

R8 Address to IPAs (Client, Server, Gateway)

R9 Pointer to Filename String (i.e., string start)

R10 Pointer to Filename String (i.e., string end + 1)

R11 Pointer to Argument String (i.e., string start)

R12 Pointer to Argument String (i.e., string end + 1)