NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NetWare 4.01 OS Patches DOCUMENT ID: TID021891 DOCUMENT REVISION: A DATE: 13DEC94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: 401PT5.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. ----------------------------------------------------------------- ----------------------------------------------------------------- The change from 401PT4 to 401PT5 is that UNLDIRFX.NLM has been removed due to a potential problem this patch may cause. Versions of this patch prior to 9-13-94 can cause GPPE abends, often during the process of deleting a user. The 9-13-94 or later version of this patch which has corrected the problem is available from the 401ITX.EXE download from the NSD forum. BCKTTSFX NLM ============ SYMPTOM Typically after re-booting 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: Different versions of this patch are available for the following NetWare Operating Systems: V3.11, V3.12, V4.01, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- COMPVLFX NLM ============ SYMPTOM SOLUTION Apply COMPVLFX NLM 1636 12-21-93 9:07a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Fix for CCDSetFile called with invalid file. This occurs after a compressed file (*.exe , *.com, *.bat) is copied to a volume with compression is turned off and then executed Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- CRDIRFIX NLM ============ SYMPTOM The following error is return if an attempt is made to create a directory with an blank character(alt-25) as the last character in the name. "Unable to create directory" SOLUTION Apply CRDIRFIX NLM 1313 02-22-94 4:22p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Fix to allow the addition of a blank Character (alt-255) to the end of a directory name. 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 v3.12 and v4.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 3.11 server. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- DAICCFIX NLM ============ SYMPTOM This patch deals with applications that directly control hardware devices through NetWare (i.e. Jukeboxes, worms, tapes, etc.). 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 (i.e. ABEND, hang, etc.) would depend on the specific application. The patch applies to applications which 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 Apply DAICCFIX NLM 1031 02-08-94 9:47a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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 which applies to devices using DAI emulation. SOLUTION Apply DEVIOFIX NLM 1024 08-23-93 3:16p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- DIRSPCFX NLM ============ SYMPTOM Disk space can not be accounted for. SOLUTION Apply DIRSPCFX NLM 1128 02-22-94 4:20p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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. 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. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. To install the patch, load patchman for the Operating System which is running and the version of EADATFIX.NLM in the same directory. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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" This errors would be received if using the drives ICON from the DESKTOP to view a NetWare volume and most often with a CDRom 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: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Also it is suggested to use NetWare Requester for OS/2 v2.10 to help correct the problem. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Run VREPAIR on all volume to correct all Invalid data errors and Invalid score card errors, then load EASCORFX.NLM. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Run VREPAIR on all volume to correct all Invalid data errors and Invalid score card errors, then load EASCORFX.NLM. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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. The file server may possibly hang when a system is in the process of re-mirroring and when there is extremely high I/O traffic on the bus. SOLUTION Apply ELEVFIX NLM 1650 02-22-94 4:24p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- EXTENDFX NLM ============ SYMPTOM The following message appears on the console. "User on connection attempted to extend the length of a file with no owner File Name ". Also, 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: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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. NOTE: THIS PATCH MUST BE LOADED BEFORE ANY VOLUMES ARE MOUNTED AND CAN BE LOADED FROM THE STARTUP.NCF. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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 "set reply to get nearest server = off" load the GNSOFFFX.NLM patch. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- LOSTSRFX NLM ============ SYMPTOM When a Cisco router send a SAP packet whose first SAP entry has the service type set to 0000 (unknown service) the 4.01 server ignores all SAP's contained in that packet. This will cause the 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: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- MAXECBFX NLM ============ SYMPTOM The set parameter "Maximum Packet Receive Buffers" would traditionally only allow a maximum value of 2000. This caused a limitation in the number of clients a comm server could support. SOLUTION Apply MAXECBFX NLM 1940 06-22-94 9:28a The MAXECBFX.NLM allows the "Maximum Packet Receive Buffers" to be maximum value of 4000. This will increase the number of clients a comm server can support to 1700. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- MEMFRGFX NLM ============ SYMPTOM This MEMFRGFX.NLM provides an alternative method of registering memory for 4.01 NetWare. 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 which have large amounts of volume space to mount. The following errors in conjunction with lots of available cache are indicators of the segmented memory problem. At the workstation- SHELL-331-92: Out of dynamic work space during CREATE A SUBDIRECTORY Abort, Retry? At the server console- SERVER-4.0-2335: Error expanding SERVERNAME/VOLUME directory because directory size limit was reached. Issue/Problem: A client was creating directories on the network volume. At about 125,000 directories, the above errors occurred. Once this condition was achieved and the volume was dismounted, it would fail to mount with an error message at the server console:SERVER-4.00-4.25: Insufficient memory for directory tables SOLUTION Apply MEMFRGFX NLM 2582 03-28-94 9:12a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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 patch fixes this problem by providing an alternate means of registering server memory. Installation Instructions: NCF FILE: STARTUP.NCF 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 The will always be 1000000 hex (16 MB). The 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 163840k bytes 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 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: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. MMACCFIX.NLM fixes this condition by patching the media manager accelerator module of the NetWare 4.01 OS code. This patch is recommended for general application on all 4.01 NetWare servers. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- NCPIDFIX NLM ============ SYMPTOM The IPXRTR.NLM is loaded and protocols are then bound, the IPXRTR.NLM is then unloaded manually. The internal router will then take over and all of the protocols that were bound are lost, causing connections to also be lost. SOLUTION Apply NCPIDFIX NLM 1837 04-05-94 5:17p The NCPIDFIX.NLM allows the protocols to remain bound during the switch over. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- PBWANFIX NLM ============ SYMPTOM WAN links saturated with packets. SOLUTION Apply PBWANFIX NLM 2523 04-19-94 9:44a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- PM401 NLM ============ SYMPTOM SOLUTION Apply PM401 NLM 8113 02-03-94 1:09a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. This README file accompanies PM401.NLM (patch manager for NetWare v4.01). The following files are included for this revision: This version of the patch manager replaces any and all previous versions of the patch manager for NetWare v4.01. PM401.NLM can only be used with NetWare v4.01. PM401.NLM is the Patch Manager which tracks and manages all official patches for NetWare v4.01. Patches for NetWare v4.01 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 " 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 (PM401.NLM) must be loaded before any dynamic or semi-static patches can be loaded. If PM401.NLM is not already loaded, the .NLM will attempt to locate PM401.NLM and, if found, will load it automatically. PM401.NLM only needs to be loaded once; all NLM patches can then be loaded. PM401.NLM cannot be unloaded until all patches that rely on it are first unloaded. ----------------------------------------------------------------- REALMFIX NLM ============ SYMPTOM This patch deals with applications that directly control hardware devices through NetWare (i.e. Jukeboxes, worms, tapes, etc.). 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 (i.e. ABEND, hang, etc.) would depend on the specific application. The patch applies to applications which 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. Application requests made to a device driver using the device IOCTL and DeviceBlockingIOCTL API's are aborted if NetWare is in the process of switching to real mode. Application requests made to a device driver using the DeviceIOCTL and DeviceBlockingIOCTL API's are aborted if NetWare is in the process of switching to real mode (i.e. the DOS Mode semaphore is set). The API's should instead delay the execution of the request. FIXED 2 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. SOLUTION Apply REALMFIX NLM 2756 02-08-94 9:37a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- RTCHGFIX NLM ============ SYMPTOM This patch fixes a problem with packet signing after a switch over occurs on either an SFT III server or a router switch over (i.e. networks with redundant routes). 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 will discard all of the packets from the server attempting the renegotiation. The workstation would eventually timeout or appear to be hung. The key to the patch is that packet signing would have to be enabled or order for this problem to happen. SOLUTION Apply RTCHGFIX NLM 952 12-21-93 11:38a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- SPXDDFIX NLM ============ SYMPTOM This fixes a problem with the way SPX handles retried connect requests. If the connection had already transitioned into SESSION_TERMINATED when the retry came in, it was treated as a new connection request. 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. SOLUTION Apply SPXDDFIX NLM 1112 03-10-94 9:45a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. Before the patch, 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. The patch causes all inbound packets after SPXTerminateConnection has been called to just be dropped. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- SPXFIX2 NLM ============ SYMPTOM Fix 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 re-posting it back to the application socket. SOLUTION Apply SPXFIX2 NLM 1023 11-23-93 8:52a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. This bug is a side effect of SPXFIX2 v2.00 (which is native to NetWare v3.12) that leaves SPX terminate ack packets in system ECB's rather than copying them into application ECB's. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- SPXNSFIX NLM ============ SYMPTOM If the session did not exist, SPX failed to interpret terminate ACKs as system packets. SOLUTION Apply SPXNSFIX NLM 1060 05-26-94 8:29a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. When an application errors out because the session does not exist, SPX posts the system buffer to the socket rather than returning it to the Link Support Layer (LSL). The SPXNSFIX.NLM for NetWare 4.01, 3.12, and 3.11 fixex the way that SPX handles the Terminate Acknowledgement packets on sessions that do not exist. Installation Instructions: NCF File: ----------------------------------------------------------------- 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 3 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: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v3.11 SFT is in SFTITx.EXE. The problem is resolved by loading the SYNCMFIX.NLM patch. You must load the patch manager 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. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- UNLDIRFX NLM ============ SYMPTOM ABEND "UnLockDirectoryEntry called with entry that was already unlocked" happens in INWPurgeTrustee when UnLockDirectoryEntry is called with TNode- >TFileEntryNumber which 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 the current UNLDIRFX.NLM (9-13-94 or later), currently available in the 401ITX.EXE download file on the NSD forum. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- Self-Extracting File Name: 401PT5.EXE Revision: A Files Included Size Date Time \ 401PT5.TXT (This File) PM401.NLM 8113 02-03-94 1:09a 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 MAXECBFX.NLM 1940 06-22-94 9:28a MEMFRGFX.NLM 2582 03-28-94 9:12a MMACCFIX.NLM 960 11-09-93 10:10a NCPIDFIX.NLM 1837 04-05-94 5:17p PBWANFIX.NLM 2523 04-19-94 9:44a REALMFIX.NLM 2756 02-08-94 9:37a RTCHGFIX.NLM 952 12-21-93 11:38a SPXDDFIX.NLM 1112 03-10-94 9:45a SPXNSFIX.NLM 1060 05-26-94 8:29a SPXRTFIX.NLM 1051 06-15-94 7:41a SYNCMFIX.NLM 974 11-09-93 10:50a ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ÿ