CLI Reference Guide

4-12
System Messages
FIO-1.00-65: The NetWare DOS Requester is being loaded in a MS
Windows DOS box. The FIO.VLM file will load successfully without
packet burst support.
Explanation: This message is only a warning. The NetWare® DOS
Requester™ software functions properly without the use of the Packet
Burst™ protocol. Packet Burst, which is a part of the FIO.VLM file, cannot
function when loaded in an MS Windows DOS box.
Action: You can use Packet Burst if it is loaded before starting MS
Windows. To do this, exit MS Windows and load the VLM™ files; then
restart MS Windows.
GENERAL-1.00-1: The message file <name> is invalid. The program
cannot be loaded.
Explanation: The .MSG file is invalid. This problem could be the result of a
corrupted file, a bad translation, or an outdated file version.
Action: Either update the .MSG file with a valid copy or delete the file. The
NetWare® DOS Requester™ software uses the default messages that are
bound to the binary files.
GENERAL-1.00-5: <Module1>.VLM is not loaded. The
<module2>.VLM file cannot be loaded before <module1>.VLM. Load
the <module1>.VLM file first then try to load the <module2>.VLM file.
Explanation: The <module2>.VLM file requires that the <module1>.VLM
file be loaded first. Either the current configuration has <module1>.VLM
and <module2>.VLM loading out of order, or <module1>.VLM did not load
successfully.
Action: Make sure that <module1>.VLM is configured to load before
<module2>.VLM. To do this, change the load order of the VLM= parameter
in the NET.CFG file.
GENERAL-1.00-7: In order to load the <module3>.VLM, one of the
following VLMs must be loaded: <module1>.VLM, <module2>.VLM.
Explanation: The <module3>.VLM file requires that the <module1>.VLM
or <module2>.VLM file be loaded first. Either the current configuration has
<module3>.VLM loading before <module1>.VLM or <module2>.VLM, or
<module1>.VLM or <module2>.VLM did not load successfully.