Dec 082017
 
Latest release of Netware v3.11 operating system patches.
File 311PT1.ZIP from The Programmer’s Corner in
Category Network Files
Latest release of Netware v3.11 operating system patches.
File Name File Size Zip Size Zip Type
311PT1.DOC 24020 6880 deflated
AFPFIX1.NLM 2663 1157 deflated
DIRLPFIX.NLM 1508 790 deflated
DOTFIX.NLM 1343 721 deflated
ELRDFIX.NLM 2953 1733 deflated
EVENTFIX.NLM 2174 1000 deflated
MFIXOPEN.NLM 1459 812 deflated
MKDIRFIX.NLM 2071 982 deflated
NCPSPFIX.NLM 1644 827 deflated
OS2OPNFX.NLM 1389 640 deflated
PAPFIX1.NLM 1145 559 deflated
PAPFIX3.NLM 1310 701 deflated
PATCHMAN.NLM 8939 4588 deflated
PCHMN221.DOC 6153 2390 deflated
REMDEVFX.NLM 1299 569 deflated
SPXFSFIX.NLM 1617 842 deflated
SYNCTIME.NLM 2131 1211 deflated
TRSTFIX.NLM 1621 861 deflated
WORMROFX.NLM 1081 497 deflated
WSDFIX.NLM 1733 789 deflated

Download File 311PT1.ZIP Here

Contents of the 311PT1.DOC file


README FILE FOR 311PT1.ZIP
This file contains the latest release of NetWare v3.11 Operating
System Patches. The following files are included in this release:

311PT1 DOC (This file)
AFPFIX1 NLM 2663 01-06-92 7:22p
DIRLPFIX NLM 1508 12-12-91 1:07p
DOTFIX NLM 1343 12-12-91 1:29p
ELRDFIX NLM 2953 12-17-91 4:33p
EVENTFIX NLM 2174 12-12-91 1:47p
MFIXOPEN NLM 1459 10-03-91 5:00p
MKDIRFIX NLM 2071 12-12-91 1:49p
NCPSPFIX NLM 1644 10-04-91 9:13a
OS2OPNFX NLM 1389 11-22-91 2:45p
PAPFIX1 NLM 1145 12-02-91 3:18p
PAPFIX3 NLM 1310 01-08-92 10:32a
PATCHMAN NLM 8939 12-12-91 11:32a
REMDEVFX NLM 1299 10-03-91 5:04p
SPXFSFIX NLM 1617 12-12-91 1:59p
SYNCTIME NLM 2131 12-17-91 4:17p
TRSTFIX NLM 1621 12-17-91 4:52p
WORMROFX NLM 1081 10-03-91 4:49p
WSDFIX NLM 1733 10-09-91 3:39p
PCHMN221 DOC 6153 12-31-91 2:22p

IMPORTANT NOTES:
1. The patches for the 3.11 Operating System included with this
release are for all number-of-user versions of NetWare v3.11.
There are some specific notes regarding the use of these patches
with any 3.11 Operating System patches dated prior to October of
1991. These notes are included below under the heading NOVELL
TECHNICAL BULLETIN and should be reviewed by anyone using these
patches.

2. Another documentation file accompanies these patches under the
name PCHMN221.DOC. This file explains the use of PATCHMAN.NLM,
which is required to manage these patches.

3. Each of the patches is listed below along with a description
and a list of which files it replaces.

4. A brief discussion of the patch concept and how to install a
patch is included below.


DESCRIPTION OF THE PATCHES

AFPFIX1 NLM
2663 01-06-92 7:22p This patch is only for NetWare for
Macintosh. AFPFIX1.NLM corrects a problem
with copying folders (containing files)
into drop boxes on the NetWare v3.11
server. This patch fixes all known drop
box problems in both System 6 and 7 for
all released versions of AFP.NLM. This
patch supersedes the original AFPFIX1.NLM
version and the correction in AFP.NLM
v3.01.

**NOTE: This patch supersedes AFPFIX.NLM (4-11-91 907) previously
distributed under the name AFPFIX.ZIP on forum NOVLIB, library 8


DIRLPFIX NLM
1508 12-12-91 1:07p This patch fixes a problem in NetWare 386
v3.11 that results in an infinite loop
when the DOS DIR command is used in a
subdirectory where more than 65,535 files
exist. This loop will also occur with
the FindFirst and FindNext DOS function
calls.

**NOTE: This patch supersedes DIRLPFIX1.NLM (4-9-91 797) previously
distributed under the name DRLFX1.ZIP on forum NOVLIB, library 4.
It also supersedes DIRLPFIX.NLM (10-2-91 1532) previously distributed
under the name of DRLFX1.ZIP in the NSD area of Netwire.


DOTFIX NLM
1343 12-12-91 1:29p This patch fixes the problem of multiple
directories of the same name being
created at the SYS: root level.
Currently, if the user creates
directories ending in two dots: ".."
(e.g. "STATS.."), multiple directories of
the same name will be created. A DIR
listing will show multiple directories of
the same name. For example:

>DIR

STATS
STATS
STATS

DOTFIX.NLM fixes the problem so that if
the user tries to create directories with
the same name, the error message "Unable
to create directory" appears.

**NOTE: This file supersedes DOTFIX.NLM (10-2-91 1351) previously
distributed under the name of DOTFIX.ZIP in the NSD area of
Netwire.


ELRDFIX NLM
2953 12-17-91 4:33p This patch is to be used in systems where
disk read performance is being effected
by workstations doing large amounts of
disk writes. The patch changes the disk
elevator queuing scheme to give priority
to disk reads.

**NOTE: This file supersedes ELRDFIX.NLM(10-2-91 2973) previously
distributed under the name ELRDFX.ZIP in the NSD area of Netwire.


EVENTFIX NLM
2174 12-12-91 1:47p This patch is required by any NLM that
needs object deletion notification.
Symptoms of this bug will vary, depending
on the NLM being run.

This patch addresses a problem that
occurs when a delete bindery object call
is made to the OS. The OS reports the
event after the object is already
deleted, thus preventing the application
from accessing information on the object
when the event is reported. This patch
fixes this problem; the bindery object is
not deleted until after the event is
reported.

**NOTE: This file supersedes EVENTFIX.NLM(10-2-91 2206) previously
distributed under the name OBJDEL.ZIP in the NSD area of Netwire.


MFIXOPEN NLM
1459 10-03-91 5:00p This patch is intended for all
number-of-user versions of NetWare 386
v3.11 that are running the MAC gateway
VAPS instead of the AFP NLMs. This patch
fixes the problem that MAC users have
when trying to open files that are
flagged Read Only. The user is unable to
open the file, and receives the error
message: "File not found."

**NOTE: This file supersedes MFIXOPEN.NLM(7-3-91 1112) previously
distributed under the name MFXOP1.ZIP in forum NOVLIB, library 4 of
Netwire. It also supersedes MFIXOPEN.NLM (10-2-91 1459) previously
distributed under the name MFXOP1.ZIP in the NSD area of Netwire.


MKDIRFIX NLM
2071 12-12-91 1:49p This patch fixes error codes returned by
create directory, and invalid error codes
returned when copying a file to an
invalid path. It replaces and supersedes
the previously released patch,
DIRHFIX1.NLM. Since DIRHFIX1.NLM and
MKDIRFIX.NLM patch some of the same
areas, they cannot coexist. To run
MKDIRFIX.NLM, DIRHFIX1.NLM must be
removed from the system.

Additionally, this fix changes error
codes returned from
"ERR_BAD_DIR_HANDLE-program aborted" to
"ERR_INVALID_PATH" in the case where the
server is scanning a directory path and a
file name exists in the middle of that
directory path. (For example: Makedir:
dir1/dir2/dir3 where dir2 is a filename.)

**NOTE: This file supersedes MKDIRFIX.NLM(10-2-91 2087) previously
distributed under the name MKDIR1.ZIP in the NSD area of Netwire.


NCPSPFIX NLM
1644 10-04-91 9:13a This patch prevents a zero-length
WriteToSpool NCP from being processed.
This problem has been known to cause an
ABEND:GENERAL PROTECTION PROCESSOR
EXCEPTION and corrupt an entire volume.

**NOTE: This file supersedes NCPSPFIX.NLM(10-2-91 1644) previously
distributed under the name NCPSP1.ZIP in the NSD area of Netwire.


OS2OPNFX NLM
1389 11-22-91 2:45p This patch allows a user to use the
"TYPE" command to view a file even though
SCAN file rights have not been granted.
Without this patch, if the user is
granted all rights but the SUPERVISOR and
SCAN file rights (including Read) the
file still cannot be "TYPE"ed. This
patch fixes this problem.


**NOTE: This file is the same file as OS2OPNFX.NLM previously
distributed under the name OS2OPN.ZIP direct from Novell on a Field
Test (or BETA) basis. This file has passed testing.


PAPFIX1 NLM
1145 12-02-91 3:18p This patch is only for V3.0 NetWare for
Macintosh. PAPFIX1.NLM is a patch to
APPLETLK.NLM v3.0. This patch resolves a
problem where server PAP sessions of
greater than 255 transactions would be
interrupted and fail. The AppleTalk
stack would then generate an error
message stating that the Tickle Timer
popped on the affected connection.

This problem would cause ATPS.NLM to
consistently fail to print files over one
megabyte in size or to return font lists
greater than 255 entries to Macintosh
clients. In these circumstances, ATPS
would return the message "PAP write: no
such device or address".

This patch is for use with v3.0 NetWare
for Macintosh; the problem is resolved
with v3.01 NetWare for Macintosh.

**NOTE: This file supersedes PAPFIX1.NLM(4-26-91 1033) previously
distributed under the name PAPFIX.ZIP in forum NOVLIB, LIB 8.


PAPFIX3 NLM
1310 01-08-92 10:32a This patch is only for V3.0 NetWare for
Macintosh. PAPFIX3.NLM modifies
APPLETLK.NLM v3.0 to resolve a problem
that ATPS.NLM has connecting to certain
non-Apple printers that require an
incrementing value in the WaitTime field
of PAP OpenConn packets.

The symptom of this problem visible to
users would be that ATPS.NLM generates
messages such as "Printer busy, status-
idle" and may not advertise the affected
queue on AppleTalk. This problem is
resolved with v3.01 NetWare for
Macintosh.

**NOTE: This file supersedes PAPFIX3.NLM(6-5-91 1326) previously
distributed under the name PAPFX3.ZIP in forum NOVLIB, LIB 8.


PATCHMAN NLM
8939 12-12-91 11:32a PATCHMAN.NLM is the Patch Manager which
tracks and manages all dynamic patches
for NetWare 386 v3.10 or above. All 3.11
Operating System patches included with
this documentation will require
PATCHMAN.NLM V2.20 or above. The version
of PATCHMAN included in this file is
v2.21. Please see PCHMN221.DOC that is
included with this file for further
explanation on PATCHMAN.NLM.

**NOTE: This file supersedes ALL PREVIOUS versions of PATCHMAN (FOR
VERSION 3.11 ONLY!).

REMDEVFX NLM
1299 10-03-91 5:04p This patch fixes a problem formatting
removable devices. If INSTALL.NLM is
loaded and FORMAT is run, the 3.11
Operating System causes an abend with the
message "ABEND: Kernel detected a process
switch during interrupt time."

**NOTE: This file supersedes REMDEVFX.NLM(8-2-91 1107) previously
distributed under the name REMDEV.ZIP in forum NOVLIB, LIB 4. It
also supersedes REMDEVFX.NLM(10-2-91 1299) previously available
under the name REMDEV.ZIP in the NSD area of Netwire.


SPXFSFIX NLM
1617 12-12-91 1:59p This patch fixes a problem that results
in a file server GPI in the
SPXFindSession. This ABEND is known to
occur when using Madge "Smart IPX" Token
Ring drivers.

The problem is caused by a connect
request SPX packet which arrives at the
server without the system bit being set.
This causes the server to look up the
session with ID = FFFF (session ID for
system packets), but since the system bit
isn't set, the server looks in the
session table for a client with a
corresponding ID. This causes
SPXFindSession to look beyond the end of
memory, resulting in a GPI ABEND.

The patch adds a test to SPXFindSession
to check for sessions beyond the end of
the session table. With this patch, if a
connect request SPX packet is sent
without the system bit set, the packet
will be discarded as invalid and the
workstation that sent the invalid packet
will hang.

**NOTE: This file supersedes SPXFSFIX.NLM(10-2-91 1625) previously
distributed under the name SPXFIX.ZIP in the NSD area of Netwire.


SYNCTIME NLM
2131 12-17-91 4:17p This patch forces the server's date/time
to be synchronized to the hardware's
clock at specified intervals. These
NLM's eliminate the gradual loss of time
experienced by the server due to "missed"
clock ticks while the server is in real
mode.
**NOTE: This file supersedes SYNC311.NLM(9-27-91 1987) previously
distributed under the name TIM386.ZIP in the NSD area of Netwire.

**NOTE ALSO: This file should not be confused with TIM386.ZIP
located in forum NOVLIB, Library 4, which is for Netware 386 v3.10a
and specifically refers to v3.10a in the documentation that comes
with that file.


TRSTFIX NLM
1621 12-17-91 4:52p This patch fixes a problem found when 9
or more trustee directory assignments for
individual users or groups are made at
the root level of the same volume
(usually volumes other than the SYS:
volume). Although the assignments are
made as they should be, the 9th and above
cannot be seen from SYSCON. (They do
appear in FILER or TLIST.)

This patch adds a check for the parent of
the trustee node that contains the ninth
trustee assignment; if the parent node is
the root of the volume, it checks for
trustee assignments.

This patch also fixes a problem found
when granting trustee rights to an
existing group. The rights appear to be
correct in SYSCON when viewed from user
SUPERVISOR, but these new rights do not
appear when viewed by the individual
user. These rights are not actually in
effect. When viewed as a group member,
the user gets the error: "GetTrusteePaths
returned error 242".

**NOTE: This file supersedes TRSTFIX.NLM(10-11-91 1603) previously
distributed under the name TRSTFX.ZIP in NSD area of Netwire.


WORMROFX NLM
1081 10-03-91 4:49p Currently, if a removable device is
initially mounted read/write, and then
the cartridge is removed and a new device
is inserted that has the write disable
tab set, the OS does not recognize that
the device is now Read only. This patch
fixes this problem.

**NOTE: This file supersedes WORMROFX.NLM(8-2-91 929) previously
distributed under the name WORMROFX.ZIP in forum NOVLIB, Library 4.
It also supersedes WORMROFX.NLM (10-2-91 1081) previously located
in the NSD area of Netwire.


WSDFIX NLM
1733 10-09-91 3:39p This patch fixes a problem with APIs that
allow users to access files on volumes
where they have no rights. This patch
generates a new handle so that rights are
re-enumerated with each volume change.

**NOTE: This is the same file as WSDFIX.NLM(10-9-91 1733)
previously distributed under the name WSDFIX.ZIP in NSD area of
Netwire.



INSTALLATION AND INFORMATION ABOUT NetWare v3.11 O.S. PATCHES
Each of the patches listed above are intended for 386 v.3.11 and
are dynamic patches which are loaded at the file server console as
a NetWare Loadable Modules. They require PATCHMAN.NLM v2.20 or
later in order to load.

*** PLEASE NOTE THE TECHNICAL BULLETIN ON THE 3.11 OPERATING SYSTEM
PATCHES INCLUDED BELOW.

Unlike patches previous to those for Netware 386 v3.10, the
SERVER.EXE file is never modified by these patches. These patches
patch the Operating System in memory, not on the disk. This means
that each patch must be loaded each time before any "fixes" take
effect. It is recommended that the command "LOAD " be
placed in the server's AUTOEXEC.NCF file to ensure that
the patch is always in effect when the server is initially brought
up.

Since they are NLM's, the patches can be loaded and unloaded
without ever having to bring the server down. Once loaded, the
Operating System is patched and ready to go.

Unloading the patches will restore the Operating System to its
original "un-patched" state.

Like all NLM-type patches, REMDEVFX.NLM requires the Patch Manager
(PATCHMAN.NLM) to be loaded before it can be loaded. If PATCHMAN
is not already loaded, the first patch will attempt to locate
PATCHMAN and load it automatically if found. PATCHMAN only needs
to be loaded once. All other patches will load once PATCHMAN is
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.

Installation:
To install a specific patch or patches, simply place the patch file
in the same directory as the other NLM files (SYS:SYSTEM or DOS
partition), and type "LOAD " for each patch you which
to load. Once a patch has loaded, all changes are in
effect until it is unloaded. If an error message appears, contact
Novell Technical Support. As suggested above, you will probably
want to enter the LOAD commands into your AUTOEXEC.NCF file to
insure that the patches are loaded automatically.



NOVELL TECHNICAL BULLETIN

TITLE: Effects of v3.11 Serialization Changes on
Patches and Fixes
DOCUMENT ID#: TB.P.298
DATE: 4 December 1991
PRODUCT: NetWare
PRODUCT REVISION: v3.11
SUPERSEDES: N/A

SYMPTOM: Errors, such as "Unexpected code encountered
in area to be patched" during implementation
of patches and fixes.

ISSUE/PROBLEM

Because of the unanticipated success of NetWare v3.11, the
available serialization range was exhausted. As a result, the
v3.11 operating system has been modified to extend that
serialization range. This modification has required a
corresponding change to all v3.11 operating system patches,
including those previously released. It does not affect any
patches or fixes other than v3.11 operating system patches. When
a user attempts to apply an unmodified NetWare v3.11 operating
system patch to a v3.11 operating system with the extended
serialization range, he or she may receive an error similar to the
one above.

SOLUTION

The modified NetWare v3.11 operating system patches can be applied
to any v3.11 operating system if the PATCHMAN.NLM (v2.20 or later)
that accompanies them is loaded at the file server. PATCHMAN.NLM
performs the application of a given patch to the v3.11 operating
system as it resides in file server memory.

Users should be aware of five important points:

1) PATCHMAN.NLM v2.20 (or later) must be loaded.

2) The modified patches, with PATCHMAN.NLM v2.20 (or later), will
successfully load on NetWare v3.11 operating systems without
the extended serialization range.

3) The re-released patches will not be successfully implemented
if PATCHMAN NLM v2.20 (or later) is not loaded.

4) Unmodified v3.11 operating system patches will work
successfully only on operating systems without the extended
serialization range. They will not work on a newly modified
operating system, nor on an operating system also running
modified patches or PATCHMAN v2.20 (or later).
5) The re-released NetWare v3.11 operating system patches are
dated October 1991 or later.

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

Novell, Inc. makes no representations or warranties with respect to
any NetWare software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose.

Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc. Further, Novell reserves
the right to discontinue distribution of any NetWare software.

Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of re-creating lost data, the
cost of any substitute equipment or program, or claims by any party
other than you. Novell strongly recommends a backup be made before
any software is installed. Technical support for this software
may be provided at the discretion of Novell.
*****************************************************************


 December 8, 2017  Add comments

Leave a Reply