3Com e-PC c10/s10, User Manual

Page: 95 / 122

C C h h a a p p t t e e r r 9 9 8 8 3 3
The boot sequence (DOS, Windows 3.1 clients) for Windows NT works as follows:
When a remoteboot client starts, the NIC initializes and broadcasts a FIND frame.
The Remoteboot Service receives the FIND frame, which contains the client’s NIC ID.
The Remoteboot Service checks the remoteboot database on the server to see if a PC
record already exists.
If a record does not exist and the NIC’s prefix is recognized by the Remoteboot
Service, the service records this NIC ID but does not boot the client. To boot the
client, you must convert this NIC ID record to a PC record using Remoteboot Manager.
If a PC record does exist with this NIC ID, the Remoteboot Service sends a FOUND
frame containing the server’s NIC ID to the MBA ROM on the client.
MBA accepts the first FOUND frame it receives and returns the SEND FILE REQUEST
frame to the NIC ID of the server that sent it.
When the Remoteboot Service receives the SEND FILE REQUEST frame, it uses FILE
DATA RESPONSE frames to send a boot block to MBA. The PC record in the
remoteboot database specifies which boot block to send (MS-DOS or Windows 3.1).
When MBA receives the last FILE DATA RESPONSE frame, it clears the screen and
transfers execution to the entry point of the boot block.
MBA boots the operating systems specified by the boot block as appropriate for the
client. For an MS-DOS or Windows 3.1 client, this completes the basic boot process.
B
B
o
o
o
o
t
t
S
S
c
c
r
r
e
e
e
e
n
n
When booting with MBA, the PC displays a screen similar to Figure 24.
IGURE BOOT SCREEN