NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NetWare 3.12 OS Patches DOCUMENT ID: TID021892 DOCUMENT REVISION: A DATE: 13DEC94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: 312PT5.EXE NOVELL PRODUCT and VERSION: NetWare 3.12 ABSTRACT: This file contains the latest operating system test patches for NetWare 3.12. Included with this prerelease are all patches for all user-versions of NetWare 3.12. The patches included have been system tested by Novell. ----------------------------------------------------------------- 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 312PT4 to 312PT5 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 312ITX.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 985 04-26-94 9:00a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 ----------------------------------------------------------------- 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 1361 04-26-94 9:03a 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 ----------------------------------------------------------------- DIRSPCFX NLM ============ SYMPTOM Disk space can not be accounted for. SOLUTION Apply DIRSPCFX NLM 1212 04-26-94 9:06a 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 can not be used for any thing other than Extended Attributes. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DIRSRCFX NLM ============ SYMPTOM When running out of short term alloc memory, the server ABEND's. SOLUTION Apply DIRSRCFX NLM 1087 05-09-94 11:00a 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. Changed procedure INWDirectorySearch to first look at the code returned from the GetDirectoryHandle call made above before referencing the DirHandle. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- EAACCFIX NLM ============ SYMPTOM The following Error message: SYS0002 Access Denied is received when trying to copy a file with Extended Attributes from a NetWare v3.12 file server if the users only has Read and FileScan rights. SOLUTION Apply EAACCFIX NLM 970 04-26-94 9:06a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 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 ----------------------------------------------------------------- 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 1181 04-26-94 4:33p 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 1182 04-26-94 9:00a 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 ----------------------------------------------------------------- ELEVFIX NLM ============ SYMPTOM A window exists 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 1717 04-26-94 9:08a 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 ----------------------------------------------------------------- GLOCKFIX NLM ============ SYMPTOM NWScanPhysicalLocksByFile fails if more than 23 locks on a file. NWScanPhysicalLocksByFile is an assembly call. It is making the NCP 23 238. The lanalyzer shows that garbage is returned by this NCP when more than 23 locks are placed on a file. SOLUTION Apply GLOCKFIX NLM 1080 03-09-94 8:30a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, 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. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- GNSFIX NLM ============ SYMPTOM This patch fixes a problem found when re-booting and attempting to get a connection to the file server. If all of the connections are in use, (e.g. 20 for the 20-user version, 50 for the 50-user version, etc.), and one of the users re-boots, the user will not be able to log back in to the server. This problem will only occur if there is only one network. If the user is on an internet, a re-connection will be possible. The problem is that once a user re-boots, his connection is not terminated at the server until a time out limit is reached (usually 15 minutes). SOLUTION Apply GNSFIX NLM 1099 03-28-94 8:47a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, 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. This patch corrects the problem by checking the source node address of the incoming packet to the node address of all workstations the server currently thinks it is attached to. If a match is found the server responds to the workstation, thus re-creating a connection in the same slot the workstation had prior to its reboot. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- IPXRCVFX NLM ============ SYMPTOM These patches fix a problem with receiving a GPPE ABEND because of the generation of an NCP request that IPX.386 did not handle correctly, thus causing an invalid fragment count. A problem has been encountered with the NetWare SFT III operating system that is produced by Running ARCServe 4.0 on one of the mirrored NetWare SFT III servers. If ARCServe is backing up a file to the tape and the secondary server restarts for any reason, upon re-synchronizing the memory the operating system will ABEND with a General Protection Processor Exception (GPPE) error. This error only occurs if a file is being copied to the tape at the time. If ARCServe is loaded but not in the process of copying a file to tape, then the problem is not apparent. CAUSE The problem is that an NCP request is generated that IPX.386 did not handle correctly, causing an invalid fragment count that would bring down the primary server. Because the primary server is being re-mirrored to the secondary server, the secondary server dies as well. SOLUTION Apply IPXRCVFX NLM 976 04-26-94 9:04a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, 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. Installation Instructions: NCF FILE: MSAUTO.NCF, IOAUTO.NCF The patch needs to be loaded in both the MSEngine and IOEngine. 1. Copy the IIPXRCFX.NLM and PM311IO.NLM files to the NetWare boot directory. 2. Copy the IPXRCVFX.NLM and PATCHMAN.NLM files to the SYS:SYSTEM directory. 3. Edit the IOSTART.NCF file to load the PM311IO.NLM and IIPXRCFX.NLM files. 4. Edit the MSSTART.NCF file to load PATCHMAN.NLM and IPXRCVFX.NLM files. ----------------------------------------------------------------- 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 1006 04-26-94 8:54a 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 ----------------------------------------------------------------- PBWANFIX NLM ============ SYMPTOM WAN links saturated with packets. SOLUTION Apply PBWANFIX NLM 3028 04-19-94 9:41a 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 ----------------------------------------------------------------- PM312 NLM ============ SYMPTOM SOLUTION Apply PM312 NLM 9221 03-24-94 11:06a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 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 PM312.NLM. The following files are included for this revision: PM312.NLM replaces any and all previous versions of PM312.NLM. PM312.NLM is the Patch Manager which tracks and manages all official patches for NetWare 386 v3.12. Patches for NetWare 386 v3.12 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. To install PM312.NLM, log into the server as supervisor or supervisor equivalent and copy PM312.NLM into the SYS:SYSTEM subdirectory. The Patch Manager (PM312.NLM) must be loaded before any dynamic or semi-static patches can be loaded. If PM312 is not already loaded, the .NLM will attempt to locate PM312 and, if found, will load it automatically. PM312 only needs to be loaded once; all NLM patches can then be loaded. PM312 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 3207 02-08-94 9:14a 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 ----------------------------------------------------------------- RKIELFIX NLM ============ SYMPTOM Message Correction for the following ABEND Message: "Richard Kiel memorial ABEND #27" SOLUTION Apply RKIELFIX NLM 1044 05-04-94 2:38p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 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 new ABEND message is "Invalid entry in message list.". In the OS there is a process that checks the consistency of the message list. When this list is found to be invalid the OS will return this ABEND message. Follow the Guidelines for troubleshooting in the System Messages Manual Appendix "A". 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 984 12-21-93 11:30a 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 ----------------------------------------------------------------- RTRTIME NLM ============ SYMPTOM The speed of the network link is slow enough to require increasing timeout values to more than the default value. SOLUTION Apply RTRTIME NLM 2054 02-23-94 4:19p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12 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 provides a new server console command "ROUTER TIMEOUT" which adjusts the RIP and SAP information timeout value. This patch would be used on a network where the speed of the network link is slow enough to require increasing timeout values to more than the default value. The default RIP/SAP timeout value is 4 minutes, which means that the server router will keep Server or Network information for 4 minutes without that information being updated. If the server does not get updated RIP/SAP information within the time specified by the timeout value, the RIP/SAP information is removed from the server's tables. This new console command allows the router timeout value to be changed in the range of 4 to 255 minutes. SYNTAX: ROUTER TIMEOUT 100 This command would change the timeout default from 4 to 100 minutes. RTRTIME.NLM is intended for 386 v3.12 and is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. RTRTIME.NLM requires the latest version of PATCHMAN.NLM in order to load. 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 1148 03-10-94 9:48a 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 1035 11-23-93 9:13a 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 1044 05-26-94 8: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. 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 1025 04-26-94 8:58a 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 312ITX.EXE download file on the NSD forum. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- UNLOADFX NLM ============ SYMPTOM NLMs dynamically importing can ABEND if not unloaded in same order. The OS needs a patch to check for a NULL pointer on unload. SOLUTION Apply UNLOADFX NLM 992 11-11-93 2:32p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 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 ----------------------------------------------------------------- WSMSGFIX NLM ============ SYMPTOM This patch fixes a problem with WS's when sending double byte broadcast messages. The double byte characters would get cut in half. To reproduce the problem: 1) Login from 2 workstations. 2) From one of the workstation send an double-byte message which is longer than 55 bytes to the other workstation. send "XXXXXXXXX..........." to STATION_ID XXXXXXXXXX.... is a double byte message longer than 55 bytes. 3) At the recipient workstation press Ctrl and ENTER key to clear the first part of the message. 4) The second part of the message appears on the recipient, but the message is collapsed. This is not a utility problem, but rather a server problem. When the message is too long to be displayed on the screen, the server divides the message without checking to see whether-or-not the character is double-byte. If the division takes place on the second half of a double-byte character, the characters displayed are changed. Double-byte characters must not be split. SOLUTION Apply WSMSGFIX NLM 1132 12-16-93 10:00a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 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 ----------------------------------------------------------------- Self-Extracting File Name: 312PT5.EXE Revision: A Files Included Size Date Time \ 312PT5.TXT (This File) PM312.NLM 9221 03-24-94 11:06a GNSFIX.NLM 1099 03-28-94 8:47a ELEVFIX.NLM 1717 04-26-94 9:08a RTRTIME.NLM 2054 02-23-94 4:19p SPXFIX2.NLM 1035 11-23-93 9:13a BCKTTSFX.NLM 985 04-26-94 9:00a CRDIRFIX.NLM 1361 04-26-94 9:03a DIRSPCFX.NLM 1212 04-26-94 9:06a DIRSRCFX.NLM 1087 05-09-94 11:00a EAACCFIX.NLM 970 04-26-94 9:06a EADATFIX.NLM 1181 04-26-94 4:33p EAREPLFX.NLM 1182 04-26-94 9:00a GLOCKFIX.NLM 1080 03-09-94 8:30a IPXRCVFX.NLM 976 04-26-94 9:04a MASTERTD.TXT 1370 08-17-94 3:14p MMACCFIX.NLM 1006 04-26-94 8:54a PBWANFIX.NLM 3028 04-19-94 9:41a REALMFIX.NLM 3207 02-08-94 9:14a RKIELFIX.NLM 1044 05-04-94 2:38p RTCHGFIX.NLM 984 12-21-93 11:30a SPXDDFIX.NLM 1148 03-10-94 9:48a SPXNSFIX.NLM 1044 05-26-94 8:45a SYNCMFIX.NLM 1025 04-26-94 8:58a UNLOADFX.NLM 992 11-11-93 2:32p WSMSGFIX.NLM 1132 12-16-93 10:00a ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ÿ