CLI Reference Guide

4-25
System Messages
Action: If you want NCP authentication, make sure that SECURITY.VLM
is configured to load before NWP.VLM and that it loads successfully before
attempting to load NWP.VLM. If you do not want NCP authentication, add
SIGNATURE LEVEL=0 to the NetWare DOS Requester section of the
NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more
information.
REDIR-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.
REDIR-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. 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.
REDIR-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. 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.
REDIR-1.00-42: There is a missing or invalid value for ‘<parameter>’
on line <number> of the configuration file. This entry will be ignored.
Correct the line specified in the configuration file before continuing.