Co-Existence of Apricot and Microsoft Remote
Boot Services on LAN Manager 2.X Servers
If a mixture of Apricot LS PROs and older On-Board Ethernet machines are
to be remote booted onto Microsoft LAN Manager 2.1, then both the Apricot and the
Microsoft Remote Boot Services will need to be enabled on the server.
The older Apricot machines with On-Board Ethernet use the Intel 82592
Ethernet processor and will only remote boot onto the Apricot Remote Service. The LS PRO
uses the new Intel 82596 Ethernet processor and uses RPL, hence the need to use the
Microsoft Remote Boot Service.
The existing Apricot Remote Boot Protocol will co-exist with Microsoft
LAN Manager Remote Boot, with only one modification. If this configuration is required,
use the following procedure :
| a) |
Configure the server if needed to use Apricot Remote Boot
(without Microsoft RPL). |
| b) |
Exit Setup and edit the file
\LANMAN\DRIVERS\XIF\BOORSERV.XIF so that the line
Class = RPL
reads
Class = APRICOT
(There can only be one protocol, of any given class, configured at any
time.) |
| c) |
Re-run Setup, and configure the server as required, for
RPL and Apricot Remote Boot. |
----------oOo---------- |
