NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NetWare 3.12 OS Patches DOCUMENT ID: TID022054 DOCUMENT REVISION: A DATE: 09MAR95 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: 312PT6.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 release 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. ----------------------------------------------------------------- Copy all files from the START directory to the DOS partition. Copy all files from the AUTO directory to SYS: Volume. Edit the STARTUP.NCF & AUTOEXEC.NCF files. There are some sample NCF file that may help the Installation. NOTE: STARTUP.NCF will NOT allow execution of an NCF file from with in it. It is necessary to copy the Contents form the sample START.NCF to your existing STARTUP.NCF. AUTOEXEC.NCF will allow the execution of an NCF file, so simply call the AUTO.NCF file from with in AUTOEXEC.NCF. It may be necessary to edit the sample NCF file to specify correct paths.... ----------------------------------------------------------------- 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 1218 07-15-94 8:26a 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 ----------------------------------------------------------------- BHANDFIX NLM ============ SYMPTOM: SOLUTION: Apply BHANDFIX NLM 972 10-18-94 12:16p 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. BHandFix (Bad Handle Fix) fixes a GPPE when proc InternalReadFile in fileio.386 receives a bad handle and jumps to label ReadInvalidHandle: The code at this label has been modified to not set the RALastReadStartOffset field of the fcb to -1. The label is also jumped to when the TNode field of the fcb is 0. Return from InternalReadFile with error code without trying to set field RALastReadStartOffset in FCB 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 ----------------------------------------------------------------- CTRSTKFX NLM ============ SYMPTOM: Bug in LSLControlStackFilter functions NetWare v3.1x & v4.0x. SOLUTION: Apply CTRSTKFX NLM 972 12-21-94 12:48p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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. Problems found with NLA Requests to turn on Promiscuous Mode while HSL.NLM (Hub Support Layer) is loaded (NLA part of the NMS & RMON stuff) causes the server to hand (NW v3.x & NW v4.0x). Problem due to code in LSL function LSLControlStackFilter, at label , have after testing for entries in DefaultChainTable have which should be the line . Installation Instructions: NCF FILE: STARTUP.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 1076 02-09-94 3:42p 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 ----------------------------------------------------------------- DBLDEBFX NLM ============ SYMPTOM: Getting duplicate characters on some fast machines in debugger SOLUTION: Apply DBLDEBFX NLM 1176 05-26-94 12:52p 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. FIXED the non-interrupt (polled) keyboard handler so that it will check the keyboard controller's status to make sure that a key is really there. This is needed because on really fast machines, with slow keyboard controllers that manually desert the interrupt line, when we loop around and poll the PIC after reading a key, the interrupt line may still be asserted making us think there is another key waiting, thus causing 'double keys'. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- DHANDFX NLM ============ SYMPTOM: The file server will exhibit a GPPE or other abends having to do with corrupt directory handles. This is most notably seen when running Appletalk,NFS gateway, or Groupwise nlms, but can be seen when loading any set of nlms which exceeds the 20 handle limit. CAUSE: It was discovered that directory handles were getting overwritten or reused by some other process before the current process was finished with it. This would result in an ABEND or other corruption. It was found that connection zero (commonly used by nlms at the server) was not properly handling the case where 20 or more handles were required. SOLUTION: Apply DHANDFX NLM 3650 12-23-94 12:04p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, 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. The 3.12 version of this patch incorporates two formerly released patches for 3.12 NetWare which were called, DIRSRCFX.NLM and CRDIRFIX.NLM. DHANDFX.NLM will NOT load concurrently with these patches. If you are running these two patches please remove them prior to loading the DHANDFX.NLM Installation Instructions: NCF FILE: STARTUP.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, 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: 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 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: STARTUP.NCF ----------------------------------------------------------------- EAFLTFIX NLM ============ SYMPTOM: ABEND: Invalid Semaphore passed to kernal Because of the nature of this issue, a multiple type of abends could be possible or seen, including GPPEs. This problem is only visible using debugging tools. It can only be seen in a core memory image or a trace from a sniffer or lanayzler. TROUBLESHOOTING: Apply the patch or fix the client sending the bad packets. CAUSE: A client or clients are sending NCP packet Case 86 with an invalid value for the volume number. This causes NetWare to index a table incorrectly SOLUTION: Apply EAFLTFIX NLM 1309 12-21-94 12:59p 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. Fixed with patch EAFltFix.NLM (EA Filter Fix) which does some packet error checking (For EA Type Packets) to makes sure the client is not sending invalid packets. Installation Instructions: NCF FILE: STARTUP.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: STARTUP.NCF ----------------------------------------------------------------- EASUBFIX NLM ============ SYMPTOM: When copying a long directory with EA's and only have R F rights the server returns 140 error. SOLUTION: Apply EASUBFIX NLM 965 07-26-94 7:44a 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. Login to a 3.12 server that has a name space loaded. Go to a directory that has a long directory in it. Make sure you only have R F rights in the source directory. Then use FILER to copy the subdirectory structure, on the long directories you will get an error. Problem was traced to NWFindFirstEA() returns error code 140 ( No Set Privileges). FIXED a bug OpenEAHandle, were is you only had read rights on a file, you could not read the EA's on that file. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EAWRITFX NLM ============ SYMPTOM: When using an OS/2 file and trying to copy the file from a local drive to a file server with the directory flagged FWC the copy fails. If read rights are added it succeeds. SOLUTION: Apply EAWRITFX NLM 1048 07-26-94 7:48a Change procedure OpenEAHandle to check for WriteExistingFileBit if the user does not have ModifyEntry rights. If the user does have WriteExistingFile rights he is granted Write and Read Privileges. 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. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EAWRNFX NLM ============ SYMPTOM: The server was running out of allocated storage space for extended attributes without warning. SYMPTOM: The user is unable to manage extended attribute storage space in any given NetWare volume. SYMPTOM: There is a lack of extended attribute management functions. SOLUTION: Apply EAWRNFX NLM 4053 07-13-94 4:45p 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. EAWRNFX.NLM addresses issues with the management of EA's or Extended Attributes on a NetWare volume. Using this NLM will allow the user to control the amount of volume space allowed for EA storage on a volume. It will also alert users and the error log as to when space for EA storage is running low. After EAWRNFX is loaded two additional settings are available. To see these settings, type EA STATS at the server console prompt. The following information will be displayed: ----------------------------------------------------------- EA WARNING BROADCAST PERCENT = 85 EA WARNING BROADCAST INTERVAL = 1 min. VOLUME NAME % ALLOWED % USED OF ALLOWED [SYS ] 30 1 [JUMBO ] 30 45 ----------------------------------------------------------- EA WARNING BROADCAST PERCENT = 85 This statement depicts the level at which a warning would be broadcast. When 85 percent of the allotted volume space for EA's is utilized, a warning will be broadcast. To set this amount to 75 percent, you should typed the following at the console prompt or insert it in the AUTOEXEC.NCF file: EA WARNING BROADCAST PERCENT = 75 EA WARNING BROADCAST INTERVAL = 2 min. This statement depicts how often the warning broadcast will be sent to the network. To set this amount to 5 minutes the following would be type at the console prompt or inserted in the AUTOEXEC.NCF file: EA WARNING BROADCAST INTERVAL = 5 % ALLOWED The % ALLOWED statement to the right of the screen depicts the percentage of volume space allowed for EA storage. % USED OF ALLOWED The % USED OF ALLOWED depicts the percentage of the space allocated for EA storage that has been used. Additional information: The % USED OF ALLOWED field depicts a high water mark for EA storage on the volume in question. If, for example, this value hits 90 percent and half of these files are deleted, the value will remain at 90 percent until the volume is purged. After the volume is purged, the value would return to 45 percent. However, it is important to understand that EA's are stored as extended directory entries and after the space has been used for EA storage, it can never be reused for common file storage unless the volume isre-initialized. After EA related data has been purged, that purged area can be reused for EA storage in the future. Installation Instructions: NCF FILE: STARTUP.NCF 1. For this patch to function correctly, a patch by the name of DIRSPCFX.NLM must also be applied. DIRSPCFX.NLM corrects a problem in the directory entry table with extended attribute and directory usage on a NetWare volume. It is explained in detail in its own field test file. 2. For EAWRNFX.NLM to function correctly, all three files must be used! All three files should be copied to the DOS partition from where SERVER.EXE is booted. These files should be loaded from STARTUP.NCF, probably on the last three lines, in the following manner: LOAD PM312.NLM LOAD DIRSPCFX.NLM LOAD EAWRNFX.NLM PERCENT = 30 The PERCENT = 30 parameter can take the place of the SET MAXIMUM PERCENT OF VOLUME SPACE ALLOWED FOR EXTENDED ATTRIBUTES = 30 command that would be commonly found in the AUTOEXEC.NCF file. Setting this parameter in the STARTUP.NCF before the SYS: volume loads allows the SYS: volume to benefit from the setting. The value 30 is an arbitrary setting for this example. ----------------------------------------------------------------- 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 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: STARTUP.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: STARTUP.NCF ----------------------------------------------------------------- GTALLYFX NLM ============ SYMPTOM: Server Abends when out of memory in eavprim.c SOLUTION: Apply GTALLYFX NLM 1490 10-18-94 12:42p Set pointer to NULL when struct is allocated and the check for NULL before calling free. 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: STARTUP.NCF ----------------------------------------------------------------- HFFIX NLM ============ SYMPTOM: The Server will hang if there is data lost after a hotfix. SOLUTION: Apply HFFIX NLM 1054 05-26-94 11:46a 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: STARTUP.NCF ----------------------------------------------------------------- IOHANDFX NLM ============ SYMPTOM: On releasing IO handles, the OS does not clean up the application link field. Do the following steps to reproduce the problem: 1. Load CDROM.NLM on a 3.12 server with a CDROM. 2. CD MOUNT # (to mount the CD). 3. CD CHANGE # ( to mount a different CD). 4. Take the CD out at the prompt and press any key to continue. 5. Unload CDROM.NLM. 6. Load CDROM.NLM. You can repeat steps 5 and 6 after putting a CD back into the device and the CD can no longer be seen until the disk driver is unloaded and loaded again. SOLUTION: Apply IOHANDFX NLM 1070 05-26-94 11:41a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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. Installation Instructions: NCF FILE: STARTUP.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. 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: STARTUP.NCF ----------------------------------------------------------------- IPXSOCK NLM ============ SYMPTOM: Connections with NetWare for SAA server cannot exceed 33. TROUBLESHOOTING: Applications such as Hostprint (from NetWare for SAA) may require more than 100 IPX sockets (which translates to only 33 host connections) on a NetWare 3.11 server. When you attempt to make additional connections beyond 33, the operation will fail. CAUSE: Normally, a 3.11 server has a maximum of 100 IPX sockets. SOLUTION: Apply IPXSOCK NLM 3971 07-20-94 12:05p 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. IPXSOCK.NLM will increase the maximum number of IPX sockets on NetWare 3.11 from 100 to 1024. Installation Instructions: NCF FILE: AUTOEXEC.NCF 1. Copy IPXSOCK.NLM into the same directory as the other NLM files (SYS:SYSTEM or DOS partition). 2. At the server console type LOAD IPXSOCK Where is between 101 - 1024. This patch will not unload unless the number of open IPX sockets is less than or equal to 100. This is because PATCHMAN must re-map the in-use socket to the original 100 entries in the socket table. ----------------------------------------------------------------- LSTECBFX NLM ============ SYMPTOM: Lost ECB's when running endurance tests with packet signing When running endurance tests with packet signing on, the IPX protocol stack will get into a state where ECB's will start to be lost. The problem occurs when two packets arrive at the same time. The second one will be lost. This problem is unique to 3.12. It was a result of some optimization that took place. The problem does not occur in 4.00 or later, nor does it happen in 3.11 with PBURST.NLM loaded. SOLUTION: Apply LSTECBFX NLM 1302 07-26-94 7:51a 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: STARTUP.NCF ----------------------------------------------------------------- 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: STARTUP.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: STARTUP.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. Installation Instructions: NCF FILE: STARTUP.NCF 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. ***************************************************************** 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. ***************************************************************** ----------------------------------------------------------------- READQFIX NLM ============ SYMPTOM: When a Queue is full, the File Server will get into an infinite loop trying to service Queue Management System (QMS) requests. Note that pconsole makes QMS requests for building a list of jobs, inserting and deleting print jobs, as well as inserting and deleting print queues. Symptoms observed when this problem occurs include, but are not limited, to utilization up to 96 %, users loosing connections and Packet Receive Buffers count going high. SOLUTION: Apply READQFIX NLM 1612 08-10-94 4:37p By applying ReadQFix.NLM, the file server can correctly process a QMS request for a queue which is full. Note that if a queue is full prior to loading ReadQFix, the following error message may appear on the console at any time after loading ReadQFix. "WARNING: Error detected in Queue. ID=xxxxxxxx" If this happens the queue with the given ID number should be deleted and recreated. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, 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. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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 ----------------------------------------------------------------- REGOBJFX NLM ============ SYMPTOM: Generic Info Valid bit not set for non-media objects Device, magazine, etc. objects don't set the valid bit in the status field. This causes an Media Manager application to loop forever waiting the in information be become "valid". SOLUTION: Apply REGOBJFX NLM 1035 05-26-94 1:06p 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: STARTUP.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: STARTUP.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 ----------------------------------------------------------------- SERVHOPS NLM ============ SYMPTOM: This nlm is normally used when there is a mixture of 3.11 and SFTIII servers on the same segment and remote booting is done on a specific server. However it can be used in any situation where increased hop count is desired. SOLUTION: Apply SERVHOPS NLM 1891 04-06-94 1:39p 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. load servhops.nlm, then at console prompt type: SERVER HOPS N (WHERE N IS THE NUMBER OF HOPS YOU WANT TO ASSIGN THE SERVER. IT CAN BE 1 TO 15 HOPS.) Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- SIGLOGFX NLM ============ SYMPTOM: NWP_LOGIN when password has expired in bindery corrupts connection SOLUTION: Apply SIGLOGFX NLM 1159 12-21-94 1:06p Solutions Specifics: Servers 4.02 and 3.12 Signature level 1 Client VLMs dated 5-26-94 Signature level 2 Login 4.084 and 4.093 Login SPD 70145 Create user (TEST), assign a password and expire that password but have grace logins available. Login to user DS mode "login server/TEST" When asked to change password, reply N Login to user bindery mode "login server/TEST /B". You will get Abort, Retry, Fail error. All you can do is reply F. Then login gets several 8801 errors, invalid connection. Server gets "Server 4.0-2506 An NCP request with an invalid security signature was received from user TEST.... Possible intruder or network is corrupt." When the API calls vlm with NWP_LOGIN, everything after this fails. From codeview, the vlm request is made, then codeview is exited. The server gets several beeps and error messages then the dos prompt "invalid drive.." is displayed. Login works in this situation if NETX.EXE is used The problem we are seeing is that certain NCP packets do not function properly on the server side with signing turned on. In this case it is a PING FOR NDS packet. During a BINDERY login to a 4.x server after the KEYED LOGIN NCP is sent and returned, a PING is sent with signing turned on. The server does one of two things in response: 1) It will either respond to the ping with no signing, in which case the client will fail the login because signing is required; or 2) it will output intruder alert messages at the console and never respond to the ping. This happens using the 4.x LOGIN.EXE when doing a BINDERY emulation login. Using a 3.x login for BINDERY does not do the ping and therefore succeeds. Installation Instructions: NCF FILE: STARTUP.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 fixes the way that SPX handles the Terminate Acknowledgement packets on sessions that do not exist. Installation Instructions: NCF FILE: AUTOEXEC.NCF ----------------------------------------------------------------- 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 ----------------------------------------------------------------- SYNCTIME NLM ============ SYMPTOM: The file server may gain or loose time, after a operating for a while. CAUSE: The fileserver time is by default taken from the software clock which is subject to lost timer ticks which may cause the server to loose time. SOLUTION: Apply SYMCTIME NLM 1948 05/03/94 5:03p The SYNCTIME.NLM causes the server to update its' time periodically from the hardware clock.. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.11 SFT III, 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. ----------------------------------------------------------------- TRBUFFIX NLM ============ SYMPTOM: Transfer buffer sequence number are returned out of order-causing data corruption FIXED a problem in the elevator-off code where the requests were being serviced LIFO instead of FIFO. SOLUTION: Apply TRBUFFIX NLM 1059 05-26-94 12:57p 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: 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 UNLDIRFX NLM 1971 12-21-94 1:24p 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. Installation Instructions: NCF FILE: STARTUP.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 ----------------------------------------------------------------- WRLENFIX NLM ============ SYMPTOM: WrLenFix.NLM (Write Length Fix) fixes an illegal NETX packet which requests to write over the 4 gig boundary (i.e. start offset = -1, bytes to write = 2). To stop the ABEND we truncate the length of the write just like the VLM's do so there is no wrap condition. SOLUTION: Apply WRLENFIX NLM 1087 12-21-94 1:23p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, 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. Installation Instructions: NCF FILE: STARTUP.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: 312PT6.EXE Revision: A Files Included Size Date Time \ 312PT6.TXT (This File) \AUTO\ AUTO.NCF 345 03-07-95 4:49p SPXFIX2.NLM 1035 11-23-93 9:13a DAICCFIX.NLM 1076 02-09-94 3:42p DBLDEBFX.NLM 1176 05-26-94 12:52p GLOCKFIX.NLM 1080 03-09-94 8:30a REALMFIX.NLM 3207 02-08-94 9:14a RTCHGFIX.NLM 984 12-21-93 11:30a SPXDDFIX.NLM 1148 03-10-94 9:48a SPXNSFIX.NLM 1044 05-26-94 8:45a UNLOADFX.NLM 992 11-11-93 2:32p WSMSGFIX.NLM 1132 12-16-93 10:00a \OTHER\AUTO\ IPXSOCK.NLM 3971 07-20-94 12:05p RTRTIME.NLM 2054 02-23-94 4:19p SERVHOPS.NLM 1891 04-06-94 1:39p SYNCTIME.NLM 1948 05-03-94 5:03p \START\ HFFIX.NLM 1054 05-26-94 11:46a PM312.NLM 9221 03-24-94 11:06a START.NCF 1209 03-07-95 4:47p GNSFIX.NLM 1099 03-28-94 8:47a DHANDFX.NLM 3650 12-23-94 12:04p EAWRNFX.NLM 4053 07-13-94 4:45p ELEVFIX.NLM 1717 04-26-94 9:08a BCKTTSFX.NLM 1218 07-15-94 8:26a BHANDFIX.NLM 972 10-18-94 12:16p CTRSTKFX.NLM 972 12-21-94 12:48p DIRSPCFX.NLM 1212 04-26-94 9:06a EAACCFIX.NLM 970 04-26-94 9:06a EADATFIX.NLM 1181 04-26-94 4:33p EAFLTFIX.NLM 1309 12-21-94 12:59p EAREPLFX.NLM 1182 04-26-94 9:00a EASUBFIX.NLM 965 07-26-94 7:44a EAWRITFX.NLM 1048 07-26-94 7:48a GTALLYFX.NLM 1490 10-18-94 12:42p IOHANDFX.NLM 1070 05-26-94 11:41a IPXRCVFX.NLM 976 04-26-94 9:04a LSLUNBFX.NLM 1035 12-21-94 1:19p LSTECBFX.NLM 1302 07-26-94 7:51a MMACCFIX.NLM 1006 04-26-94 8:54a PBWANFIX.NLM 3028 04-19-94 9:41a READQFIX.NLM 1612 08-10-94 4:37p REGOBJFX.NLM 1035 05-26-94 1:06p RKIELFIX.NLM 1044 05-04-94 2:38p SIGLOGFX.NLM 1159 12-21-94 1:06p SYNCMFIX.NLM 1025 04-26-94 8:58a TRBUFFIX.NLM 1059 05-26-94 12:57p UNLDIRFX.NLM 1971 12-21-94 1:24p WRLENFIX.NLM 1087 12-21-94 1:23p ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ÿ