using the bootstrap loader

OVERVIEW OF BOOTSTRAP LOADER OPERATIONS
Remote Third Stage
The remote third stage is similar to the generic third stage in that it only runs in real
address mode and can only load applications in the first 840K of memory. This third stage
works with the iSBC 552A first stage device driver to load the operating system from a
remote device using the Ethernet Local Area Network (LAN).
The remote third stage is different from the generic third stage in that it is loaded by a
combination of the first stage iSBC 552A device driver and the firmware executing on the
iSBC 552A board, not the second stage.
Naming the Third Stage
Both the generic and the device-specific third stages are stored as executable files. The
base portion of this file's name -- the filename minus any extension -- must be the same as
the base portion of the file containing the application system to be loaded. Because the
name of the third stage and the name of the application system must match, you must
provide a separate third stage file for each bootable system on the volume. To provide
additional third stage files, simply make a copy of the third stage file you are now using.
Name the copy so it matches the application system you intend to load.
1.2.4 Load File
1-6
The load file is a file containing the application system you are booting. The load file
should be on an iRMX 1- or iRMX II-formatted named volume. This volume must have
been formatted by the Human Interface FORMAT command. If the load file is an iRMX
II application, the volume must also have a file containing the third stage of the Bootstrap
Loader.
If your load file is an iRMX II application, the name of that file must correspond to the
name of the Bootstrap Loader third stage, as follows:
• The base portion of the load file's name (the filename minus the extension) must be
the same as that of the file containing the third stage.
• The extension portion of the load file's name must consist of the characters ".286".
Bootstrap Loader