NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NetWare 4.01 OS Patches DOCUMENT ID: TID022070 DOCUMENT REVISION: A DATE: 28MAR95 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: 401PT6.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 release are all patches for all user-versions of NetWare 4.01. 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 1157 07-15-94 8:31a 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. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- COMCLSFX NLM ============ SYMPTOM: Copying compressed files from Server A to Server B using NCOPY /R or NCOPY /R/U leads to server reboot. SOLUTION: Apply COMCLSFX NLM 911 07-26-94 8:28a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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. If a user uses NCOPY /R or NCOPY /R /U to move a compressed file from a NetWare 4.x server to another NetWare 4.x server, and then at some future date that file is opened and accessed from either a client or the OS at the target server; that file server will reboot. This was caused by compression using a NoSleep WorkToDo that, when executed, slept on disk IO's. This caused the WorkerThreadAvailList to be NULL and the machine to ABEND with a page fault if the machine was under heavy load and all server processes were busy. This condition was caused by ArcServe backing up a file server with several compressed files. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- COMCORFX NLM ============ SYMPTOM: Accessing corrupt compressed files causes server abend, reset, or congestion SOLUTION: Apply COMCORFX NLM 1563 07-26-94 7:46a 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: 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: STARTUP.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: STARTUP.NCF ----------------------------------------------------------------- COMRAFIX NLM ============ SYMPTOM: Accessing corrupt compressed files causes server ABEND, reset, or congestion SOLUTION: Apply COMRAFIX NLM 1066 07-26-94 8:11a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 ----------------------------------------------------------------- COMRESFX NLM ============ SYMPTOM: Restored files are immediately compressed even though file/directory not flagged as compressed. From either ArcServe 5.01 or FileSafe (workstation based restore -- NetWare aware) if files are restored to a 4.01 volume that has compression enabled on the volume causes the server to immediately compress the files. Neither the files nor the directory are flagged for immediate compress. This causes a delay during restore since the server tries to compress every file written to the volume. Not within Daily Check Start Hour to Daily Check Stop Hour window. Only work around is to SET ENABLE FILE COMPRESSION=OFF. SOLUTION: Apply COMRESFX NLM 925 05-26-94 9:58a 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. FIXED INWModifyDirectoryEntry so that it does not try to immediately compress a file when it's last updated time meets the compression criteria, this allows a restore session to restore files without compression bringing the server to its knees. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- COMSEQFX NLM ============ SYMPTOM: The customer restored a backup. One particular file, when opened would cause the server to ABEND when it was opened. The restored file was sparse, and had been backed up from a volume with a smaller allocation size. SOLUTION: Apply COMSEQFX NLM 1038 05-09-94 9:29a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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. FIXED decompression problem. If a sparse file was created on a volume with block size x and then copied compressed to a volume of block size y and x < y then decompress build file would build an invalid fat chain causing a later non-sequential IO request during decompression to ABEND. 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 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: STARTUP.NCF ----------------------------------------------------------------- CTRSTKFX NLM ============ SYMPTOM: Bug in LSLControlStackFilter functions NetWare v3.1x & v4.0x. SOLUTION: Apply CTRSTKFX NLM 923 12-21-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. 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 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 ----------------------------------------------------------------- DBLDEBFX NLM ============ SYMPTOM: Getting duplicate characters on some fast machines in debugger SOLUTION: Apply DBLDEBFX NLM 1128 05-26-94 10:54a 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: STARTUP.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: STARTUP.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: STARTUP.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 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 1038 05-09-94 10:46a 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: 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: 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 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: STARTUP.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: 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 925 07-26-94 7:42a 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 ----------------------------------------------------------------- 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: 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 2035 11-11-93 2:08p 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-initializedd. 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 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: STARTUP.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: STARTUP.NCF ----------------------------------------------------------------- HFFIX NLM ============ SYMPTOM: The Server will hang if there is data lost after a hotfix. SOLUTION: Apply HFFIX NLM 1002 05-26-94 11:17a 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 ----------------------------------------------------------------- IMPORTFX NLM ============ SYMPTOM: ImportPublicSymbol uses lots of memory When NWDSCreateContext(CLIB.NLM) is called, it calls NWDSGetDefaultNameContext(CLIB.NLM) which then calls ImportPublicSymbol to resolve the address of DSGetBinderyEmulatorContext.(DS.NLM). If the call is made many times, the server runs out of memory. After some investigation, it has been found that each time a symbol is imported, that symbol is entered into the NLM's dependency list irrespective of whether it has already been imported or not. Every time the symbol is imported, memory is re-allocated so as to accommodate the newly imported symbol. The garbage collection routine also does not kick in immediately to use the large amount of free memory available. SOLUTION: Apply IMPORTFX NLM 1016 05-26-94 11:21a 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. FIXED a bug in ImportPublicSymbol where it was not properly detecting the case where an NLM is dynamically importing a symbol they have already imported; this becomes a problem when they do it over and over again causing the table that tracks NLM symbol dependencies to grow unnecessarily. It also got the import counts out of synch. 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 1021 05-26-94 9:29a 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 ----------------------------------------------------------------- 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 ----------------------------------------------------------------- LSLPIDFX NLM ============ SYMPTOM: RCONSOLE not returning list of servers because OS isn't properly handling SPX Diagnostic request SOLUTION: Apply LSLPIDFX NLM 1090 09-16-94 9:10a 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. RConsole from NetWare 4.01 retrieves RConsole servers through an SPX diagnostic request (return all known servers). There is a check for SpxSendEcb->status to determine if status is ok. If the status is not ok the routine will return and not process the diagnostic request. Appearently, SPX was designed to work in this manner, since processing the diagnostic request under certain conditions could cause a server abend. Once a server determines that the SpxSendEcb ->status is not OK, the request is not processed. However, SpxSendEcb should be reset back to allow processing of the next diagnostic SPX packet. End result -- empty list in RConsole. I have more information. To create this problem, run test in isolated environment. Use one NetWare 4.01 server and one client. On the server side, load remote and rspx. On the client side, run ipxodi and vlm. Issue rconsole and make sure client can see the rconsole server. Exit from the rconsole.exe. Set a break point on address f80a36b7 which is the diagnostic data send ESR (SpxSendESR) and type go to return to NetWare. Issue rconsole and select SPX. The break point should get hit. Reboot the client machine. Issue a go on the server. From now on, rconsole will always return an empty rconsole server list because of the reason Gary mentioned in the above. It appears the SPXSENDECB status flag never gets reset. Installation Instructions: NCF FILE: STARTUP.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 ----------------------------------------------------------------- MEMALLFX NLM ============ SYMPTOM: "Short term memory allocator out of memory" Customer sees these messages frequently on his server. Usually happens during heavy traffic times. Typically happens once a day but may skip a day occasionally. Problem seems to stop when users log out and/or files are closed. Performance at the WS's during the times this message is occurring is extremely slow, may lose connection. The server is a Netframe with 128M of ram, diagnostic NLM's have shown that there is plenty of contiguous, clean memory available at the time the request for memory is being made but fails. Drivers for NIC and HBA are Netframe type. NFS has been removed from the server in attempt to isolate the problem but no help. SOLUTION: Apply MEMALLFX NLM 1330 12-21-94 11:15a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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. Implemented patch to AllocateMappedMemory() to not cause the guard pages to be allocated and to also jump to the physical cache pool to allocate RAM if the other areas were depleted. Installation Instructions: NCF FILE: STARTUP.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: STARTUP.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: STARTUP.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: STARTUP.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. ***************************************************************** 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. ***************************************************************** 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 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 ----------------------------------------------------------------- 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 984 05-26-94 11:29a 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 ----------------------------------------------------------------- REISRFIX NLM ============ SYMPTOM: After installing the product update for 4.01 Proliant 2000 Pentium ABEND. "Stack overflow detected by kernal" SOLUTION: Apply REISRFIX NLM 1227 07-26-94 7:50a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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. The latest change to their 4.01 servers was product update for 4.01 and after applying the patches the servers have randomly been going down, when one server went down other sent in image on all three machines. In 4.01 OS file IPXPROTO.386 procedure SendPacket() interrupts are enabled at line 2304. This is causing a stack overflow problem whenever the servers receives a large number of type 20 (NETBIOS BROADCAST) packets. The patch ReISRFix.NLM patches the code by pushing the flags on entrance before the CLI is executed and then popping the flags on exit instead of re-enabling interrupts with an STI. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- RELLOGFX NLM ============ SYMPTOM: TTSEndTrans() broke with NETX; works with VLMS SOLUTION: Apply RELLOGFX NLM 1018 07-26-94 7:37a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 ----------------------------------------------------------------- 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 ----------------------------------------------------------------- SALFILFX NLM ============ SYMPTOM: Directory entries remained locked when error occurs in salvaging SOLUTION: Apply SALFILFX NLM 1098 12-21-94 11:45a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 causes connections to lock up that are doing salvaging of deleted files. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SERCHKFX NLM ============ SYMPTOM: A Third party company has a NLM that can take over when a server is down, and continue to provide services for the downed server. The check for the socket number causes their licensing to detect a duplicate server. It is not really necessary to check, when the socket number will be forced. SOLUTION: Apply SERCHKFX NLM 1013 05-09-94 10:39a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 ----------------------------------------------------------------- SERNUMFX NLM ============ SYMPTOM: Serial number appears reverse order, byte swapped from the S/N on diskette or server console. SOLUTION: Apply SERNUMFX NLM 944 05-26-94 11:32a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 ----------------------------------------------------------------- SIGLOGFX NLM ============ SYMPTOM: NWP_LOGIN when password has expired in bindery corrupts connection SOLUTION: Apply SIGLOGFX NLM 1011 12-21-94 11:51a 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 AnNCP 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 the login beacuse signibg 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 therfore 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 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: STARTUP.NCF ----------------------------------------------------------------- SPXDIAFX NLM ============ SYMPTOM: RConsole from NetWare 4.01 retrieves RConsole servers through an SPX diagnostic request (return all known servers). In the routine SpxSeqPackRXESR there is a check for SpxSendEcb->status to determine if status is ok. If the status is not ok the routine will return and not process the diagnostic request. SPX was designed to work in this manner, since processing the diagnostic request under certain conditions could cause a server abend. Once a server determines that the SpxSendEcb ->status is not OK, the request is not processed. However, SpxSendEcb should be reset back to allow processing of the next diagnostic SPX packet. SOLUTION: Apply SPXDIAFX NLM 989 05-09-94 8:51a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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 ----------------------------------------------------------------- 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: 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 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 ----------------------------------------------------------------- TRBUFFIX NLM ============ SYMPTOM: Transfer buffer sequence number are returned out of order-causing data coruption FIXED a problem in the elevator-off code where the requests were being serviced LIFO instead of FIFO. SOLUTION: Apply TRBUFFIX NLM 998 05-26-94 10: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. 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 1805 12-21-94 11:57a 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 ----------------------------------------------------------------- Self-Extracting File Name: 401PT6.EXE Revision: A Files Included Size Date Time \ 401PT6.TXT (This File) \AUTO\ AUTO.NCF 320 03-22-95 3:18p SPXFIX2.NLM 1023 11-23-93 8:52a DAICCFIX.NLM 1031 02-08-94 9:47a LOSTSRFX.NLM 959 03-30-94 1:19p MAXECBFX.NLM 1940 06-22-94 9:28a REALMFIX.NLM 2756 02-08-94 9:37a RTCHGFIX.NLM 952 12-21-93 11:38a SPXNSFIX.NLM 1060 05-26-94 8:29a SPXRTFIX.NLM 1051 06-15-94 7:41a \OTHER\AUTO\ EAWRNFX.NLM 2035 11-11-93 2:08p \OTHER\START\ MEMFRGFX.NLM 2582 03-28-94 9:12a \START\ HFFIX.NLM 1002 05-26-94 11:17a PM401.NLM 8113 02-03-94 1:09a START.NCF 1697 03-22-95 3:15p DFSRFIX.NLM 925 03-28-94 9:07a ELEVFIX.NLM 1650 02-22-94 4:24p BCKTTSFX.NLM 1157 07-15-94 8:31a COMCLSFX.NLM 911 07-26-94 8:28a COMCORFX.NLM 1563 07-26-94 7:46a COMPRFIX.NLM 1487 03-28-94 9:03a COMPVLFX.NLM 1636 12-21-93 9:07a COMRAFIX.NLM 1066 07-26-94 8:11a COMRESFX.NLM 925 05-26-94 9:58a COMSEQFX.NLM 1038 05-09-94 9:29a CRDIRFIX.NLM 1313 02-22-94 4:22p CTRSTKFX.NLM 923 12-21-94 11:41a DBLDEBFX.NLM 1128 05-26-94 10:54a DEVIOFIX.NLM 1024 08-23-93 3:16p DIRSPCFX.NLM 1128 02-22-94 4:20p DIRSRCFX.NLM 1038 05-09-94 10:46a EADATFIX.NLM 997 03-28-94 9:08a EAREPLFX.NLM 1169 02-22-94 4:23p EASCORFX.NLM 1062 11-09-93 10:59a EASUBFIX.NLM 925 07-26-94 7:42a EAUNIQFX.NLM 1147 11-09-93 11:02a EXTENDFX.NLM 986 11-11-93 12:07p GNSOFFFX.NLM 1049 02-23-94 11:36a IMPORTFX.NLM 1016 05-26-94 11:21a IOHANDFX.NLM 1021 05-26-94 9:29a LSLPIDFX.NLM 1090 09-16-94 9:10a MEMALLFX.NLM 1330 12-21-94 11:15a MMACCFIX.NLM 960 11-09-93 10:10a NCPIDFIX.NLM 1837 04-05-94 5:17p PBWANFIX.NLM 2523 04-19-94 9:44a REGOBJFX.NLM 984 05-26-94 11:29a REISRFIX.NLM 1227 07-26-94 7:50a RELLOGFX.NLM 1018 07-26-94 7:37a SALFILFX.NLM 1098 12-21-94 11:45a SERCHKFX.NLM 1013 05-09-94 10:39a SERNUMFX.NLM 944 05-26-94 11:32a SIGLOGFX.NLM 1011 12-21-94 11:51a SPXDDFIX.NLM 1112 03-10-94 9:45a SPXDIAFX.NLM 989 05-09-94 8:51a SYNCMFIX.NLM 974 11-09-93 10:50a TRBUFFIX.NLM 998 05-26-94 10:41a UNLDIRFX.NLM 1805 12-21-94 11:57a ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ÿ