3Com e-PC c10/s10, User Manual, Page: 89 / 122

C C h h a a p p t t e e r r 8 8 7 7 7 7
starting position (or file offset) of the next line in the file. After completing execution of the
current command line, execution in the .BAT file continues at the previously retained offset.
When you execute VLM (or NETX) from the image disk batch file, VLM senses that MBA was
used to boot the PC, and tells MBA to clean up. After MBA does some housekeeping and
removes itself from memory, the image file is closed, and drive A: is restored. VLM (or
NETX) then transfers control to the same .BAT file in SYS:LOGIN, at the point where it left
off in the image disk. In this guide, this is called the “VLM Transfer Point”. Understanding this
transfer point is important in solving problems with missing batch files, and in supporting
more than one boot image file in the SYS:LOGIN directory.
T
T
r
r
o
o
u
u
b
b
l
l
e
e
s
s
h
h
o
o
o
o
t
t
i
i
n
n
g
g
Q
Q
u
u
i
i
c
c
k
k
F
F
i
i
x
x
e
e
s
s
:
:
W
W
h
h
a
a
t
t
t
t
o
o
C
C
h
h
e
e
c
c
k
k
F
F
i
i
r
r
s
s
t
t
When things do not work, check the following situations to resolve the most likely problems:
If you are not using the Boot Image Editor Loader option, check that RPLODI is loaded
after LSL.COM and before the ODI driver. If RPLODI is not loaded, the boot image
hangs while loading the ODI driver, or shortly afterwards.
Check that the Ethernet frame type configured in MBA is the frame type that is loaded
at the file server.
Within an image file, check for explicit references to drive A: within any pathname;
avoid explicit drive A: references.
DOS 6.x sets COMSPEC to A:\COMMAND.COM, and may set PATH to A:\. Just before
loading VLM, clear PATH and change the COMSPEC variable to the DOS search drive
that is established after login, as follows:
set path=
set comspec=x:command.com
vlm
If the PC hangs at the “Jumping to Boot Record” message, it could be one of the
following:
The diskette you used to create the boot image file was infected with a boot sector
virus. Check the original diskette, or use Boot Image Editor to map the image to drive
A: and scan for virus infections.
When the “invalid path for EMM386” error message is displayed while loading
Windows 3.x, add the “/y” parameter to the EMM386 command line in the boot image
file to define the network path where EMM386.EXE is located. For example,
device = emm386.exe /y=x:\dos\v6.22\emm386.exe
M
M
B
B
A
A
M
M
e
e
s
s
s
s
a
a
g
g
e
e
s
s
This section describes all of the MBA for NetWare generic messages. There may be other
error messages specific to your version of MBA.
MSD: no reply (only in verbose mode)
This is not an error message, but merely an indication that MBA could not locate the optional
MSD NLM on your network. See “
Multiple Servers: How the MSD NLM Can Help ” for further
information.