3Com e-PC c10/s10, Руководство пользователя, Страница: 79 / 122

C C h h a a p p t t e e r r 8 8 6 6 7 7
B B o o o o t t U U s s i i n n g g M M B B A A
The PC can now be booted using MBA. Perform the following steps as needed:
1. In order for multiple PCs to boot using this file, it must be flagged as shareable. When
Boot Image Editor creates an image file it automatically flags the file as shareable. If you
need to set it manually (e.g. if you created the image with DOSGEN), use the NetWare
FLAG command:
flag net$dos.sys sh (for netware 4.x and 5.x)
or
flag net$dos.sys s (for netware 3.x)
2. If your network has more than one file server, copy the boot image file and
AUTOEXEC.BAT to each server's SYS:LOGIN directory. If you use the optional MSD NLM,
you do not need to worry about copying these files across all file servers. See “
Multiple
Servers: How the MSD NLM Can Help ” in this chapter.
You have now created a single boot image file that any PC with MBA installed can load and
boot from the network. If your MBA-equipped PCs have different booting requirements, there
are two ways to meet these requirements:
You may use the CHKID and ROMTYPE utilities (provided with MBA) which allow you to
load drivers conditionally based on node address or NIC type.
You may have to create additional boot image files if different operating systems are
used. See “ Supporting Different PCs with One Boot Image ”, and “ Creating Additional
Boot Image Files .”
S
S
u
u
p
p
p
p
o
o
r
r
t
t
i
i
n
n
g
g
D
D
i
i
f
f
f
f
e
e
r
r
e
e
n
n
t
t
P
P
C
C
s
s
w
w
i
i
t
t
h
h
O
O
n
n
e
e
B
B
o
o
o
o
t
t
I
I
m
m
a
a
g
g
e
e
Although boot image files may be shared by many identical PCs, you may wish to create
additional boot image files for other PCs which require different drivers to be loaded either in
CONFIG.SYS or AUTOEXEC.BAT.
Using the CHKID and ROMTYPE utilities provided with MBA, you can avoid having to create
additional boot image files by steering through CONFIG.SYS and AUTOEXEC.BAT based on
the PC's node address and NIC type.
For example:
Using CHKID you could specify that a certain CONFIG.SYS driver is loaded only for one
or more PC node addresses. CHKID may also be used within AUTOEXEC.BAT.
Using ROMTYPE in AUTOEXEC.BAT, you could support many different ODI drivers
within one boot image, automatically loading the one appropriate for each of your PCs.
Refer to “ Other Tools ” for information on CHKID and ROMTYPE.