System Messages

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 displ ay 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.

4-33