Category : Network Files
Archive   : DLDRFX.ZIP
Filename : README.TXT

Output of file : README.TXT contained in archive : DLDRFX.ZIP
This README file accompanies the DELDIRFX.NLM patch file for NetWare 386
v3.10 Rev A. The following file is included for this patch:

DELDIRFX NLM 1729 08-29-90 10:48a
PATCHMAN NLM 3005 08-29-90 10:38a

DELDIRFX is a dynamic patch which is loaded at the file server console as a
NetWare Loadable Module. This patch fixes a bug in NetWare 386 V3.10a that
would cause the server to ABEND with the message:

"DeleteDirectory found invalid phantom list."

whenever an attempt was made to delete a directory which contained a certain
number of trustees assigned to it. The number of trustees had to be greater
than eight and the binary representation for that number had to have the
number two bit set. For example, the binary representation of 10 trustees
is 1010; the second bit is set in this binary number.

To implement this patch, the NetWare 386 Patch Manager (PATCHMAN.NLM) must
first be loaded.

Three types of patches can be managed with PATCHMAN: dynamic, semi-static,
and static. Dynamic patches are .NLM files that can be loaded/unloaded while
the server is running. Unloading a dynamic patch will restore the Operating
System to its original "un-patched" state. Semi-static patches can also be
loaded while the server is running, but they cannot be unloaded. It is not
possible to undo the effects of a semi-static patch without first downing the
server and bringing it back up without loading the semi-static patch. A
static patch is a DOS executable program that makes changes to the SERVER.EXE
file. This type of patch is applied once and its effects are permanent. It
is suggested that static patches be applied to a copy of the SERVER.EXE file,
not the original file.

Dynamic and semi-static patches modify the Operating System in memory, not
on the disk. This means that dynamic and semi-static patches must be loaded
each time the Operating System is brought up in order for any "fixes" to take
effect. It is recommended that the command "LOAD " be placed in the
file server's AUTOEXEC.NCF file to ensure that the patch is always in effect
when the server is initially brought up. Typing MODULES at the server
console will show which dynamic patches have been loaded, but will not show
semi-static or static patches.

The Patch Manager (PATCHMAN.NLM) must be loaded before any dynamic or semi-
static patches can be loaded. If PATCHMAN is not already loaded, the
.NLM will attempt to locate PATCHMAN and, if found, will load it
automatically. PATCHMAN only needs to be loaded once; all .NLM patches can
then be loaded. PATCHMAN cannot be unloaded until all patches that rely on
it are first unloaded.

To implement this patch:

1) Copy PATCHMAN.NLM and the patch .NLM file 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) LOAD the patch .NLM file.

NOTE: 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.


Novell, Inc. makes no representations or warranties with respect to this
software patch, and specifically disclaims any express or implied warranties
of merchantability 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   : DLDRFX.ZIP
Filename : README.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: