CLI Reference Guide

4-5
System Messages
BIND-1.00-45: The parameter specified for the following option was out
of range and has been adjusted.
Explanation: A configurable parameter has been configured too high or too
low to be valid. The parameter is specified on the line following the
message.
Action: Check and correct the parameter specified in the NET.CFG file. See
Chapter 2, “NET.CFG Options Reference,” for more information.
CONN-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.
CONN-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.
CONN-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.
Action: Make sure that <module1>.VLM or <module2>.VLM loads
successfully before <module3>.VLM.