Download iRMX Network User`s Guide and Reference

Table 15-1. Boot Client Systems
System Bus*
CPU
NIC
Operating System**
PC
386 or higher
EtherExpress 16
RPC or RFW
MB2
SBC 486DX33
SBC 486DX66
SBC 486SX25
EWENET module
RPC
MB1
SBC 386/2X
SBC 386/3X
SBC 386/12
SBC 486/12
SBC 552A
III
*
**
MB1 specifies Multibus I; MB2 specifies Multibus II; PC specifies PC Bus
III specifies iRMX III OS; RPC specifies iRMX for PCs; RFW specifies DOSRMX.
For simplicity, this chapter often refers to the three remote boot client configurations
as the Multibus I, Multibus II, and PC Bus systems. Remember, however, that
remote booting also requires one of the supported CPU boards and NICs listed in
Table 15-1 and that each hardware configuration runs only one or two versions of the
iRMX OS. The following requirements also apply:
As a general rule, the boot client must contain, in PROM, an iRMX remote first stage
bootstrap loader. However, this is not necessarily true for PCs.
PC Bus and Multibus II systems; there are two possible methods:
•
The boot client NIC contains, in ROM, an iRMX remote first stage bootstrap
loader. You create the ROM using software supplied with the iRMX OS and the
instructions later in this chapter.
•
To remotely boot DOSRMX on a PC or PC-compatible Multibus II board, you
can boot DOS from a local disk or diskette. Then you can use the loadrmx
command to remotely boot DOSRMX.
See also:
loadrmx, Command Reference
Multibus I systems
The CPU boards that support remote booting come with the iRMX remote first
stage bootstrap loader in PROM. The first stage includes the remote device
driver for the 552A board.
See also:
334
Chapter 15
Bootstrap Loader Reference for more about remote booting
Multibus I systems
Remote Booting