NetWare Message File: NLMLib 4.11, Tran 1.0 2 0@LtYl)LCY$m 8 G h  ( @ c  \  )  <<< BAD MESSAGE >>>NLMLib messages begin here...Event RegistrationNLMLib BSD SocketFile System HookIPX/SPX socketsNLMLib-4.11-022: An error occurred loading the NLM with the /P option. There was insufficient server memory available.NLMLib-4.11-023: An invalid namespace was specified using the /N option. Only the namespace strings 'DOS,' 'MAC,' 'NFS,' 'FTAM' and 'OS2' are valid.NLMLib-4.11-024: Login using the /S option loading the NLM failed: rc = %d. An incorrect username or password may have been used in the login process.Login using the /S option loading the NLM was successful.NLMLib-4.11-009: This version of NLMLib.NLM will run only on NetWare v4.10 or later. Please obtain the correct version before attempting to load NLMLib.NLM.NLM Runtime Library Internal MemoryNLMLib-4.11-011: NLMLib failed to allocate an internal memory resource tag. There may not be enough server memory, or server memory may be corrupted.Service Advertising (instances)NLMLib-4.11-013: RegisterTrackedResource() for Service Advertising failed, rc = %d. An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted.NLMLib BSD SocketsNLMLib-4.11-014: RegisterTrackedResource() for BSD Sockets failed, rc = %d. An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted.Remote Server Sessions (instances)NLMLib-4.11-015: RegisterTrackedResource() for Remote Server Sessions failed, rc = %d. An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted. The NetWare NLM Runtime Library was unloaded NLMLib Worker ThreadsNLMLib-4.11-025: NLMLib failed to allocate an internal work-to-do resource tag. There may not be enough server memory or server memory may be corrupted.NLMLib-4.11-026: Could not initialize FS Hooks. NLMLib-4.11-027: IPX is required for this NLM to run in the I/O engine. NLMLib-4.11-066: An internal NLM start-up error has occurred: %s NLMLib-4.11-067: NLMLib failed to allocate the Connection tasks. An internal system error has occurred.Service Advertising Resource Tagsel pid glitchGeneric Socket Adapter AES StateSemaphore Resource TagDS Event Registration NLMLib-4.11-100: NLMLib cannot be loaded until Threads.NLM is updated! NLMLib-4.11-101: NLMLib cannot be loaded until Requestr.NLM is updated! C Library Environment: C Library Environment Resource TagC Library Environment Memory Resource TagC Library Environment Semaphore Resource TagNLMLib-4.11-200: No environment variables set! NLMLib-4.11-201: Unable to allocate resource tag. NLMLib-4.11-202: Unable to register console command (0x%X). NLMLib-4.11-203: Unable to allocate resource tag for memory. NLMLib-4.11-204: Unable to allocate resource tag for semaphore. NLMLib-4.11-205: Variable '%s' not found! Berkeley Sockets List SemaphoresNLMLib-4.11-081: NLMLib failed to allocate the internal memory resource tag for the Berkeley Sockets Semaphores. There may not be enough server memory, or server memory may be corrupted.NLMLib-4.11-082: select() overflow detected from: %s. NLMLib-4.11-082: NLMLib failed to initialize the Berkeley Socket semaphores. An internal system error has occurred.VeRsIoN=4.11CoPyRiGhT=Copyright (c) 1997, Novell, Inc. All rights reserved.NLMLib messages end here...