8
8
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
MBA Messages
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.
File server could not be found
The file server is either down or not responding to connection requests. Check that
your PC is connected to an active network cable segment.
Error opening boot file
The main reason why this message could appear is that you have more than one
file server on your network, and some of them
do not have the needed boot files
in their SYS:LOGIN directories. See “
Multiple Servers: How the MSD NLM Can
Help
” for further information.
It is also possible that the file exists, but it is open and locked by another PC.
Check that the file exists and is flagged as shareable. Load the MONITOR NLM on
the file server console to check if the file is in use by another connection.
Another reason could be that you've run DOSGEN to generate your boot image file
(NET$DOS.SYS or equivalent), but you generated this file in the SYS:SYSTEM
directory. All boot image files need to be in the SYS:LOGIN directory.
Error reading boot diskette file
An error occurred while reading the boot image file. This problem is usually a
hardware-related difficulty or a virus infection that caused the read to fail after
many retries, and earlier error messages. If other messages were displayed, refer
to their explanation for suggestions on what the problem could be.
Rx2
(only in verbose mode)
This message may appear when in the verbose mode during the boot process on a
heavily congested network. There is no cause for alarm if you see several of these
messages in a row, but if many of them appear consecutively, it usually indicates
a network problem.
Rx2 indicates that MBA timed out while waiting for a packet. If you have an
Ethernet version of MBA, this message may appear continuously, indicating that
the Ethernet frame type MBA is using to communicate is not supported at the
server.
With some ODI drivers, you may see Rx2 messages if you have forgotten to load
RPLODI before loading the ODI driver; check that RPLODI.COM is being loaded. In
other cases, Rx2 may appear, indicating an improper network cable connection.
82
