Chapter 4 System Messages

A system message points to a software or hardware error that doesn't allow further processing.

An explanation of the nature of the message and a recommended course of action follow each message.

AUTO-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.

AUTO-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.

AUTO-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.

AUTO-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

AUTO-1.00-43: There is a missing or invalid ON/OFF 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.

Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

AUTO-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.

BIND-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.

BIND-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.

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.

BIND-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

BIND-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

BIND-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

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.

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.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

CONN-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

CONN-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

CONN-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-50: DOS version is not 3.1 or later. The NetWare Requester for DOS cannot be loaded. Reboot your computer with DOS 3.1 or later; then load the NetWare Requester for DOS files.

Explanation: The NetWare® DOS Requester™ software requires DOS 3.1 or later in order to operate. Because the current DOS version is not 3.1 or later, the NetWare DOS Requester cannot be loaded.

Action: Upgrade the DOS version on your machine to 3.1 or later.

CONN-1.00-51: An older version of the shell is loaded. The NetWare Requester for DOS cannot be loaded. Unload the shell; then load the NetWare Requester for DOS files.

Explanation: The NetWare® DOS Requester™ software cannot be loaded with the NetWare shell. The NetWare shell has been loaded in your machine. For NetWare shell compatibility.

Action: Type "NETX /U" to unload the NetWare shell. If the version of the NetWare shell in use does not support the /U parameter, reboot the machine without loading the NetWare shell. See Chapter 2, "NET.CFG Options Reference," for more information.

CONN-1.00-52: The NetWare DOS Named Pipes Extender is currently loaded. The NetWare Requester for DOS cannot be loaded. Unload the NetWare DOS Named Pipes Extender; then load the NetWare Requester for DOS files.

Explanation: The NetWare® DOS Requester™ software cannot be loaded after the NetWare DOS Named Pipes Extender. To use both the NetWare DOS Requester and NetWare DOS Named Pipes Extender, load the NetWare DOS Requester first.

Action: Type "DOSNP /U" to unload the DOS Named Pipes Extender; then load the NetWare DOS Requester before reloading the DOS Named Pipes Extender. See "Named Pipes Options" for more information about Named Pipes parameters in the NET.CFG file.

DOSCLINST-1.0-1: <Filename> could not be installed.

Explanation: The indicated file could not be installed on the destination drive because either the file was not found on the master diskettes or the INSTALL utility was unable to write to the INSTALL directory.

Action: Make sure that the file is on the master diskettes. Also make sure that the destination drive is not write-protected or has some other condition that would prevent the indicated file from being copied.

DOSCLINST-1.0-2: This program requires more disk space. Installation could not be completed.

Explanation: Adequate disk space is not available on the destination drive. More space must be available for the installation to be completed.

Action: Delete unnecessary files from the hard disk.

DOSCLINST-1.0-3: The INSTALL.OVL file could not be found.

Explanation: The INSTALL.OVL file could not be found. This file is an integral piece of the INSTALL utility; it must be in the same directory as the INSTALL.EXE file.

Action: Make sure that INSTALL.OVL is in the same directory as the INSTALL.EXE file; then run INSTALL again.

DOSCLINST-1.0-4: A read error occurred while the program was reading INSTALL.OVL.

Explanation: The file INSTALL.OVL has been corrupted. The INSTALL utility requires INSTALL.OVL for successful installation.

Action: Copy INSTALL.OVL from the master diskettes to the same directory as the INSTALL.EXE file; then run INSTALL again.

FIO-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.

FIO-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.

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.

FIO-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

FIO-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

FIO-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

FIO-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.

FIO-1.00-60: Too much cache is configured. The FIO.VLM file will reduce the cache blocks by <number> blocks and load successfully. Check the CACHE BUFFERS and BUFFER SIZE parameters in the NET.CFG file; then load the FIO.VLM file.

Explanation: The amount of cache available in DOS is limited by conventional memory. Neither of the parameters determining the amount of memory to be used, CACHE BUFFERS nor BUFFER SIZE, can be configured to use more than 64 KB of memory.

Action: Reduce the CACHE BUFFERS or BUFFER SIZE parameter in the NET.CFG file. See Chapter 2, "NET.CFG Options Reference," for more information.

FIO-1.00-61: The IPX interface is not loaded. The FIO.VLM file will load successfully without packet burst support. Load the IPXODI v2.00 or later to use packet burst or add PB BUFFERS=0 to the NET.CFG file; then load FIO.VLM.

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, requires IPXODI.COM version 2.00 or later to function properly. No IPX™ interface was loaded in this machine.

Action: If you want Packet Burst, make sure that IPXODI.COM version 2.00 or later is loaded before the NetWare DOS Requester. If you do not want Packet Burst, add PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file. See See Chapter 2, "NET.CFG Options Reference," for more information.

FIO-1.00-62: The LSL interface is not loaded. The FIO.VLM file will load successfully without packet burst support. Load the LSL module or add PB BUFFERS=0 to the NET.CFG file; then load FIO.VLM.

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, requires the LSL.COM file to be loaded to function properly.

Action: If you want Packet Burst, make sure that the LSL.COM file is loaded before the NetWare DOS Requester. If you do not want Packet Burst, add PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file. See Chapter 2, "NET.CFG Options Reference," for more information.

FIO-1.00-63: The IPX socket for packet burst could not be opened. The FIO.VLM file will load successfully without packet burst support. configure the IPXODI.COM file for enough sockets in the NET.CFG file or add PB BUFFERS=0 to the NET.CFG file; then load the FIO.VLM file.

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, requires an IPX™ socket to function properly. The request to open a socket failed, indicating that not enough IPX sockets are available.

Action: If you want Packet Burst, make sure that the IPX interface is configured for enough sockets in the NET.CFG file before loading the NetWare DOS Requester. If you do not want Packet Burst, add PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file. See Chapter 2, "NET.CFG Options Reference," for more information.

FIO-1.00-64: The IPX interface is not version 2.00 or later. The FIO.VLM file will load successfully without packet burst support. Load the IPXODI.COM file version 2.00 or later or add PB BUFFERS=0 to the NET.CFG file; then load the FIO.VLM file.

Action: If you want Packet Burst, make sure that IPXODI.COM version 2.00 or late is loaded before the NetWare DOS Requester. If you do not want Packet Burst, add PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file. See Chapter 2, "NET.CFG Options Reference," for more information.

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.

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.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

GENERAL-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

GENERAL-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time VLM.EXE is loaded, delete or correct the line specified by the error message.

GENERAL-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 in the NET.CFG file. See Chapter 2, "NET.CFG Options Reference," for more information.

IPXNCP-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.

IPXNCP-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.

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.

IPXNCP-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

IPXNCP-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

IPXNCP-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

IPXNCP-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.

IPXNCP-1.00-53: The IPX interface is not loaded. The IPXNCP.VLM file cannot be loaded. Load the IPXODI.COM file first and then try loading the IPXNCP.VLM file.

Explanation: An attempt was made to load the IPXNCP.VLM file without having previously loaded the IPX™ interface.

Action: Load the IPXODI.COM file before attempting to load IPXNCP.VLM.

IPXNCP-1.00-54: The IPX sockets could not be opened. The IPXNCP.VLM file cannot be loaded. Configure the IPXODI.COM file for enough sockets in the NET.CFG file and then try to load the IPXNCP.VLM file.

Explanation: The IPXNCP.VLM file failed to open the IPX™ sockets needed in order to run. The IPXNCP.VLM file requires that four or more IPX sockets be available to run.

Action: Increase the number of IPX sockets available by using the IPX SOCKETS= parameter in the NET.CFG file; then reload the IPXODI.COM and IPXNCP.VLM files.

IPXNCP-1.00-55: The IPX interface does not support checksums. The IPXNCP.VLM file will load successfully without using checksums. Make sure the installed IPXODI. COM is version 2.01 or later and that it is not bound to a board configured to use the ETHERNET_802.3 frame format.

Explanation: The IPXNCP.VLM file loads without supporting checksums. For checksum to be supported in IPXNCP.VLM, the loaded IPXODI.COM file must support checksums. Either the loaded version of the IPXODI.COM file does not have checksum support or the protocol bound to the IPX™ software does not support checksums.

Action: No action required at this point. However, to avoid receiving this message the next time the IPXNCP.VLM file is loaded, either load the IPXODI.COM file with checksum support enabled or add CHECKSUM=OFF to the NetWare DOS Requester section of the NET.CFG file. See Chapter 2, "NET.CFG Options Reference," for more information.

IPXNCP-1.00-56: The IPX socket for large internet packets could not be opened. The IPXNCP.VLM file will load successfully without using large internet packets. Configure the IPXODI.COM file for enough sockets in the NET.CFG file or add LARGE INTERNET PACKETS=OFF to the NET.CFG file; then load the IPXNCP.VLM file.

Explanation: This message is only a warning. The NetWar® DOS Requester™ software functions properly without the use of large internet packets. The large internet packet protocol, which is a part of the IPXNCP.VLM module, requires an IPX socket to function properly. The request to open a socket failed, indicating that not enough IPX sockets are available.

Action: If you want large internet packets, make sure that the IPX interface is configured for enough sockets in the NET.CFG file before loading the NetWare DOS Requester. If you do not want large internet packets, add LARGE INTERNET PACKETS=OFF to the NetWare DOS Requester section of the NET.CFG file.See Chapter 2, "NET.CFG Options Reference," for more information.

NDS-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.

NDS-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.

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.

NDS-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

NDS-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NDS-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NDS-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.

NETX-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.

NETX-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.

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.

NETX-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 before <module3>.VLM can run effectively. 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.

NETX-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NETX-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NETX-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.

NETX-1.00-57: DOS is only configured for <number> drives, NETX.VLM requires 26 drives for full functionality. The NETX.VLM file will load with partial support. Add LASTDRIVE=Z to the CONFIG.SYS file and reboot the workstation; then load the NETX.VLM file.

Explanation: This message is only a warning. However, if you want full compatibility with the NetWare® shell, you must set the DOS LASTDRIVE parameter in the CONFIG.SYS file to Z. Otherwise, problems occur when mapping drives, etc.

Action: Set LASTDRIVE=Z in the CONFIG.SYS file; then reboot the client workstation before loading the NetWare DOS Requester™ software.

NETX-1.00-58: The PRINT.VLM file has not been loaded. The NETX.VLM file will load successfully without print services. To enable printing services, load the PRINT.VLM file before loading the NETX.VLM file.

Explanation: This message is only a warning. For full NetWare® shell compatibility, the PRINT.VLM file must be loaded.

Action: If you want print functionality, load the PRINT.VLM file before loading the NETX.VLM file.

NMR-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.

NMR-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.

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.

NMR-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

NMR-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NMR-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NMR-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.

NWDRV-3.00-00: The NetWare VLM is not loaded or is not configured correctly. All network functions will be disabled. Reconfigure the VLM and restart MS Windows.

Explanation: Without the NetWare® DOS Requester™ (VLM) software, the client workstation cannot communicate with NetWare servers. The NetWare MS Windows driver (NETWARE.DRV) depends on the VLM™ software in order to provide network support for MS Windows.

Action: Exit MS Windows. Go to the directory where the VLM.EXE file is located and type "VLM". Then restart MS Windows.

NWDRV-3.00-10: The VNETWARE.386 file has not been loaded. All network functions will be disabled. To use NetWare, install VNETWARE.386 and restart MS Windows.

Explanation: The NetWare® MS Windows driver (NETWARE.DRV) depends on the VNETWARE.386 file to run MS Windows in enhanced mode.

Action: Exit MS Windows. Copy the VNETWARE.386 file to the MS Windows SYSTEM (for example, C:\WINDOWS\SYSTEM). VNETWARE.386 should be on the NetWare Client For DOS and MS Windows Disk 3 diskette. Also make sure that the "[386Enh]" section of the SYSTEM.INI file has the following line: NETWORK=*VNETBIOS, VNETWARE.386, VIPX.386. Then restart MS Windows.

NWDRV-3.00-50: The temporary drive could not be mapped. Contact the network supervisor.

Explanation: The NetWare® MS Windows driver (NETWARE.DRV) allocates temporary drives on the server to perform some functions.

Action: Contact the network supervisor to make sure that NetWare is running and the server is operating correctly.

NWP-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.

NWP-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.

NWP-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.

NWP-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NWP-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

NWP-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.

NWP-1.00-59: The SECURITY.VLM file has not been loaded. The NWP.VLM file will load successfully without NCP signature support. Load the SECURITY.VLM file before loading the NWP.VLM file or add SIGNATURE LEVEL=0 to the NET.CFG file; then load NWP.VLM.

Explanation: This message is only a warning. The NetWare® DOS Requester™ software functions properly without NetWare Core Protocol™ (NCP) authentication. For NCP™ authentication to operate properly, the SECURITY.VLM file must be loaded before the NWP.VLM file. Either NWP.VLM is being loaded before SECURITY.VLM or SECURITY.VLM did not load successfully.

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.

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.

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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

REDIR-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

REDIR-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.

RSA-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.

RSA-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.

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.

RSA-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

RSA-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

RSA-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

RSA-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.

SECURITY-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.

SECURITY-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.

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.

SECURITY-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

SECURITY-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

SECURITY-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time VLM.EXE is loaded, delete or correct the line specified by the error message.

SECURITY-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.

SECURITY-1.00-67: The SECURITY.VLM file must be loaded before any other NetWare Protocol Module. The SECURITY.VLM file will not be loaded. Load the SECURITY.VLM file before loading any NetWare Protocol Modules.

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.

TRAN-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.

TRAN-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.

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.

TRAN-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.

Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.

TRAN-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

TRAN-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

TRAN-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.

VLM-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.

VLM-1.00-8: The VLM.EXE file is already loaded. VLM.EXE cannot be reloaded. If you want to load VLM.EXE with a different configuration, unload VLM.EXE first with the /U parameter and then try loading the VLM.EXE file.

Explanation: The VLM.EXE file has already been loaded into memory. There cannot be two copies of the VLM.EXE file loaded in memory at one time.

Action: If the VLM.EXE file is being reloaded in an attempt to reconfigure the VLM™ program already loaded, you must first unload VLM.EXE using the /U parameter; then reload VLM.EXE.

VLM-1.00-9: The VLM.EXE file is testing the VLMs.

Explanation: This message is used to show the progress the VLM.EXE file is making in configuring the VLM™ programs to be loaded. Because this process can take a few seconds, the progress is displayed using a period (.) to indicate each VLM being tested.

Action: No action is required; this is simply an information message.

VLM-1.00-10: The conventional memory block for the EMS stack cannot be resized. The VLM.EXE file cannot be loaded. DOS memory is probably corrupt. Reboot your computer and then try to load the VLM.EXE again.

Explanation: This error indicates that the DOS memory chain has been corrupted.

Action: It is unsafe to continue operating the computer. The best solution is to reboot the computer; then try to load the VLM.EXE file.

VLM-1.00-11: There is insufficient memory to load the VLMs. The VLM.EXE file cannot be loaded. Reconfigure the VLMs to be loaded in the NET.CFG file and then try to load the VLM.EXE file.

Explanation: The VLM.EXE file can use expanded memory (EMS), extended memory (XMS), or conventional memory. The VLM.EXE file has determined that there is not enough of any one of these types of memory to support loading the VLM™ files.

Action: Check the amount of all memory available. Some memory managers provide dynamic memory pools by converting extended memory to expanded memory or vice versa. Other memory managers require you to configure the amount and type of memory you want. In either case, do one of the following:

Make sure there is enough memory of any one type to support the VLM files.
Reduce the number of VLM files to be loaded, either by using the EXCLUDE= parameter in the NET.CFG file or by renaming the files so the VLM.EXE file does not recognize the .VLM file that you do not want loaded.

VLM-1.00-15: An invalid command line parameter was specified.

Explanation: The VLM.EXE file was loaded with an invalid command line parameter.

Action: Run VLM.EXE with the /? parameter (for example, type "VLM /?") to display the valid parameters; then load the VLM.EXE file with a valid command line parameter.

VLM-1.00-16: The VLM.EXE file <version> is currently loaded.

Explanation: This message is displayed during the VLM.EXE file diagnostics display. (The diagnostics display is accessed by running the VLM.EXE file with the /D parameter.)

Action: No action is required; this is simply an information message.

VLM-1.00-17: The VLM.EXE file is not currently loaded.

Explanation: This message is displayed during the VLM.EXE file diagnostics display. (The diagnostics display is accessed by running the VLM.EXE file with the /D parameter.)

Action: No action is required; this is simply an information message.

VLM-1.00-30: A task switcher has been detected in memory. The VLM.EXE file cannot be loaded under a task switcher. Exit the task switcher; then try again.

Explanation: The NetWare® DOS Requester™ software cannot function properly when loaded after a task switcher. A task switcher has been previously loaded. (Task switchers include DR DOS® TaskMax, MS-DOS* 5.0 DOSSHELL, and MS Windows 3.1 in standard mode.)

Action: Unload the task switcher before attempting to load the NetWare DOS Requester.

VLM-1.00-31: Network error on server <name>. Check network cabling or server status.

Explanation: This is a critical communications error between the client workstation and the NetWare® server. This error may also appear as "General failure on device NETWORK." A communications error can be caused by either a hardware or software failure.

Action: Check the hardware and make sure that the network cable is connected properly and that the NetWare server is up and running properly. If the condition persists, report the problem to your Novell Authorized ResellerCLM representative.

VLM-1.00-32: The VLM.EXE file is not loaded. VLM.EXE cannot be unloaded.

Explanation: An attempt was made to unload the VLM.EXE file using the / U parameter.

Action: The condition that caused this message to occur is invalid, so no action is required.

VLM-1.00-33: The loaded VLM.EXE file has a different version. VLM.EXE cannot be unloaded. Make sure the VLM.EXE file you are using has the same version number and then try to unload VLM.EXE.

Explanation: An attempt was made to unload the VLM.EXE file using the / U parameter.

Action: Use the same version of the VLM.EXE file to try the unload as was used to load; otherwise, the VLM.EXE file that is loaded in memory can be removed only by rebooting the computer.

VLM-1.00-34: The loaded VLM.EXE file indicates it is unsafe to execute an unload for VLM number <number>. VLM.EXE will not be unloaded. Unload all memory resident programs (TSRs) that were loaded after the VLM.EXE file and then try to unload VLM.EXE.

Explanation: An attempt was made to unload the VLM.EXE file using the / U parameter. The loaded VLM.EXE file refused to unload. This usually is caused by interrupts being used after the VLM.EXE file was loaded. Another possible cause is that a VLM™ program is in an unsafe state to unload.

Action: Unload all the TSR (terminate-and-stay-resident) programs that were loaded after the VLM.EXE file; then try to unload VLM.EXE. Make sure all loaded VLM programs are in use before unloading.

VLM-1.00-36: The VLM.EXE file cannot use expanded memory (EMS). VLM.EXE will use an alternate memory scheme.

Explanation:An attempt was made to load the VLM.EXE file in expanded memory (EMS) using the /ME parameter. Either no LIM EMS 4.0 expanded memory manager is present or insufficient expanded memory is available to load the VLM™ program. The VLM.EXE file attempts to use an alternate type of memory, either extended (XMS) or conventional, before failing to load.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure an expanded memory manager is loaded with sufficient memory, or do not specify the / ME parameter when loading VLM.EXE.

VLM-1.00-37: The VLM.EXE file is using expanded memory (EMS).

Explanation: This message indicates that the VLM.EXE file is loading the VLM™ programs into expanded memory (EMS).

Action: No action is required; this is simply an information message.

VLM-1.00-38: The VLM.EXE file cannot use extended memory (XMS). VLM.EXE will use an alternate memory scheme.

Explanation: An attempt was made to load the VLM.EXE file in extended memory (XMS) using the /MX parameter. Either no XMS 2.0 extended memory manager is present or insufficient extended memory is available to load the VLM™ programs. The VLM.EXE file attempts to use an alternate type of memory, either expanded (EMS) or conventional, before failing to load.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure an extended memory manager is loaded with sufficient memory, or do not specify the / MX parameter when loading VLM.EXE.

VLM-1.00-39: The VLM.EXE file is using extended memory (XMS).

Explanation:This message indicates that the VLM.EXE file is loading the VLM™ programs into extended memory (XMS).

Action: No action is required; this is simply an information message.

VLM-1.00-40: The VLM.EXE file cannot use conventional memory. VLM.EXE will use an alternate memory scheme.

Explanation: An attempt was made to load the VLM.EXE file in conventional memory using the /MC parameter. Insufficient conventional memory is available to load the VLM™ programs. The VLM.EXE file attempts to use an alternate type of memory, either expanded (EMS) or extended (XMS), before failing to load.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure there is sufficient conventional memory, or do not specify the /MC parameter when loading VLM.EXE.

VLM-1.00-41: The VLM.EXE file is using conventional memory.

Explanation: This message indicates that the VLM.EXE file is loading the VLM™ programs into conventional memory.

Action: No action is required; this is simply an information message.

VLM-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.

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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

VLM-1.00-43: There is a missing or invalid ON/OFF 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.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

VLM-1.00-44: There is an invalid string length specified for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.

Explanation: The configuration file contains a parameter that is defined to use a string of a specified minimum or maximum length, but a string has been entered that does not fit the specified limits. This invalid line is ignored by the configuration process.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

VLM-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.

VLM-1.00-46: A duplicate VLM ID was found during VLM load test. The file will not be loaded. Check the VLM= and USE DEFAULTS= parameters specified in the NET.CFG file before continuing.

Explanation: The VLM™ programs for the NetWare® DOS Requester™ software have been improperly configured to include two programs with the same VLM ID. This can be caused by either a VLM being included twice in the VLM= parameter list, or by a VLM attempting to reuse a VLM ID assigned to a different VLM.

Action: Check the NET.CFG file for duplicates in the VLM list. Make sure that the USE DEFAULTS= parameter is set to OFF. See Chapter 2, "NET.CFG Options Reference," for more information.

VLM-1.00-47: A file server could not be found. Check the network cabling and the server's status before continuing.

Explanation: No NetWare® server was found when attempting to build an initial connection. This could be caused by any of the following:

An improperly configured network board or LAN driver
Improperly configured IPX™ software
A disconnected network cable
An attempt to load the NetWare DOS Requester™ software before a NetWare server has been initialized.

Try one or more of the following:

Ensure that the network board and LAN driver are properly configured by checking the network board settings and the NET.CFG file settings.
See Chapter 2, "NET.CFG Options Reference," for more information.
Ensure that IPX is configured to be bound properly to the right LAN driver.
Check the network cabling.
Ensure that a NetWare server is up and running before attempting to load the NetWare DOS Requester.

VLM-1.00-60: There is an unrecognized entry `<entry>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.

Explanation: The configuration file contains a parameter under a header where it does not belong. This invalid line is ignored by the configuration process.

Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.

Chapter 4 System Messages

Technical documentation

» Table of Contents

» Index