
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              NetWare 4.01 OS Patches
DOCUMENT ID:        TID021320
DOCUMENT REVISION:  A
DATE:               08JUN94
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         401PT2.EXE

NOVELL PRODUCT and VERSION:
NetWare 4.01

ABSTRACT:

This file contains the latest operating system test patches for NetWare 4.01. 
Included with this prerelease are all patches for all user-versions of NetWare
4.01.  The patches included have system tested by Novell.  This Patch Kit is
more current than the NW4UPD_101 Update CD-ROM and contains additional
patches.

------------------------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
------------------------------------------------------------------------------

-----------------------------------------------------------------
BCKTTSFX NLM
============

SYMPTOM

Typically, after rebooting the server and going though the process of backing
out the TTS files, the server would hang with no messages.

SOLUTION

Apply BCKTTSFX NLM.       932 03-28-94   8:49a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.11, 3.12, 4.01

This Patch corrects a problem with backing out more than 263 Transaction
Tracking System (TTS) files.

It is important to Load BCKTTSFX.NLM after loading PATCH MANAGER in the
STARTUP.NCF file to allow the patch to work properly.

-----------------------------------------------------------------
COMPRFIX NLM
============

SYMPTOM

A case has been found where compression will causes an ABEND when server
memory is low and there has been several attempts for the compressor to get
more memory.

SOLUTION

Apply COMPRFIX NLM.      1487 03-28-94   9:03a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

-----------------------------------------------------------------
COMPVLFX NLM
============

SYMPTOM

After a compressed file (*.exe, *.com, *.bat) is copied to a volume with
compression turned off then executed, CCDSetFile is called with invalid file.

SOLUTION

Apply COMPVLFX NLM.     1636 12-21-93   9:07a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

This patch fixes CCDSetFile called with invalid file.  This occurs after a
compressed file  (*.exe, *.com, *.bat) is copied to a volume with compression
turned off then executed.

-----------------------------------------------------------------
CRDIRFIX NLM
============

SYMPTOM

The following error is returned if an attempt is made to create a directory
with an blank character (Alt+255) as the last character in the name.

MESSAGE

     Unable to create directory

SOLUTION

Apply CRDIRFIX NLM.      1313 02-22-94   4:22p


Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

Fix to allow the addition of a blank Character (Alt+255) to the end of a
directory name.

NetWare 3.11 allows the user to create directories for security reasons that
have a "blank"(Alt+255) as the last character of the directory name.  To allow
Netware 3.12 and 4.01 to have a  blank Character (Alt+255) to the end of a
directory name, apply this patch.

Example:  md test(Alt+255)

This works in DOS and on a NetWare 3.11 server.

-----------------------------------------------------------------
DAICCFIX NLM
============

SYMPTOM

If an error condition occurs, such as reaching the end of a tape, an error
code is returned to the calling application.  The error code would be
scrambled, resulting in the wrong error passed to the application.  The
result, as far as the Server (that is ABEND, hang, and so forth) would depend
on the specific application.

SOLUTION

Apply DAICCFIX NLM.      1031 02-08-94   9:47a

This patch deals with applications that directly control hardware devices
through NetWare (that is, Jukeboxes, worms, tapes, and so forth).  The patch
applies to applications that use a DAI interface to communicate with the
server's hardware.  Check with the vendor of the application to verify the use
of the DAI interface and apply the patch if necessary.

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

-----------------------------------------------------------------
DEVIOFIX NLM
============

SYMPTOM

Problem reported by Compaq with devices using DAI emulation.  Insight Manager,
on NetWare 4.01 servers, with a failed storage device, may show the device as
grey, rather than red.  Insight Manager, on NetWare 4.01 servers, with a
manually deactivated storage device, may show the device as grey, rather than
green.  This is a problem that applies to devices using DAI emulation.

SOLUTION

Apply DEVIOFIX NLM.      1024 08-23-93   3:16p

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

-----------------------------------------------------------------
DFSRFIX  NLM
============

SYMPTOM

When using Direct File System Read, the time stamp on the file is updated each
time the file is read.

SOLUTION

Apply DFSRFIX  NLM.       925 03-28-94   9:07a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

-----------------------------------------------------------------
DIRSPCFX NLM
============

SYMPTOM

Disk space cannot be accounted for.

CAUSE

The Set parameter only searched one of the mirrored tables for extended
attributes to verify that the limit had been met, which allows the set
parameter to use twice as much space as indicated.  The Table for Extended
Attributes will grow; however, it will never decrease in size.  So, after the
space is allocated for the EA table, it cannot be used for any thing other
than Extended Attributes.

SOLUTION

Apply DIRSPCFX NLM.      1128 02-22-94   4:20p

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.11, 3.12, 4.01

The DIRSPCFX.NLM file is a fix to the set parameter "Maximum Percent of Volume
Used By Directory."  The limits of this set parameter are 5 to 50 percent
default and the setting is 13 percent.

The set parameter "Maximum Percent of Volume Used By Directory" can use double
the disk space set.

Example:

If the Set parameter is 13 percent, the actual space that can be used by
Extended Attributes is 26 percent.


-----------------------------------------------------------------
EADATFIX NLM
============

SYMPTOM

A problem exists with Extended Attributes when performing a drag and drop COPY
of a directory structure from an OS/2 client.  Which would cause the Extended
Attribute for the new Parent Directory to be corrupt.
VREPAIR returned the following error message:

     Error at extended directory entry xxxx
     Invalid Data error
     Invalid Score card error

SOLUTION

Apply EADATFIX NLM.       997 03-28-94   9:08a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.11, 3.12, 4.01

To install the patch, load patchman for the operating system that is running
and the version of EADATFIX.NLM in the same directory.

-----------------------------------------------------------------
EAREPLFX NLM
============

SYMPTOM

The following errors could be seen on a OS/2 Client:

1.   "The Drive ";,is not a valid Drive"
2.   " " " is either read-only or is being used by another program"

These errors would be received when using the drives ICON from the DESKTOP to
view a NetWare volume and most often with a CD-ROM mounted volume.  Sometimes
after receiving these errors, the connection to the File Server would be lost.

SOLUTION

Apply EAREPLFX NLM.      1169 02-22-94   4:23p

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.11, 3.12, 4.01

Also it is suggested to use NetWare Requester for OS/2 v2.10 to help correct
the problem.

-----------------------------------------------------------------
EASCORFX NLM
============

SYMPTOM

A problem exists with Extended Attributes on files that have been deleted. 
When a file with extended attributes was deleted, the Directory Entry was
changed to reflect the deleted state of the file.  The Extended Directory
Entries for the Extended Attributes were not all updated to correctly reflect
this deleted state.

The following error messages would be seen when running VREPAIR:

     Error at extended directory entry XXXX
     Invalid data error
     Invalid score card error

SOLUTION

Apply EASCORFX NLM.      1062 11-09-93  10:59a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

          3.11, 4.01

Run VREPAIR on all volume to correct all Invalid data errors and Invalid score
card errors, then load EASCORFX.NLM.

-----------------------------------------------------------------
EAUNIQFX NLM
============

SYMPTOM

A problem exists with Extended Attributes on files that have been deleted.

When a file with extended attributes was deleted, the extended directory entry
for the file was not updated properly to reflect the deleted status of the
file.

The following error messages would be seen when running VREPAIR:

     -Error at file entry XXXX
     Original Entry - Deleted DOS file entry
     Name: yyyy
     Size: zzzz
     The Extended Attribute / Directory information is Invalid

     Corrected Entry - Deleted DOS file entry
     Name: yyyy
     Size: zzzz

SOLUTION

Apply EAUNIQFX NLM.      1147 11-09-93  11:02a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.11, 4.01

Run VREPAIR on all volume to correct all Invalid data errors and Invalid score
card errors, then load EASCORFX.NLM.

-----------------------------------------------------------------
ELEVFIX  NLM
============

SYMPTOM

A window exist where two identical requests to access the same sector on the
hard disk could get placed in the elevator queue at the same time resulting in
a file server lock up.

SYMPTOM

The file server may possibly hang when a system is in the process of
remirroring and when there is extremely high I/O traffic on the bus.

SOLUTION

Apply ELEVFIX  NLM.      1650 02-22-94   4:24p

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

-----------------------------------------------------------------
EXTENDFX NLM
============

SYMPTOM

The following message appears on the console.


MESSAGE

     User <username> on connection <connectionnumber>
     attempted to extend the length of a file with no
     owner  File Name <filename>

SYMPTOM

At the workstation, a message indicating that the disk is full may be
received.

SOLUTION

Apply EXTENDFX NLM.       986 11-11-93  12:07p

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01


THIS PATCH MUST BE LOADED BEFORE ANY VOLUMES ARE MOUNTED AND CAN BE LOADED
FROM THE STARTUP.NCF.

This patch does not change the ownership of the file but will allow files with
no owner to be extended.  Disk space being used by files with no owner will
not be added to the disk space used by the user that is attempting to extend
the file.  This is not a problem unless disk space usage is being limited for
the specified user.

-----------------------------------------------------------------
GNSOFFFX NLM
============

SYMPTOM

With "reply to get nearest server" set off, the specified server still
responds first to workstations loading the NetWare Requester.

SOLUTION

Apply GNSOFFFX NLM.      1049 02-23-94  11:36a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

The above mentioned set parameter was designed to stop the file server from
responding while still allowing other services on the specified server to
reply.  With NetWare 4, while the file server is not responding, the Directory
service is responding to the workstations allowing them to attach to the
specified server.  On the server that you have the "set reply to get nearest
server = off" parameter, load the GNSOFFFX.NLM patch.

-----------------------------------------------------------------
LOSTSRFX NLM
============

SYMPTOM

When a Cisco router sends a SAP packet whose first SAP entry has the service
type set to 0000 (unknown service), the NetWare 4.01 server ignores all SAPs
contained in that packet.  This will cause the NetWare 4.01 server to accept
any SAP from that packet.  Therefore, NLIST SERVERS /B doesn't show certain
servers.

SOLUTION

Apply LOSTSRFX NLM.       959 03-30-94   1:19p

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

-----------------------------------------------------------------
MEMFRGFX NLM
============

SYMPTOM

on servers that have greater than 80 megabytes of server RAM and that have
large amounts of volume space to mount.
A client was creating directories on the network volume. At about 125,000
directories, the following errors occurred:

At the workstation:

MESSAGE

     SHELL-331-92: Out of dynamic work space during CREATE A
     SUBDIRECTORY Abort, Retry?

At the server console:

MESSAGE

     SERVER-4.0-2335:  Error expanding SERVERNAME/VOLUME
     directory because directory size limit was reached.

TROUBLESHOOTING

After this condition was achieved and the volume was dismounted, it would fail
to mount with an error message at the server console:

MESSAGE

     SERVER-4.00-4.25: Insufficient memory for directory tables.

These errors with lots of available cache are indicators of the segmented
memory problem.

SOLUTION

Apply MEMFRGFX NLM.      2582 03-28-94   9:12a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     4.01

MEMFRGFX.NLM addresses an issue on NetWare where a server would run out of
memory while mounting the volume or when dynamically expanding the directory
entry table.  This MEMFRGFX.NLM patch fixes this problem by providing an
alternate method of registering server memory for NetWare 4.01.

It fixes a condition where the normal auto registration of memory would
represent memory with non-contiguous blocks.  Consequently, only a portion of
memory is available for mounting volumes and growing the directory entry. 
This condition will only manifest itself on servers that have greater than 80
megabytes of server RAM and that have large amounts of volume space to mount.

To install and implement this version of MEMFRGFX.NLM:

1.  Copy MEMFRGFX.NLM to the same directory where SERVER.EXE and the
STARTUP.NCF files reside.

2.  Modify the startup .ncf file and add the set parameter, "set auto register
memory above 16 megabytes=off" as the first line.

3.  After disabling the auto registration of memory and before loading any
other driver or patch, load the MEMFRGFX.NLM patch with the following syntax:

     LOAD MEMFRGFX.NLM <STARTING MEMORY ADDRESS>
     <LENGTH>

The <starting memory address> will always be 1000000 hex (16 MB).  The
<length> in hex can be calculated by taking the total amount of File Server
memory as reported by the hardware memory POST, converting that number to
hexadecimal and then subtracting 1000000 hex therefrom.

For example, if the file server post reports 163840 KB of RAM, the calculation
would be as follows:

     163,840,000 bytes = 9C40000 hex bytes
     9C40000 hex minus 1000000 hex = 8C40000 hex

In this case, the command would be the following:

     LOAD MEMFRGFX.NLM 1000000 8C40000

4.   You can then proceed with the loading of any other STARTUP.NCF commands
as usual.

-----------------------------------------------------------------
MMACCFIX NLM
============

SYMPTOM

The workstation will hang while performing reads from the file server.  High
(100%) utilization at the server console.  By typing "scan for new devices" at
the console prompt, the high utilization drops but will climb back up over
time.

SOLUTION

Apply MMACCFIX NLM.       960 11-09-93  10:10a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

MMACCFIX.NLM fixes this condition by patching the media manager accelerator
module of the NetWare 4.01 operating system code.  This patch is recommended
for general application on all NetWare 4.01 servers.

-----------------------------------------------------------------
PBWANFIX NLM
============

SYMPTOM

WAN links saturated with packets.

SOLUTION

Apply PBWANFIX NLM.      1291 10-18-93  11:39a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

Description of problem addressed by PBWANFIX.NLM.  Due to the nature of packet
burst, it is very easy to saturate WANS with packets that have already been
sent and arrived correctly.

-----------------------------------------------------------------
REALMFIX NLM
============

SYMPTOM

If an error condition occurs such as reaching the end of a tape, an error code
is returned to the calling application.  The error code would be scrambled,
resulting in the wrong error passed to the application.  The result, as far as
the Server (that is ABEND, hang, and so forth) depends on the specific
application.

SYMPTOM

Application requests made to a device driver using the DeviceIOCTL and
DeviceBlockingIOCTL APIs are aborted if NetWare is in the process of switching
to real mode (that is the DOS Mode semaphore is set).  The APIs should instead
delay the execution of the request.

SOLUTION

Apply REALMFIX NLM.      2756 02-08-94   9:37a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

This patch deals with applications that directly control hardware devices
through NetWare (that is Jukeboxes, worms, tapes, and so forth).
The patch applies to applications that use a DAI interface to communicate with
the server's hardware.  Check with the vendor of the application to verify the
use of the DAI interface and apply the patch if necessary.

This patch fixes two DAI emulation bugs:

Fixed the device IOCTL routine to return the driver specified error code
instead of the media manager code.

Fixed the IOCTL routines to postpone the execution of the IOCTL if the
DOSDiskSemaphore is set instead of returning with an error.

-----------------------------------------------------------------
RTCHGFIX NLM
============

SYMPTOM

When packet signing was enabled and a switch over occurs on an NetWare SFT III
server or a router switch over, the workstation would timeout or appear to be
hung.

CAUSE

When the switch over occurs, the packet size would be renegotiated between the
server and the workstation.  The server in would send unsigned packets to the
workstation during the renegotiation process.  The workstation, expecting
signed packets discards all of the packets from the server attempting the
renegotiation.  The workstation would eventually timeout or appear to be hung.

SOLUTION

Apply RTCHGFIX NLM.       952 12-21-93  11:38a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

This patch fixes a problem with packet signing after a switch over occurs on
an NetWare SFT III server or a router switch over (that is networks with
redundant routes).  The key to the patch is that packet signing would have to
be enabled for this problem to happen.

----------------------------------------------------------------
SPXDDFIX NLM
============

SYMPTOM

If the connection had already transitioned into SESSION_TERMINATED when the
retry came in, it was treated as a new connection request.

SYMPTOM

Data was handled incorrectly by an application.

CAUSE

SPX was still acknowledging data packets that arrived after
SPXTerminateConnection was called; therefore, data that arrived after the
application initiated a disconnect by calling SPXTerminateConnection, was
acknowledged and delivered to the application.  Depending on how the
application was written this could give the transmitting side an invalid
picture of the guaranteed delivery of the data by leaving both endpoints with
different information about the state and completeness of the data.

SOLUTION

Apply SPXDDFIX NLM.      1112 03-10-94   9:45a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

This patch fixes the problem with the way SPX handles retried connect
requests.  The patch causes all inbound packets after SPXTerminateConnection
has been called to just be dropped.

Also fixes a problem where SPX was still acknowledging data packets that
arrived after SPXTerminateConnection was called.  This could lead to incorrect
handling of the data by the application, leaving both endpoints with different
information about the state and completeness of the data.

NOTE: This SPX problem is masked by the SPXS.NLM that ships with NMS 2.0 and
SPXS.NLM included in STRTL2.EXE.  The fix for this specific issue is addressed
by SPXDDFIX.NLM.

-----------------------------------------------------------------
SPXFIX2  NLM
============

SYMPTOM

An SPX terminate ack is received on a non-existent session.

CAUSE

This bug is a side effect of SPXFIX2 v2.00 (that is native to NetWare 3.12)
that leaves SPX terminate ack packets in system ECBs rather than copying them
into application ECBs.

SOLUTION

Apply SPXFIX2  NLM.      1023 11-23-93   8:52a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

This patch fixes SPX code in the case where an SPX terminate ack is received
on a non-existent session.  When the terminate ack is received and the session
does not exist, this fix returns the ECB to IPX rather than reposting it to
the application socket.

-----------------------------------------------------------------
SYNCMFIX NLM
============

SYMPTOM

One drive off of one HBA is mirrored to two drives both of which are on the
other HBA.  (A total of three drives mirroring the same data).  The single
drive off of the first HBA is in sync and the other two drives off of the
second HBA are mirrored to the first drive.  The server is downed while the
two secondary mirrored drives are still out of sync, (install NLM shows them
still to be in the mirroring process).

When SERVER.EXE is invoked, INSTALL.NLM shows the primary drive as In Sync and
one of the secondary drives as In Sync and the other as Out Of Sync.  The two
secondary drives are the only ones showing disk activity as if they are
mirroring each other and ignoring the actual in sync primary drive.

SOLUTION

Apply SYNCMFIX NLM.       974 11-09-93  10:50a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.12, 4.01

The problem is resolved by loading the SYNCMFIX.NLM patch.  You must load the
patch manager (PM401.NLM) and the SYNCMFIX.NLM in the startup.ncf before the
disk driver or move the disk driver load statements to the AUTOEXEC.NCF and
have them loading after the patch manager and the SYNCMFIX.NLM patch.

-----------------------------------------------------------------
UNLDIRFX NLM
============

SYMPTOM

ABEND "UnLockDirectoryEntry called with entry that was already unlocked"
happens in INWPurgeTrustee when UnLockDirectoryEntry is called with
TNode->TFileEntryNumber that sometimes gets overwritten by the call to
ImmediateReuseGetDirectoryEntry.

Whenever the directory structure for the file entry isn't in RAM,
ImmediateReuseGetDirectoryEntry reads in a directory block over the top of the
current block and invalidates the TNode pointer.

NOTE: Locking the file entry doesn't guarantee the TNode is locked.

SOLUTION

Apply UNLDIRFX NLM.      1807 04-13-94   9:38a

Solution Specifics:

Versions of this patch will run on the following NetWare operating systems:

     3.11, 3.12, 4.01

Self-Extracting File Name:  401PT2.EXE     Revision:  A

Files Included     Size     Date      Time

\
  401PT2.TXT         (This File)
   PM401.NLM       8113   02-03-94    1:09a
   PM401.TXT       3674   06-08-94   11:53a
 DFSRFIX.NLM        925   03-28-94    9:07a
 ELEVFIX.NLM       1650   02-22-94    4:24p
 SPXFIX2.NLM       1023   11-23-93    8:52a
BCKTTSFX.NLM        932   03-28-94    8:49a
COMPRFIX.NLM       1487   03-28-94    9:03a
COMPVLFX.NLM       1636   12-21-93    9:07a
CRDIRFIX.NLM       1313   02-22-94    4:22p
DAICCFIX.NLM       1031   02-08-94    9:47a
DEVIOFIX.NLM       1024   08-23-93    3:16p
DIRSPCFX.NLM       1128   02-22-94    4:20p
EADATFIX.NLM        997   03-28-94    9:08a
EAREPLFX.NLM       1169   02-22-94    4:23p
EASCORFX.NLM       1062   11-09-93   10:59a
EAUNIQFX.NLM       1147   11-09-93   11:02a
EXTENDFX.NLM        986   11-11-93   12:07p
GNSOFFFX.NLM       1049   02-23-94   11:36a
LOSTSRFX.NLM        959   03-30-94    1:19p
MEMFRGFX.NLM       2582   03-28-94    9:12a
MMACCFIX.NLM        960   11-09-93   10:10a
NCPIDFIX.NLM       1837   01-18-94    4:22p
PBWANFIX.NLM       1291   10-18-93   11:39a
REALMFIX.NLM       2756   02-08-94    9:37a
RTCHGFIX.NLM        952   12-21-93   11:38a
SPXDDFIX.NLM       1112   03-10-94    9:45a
SYNCMFIX.NLM        974   11-09-93   10:50a
UNLDIRFX.NLM       1807   04-13-94    9:38a

Installation Instructions:

See solution specific for specific patch application instructions.

----------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners.  Consult your product manuals for complete trademark
information.
----------------------------------------------------------------

