Category : Network Files
Archive   : NCPLIM.ZIP
Filename : NCPLIMIT.TXT

 
Output of file : NCPLIMIT.TXT contained in archive : NCPLIM.ZIP
This README file accompanies NCPLIMIT for NetWare v3.10 rev. A. The
following files are included for this patch:

NCPLIMIT NLM 1980 12-12-90 9:25a
NCPLIMIT MAP 4438 12-12-90 9:25a
NCPLIMIT DOC 18591 12-17-90 11:52a
PATCHMAN NLM 4178 10-29-90 12:51p

NCPLIMIT is a dynamic patch which is loaded at the file server console as a
NetWare Loadable Module. This patch provides for better management of file
searches done on a NetWare 386 V3.10a server.

This patch adjusts to applications written using the findfirst function. If
the findfirst search function is not completed correctly, NetWare 386 will
generate the warning message "You exceeded your outstanding NCP directory
search limit." If loading this NLM does not eliminate the warning message,
the application will need to be rewritten according to the recommendations
described in NCPLIMIT.DOC.

Unlike v3.0 patches, the SERVER.EXE file is not modified by this patch.
NCPLIMIT.NLM will patch the Operating System in memory, not on the disk.
This means that NCPLIMIT must be loaded each time the server is brought up
for the patch to take effect. It is recommended that the command "LOAD
NCPLIMIT" be placed in the server's AUTOEXEC.NCF file to ensure that the
patch is always in effect when the server is brought up.

Since it is a NetWare Loadable Module, NCPLIMIT can be loaded and unloaded
without having to bring the server down. Once loaded, the Operating System
is patched and ready to go. Unloading NCPLIMIT will restore the Operating
System to its original "un-patched" state.

Like all NLM-type patches, NCPLIMIT requires the Patch Manager (PATCHMAN.NLM)
to be loaded before it can be loaded. If PATCHMAN is not already loaded,
NCPLIMIT will attempt to locate PATCHMAN and load it automatically if found.

PATCHMAN only needs to be loaded once and then all NLM patches can be loaded.
PATCHMAN cannot be unloaded until all patches that rely on it are first
unloaded. Typing "PATCHES" at the system command line once PATCHMAN is
loaded will display all patches currently loaded on the file server.

To implement this patch:

1) Copy PATCHMAN.NLM and the NCPLIMIT.NLM and NCPLIMIT.MAP files to the
same directory as the other NLM files on your system (SYS:SYSTEM is
suggested).

2) After the system is brought up, type LOAD PATCHMAN at the console.

3) Type LOAD NCPLIMIT. A message will appear saying that the Operating
System has been successfully patched. From this point on, all changes
are in effect until NCPLIMIT is unloaded. If an error message appears,
contact your NetWare support provider.

NOTE: Changes made by patches are typically addressed in future releases of
NetWare. This patch and PATCHMAN.NLM will only operate on NetWare 386
v3.10a. Future versions of NetWare 386 will require a version of
PATCHMAN specific to that release.

*****************************************************************************
DISCLAIMER

Novell, Inc. makes no representations or warranties with respect to this
software patch, and specifically disclaims any express or implied warranties
of merchantability, title, or fitness for a particular purpose.
Novell's intentions for this software patch is to provide a temporary
work-around to the anomalies described in this file. Such work-arounds are
typically addressed in future releases of NetWare.
Novell will not be responsible for any data loss that may result from
implementing this patch. Novell strongly recommends a backup be made before
any patch is applied. Technical support for this patch is provided at the
discretion of Novell.
*****************************************************************************


  3 Responses to “Category : Network Files
Archive   : NCPLIM.ZIP
Filename : NCPLIMIT.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/