OSPATCH.TXT         This is the README for the UPDATE OS Patches
                              Installation and Usage Instructions
*********************************************************************************
File Listing

HTFXFX    NLM                 1036                05-15-92
FATFIX    NLM                 3357                04-23-92
NCOMFIX   NLM                 2109                12-14-92
PATCHMAN  NLM                 9632                02-04-93
VREPAIR   NLM                 88941               09-10-92
DUPFIX    NLM                 1513                09-16-92

*********************************************************************************
1. 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. PATCHMAN.NLM is required when loading the dynamic patches (nlms).

3. Each of the patches included in this release is listed below.

4. Also included below is a brief discussion of the patch concept 
   and installation instructions.

5. Note that specific instructions are given for the use of 
   FATFIX.NLM below the description of that patch.

**************************************************************************
OS Patch descriptions: (files are dynamic patches)

HTFXFX   NLM      
1036 05-15-92   9:36a         Corrects a problem when using disk block 
                              sizes larger than 4K and cache buffer sizes 
                              larger than 4K.  If a block was read from
                              the redirection area while copying a file 
                              in the above circumstance, it could cause 
                              the destination block to become corrupted.

FATFIX   NLM     
 3357  4-23-92 12:53p         This patch fixes a problem with TurboFAT 
                              and FAT corruption in general, when multiple 
                              workstations randomly access large database 
                              files.  (The min. size of a TurboFat database
                              file is, using a default 4k block size and 64
                              blocks as the TurboFat, 64 * 4k = 256k.  If
                              you have set up a different block size
                              substitute that number.)

DUPFIX   NLM
1513 09-16-92  10:22a

                              This patch fixes a problem in which a certain
                              sequence of events would cause duplexed drives
                              to report all mirrored drives were in sync
                              after a hardware failure, yet they were not.
                              DUPFIX.NLM must be loaded in memory at the 
                              time a hardware error occurs with the disk
                              drive.


********* IMPORTANT SPECIFIC INSTRUCTIONS FOR FATFIX.NLM *********

          It is important to note that the latest version of
          VREPAIR.NLM should be run before implementing this patch.
            (Use the Vrepair.nlm that is included with this zip file.)
          FATFIX.NLM will prevent corruption of the FAT and TURBOFAT,
          but VREPAIR is required to correct previous corruption.
            The steps below should guide you through using FATFIX.NLM.

     3.   In order to use this patch, first add the following two
          lines to your AUTOEXEC.NCF file after the assignment of
          the "IPX INTERNAL NET" number (See page 150 of the
          NetWare v3.11 "Installation" manual for an example of
          this statement):

          LOAD PATCHMAN
          LOAD FATFIX

          It is important that these lines are added immediately
          after the assignment of the internal network number.  After 
          editing, be sure to save the file.
     2.   After editing the AUTOEXEC.NCF file do the following
          things:

          2a. LOAD VREPAIR at the console.
          2b. Dismount the volumes.
          2c. Run VREPAIR on all volumes until there are no further 
              errors reported (This make take one or more         
              attempts).
          2d. Down the server.
          2e. Bring the server back up with the modified     
          AUTOEXEC.NCF file.

FULL README FOR VREPAIR V2.18 09-10-92

********* NOTE *****************************************************
 This version of VREPAIR supersedes all 3.1X versions of VREPAIR
********************************************************************

Problems Addressed:
This version of VREPAIR checks for collisions in such a way that 
speed is significantly increased. Also, a problem has been fixed in 
the read ahead code that could cause a wrong value to be passed to 
the comparison algorithm if the read ahead had not completed one 
request before a second request is passed in.

This version of VREPAIR WILL ALLOW YOU TO PURGE DELETED FILES FROM
THE DRIVE.  The default option under this new version is to retain
all deleted files.  However, if you wish to purge the deleted files
from the disk, choose "SET VREPAIR OPTIONS" from the VREPAIR main
menu.  You will then be shown the default options at the top of the
screen of which one will be "Retain Deleted Files".  To change this
default, simply choose Option 4, "Purge All Deleted Files".

WARNING!!!!!  Be aware that after VREPAIR is run with this option all
"SALVAGEABLE" files will be gone. 

This version of VREPAIR enhances the functionality to support correction
of some errors that in the past, vrepair reported as unrepairable.  These
are many of the directory FAT errors.  This version of VREPAIR also fixes
a problem checking extended attributes.

To INSTALL this version of VREPAIR.NLM:
 
     1)    Bring up the file server without attempting to mount the
           bad volume.

     2)    Using the diskette that has this version of VREPAIR on
           it type, at the console prompt, LOAD A:VREPAIR.

                    NOTE: IF YOU ARE USING THIS VERSION OF VREPAIR ON 
                    A NETWARE 386 V3.10 SERVER, YOU MUST LOAD VRSHIM.NLM 
                    BEFORE LOADING VREPAIR.NLM.


You can load VREPAIR from the network drive or a C partition,
however, it is recommended that this VREPAIR be loaded from the A drive 
so as not to confuse it with the standard VREPAIR already loaded on the 
system.

****Note: The problems you have encountered that required the use of 
VREPAIR may have been caused by hard drive and/or disk controller 
problems and the necessary steps should be taken to trouble shoot the 
system.

****************************************************************************

NCOMFIX NLM
2109 12-14-92   8:00a	NComFix.NLM fixes the Abends "Resource tag
			link error detected in NCompleteRequest"
			and "Invalid disk request passed to
			ReturnDiskRequest".

****************************************************************************

README for PATCHMAN.NLM v2.30.

This version of PATCHMAN replaces any and all previous versions of
PATCHMAN. PATCHMAN v2.30 can only be used with NetWare v3.11+ (all
number-of-user versions). NetWare v3.10a requires PATCHMAN v1.20b.

PATCHMAN.NLM is the Patch Manager for which tracks and manages all
official patches for NetWare 386 v3.10+.

Patches for NetWare 386 v3.10+ consist of three types: 

     DYNAMIC -- Dynamic patches are implemented as .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 -- 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.  

     STATIC -- A static patch is a DOS executable program that
     modifies the SERVER.EXE file.  This type of patch is applied
     once and its effects are permanent.  It is suggested that a
     backup of the original SERVER.EXE file be made before applying
     a static patch.  (In other words, do not patch the SERVER.EXE
     on your original distribution diskette!)

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 <patch>" be placed in the file server's AUTOEXEC.NCF
file to ensure that the patch is always in effect as soon as the
server is brought up.

In order to see which patches are currently loaded on the system,
type "PATCHES" at the file server command line.  The patches will
then be grouped and displayed according to their type (i.e. -
STATIC, SEMI-STATIC, or DYNAMIC).  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 <patch>.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. 

DYNAMIC PATCH INSTALLATION AND INFORMATION:
*************************************************************************

Each of the dynamic patches listed above are intended for 386 v.3.11.
The dynamic patches are loaded at the file server console as NetWare
Loadable Modules and require PATCHMAN.NLM v2.20 or later in order to load.

It is recommended that the command "LOAD <patch name>" 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 <patch name>" for each patch you wish
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 six 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.

6)   All NetWare v3.11 patches, with the latest PATCHMAN.NLM, are
     zipped into the file 311PTx.ZIP (where x was 1 at the time
     this bulletin was released) and this file will be updated with
     a successively higher value of x as v3.11 patches and
     PATCHMAN.NLM are updated.

***************************************************************** 
                    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.
*****************************************************************