home *** CD-ROM | disk | FTP | other *** search
- This README file accompanies PATCHMAN.NLM v2.23. The following
- files are included for this revision:
-
- PATCHMAN NLM 9051 4-16-92 11:21a
- PCHMN222 DOC (This file)
-
- This version of PATCHMAN replaces any and all previous versions of
- PATCHMAN. PATCHMAN v2.23 can only be used with NetWare v3.11+ (all
- number-of-user versions). NetWare v3.10a requires PATCHMAN v1.20b.
-
- *** PLEASE NOTE THE TECHNICAL BULLETIN ON THE 3.11 OPERATING SYSTEM
- PATCHES INCLUDED BELOW.
-
-
- 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.
-
-
-
- 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.
- *****************************************************************