System Messages
An explanation of the nature of the message and a recommended course of action follow each message.
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.
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.
Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.