
7
7
6
6
C
C
h
h
a
a
p
p
t
t
e
e
r
r
8
8
For example:
romtype 10b79200
If the value specified on the command line matches the value for the NIC, ROMTYPE
returns an error level of 1. If it does not match, ROMTYPE returns an error level of 0.
If you do not know the Vendor ID or Device ID for your NIC, you can obtain the values
from the MBA ROM Information Screen or by running ROMTYPE with the “-t” option.
Refer to “
Displaying MBA Information
(Shift+Shift)” in Chapter 4 for information
regarding the Information screen.
If no command line arguments are specified, ROMTYPE returns the type code of the
ROM. All ROMs are assigned a type code based on the specific NIC that the ROM
supports. For a list of current type codes see the file ROMTYPE.TXT on the MBA Utility
Disk or MBA subdirectory on the EtherCD.
For both methods, if a ROM is not present, ROMTYPE returns an error level of 0. Also, if you
include the “-t” command line switch, ROMTYPE displays the Vendor ID and Device ID or the
type code, depending on which method is used.
A
A
p
p
p
p
l
l
i
i
c
c
a
a
t
t
i
i
o
o
n
n
N
N
o
o
t
t
e
e
s
s
This section lists some techniques for using MBA in NetWare environments:
U
U
s
s
i
i
n
n
g
g
N
N
o
o
v
v
e
e
l
l
l
l
'
'
s
s
C
C
l
l
i
i
e
e
n
n
t
t
3
3
2
2
f
f
o
o
r
r
D
D
O
O
S
S
/
/
W
W
i
i
n
n
d
d
o
o
w
w
s
s
w
w
i
i
t
t
h
h
M
M
B
B
A
A
Proceed as follows when using Novell's 32-bit client for DOS/Windows (updated information
may be available from Lanworks or 3Com):
When loading Windows 3.x, NIOS.EXE attempts to reload itself from the default boot
drive. In MBA's case, this is drive A:, and since the boot image no longer exists, an
error message is displayed, preventing Windows from loading in enhanced mode.
Unlike EMM386, NIOS does not support an optional path parameter to facilitate the
reload process. One solution is to map a network drive containing NIOS.EXE to drive
A:, which would allow Windows to load.
F
F
o
o
r
r
m
m
a
a
t
t
t
t
i
i
n
n
g
g
D
D
i
i
s
s
k
k
e
e
t
t
t
t
e
e
s
s
U
U
s
s
i
i
n
n
g
g
W
W
i
i
n
n
d
d
o
o
w
w
s
s
When you boot with MBA, Windows does not allow you to format a diskette in drive A:; if you
try, the message, “Cannot format the MS-DOS startup drive” appears. As a preventive
measure, Windows does not allow you to format a diskette in the drive from which you
booted.
The easiest way to format a diskette is in a DOS box. If you want to format a bootable
diskette with system tracks, you need a diskette with a copy of DOS on it. The format
program prompts you to insert this diskette so it can copy the system tracks from it.
T
T
r
r
a
a
n
n
s
s
f
f
e
e
r
r
r
r
i
i
n
n
g
g
F
F
r
r
o
o
m
m
t
t
h
h
e
e
B
B
o
o
o
o
t
t
I
I
m
m
a
a
g
g
e
e
t
t
o
o
S
S
Y
Y
S
S
:
:
L
L
O
O
G
G
I
I
N
N
This section describes the interactions between VLM (or NETX) and MBA, and how it affects
.BAT file execution.
When you execute VLM from image disk, you are normally doing so from within a .BAT file
such as AUTOEXEC.BAT. DOS sees this .BAT file as a text file containing command lines of
variable length. After reading a command line from the .BAT file, DOS remembers the
Summary of Contents for e-PC c10/s10
Page 1: ...2 1 Edition ...
Page 2: ......
Page 4: ......
Page 12: ......
Page 22: ...1 10 0 C Ch ha ap pt te er r 2 2 ...
Page 44: ......
Page 58: ...4 46 6 C Ch ha ap pt te er r 5 5 ...
Page 92: ...8 80 0 C Ch ha ap pt te er r 8 8 ...
Page 108: ...9 96 6 A Ap pp pe en nd di ix x A A ...
Page 112: ...1 10 00 0 W Wa ar rr ra an nt ty y ...
Page 122: ...110 I In nd de ex x Updating with MBA ROM 28 Verbose mode 34 Wired for Management 58 ...