System Messages
Explanation: This message is only a warning. The NetWare® DOS Requester™ software functions properly without the NetWare Core Protocol™ (NCP) authentication. The SECURITY.VLM file must be loaded before any NetWare protocol modules (BIND.VLM or NDS.VLM) to function properly.
Action: If you want NCP™ authentication, load the SECURITY.VLM after TRAN.VLM and before any NetWare protocol module (BIND.VLM or NDS.VLM); then set the SIGNATURE LEVEL= parameter in the NET.CFG file. If you do not want NCP authentication, set SIGNATURE LEVEL=0 in the NetWare DOS Requester section of NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more information.
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.
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.
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.