Copyright: Copyright (c) 1994-1996, Novell, Inc.


ABEND, An installed Vxd module at <address> attempted to access an undefined NLM function (<function_name>).

Explanation

The function indicated is not exported by NIOS or any loaded NLM* program. This could be caused by a conflict of versions between the calling VxD program and the NLM program that the VxD program is expecting to export the function to.

** Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


ABEND, VMLID: Free called with uninitialized Zone!

Explanation

Internal memory corruption has been detected.


ABEND, VMLID: Lost in Zone Array!

Explanation

Internal memory corruption has been detected.


ABEND Messages

Explanation

Something critically wrong has occurred when NetWare* Client* 32* was trying to preform and operation.

Action

Record what you were doing at the time the message occurred. Record the abend message. Reboot the workstation. If the error persist, report the problem to a NetWare support provider.

Some specific abend messages for specific Client 32 modules are

NIOS

An installed Vxd module at <address> attempted to access an undefined NLM* function (<function_name>).

Invalid conventional memory pointer during call to DosConvMemFree:Address Invalid address value

Name of module who called the function with invalid parameters

Invalid conventional memory pointer during call to DosConvMemFree:Address address value

Module name

VMLID

 VMLID: Free called with uninitialized Zone!

 VMLID: Lost in Zone Array!

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


CLIENT32 Application name is incompatible with NetWare enhanced security support.

Action

Upgrade to a newer version of the application indicated.


CLIENT32 Drive letter: to server name could not be auto-reconnected because AUTO RECONNECT LEVEL = value which is too low.
CLIENT32 Drive letter: to server name could not be auto-reconnected because AUTO RECONNECT = value  which is too low.

Action

Increase the value set for the Auto Reconnect Level parameter. For Windows** 95**, this setting is in the NetWare* Client* 32* properties, on the "Advanced Settings" page. In DOS or Windows 3.x, this setting is in the NET.CFG file, under the NETWARE DOS REQUESTER section.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


CLIENT32 Drive letter: to server name could not be auto-reconnected because access was denied.

Action

If appropriate, give the user the rights necessary to access the server indicated.


CLIENT32 Drive letter: to server name could not be auto-reconnected because of an unknown reason error code.

Action

Log in again or map a drive again to the server indicated. For information about the error code, see "Error Codes" in the online System Messages  manual.


CLIENT32 Drive letter: to server name could not be auto-reconnected because search rights changed.

Action

Confirm the user's rights to the server indicated. If appropriate, reassign the user the rights necessary to access the server.


CLIENT32 Drive letter: to server name could not be auto-reconnected because the path was deleted while the network connection w
CLIENT32 Drive letter : to server name could not be auto-reconnected because the path was deleted while the network connection was interrupted.

Explanation

The path indicated was deleted while the user was not connected to the network.

Action

To prevent this message from recurring, change or delete the drive mapping to the server indicated.


CLIENT32 Drive letter: to server name could not be auto-reconnected because this version of the server does not support it.

Action

Upgrade the software on the server indicated to a version that supports the auto-reconnect function.


CLIENT32 Drives to server name could not be auto-reconnected because of a low memory condition.

Action

Increase the memory available at the workstation. See "Resolving Workstation Memory Problems."


CLIENT32 File in use during a file open. File: name

Action

Make sure the file is not locked or already in use. Then try opening the file again.


CLIENT32 File in use during an fcb file open. File: name

Explanation

A File Control Block (FCB) was in use when the user tried to open the file.

Action

Make sure the file is not already in use. Then try opening the file again.


CLIENT32 File in use during delete of a file. File: name

Action

Make sure the file is not already in use. Then try deleting the file again.


CLIENT32 File locked during a file open. File: name

Action

Make sure the file is not already in use. Then try opening the file again.


CLIENT32 File locked during rename a file. File: name

Action

Make sure the file is not already in use. Then try renaming the file again.


CLIENT32 File name could not be auto-reconnected because AUTO RECONNECT LEVEL =value which is too low.

Action

If possible, save the file to a local drive to prevent losing any changes. To prevent the problem from recurring, increase the value set for the Auto Reconnect Level parameter. For Windows** 95**, this setting is in the NetWare* Client * 32* properties, on the "Advanced Settings" page. In DOS or Windows 3.x, this setting is in the NET.CFG file, under the NETWARE DOS REQUESTER section.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


CLIENT32 File name could not be auto-reconnected because access was denied.

Action

If possible, save the file to a local drive to prevent losing any changes. Confirm the user's rights to the file and applicable directory. If appropriate, reassign the user the rights necessary to access the file or directory.


CLIENT32 File name could not be auto-reconnected because it was deleted while the network connection was interrupted.

Action

To see why the file was deleted, contact the network supervisor.


CLIENT32 File name could not be auto-reconnected because of a low memory condition.

Action

Increase the memory available at the workstation. See "Resolving Workstation Memory Problems."


CLIENT32 File name could not be auto-reconnected because of an unknown reason.

Action

If possible, save the file to a local drive to prevent losing any changes. Make sure the user's right to the file are appropriate and that the file exists. Try to auto-connect to the file again.


CLIENT32 File name could not be auto-reconnected because the file could not be re-created.

Explanation

Two reasons this error might occur are

The path to the file was deleted

The user's rights were changed while the network connection was interrupted

Action

If possible, save the file to a local drive to prevent losing any changes. Try connecting again. Make sure the path to the file has not been deleted. Confirm the user's rights to the file. If appropriate, reassign the user the rights necessary to access the file.


CLIENT32 File name could not be auto-reconnected because the file's locks could not be reestablished.

Action

If possible, save the file to a local drive to prevent losing any changes. Try accessing the file again. If the user is unable to access the file, clear the user's connection to release the file. The user should then be able to access the file; however, any changes not saved will be lost.


CLIENT32 File name could not be auto-reconnected because the utility that opened the stream file is too old.

Explanation

The utility that was used to open the file, such as NetWare Administrator or NETADMIN, does not support the auto-reconnect function.

Action

Upgrade the utility that opened the file. Then try opening and reconnecting to the file again.


CLIENT32 File name could not be auto-reconnected because this version of the server does not support it.

Action

If possible, save the file to a local drive to prevent losing any changes. Upgrade the software on the server to a version that supports the auto-reconnect function.


CLIENT32 Messages

CLIENT32 Application name is incompatible with NetWare enhanced security support.

CLIENT32 Drive letter: to server name could not be auto-reconnected because access was denied.

CLIENT32 Drive letter: to server name could not be auto-reconnected because AUTO RECONNECT LEVEL = value which is too low.

CLIENT32 Drive letter: to server name could not be auto-reconnected because of an unknown reason error code.

CLIENT32 Drive letter: to server name could not be auto-reconnected because search rights changed.

CLIENT32 Drive letter: to server name could not be auto-reconnected because the path was deleted while the network connection

CLIENT32 Drive letter: to server name could not be auto-reconnected because this version of the server does not support it.

CLIENT32 Drives to server name could not be auto-reconnected because of a low memory condition.

CLIENT32 File in use during a file open. File: name

CLIENT32 File in use during an fcb file open. File: name

CLIENT32 File in use during delete of a file. File: name

CLIENT32 File locked during a file open. File: name

CLIENT32 File locked during rename a file. File: name

CLIENT32 File name could not be auto-reconnected because access was denied.

CLIENT32 File name could not be auto-reconnected because AUTO RECONNECT LEVEL =value which is too low.

CLIENT32 File name could not be auto-reconnected because it was deleted while the network connection was interrupted.

CLIENT32 File name could not be auto-reconnected because of a low memory condition.

CLIENT32 File name could not be auto-reconnected because of an unknown reason.

CLIENT32 File name could not be auto-reconnected because the file could not be re-created.

CLIENT32 File name could not be auto-reconnected because the file's locks could not be reestablished.

CLIENT32 File name could not be auto-reconnected because the utility that opened the stream file is too old.

CLIENT32 File name could not be auto-reconnected because this version of the server does not support it.

CLIENT32 NETX cannot be loaded without exiting all DOS boxes.

CLIENT32 Please wait while command_from_application retries request to server_name.

CLIENT32 Please wait while server_name is processing request for command_from_application.


CLIENT32 NETX cannot be loaded without exiting all DOS boxes.

Explanation

The user tried to unload the CLIENT32.NLM from a DOS box in Windows** when other DOS boxes were open.

Action

Do one of the following:

Close all open DOS boxes and then unload the CLIENT32.NLM program

Exit Windows and then unload the CLIENT32.NLM program

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


CLIENT32 Please wait while server_name is processing request for command_from_application. To stop waiting, press Enter. NetWar
CLIENT32 Please wait while server_name is processing request for command_from_application. To stop waiting, press Enter. NetWare will then return an error and try to reconnect in the background.

Explanation

This message might appear for any of the following reasons:

The network is slow

The server is slow to respond to a request from an application

The server is down

The network cable has been disconnect from the workstation

Action

Wait while the NetWare* Client* 32* retries to process the application's request to the server. The message will clear automatically when the request has been processed.

If you are sure the server will not respond, press <Enter>. The message will be cleared and the NetWare Client 32 will reconnect to the application in the background when the server comes online.

Make sure the network cable is connected to the workstation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


CLIENT32: Please wait while command_from_application retries request to server_name. To stop waiting, press Enter. NetWare will
CLIENT32: Please wait while command_from_application retries request to server_name. To stop waiting, press Enter. NetWare will then return an error and try to reconnect in the background.

Explanation

This message might appear for any of the following reasons:

The network is slow

The server is slow to respond to a request from an application

The server is down

The network cable has been disconnect from the workstation

Action

Wait while NetWare* Client* 32* keeps trying to process the application's request to the server. The message will clear automatically when the request has been processed.

If you are sure the server will not respond, press <Enter>. The message will be cleared and NetWare Client 32 will reconnect the application to the server in the background when the server comes online.

Make sure the network cable is connected to the workstation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Definition, Error Code
Error Code

A hexidecimal or decimal number that usually indicates why an error condition has occurred. A comprehensive table of NetWare error codes is found in Appendix A of the online System Messages  manual.

Example: Hexidecimal, FFFFFD93,	Decimal, -621


Definition, Message String
Message String

Information that tells users about a problem: what happened, possibly why it occurred, and possibly what to do to recover from the problem.


Definition, Message Type, Error
Error Message

A type of message that informs the user of a problem that must be corrected before action can continue.


Definition, Message Type, Status
Status (or Informational) Message

A type of message that informs users about the current status of software or hardware.


Definition, Message Type, Warning
Warning Message

A type of message that indicates processing might continue but that a certain course of action should be taken to prevent errors from occurring in the future.


Definition, Platform Designation
Platform Designation

Indicates what platform (such as DOS, OS/2, or Mac) was the source of the message displayed.


Definition, Source module name
Source Module Name

The name of the source or the module that generated the message, such as NIOS, CLIENT32, IPX, or CNE2000.


Definition, Unique Identifying Number
Unique Identifying Number

Any number that when associated with the source module, version or platform designation, and message string uniquely identifies a message.


Definition, Version
Version

A number indicating the version of the module that generated the message.


IPX -x- 102: Unsupported execution environment. This NLM must be loaded under DOS, Windows 3.X, or Windows 95.

Explanation

The user tried to load this NLM* program on a server. This NLM program is intended to be used only at a client workstation.

Action

Load this NLM program only at a client workstation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 103:  IPX.NLM could not allocate a V86 callback address needed for IPX/SPX Application Interface.

Explanation

To provide backward compatibility with Novell’s 16-bit IPX/SPX interfaces, IPX* must allocate conventional memory and 16-bit callback addresses. If IPX fails to allocate one of these resources, it cannot initialize.

Action

Make sure the user is using the latest version of the NetWare* Client* 32* software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 104:  IPX.NLM could not allocate conventional memory needed for IPX/SPX Application Interface.

Explanation

To provide backward compatibility with Novell’s 16-bit IPX/SPX* interfaces, IPX* must allocate conventional memory and 16-bit callback addresses. If IPX fails to allocate one of these resources, it cannot initialize.

Action

Make sure the user is using the latest version of the NetWare* Client* 32* software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 106:  IPX.NLM cannot be unloaded because it is in use by another module.

Action

Close all IPX/SPX* applications that are open. Then try to unload the IPX.NLM program again.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 114: One or more GNMA Responders are registered.

Explanation

If one or more 16- or 32-bit Generic Network Management Agent (GNMA) responders have been loaded, this will keep IPX* from being able to unload cleanly. A GNMA responder is a program that interfaces with the IPX diagnostics facility.

Action

Before unloading the IPX.NLM program, unload any Novell or third-party GNMA responders.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 11: Error Detected by IPX.NLM.

                  Error detected by routine : internal_function_information

                  Relative location : internal_offset_information

                  Debug data : data

Explanation

This message is displayed when IPX* encounters an error that it did not expect. This information is used by Novell* to debug possible internal problems.

Action

Check for possible upgrades that might address this particular problem. Report this error to a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 12:  IPX was not able to bind to any board.

Explanation

The user has defined a specific board to bind using the "Net Bind" keyword under the "Protocol IPX" heading in Windows** 3.x. Or the user has specified unusuable settings in the "Use only the following frame types" field of the Advanced IPX property page in Windows** 95**. In this case, the auto bind parameter is turned off. If the board that the user specified is not available, this means that IPX* has not been bound to any network boards.

Action

Make sure that the Net Bind or property page settings are correct. If you are unsure what these settings should be, then comment out the Net Bind setting in the NET.CFG file or remove the custom settings in the Advanced IPX property page to let IPX auto bind to the board.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX -x- 13: Board number number not registered with the LSL or repeated in Bind Statement.

Explanation

There might be duplicate "Net Bind" entries in the "Protocol IPX" section of the registry or the NET.CFG file. IPX* tries to bind to each of the boards listed, so if a duplicate board entry is found, this message appears.

Action

Using the "Primary" or "Net Bind" keywords, check the Advanced IPX property page or the NET.CFG for possible invalid or duplicate settings.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IPX Messages

IPX -x- 11: Error Detected by IPX.NLM.

IPX -x- 12: IPX was not able to bind to any board.

IPX -x- 13: Board number number not registered with the LSL or repeated in Bind Statement.

IPX -x- 102: Unsupported execution environment. This NLM must be loaded under DOS, Windows 3.X, or Windows 95.

IPX -x- 103: IPX.NLM could not allocate a V86 callback address needed for IPX/SPX Application Interface.

IPX -x- 104: IPX.NLM could not allocate conventional memory needed for IPX/SPX Application Interface.

IPX -x- 106: IPX.NLM cannot be unloaded because it is in use by another module.

IPX -x- 114: One or more GNMA Responders are registered.


NIOS Messages

NIOS-x-001; Message file name is invalid. Program load aborted.

NIOS-x-024; An attempt to obtain the VCPI protected mode entry point failed.

NIOS-x-027: The BIOS installed in this machine does not support the INT 15h keyboard intercept function. NIOS.EXE cannot be use

NIOS-x-028: All XMS memory is in use or an XMS error has occurred.

NIOS-x-029; Initial XMS memory allocation failed.  Error code (XMS_error_code, hex_value).

NIOS-x-030: An attempt to lock the initial XMS memory block failed. Error code (XMS_error_code, hex_value).

NIOS-x-036: Error during call to XMS Move XMS memory block (XMS_error code: hex_value).

NIOS-x-037: This module has already been loaded.

NIOS-x-039: An attempt to open NIOS.EXE for reading failed.

NIOS-x-040: Not enough free memory available to read in NIOS.NLM file.

NIOS-x-041: An attempt to read NIOS.EXE failed.

NIOS-x-042: Invalid command line option was specified: "option_specified_by_user"

NIOS-x-043: Invalid mode switch type "switch_type".  Enter NIOS /? for help.

NIOS-x-044: Invalid XMS API entry point. The installed memory manager is not compatible with the XMS standard.

NIOS-x-066: Pseudo module name did not free one or more resources before being destroyed.

NIOS-x-067: Physical memory block allocated from XMS exceeds the NIOS linear address mapping. Alloc block at location size numb

NIOS-x-069: Please wait while the NetWare Client shuts down...

NIOS-x-070: Invalid interrupt 'value' specified. Interrupts must be hexadecimal values in the range 0 through F.

NIOS-x-071: Module <name> passed an invalid module handle parameter to NIOS function (<name>).

NIOS-x-072: The linear address range needed by NIOS is already being used.

NIOS-x-073: Unable to locate selector in memory manager's GDT.  Use compatible VCPI mode switching command line option /MV

NIOS-x-074: Invalid memory manager IDT "Invalid Opcode" selector.  Use compatible VCPI mode switching command line option /MV

NIOS-x-075: Windows v3.0 is not supported by the 32-bit NetWare client.

NIOS-x-076: The installed 32-bit NetWare client does not support this version of Windows.

NIOS-x-077: Unable to find <NIOS_path_and_filename> which is needed to support Enhanced mode Windows.

NIOS-x-078: An error occurred during an attempt to autoload information from NIOS_path_and_filename which is needed to support

NIOS-x-083: NIOS was unable to alloc a temporary 2K conventional memory stack needed to issue a call to EISA BIOS Int 15h.  If

NIOS-x-085: The 32-bit NetWare Client does not support task switchers

NIOS-x-087: NIOS.NLM is not tacked to NIOS.EXE

NIOS-x-088: Error reading NIOS.NLM messages from message file.

NIOS-x-090: Not enough free memory to load module.

NIOS-x-091: Unable to find load file NLM_module_name

NIOS-x-092: Error expanding load file path path and filename

NIOS-x-093: Not enough free memory to load module.

NIOS-x-094: Module name did not remain resident.

NIOS-x-096: NLM_module_name is not a valid module name.

NIOS-x-097: Module NLM_module_name is not loaded.

NIOS-x-105: An attempt to load module_NLM_name failed because the specified file could not be found.

NIOS-x-106: An attempt to load module_name failed because an error occurred while accessing the module's file.

NIOS-x-107: An attempt to load module_name failed due to a lack of memory.

NIOS-x-108: An attempt to load module_name  failed because the module is not a valid NLM file.

NIOS-x-109: An attempt to load module_name  failed because the module references an undefined external: name_of_external_API_function

NIOS-x-110: An attempt to load module_name  failed because the module exports a public which has already been exported: name_of_

NIOS-x-111: An attempt to load module_name  failed because an error occurred while accessing the module's message file.

NIOS-x-112: An attempt to load module_name  failed because the module's message file is invalid or the wrong version.

NIOS-x-113: An attempt to load module_name  failed because the module is already loaded and cannot be loaded multiple times.

NIOS-x-114: An attempt to load module_name  again failed because it is a different version than the previously loaded module.

NIOS-x-115: An attempt to load module_name_to_be_loaded  failed because module module_name_already_loaded  has refused to  allow it to be loaded.

NIOS-x-116: Module_name  cannot be unloaded.

NIOS-x-117: Module_name  cannot be unloaded because it is being used by module_name.

NIOS-x-118: Invalid module handle passed to NiosUnload.

NIOS-x-119: Module_name  cannot be unloaded at this time.

NIOS-x-120: Desired_module_name  cannot be unloaded because module refusing_module_name  has refused to allow it to be unloaded.

NIOS-x-123: Module name  did not properly free 1 resource.

NIOS-x-124: Module name  did not properly free number resources.

NIOS-x-150: Could not open logfile name

NIOS-x-169: Not enough free XMS handles to grow memory pool by number  bytes. You need to increase the number of memory manager

NIOS-x-178: Invalid module handle owner field for allocated memory block number, (modHand was number).

NIOS-x-179: Module_name  called NiosFree with an invalid/corrupted or already free memory block number.


NIOS-x-001: Message file name is invalid. Program load aborted.

Explanation

NetWare was unable to load the message files for the NIOS module.

Action

Do the following:

Make sure that the NWLANGUAGE environment is set as specified for the language being used.

Make sure that another application does not have the external message file opened.

Make sure the external message file (if applicable) is in the correct location. The logic for finding a language module is as follows (the \LOAD directory is the directory where the message file indicated resides):

Look in the current directory for a .MSG file.  If it is not found, check to see if the NWLANGUAGE environment variable is set.

If the NWLANGUAGE environment variable is not set, then check the LOAD directory for the .MSG file. If the file is not there, then use the message file that is bound to the module.

If the NWLANGUAGE environment variable has been set, try to locate the message file in the <load path>\NLS\YYY (where YYY is the value specified by NWLANGUAGE). If the file is not there, then use the message file that is bound to the module.


NIOS-x-024: An attempt to obtain the VCPI protected mode entry point failed.

Explanation

This error rarely occurs. If it does, the following has occurred:

The memory manager has responded appropriately to the VCPI Presence Detection function but not to the "Get Protected Mode Interface" function.

Memory is corrupted.

The memory manager is severely broken.

Action

First, try rebooting the machine. If, after the machine is rebooted, NIOS still displays this message while it is loading, obtain another memory manager. However, if the current memory manager is Emm386, remove it and use HIMEM.SYS only.


NIOS-x-027: The BIOS installed in this machine does not support the INT 15h keyboard intercept function. NIOS.EXE cannot be use

Explanation

The BIOS on most machines supports the generation of an INT 15h function 4fh when a keyboard interrupt (9h) occurs. NIOS needs this function to support several features, including debugger support and a warm boot cleanup.

Action

Replace the BIOS with one that supports this function.


NIOS-x-028: All XMS memory is in use or an XMS error has occurred.

Explanation

Because NIOS loads mostly in extended (XMS) memory, extended memory must be available when NIOS loads. This message is displayed when the initial query made by NIOS to the memory manager to determine the available extended memory fails or returns an error to the application that no memory is available.

Action

Increase the amount of available extended (XMS) memory. See "Resolving Workstation Memory Problems."


NIOS-x-029: Initial XMS memory allocation failed.  Error code (XMS_error_code, hex_value).

Explanation

When NIOS.EXE was loading, it was unable to allocate extended memory.

Action

The action depends on the error code displayed. A description of the error code is displayed after the error number. For the specific XMS error code displayed, see the action in the documentation for the memory manager you are using, or contact the vendor of the memory manager.


NIOS-x-030: An attempt to lock the initial XMS memory block failed. Error code (XMS_error_code, hex_value).

Explanation

NIOS.EXE is unable to lock extended memory as it is loading.

Action

The action depends on the error code displayed. A description of the error code is displayed after the error number. For the specific XMS error code displayed, see the action in the documentation for the memory manager you are using, or contact the vendor of the memory manager.


NIOS-x-036: Error during call to XMS Move XMS memory block (XMS_error code: hex_value).

Explanation

When NIOS.EXE was loading, it was unable to move extended memory.

Action

The action depends on the error code displayed. A description of the error code is displayed after the error number. For the specific XMS error code displayed, see the action in manual of the memory manager you are using, or contact the vendor of the memory manager.


NIOS-x-037: This module has already been loaded.

Explanation

The user tried to load NIOS.EXE when it was already loaded. When NIOS.EXE is already running, it cannot be loaded again.

Action

Do not load NIOS.EXE twice.


NIOS-x-039: An attempt to open NIOS.EXE for reading failed.

Explanation

The NIOS client needs to be able to open the NIOS.EXE file for reading both during and after initialization. This error indicates the user was able to initialize NIOS.EXE, but is unable to open it for reading.

Action

Make sure the user has sufficient rights to read the NIOS.EXE file (on workstations that enforce user rights) and that file attributes for NIOS.EXE allow reading. Also make sure that no other applications have the NIOS.EXE file open.


NIOS-x-040: Not enough free memory available to read in NIOS.NLM file.

Explanation

The NIOS.NLM file is linked to NIOS.EXE. Although NIOS has a very small conventional memory footprint after it has initialized, it requires a larger amount of conventional memory while it is intializing. Not enough conventional memory is available for NIOS to initialize.

Action

Increase the conventional memory available at the workstation. See Resolving Workstation Memory Problems.


NIOS-x-041: An attempt to read NIOS.EXE failed.

Explanation

NIOS needs to be able to read the NIOS.EXE file both during and after initialization. The user was able to run NIOS.EXE and open it for reading, but an error occurred when NIOS was reading the file. This could indicate that the file is corrupted.

Action

Make sure that no other applications currently have the NIOS.EXE file open. If no applications have the file open and you still see this message, the file might be corrupted. In this case, replace the NIOS.EXE with a new NIOS.EXE file.


NIOS-x-042: Invalid command line option was specified: "option_specified_by_user"

Explanation

When loading NIOS.EXE, the user typed a command line option that was not valid. A list of valid options is displayed with this message.

Action

When loading NIOS.EXE, type options that are valid. To see the list again, type "NIOS /?" and press <Enter>.


NIOS-x-043: Invalid mode switch type "switch_type".  Enter NIOS /? for help.

Explanation

When loading NIOS.EXE, the user typed a switch type that was not valid.

Action

When loading NIOS.EXE, type options that are valid. To see the list, type "NIOS /?" and press <Enter>.


NIOS-x-044: Invalid XMS API entry point.  The installed memory manager is not compatible with the XMS standard.

Explanation

NIOS.EXE needs to enter the extended memory manager’s API entry point using the method described in the XMS specification. The memory manager must support this method for NIOS.EXE to function correctly. The user cannot run NIOS.EXE with the memory manager that is installed.

Action

Install a different memory manager. Then try to initialize NIOS.EXE again.


NIOS-x-066: Pseudo module name did not free one or more resources before being destroyed.

Explanation

NIOS allows loaded modules to create "pseudo modules" that really are part of the same module but are treated like separate modules. NIOS tracks each loaded module’s use of the workstation’s resources (such as memory allocations or synchronization objects). When a loaded module is unloaded, it should free all workstation resources it is using. The module indicated in the message did not free the resources it was using.

Action

The user might be able to continue working; however, the workstation's environment might be unstable. Reboot the workstation. If the problem persists, report the problem to the vendor of the module indicated.


NIOS-x-067: Physical memory block allocated from XMS exceeds the NIOS linear address mapping. Alloc block at location size numb
NIOS-x-067: Physical memory block allocated from XMS exceeds the NIOS linear address mapping. Alloc block at location size number bytes, exceeded highest physical address location by number bytes.

Explanation

When NIOS initializes, it determines the highest physical memory address in the workstation memory and maps all memory up to this address to a linear address. The installed memory manager has returned an address higher than the one NIOS determined at initialization. This difference might have occurred for any of  these three reasons:

Memory is corrupted.

The memory manager contains a bug.

NIOS is not correctly determining the highest physical address.

Action

Restart the workstation. If you continue to see this problem, try changing memory managers. If you still continue to see this problem, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-069: Please wait while the NetWare Client shuts down...

Explanation

This message is displayed when the user presses <Ctrl>+<Alt>+<Del>. It is displayed while NIOS.EXE gives all loaded modules a chance to clean up (such things as flush caches or tear down connections) before the workstation shuts down.

Action

1. Wait until the machine reboots.

2. Turn off the machine (this might result in lost data).


NIOS-x-070: Invalid interrupt 'value' specified. Interrupts must be hexadecimal values in the range 0 through F.

Explanation

NIOS provides a service to LAN drivers that parses the command line for them. If the LAN driver (such as CNE2000.LAN) was loaded with an value in the "int=" part of the command line that it cannot interpret, this message appears.

Action

Load the LAN driver with a valid interrupt value.


NIOS-x-071: Module <name> passed an invalid module handle parameter to NIOS function (<name>).

Explanation

A bug is present in the module indicated, or workstation memory might be corrupted.

Action

The user might be able to continue working; however, the workstation's environment might be unstable. Reboot the workstation. If the problem persists, report the problem to the vendor of the module indicated.


NIOS-x-072: The linear address range needed by NIOS is already being used.

Explanation

A conflict exists with another program that runs on the system level. NIOS cannot run while the other program is loaded.

Action

Unload one program at a time until the conflicting program is found. Remove the conflicting program.


NIOS-x-073: Unable to locate selector in memory manager's GDT.  Use compatible VCPI mode switching command line option /MV when

Explanation

If NIOS detects the EMM386 memory manager, it attempts to use a special mechanism that is faster for switching between processor modes and circumvents the memory manager’s standard mechanism. This faster mechanism involves the use of some well known free selectors in the GDT (Global Descriptor Table) for the EMM386 memory manager. If they are not available, NIOS must use standard VCPI mode switching.

Action

To force NIOS.EXE to use standard VCPI mode switching, reload NIOS.EXE with the /MV command line option.  Run STARTNET.BAT or manually load the modules needed to connect the client to the network.


NIOS-x-074: Invalid memory manager IDT "Invalid Opcode" selector.  Use compatible VCPI mode switching command line option /MV w

Explanation

If NIOS detects the EMM386 memory manager, it attempts to use a special mechanism that is faster for switching between processor modes and circumvents the memory manager’s standard mechanism. This faster mechanism involves hooking the interrupt for invalid opcode faults. If the current selector for this interrupt is not a 16-bit 80386 (or above) interrupt gate, NIOS must use standard VCPI mode switching.

Action

To force NIOS.EXE to use standard VCPI mode switching, reload NIOS.EXE with the /MV command line option.


NIOS-x-075: Windows v3.0 is not supported by the 32-bit NetWare client.

Action

Upgrade to a later version of Windows**.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-076: The installed 32-bit NetWare client does not support this version of Windows.

Explanation

If the user tries to initialize with Windows** 95** while NIOS.EXE is loaded, NIOS.EXE displays this message.

Action

When using Windows 95, make sure to install and use NetWare* Client* 32* for Windows 95.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-077: Unable to find <NIOS_path_and_filename> which is needed to support Enhanced mode Windows.

Explanation

To support Enhanced mode for Windows** 3.1x, the file indicated must not be deleted or changed and must remain in a readable state. This message indicates that NIOS was unable to open the file indicated for reading.

Action

Make sure file_name exists in the specified location and that its file attributes allow  reading.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-078: An error occurred during an attempt to autoload information from NIOS_path_and_filename which is needed to support
NIOS-x-078: An error occurred during an attempt to autoload information from NIOS_path_and_filename which is needed to support the Windows environment. Make sure this file has not been deleted, moved or changed. Windows load aborted.

Explanation

To support Enhanced mode Windows** 3.1x, the file indicated must not be deleted or changed and must remain in a readable state. This message indicates that NIOS was able to open the indicated file for reading but met another problem as it was reading the file. The file might be corrupted or it might be a different version from the NIOS loaded in memory.

Action

If the file is corrupted, obtain a new one. If it is a different version, restart the workstation to load the file indicated instead of the version currently loaded in memory.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-083: NIOS was unable to alloc a temporary 2K conventional memory stack needed to issue a call to EISA BIOS Int 15h.  If
NIOS-x-083: NIOS was unable to alloc a temporary 2K conventional memory stack needed to issue a call to EISA BIOS Int 15h. If Windows is active, this problem can be avoided by increasing the amount of conventional memory NIOS reserves during Windows initialization.

Action

By default NIOS.EXE reserves 8 KB, but this can be changed by specifying a different value for the NIOS GLOBAL V86 WIN PAGES parameter in the NET.CFG file.


NIOS-x-085: The 32-bit NetWare Client does not support task switchers

Explanation

NetWare* Client* 32* does not support task switchers, including the Windows** standard mode.

Action

Disable task switching in the application. Some applications, such as in GroupWise* for DOS, contain a task switcher that can be disabled. Otherwise, you cannot run these applications with NetWare Client 32.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-087: NIOS.NLM is not tacked to NIOS.EXE

Explanation

The NIOS.EXE file is corrupted or not linked properly.

Action

Obtain a new NIOS.EXE file.


NIOS-x-088: Error reading NIOS.NLM messages from message file.

Action

Do the following:

Make sure that the NWLANGUAGE environment is set as specified for the language being used.

Make sure that another application does not have the external message file opened.

Make sure the external message file (if applicable) is in the correct location. The logic for finding a language module is as follows (the \LOAD directory is the directory where the message file indicated resides):

Look in the current directory for a .MSG file.  If it is not found, check to see if the NWLANGUAGE environment variable is set.

If the NWLANGUAGE environment variable is not set, then check the LOAD directory for the .MSG file. If the file is not there, then use the message file that is bound to the module.

If the NWLANGUAGE environment variable has been set, try to locate the message file in the <load path>\NLS\YYY (where YYY is the value specified by NWLANGUAGE). If the file is not there, then use the message file that is bound to the module.


NIOS-x-090: Not enough free memory to load module.

Explanation

Not enough extended memory is available at the workstation to load the requested module.

Action

Increase the amount of available extended (XMS) memory. See "Resolving Workstation Memory Problems."


NIOS-x-091: Unable to find load file name NLM_module_name
NIOS-x-091: Unable to find load file NLM_module_name

Explanation

When typing the LOAD command, the user typed a filename that was valid but the file does not exist in any of the search areas.

Action

Check the spelling of the filename of the NLM* program and location of the file.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-092: Error expanding load file path and filename

NIOS -x- 092: Error expanding load file path path and filename

Explanation

In response to a LOAD command, NIOS was unable to determine the full DOS path name of the file indicated.

Action

Try loading the module from a different location.


NIOS-x-093: Not enough free memory to load module.

Action

Increase the amount of available extended (XMS) memory. See "Resolving Workstation Memory Problems."


NIOS-x-094: Module name did not remain resident.

Explanation

This message is displayed in response to the LOAD command after the module has completed execution. The module is no longer loaded in memory.

Action

If necessary, reload the module indicated.


NIOS-x-096: NLM_module_name is not a valid module name.

Explanation

The requested module name does not conform to the standard naming conventions for the workstation’s operating system.

Action

Check the spelling of the module name and reenter the command.


NIOS-x-097: Module NLM_module_name is not loaded.

Explanation

When the UNLOAD NLM_module_name command was entered, the module entered was not currently loaded.

Action

Check the spelling of the module name and reenter the command.


NIOS-x-105: An attempt to load module_NLM_name failed because the specified file could not be found.

Explanation

NIOS was unable to locate the file indicated. NIOS searches for the file using the following algorithm:

If a filename and a path were specified, it tries to load the requested path and filename.

If only a filename was specified, it searches the current directory, then the directories in the PATH environment variable, and then the NIOS system directory (which is the directory where NIOS.EXE resides for DOS and Windows** 3.1x, or the value of NWHOMEDIR under the [386enh] section of the SYSTEM.INI file for Windows 95**.)

Action

Make sure that the path and filename are spelled correctly and that the file resides in one of the search areas. For Windows 95, make sure NWHOMEDIR is set to the correct path.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-106: An attempt to load module_name failed because an error occurred while accessing the module's file.

Explanation

NIOS was able to find the requested module but was unable to correctly process it. The file might be corrupted.

Action

Obtain a new version of this file from the vender of the module.


NIOS-x-107: An attempt to load module_name failed due to a lack of memory.

Explanation

Not enough extended (XMS) memory is available at the workstation to load the module.

Action

Increase the amount of available extended (XMS) memory. See "Resolving Workstation Memory Problems."


NIOS-x-108: An attempt to load module_name failed because the module is not a valid NLM file.

Explanation

NIOS supports only the NetWare Loadable Module* (NLM*) executable file format.

Action

You cannot load this module.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-109: An attempt to load module_name failed because the module references an undefined external: name_of_external_API_fun
NIOS-x-109: An attempt to load module_name failed because the module references an undefined external: name_of_external_API_function_needed_by_module

Explanation

There are two common causes of this problem:

The module containing name_of_external_API_function_needed_by_module is not loaded.

The module that should contain name_of_external_API_function_needed_by_module is loaded, but it is the wrong version.

Action

Make sure you have followed installation instructions for the module indicated. If the message persists and you do not know which module contains name_of_external_API_function_needed_by_module, contact the vendor of the module indicated.


NIOS-x-110: An attempt to load module_name failed because the module exports a public which has already been exported: name_of_
NIOS-x-110: An attempt to load module_name failed because the module exports a public which has already been exported: name_of_external_API_function_needed_by_module

Explanation

Two modules are not allowed to export the same symbol or API function at the same time.

Action

Do not load both of these modules at the same time.


NIOS-x-111: An attempt to load module_name failed because an error occurred while accessing the module's message file.

Explanation

NIOS was unable to open the external message file for the module indicated.

Action

Do the following:

Make sure that the NWLANGUAGE environment is set as specified for the language being used.

Make sure that another application does not have the external message file opened.

Make sure the external message file (if applicable) is in the correct location. The logic for finding a language module is as follows (the \LOAD directory is the directory where the message file indicated resides):

Look in the current directory for a .MSG file.  If it is not found, check to see if the NWLANGUAGE environment variable is set.

If the NWLANGUAGE environment variable is not set, then check the LOAD directory for the .MSG file. If the file is not there, then use the message file that is bound to the module.

If the NWLANGUAGE environment variable has been set, try to locate the message file in the <load path>\NLS\YYY (where YYY is the value specified by NWLANGUAGE). If the file is not there, then use the message file that is bound to the module.


NIOS-x-112: An attempt to load module_name failed because the module's message file is invalid or the wrong version.

Explanation

The message file for the module indicated might have been created incorrectly or become corrupted.

Action

The module indicated cannot be loaded. Obtain a new version of the file from the vendor of the module.


NIOS-x-113: An attempt to load module_name failed because the module is already loaded and cannot be loaded multiple times.

Explanation

You cannot load the module indicated if it is already loaded.

Action

If you want to load this module, unload it then reload it.


NIOS-x-114: An attempt to load module_name again failed because it is a different version than the previously loaded module.

Explanation

You cannot load different versions of the same module.

Action

Ensure that the module you are trying to load has the same version as the module that was previously loaded.


NIOS-x-115: An attempt to load module_name_to_be loaded failed because module module_name_already_loaded has refused to allow i
NIOS-x-115: An attempt to load module_name_to_be_loaded failed because module module_name_already_loaded has refused to allow it to be loaded.

Explanation

Before NIOS actually loads a module, it checks to see if a module that is already loaded objects to the new module being loaded. If a module does object, it should also display an explanation.

Action

To understand what you might be able to do, read the explanation of the objecting module. Try unloading the objecting module and then reloading the previously desired module.


NIOS-x-116: Module_name cannot be unloaded.

Explanation

The module indicated was created so that it cannot be unloaded by the user.

Action

Do not try to unload the module.


NIOS-x-117: Module_name cannot be unloaded because it is being used by module_name.

Explanation

If a module is currently being used by another module, it cannot be unloaded.

Action

Unload the other module indicated first. Then unload the desired module.


NIOS-x-118: Invalid module handle passed to NiosUnload.

Explanation

An attempt to unload a module through a system API failed because the requested module is not loaded or does not exist.

Action

Reboot the workstation. If the problem continues, report it to a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOS-x-119: Module_name cannot be unloaded at this time.

Explanation

When a module is unloaded, through the UNLOAD command or a system API, NIOS asks the module if it will allow itself to be unloaded. If the module refuses, NIOS displays this message.

Action

This might be a temporary condition. Try unloading the module later.


NIOS-x-120: Desired_module_name cannot be unloaded because module refusing_module_name has refused to allow it to be unloaded.

Explanation

When a module is unloaded, through the UNLOAD command or a system API, NIOS produces a system event notifying all other interested modules, each of which can refuse to allow the unload. The refusing_module should have displayed a message explaining why it refused the UNLOAD request.

Action

Try unloading the refusing_module first. Then try unloading desired_module again.


NIOS-x-123: Module name did not properly free 1 resource.

Explanation

NIOS tracks each loaded module’s use of the workstation’s resources (such as memory allocations or synchronization objects). When a loaded module is unloaded, it should free all workstation resources it is using. The module indicated in the message did not free a resource it was using.

Action

The user might be able to continue working; however, the workstation's environment might be unstable. Reboot the workstation. If the problem persists, report the problem to the vendor of the module indicated.


NIOS-x-124: Module name did not properly free number resources.

Explanation

NIOS tracks each loaded module’s use of the workstation’s resources (such as memory allocations or synchronization objects). When a loaded module is unloaded, it should free all workstation resources it is using. The module indicated in the message did not free a resource it was using.

Action

The user might be able to continue working; however, the workstation's environment might be unstable. Reboot the workstation. If the problem persists, report the problem to the vendor of the module indicated.


NIOS-x-150: Could not open logfile name

Explanation

NIOS was unable to open the file specified for diagnostic message logging.

Action

Make sure the file is not open by another application and that its attributes allow reading and writing.


NIOS-x-169: Not enough free XMS handles to grow memory pool by number bytes. You need to increase the number of memory manager
NIOS-x-169: Not enough free XMS handles to grow memory pool by number bytes. You need to increase the number of memory manager XMS handles (e.g. DEVICE=HIMEM.SYS /NUMHANDLES=xx).

Explanation

All extended memory handles are in use by NIOS, loaded modules, and other applications. Without additional handles, no more extended memory can be allocated.

Action

Increase the number of handles that are available to the XMS memory managers. For instructions, see the documentation for the memory manager you are using. If you are unable to increase the number of handles, then remove some of the other applications that use extended memory.


NIOS-x-178: Invalid module handle owner field for allocated memory block number, (modHand was = number).

Explanation

The memory at the workstation might be corrupted.

Action

Restart the workstation.


NIOS-x-179: Module_name called NiosFree with an invalid/corrupted or already free memory block number.

Explanation

A bug exists in the module indicated, or the workstation memory is corrupted.

Action

The user might be able to continue working; however, the workstation's environment might be unstable. Reboot the workstation. If the problem persists, report it to a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOSWIN -x- 1: The installed NIOS.EXE is incompatible with NIOSWIN.NLM.

Explanation

The contents of the NIOS.EXE file might be corrupted.

Action

Replace the NIOS.EXE file with a copy from the NetWare* Client* distribution diskette or CD-ROM, and then restart the workstation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOSWIN -x- 2: Not enough free memory to register Windows specific producer events.

Explanation

This error might occur during the intialization phase of Windows** 3.x  if the workstation is extremely low on memory.

Action

Increase the amount of available extended (XMS) memory. See "Resolving Workstation Memory Problems."

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOSWIN -x- 4:  An attempt to create Windows semaphores failed during NIOS Windows initialization.

Explanation

This error might occur during the intialization phase of Windows** 3.x  if the workstation is extremely low on memory.

Action

Increase the amount of available extended (XMS) memory. See "Resolving Workstation Memory Problems."

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOSWIN -x- 5:  An attempt to hook IRQ Interrupt_number failed during NIOS Windows initialization.

Explanation

A hardware device driver loaded during Windows’** initialization has claimed an IRQ (hardware interrupt) that was already being used by a network board.

Action

Try changing the IRQ used by the network board, or change the IRQ used by the conflicting device. The MS-DOS MSD.EXE utility might aid in diagnosing the IRQ used by the network board or conflicting device.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOSWIN -x- 6:  Incompatible version of VPICD.386 detected during NIOS Windows initialization.

Explanation

This error might occur when loading a version of Windows** 3.x  that NIOS.EXE is not compatible with.

Action

Report this problem to NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NIOSWIN Messages

NIOSWIN -x- 1: The installed NIOS.EXE is incompatible with NIOSWIN.NLM.

NIOSWIN -x- 2: Not enough free memory to register Windows specific producer events.

NIOSWIN -x- 4: An attempt to create Windows semaphores failed during NIOS Windows initialization.

NIOSWIN -x- 5: An attempt to hook IRQ Interrupt_number failed during NIOS Windows initialization.

NIOSWIN -x- 6: Incompatible version of VPICD.386 detected during NIOS Windows initialization.


NetWare Technical Support Options

For more information about available NetWare Technical Support options, see the Client 32 Setup Help.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview, How can I find the information associated with a message?
How can I find the information associated with a message?

Look for the message string by its module name and its  unique identifying number.

In this Help, the modules are listed alphabetically in the topic Module Names. Each module contains the messages for that module. The messages are listed numerically, and then alphabetically.

Any variable information such as filenames, function names, file paths, and version will be categorized by a generic name and appear in italics in this documentation.

For example: The message "NIOS-020-001: Message file NIOS.MSG is invalid. Program load aborted." would appear as "NIOS-x -001: Message file file_name  is invalid. Program load aborted."

You can also use the Search function in Help to find a list of the messages by the module name. Make search entries such as, NIOS Messages or Client32 Messages.


Overview, What information does this Help file contain?
What information does this Help file contain?

This System Messages Help includes only messages generated by the modules included in the NetWare* Client* 32* for DOS/Windows** software.

This System Messages Help is not intended to be used as a diagnostic or troubleshooting guide, but is intended as a reference for understanding error conditions and the actions needed to correct them. It is written for experienced NetWare users.

The messages included in this System Messages Help are only the messages that needed additional information to help you understand why the error might be generated and what to do to resolve an error condition. If this information is given in the message itself, the message is not included in this Help. This Help does not contain a comprehensive list of all messages generated by this software.

Each message listed has one or more of the following fields of information:

Explanation: This field contains possible causes or reasons for displaying the message.

Action: This field contains possible strategies for resolving the problem indicated in the message.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview, What is a System Message
What is a NetWare System Message?

A NetWare* System Message is any message displayed by the NetWare networking software. NetWare System Messages include several types of messages:

Error

Warning

Status

A NetWare System Message might contain some or all of the following parts:

A source module name

A version or platform designation

A unique identifying number

A message string

An error code

A typical message for NIOS might appear as follows:

NIOS-020-001: Message file NIOS.MSG is invalid. Program load aborted.

Some variation occurs in the format of certain groups of messages. Messages for LAN drivers, for example, include a platform designation instead of a version number:

CNE2000-DOS-001: The LSL is not loaded.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Resolving Workstation Memory Problems

For DOS/Windows** Workstations

To increase the amount of available conventional memory, do one or more of the following:

Close any unnecessary applications.

Unload any unneeded TSR (terminate-and-stay-resident) programs (DOS/Windows only).

Load device drivers and TSR programs into XMS, EMS, or high memory (DOS/Windows only)

Modify the workstation environment as necessary to reduce the number of files that can be open at the same time, the number of buffers allocated for disk drives, and the memory size allocated by the shell for the DOS environment.

Install more memory in the workstation.

To increase the amount of available extended (XMS) memory, do one or more of the following.

If possible, reconfigure the way the workstation uses memory using a memory manager's configuration program.

Remove unneeded programs or modules that use extended memory.

Reduce the extended memory used by certain programs.

Reduce the EMS memory allocated.

Unload any unneeded NLM programs that use extended memory.

Reduce the size of the NetWare* Client* 32* network cache. Adjust the Max Cache Size setting. For more information on adjusting this setting, see the applicable NetWare Client 32 Help file, Windows 95** or DOS/Windows.

Reduce the size of the local disk cache (such as SMARTDRV.EXE).

Install more memory in the workstation.

For Windows 95 Workstations

All of the recommendations listed for DOS/Windows will work except those indicated; however, Windows 95 manages memory differently than previous versions of Windows. First, follow the recommendations stated in Help for Windows 95, and then use any of these recommendations. If you still have problems, contact a NetWare support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


System Messages

Overview

What is a NetWare System Message?

What information does this System Messages Help contain?

How can I find the information associated with a message?

Module Names

ABEND

CLIENT32

IPX

NIOS

NIOSWIN

VMLID

Reference

Client 32 Setup

Trademarks


Trademarks

Copyright © 1994-1996, Novell, Inc.  All rights reserved.  Patent Pending.

Novell Trademarks

Client 32 is a trademark of Novell, Inc.

GroupWise is a trademark of Novell, Inc.

IPX is a trademark of Novell, Inc.

IPX/SPX is a trademark of Novell, Inc.

LANalyzer is a registered trademark of Novell, Inc. in the United States and other countries.

Link Support Layer and LSL are trademarks of Novell, Inc.

ManageWise is a trademark of Novell, Inc.

NE2000 is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare 3 is a trademark of Novell, Inc.

NetWare 4 is a trademark of Novell, Inc.

NetWare Client is a trademark of Novell, Inc.

NetWare Core Protocol and NCP are trademarks of Novell, Inc.

NetWare Directory Services and NDS are trademarks of Novell, Inc.

NetWare DOS Requester is a trademark of Novell, Inc.

NetWare/IP is a trademark of Novell, Inc.

NetWare Loadable Module and NLM are trademarks of Novell, Inc.

NetWare Management System and NMS are trademarks of Novell, Inc.

NetWire is a registered service mark of Novell, Inc. in the United States and other countries.

Network Support Encyclopedia Professional Volume and NSEPro are trademarks of Novell, Inc.

Novell is a registered trademark of Novell, Inc. in the United States and other countries.

Novell Application Notes is trademark of Novell, Inc.

Novell Authorized Reseller is a service mark of Novell, Inc.

Novell Gold Partner is a service mark of Novell, Inc.

Novell Labs is a trademark of Novell, Inc.

The Novell Network Symbol is a trademark of Novell, Inc.

Novell Platinum Partner is a service mark of Novell, Inc.

Novell Technical Services is a service mark of Novell, Inc.

Open Data-Link Interface and ODI are trademarks of Novell, Inc.

Packet Burst is a trademark of Novell, Inc.

SPX is a trademark of Novell, Inc.

Storage Management Services and SMS are trademarks of Novell, Inc.

Virtual Loadable Module and VLM are trademarks of Novell, Inc.

Third-Party Trademarks

CompuServe is a registered trademark of CompuServe, Inc.

Hewlett Packard and HP are registered trademarks of Hewlitt-Packard Company.

IBM is a registered trademark of International Business Machines Corporation.

Intel is a registered trademark of Intel Corporation.

Microsoft is a registered trademark of Microsoft Corporation.

MS is a registered trademark of Microsoft Corporation.

MS-DOS is a registered trademark of Microsoft Corporation.

Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP.

OS/2 is a registered trademark of International Business Machines Corporation.

PostScript is a registered trademark of Adobe Systems Incorporated.

Windows is a registered trademark of Microsoft Corporation.

Windows 95 is a trademark of Microsoft Corporation.

Windows NT is a trademark of Microsoft Corporation.


VMLID Messages

VMLID: NDIS is not loaded, cannot register VMLID.

VMLID: Received Packet at Interrupt Time

VMLID: VMLID Failed initializing NDIS Protocol Stack: Error NDIS_internal_error_code

VMLID: VMLID has not received a ProtocolBindAdapter callback from NDIS.


VMLID: NDIS is not loaded, cannot register VMLID.

Explanation

The NDIS** (Network Driver Interface Specification**) VxD must be loaded before loading VMLID. If the NDIS VxD has not been loaded, a configuration problem probably exists.

Action

Reboot the workstation. If the error persists, reinstall the NetWare* Client* 32* software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


VMLID: Received Packet at Interrupt Time

Explanation

The NDIS** driver is passing data up to NDIS Protocol Stacks at interrupt time. This is an illegal function that might cause system corruption.

Action

Notify the network driver supplier about the problem. Replace the network driver.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


VMLID: VMLID Failed initializing NDIS Protocol Stack: Error NDIS_internal_error_code

Explanation

VMLID was unable to register with the NDIS** (Network Driver Interface Specification) driver as an NDIS protocol stack.

Action

Reboot the workstation. If the error persist, record the circumstances in which the error occurred and the error code displayed, and then report this information to a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


VMLID: VMLID has not received a ProtocolBindAdapter callback from NDIS.

Explanation

VMLID was not notified by NDIS** of the existence of any network adapters within a reasonable amount of time. This message could be displayed on a laptop that is started without a PCMCIA card inserted. Or it could indicate a possible problem in the registry where NDIS does not recognize that it needs to notify VMLID about inserted or present network adapters.

Action

To isolate the cause of the problem, do the following:

1.	Press <Control>+<Enter> to allow Windows** 95** to continue to load.

2.	Bring up the "Network" control panel.

3.	Verify that the installed network driver ("Adapter") is suitable for the network board in use.

4.	Check the properties of the network driver and make sure that the interrupt, port, and other settings are correct.

5.	Check the bindings for the network driver. Make sure that the two following items are listed: the "IPX/SPX Compatible Protocol" and the "Novell NDIS Support Module."

If everything in items 3 through 5 seem okay, then make sure the file for the network driver you are using is in the WINDOWS or the WINDOWS\SYSTEM directory.

If any configuration information was corrected, restart Windows 95.

If the message is still displayed after verifying everything and restarting Windows 95, verify that the network driver is loading properly and that the system is trying to load the driver. If the VXD for the network driver is not being loaded, check for problems with the network board and its configuration.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.