“<”, “>”
The “>” and “<” messages appear only after IPXODI.COM (or your board-specific
ODI driver) has loaded, but before VLM or NETX has finished loading. The “>”
indicates that the IPX layer had problems transmitting data on the network, while
the “<” indicates that there was a problem with receiving data from IPX. Since
MBA has managed to get this far in the boot sequence, it is usually a configuration
mismatch between your NIC and IPX that is causing the problem.
There are several reasons why the “>” message could appear: either you have
loaded the wrong ODI driver (perhaps for a different NIC), or the driver you have
loaded does not match your NIC's configuration. If the version of MBA you are
using does not use interrupts, check that the NIC's interrupt jumper is set to that
expected by the ODI driver.
If the “<” message appears repeatedly on an Ethernet PC, it is likely that the
Ethernet frame type for which the ODI driver is configured is not loaded at the
server.
Batch File Missing Messages and How to
Avoid Them
A cause of the “Batch file missing” message is a user login script which changes
the mapping of the first network drive from the SYS:LOGIN to some other
directory. You can avoid this problem by leaving the first network drive mapped to
SYS:LOGIN throughout the entire LOGIN script.
The LOGIN script supports a command called EXIT, which can be used to run a
.BAT file upon exiting from the LOGIN script. If you are running the LOGIN
command from a .BAT file in SYS:LOGIN, and there are further command lines in
this file, then you EXIT from your login script with a .BAT file specified, the
remainder of the SYS:LOGIN .BAT file is processed and only then is your EXIT
.BAT file processed.
83
