NOVELL TECHNICAL INFORMATION DOCUMENT ABSTRACT: 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 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. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ----------------------------------------------------------------- ADDSRVFX NLM ============ SYMPTOM: There are significant problems encountered with concurrent UNIX/NetWare access to files and directories. This patch will solve the following problems: 1) NetWare deciding to delete the UNIX file when it syncs its file system. 2) Various places where function return codes are ignored and bad data is used in subsequent code. SOLUTION: Apply ADDSRVFX NLM 1,341 12-18-95 1:13p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- ALERTFIX NLM ============ SYMPTOM: Looping process when the SYS$LOG.ERR file is being read into cache and another error is generated. There is an error which needs to loged to the SYS$LOG.ERR file. When the log file is pre-read into cache another error such as a hardware error is given when trying to pre-read the log file. This error is posted to write to the log file and the looping situation continues. SOLUTION: Apply ALERTFIX NLM 1,964 12-18-95 1:53p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- ASNCRDFX NLM ============ SYMPTOM: Problems with asynchronous reads. SOLUTION: Apply ASNCRDFX NLM 1,521 12-18-95 2:12p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. ASNCRDFX.NLM fixes a problem that may occur often when multiple threads do asynchronous reads. It is possible for a thread to read data that was written by another thread. This problem has been known to occur with the BTRIEVE.NLM application if a Btrieve data file page size is not 512, 1024, 2048 or 4096 bytes. If the page size is not one of these sizes, the data file may become corrupt. This updated version will now work with BNETX. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- AUDITFIX NLM ============ SYMPTOM: Auditing doesn't return the trustee name in Grant Trustee or Remove Trustee functions. SOLUTION: Apply AUDITFIX NLM 1,049 04-17-95 10:59a 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. A problem exists when either granting or revoking trustee rights, Auditcon creates a report of these events. When the Trustee name is retrieved for the Auditcon report, there is no Trustee name, it is blank. The events with the problems are event 19 (Grant Trustee) and event 43 (Remove Trustee). It has been determined that the call to the DS structure function MapObjectIDToNameAndType, should call DS structure function MapObjectIDToLongName. This change was made since the original call would only work in a Bindery Context while the later call works in all instances (DS and Bindery). Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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 1,648 07-15-94 8:18a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- BIGRFIX NLM ============ SYMPTOM: SOLUTION: Apply BIGRFIX NLM 1,190 12-18-95 2:25p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch allows the OS to prevent "read" requests larger than 512K from overrunning the stack. This problem has been known to occur when loading large NLM's. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- CLPHFIX NLM ============ SYMPTOM: ABEND:"ClearPhantom called with not primary directory number". SOLUTION: Apply CLPHFIX NLM 1,238 12-18-95 3:10p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DESLOTFX NLM ============ SYMPTOM: SOLUTION: Apply DESLOTFX NLM 1,144 04-10-95 10:10a Wrote patch DeSlotFx.NLM which fixes a race condition in the Deallocate / Allocate slot code where a destroy connection NCP could block then an alloc connection could come in and attempt to logout the connection and reuse it assuming it is still there. 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DEVRQFIX NLM ============ SYMPTOM: This patch addresses an ABEND: GPPE. This would happen in the ADISK process, halting at location 171bd0 when an application using the DAI call DeviceIO was loaded. SOLUTION: Apply DEVRQFIX NLM 975 12-18-95 3:59p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DHANDFX NLM ============ SYMPTOM: The file server will exhibit a GPPE or other ABEND having to do with corruptdirectory handles. This is most notably seen when running Appletalk,NFSgateway, or GroupWise NLM's, but can be seen when loading any set of NLM's 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 NLM's at the server) was not properly handling the case where 20 or more handles were required. SOLUTION: Apply DHANDFX NLM 3,340 12-23-94 11:54a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- DIAGRFSX NLM ============ Symptom: This patch fixes two network management errors. The first error caused the server to not respond to requests issued by the network management console (only re-booting would fix the problem). The second error did not allow the File Server to respond to network management requests directed to other networks connected to the File Server other than the Internal Network. SOLUTION: Apply DIAGRFSX NLM 2,150 12-18-95 4:33p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DIRLPFIX NLM ============ Symptom: This patch fixes a problem that results in an infinite loop when the DOS DIR command is used in a subdirectory where more than 65,535 files exist. This loop will also occur with the FindFirst and FindNext DOS function calls. SOLUTION: Apply DIRLPFIX NLM 1,124 06-20-95 9:10a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,214 02-22-94 3:26p 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,090 05-09-94 11:11a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- DOSUNFIX NLM ============ SYMPTOM: This patch fixes a problem with NetWare/NFS V1.2. If a file is renamed from 99999999.v0 to 99999999.V0, it causes the server to ABEND with the message: "DOSGenerateUniqueName tried over 100000000 names and couldn't get a unique one." SOLUTION: Apply DOSUNFIX NLM 1,910 12-19-95 7:29a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DOTFIX NLM ============ SYMPTOM: This patch fixes the problem of multiple directories of the same name being created at the root of the SYS: volume. Currently, if the user creates directories ending in two dots (e.g."STATS.."), multiple directories of the same name will be created. SOLUTION: Apply DOTFIX NLM 1,103 02-12-96 2:25p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DTRSTFIX NLM ============ SYMPTOM: GPPE's and ABEND'S occur because of an invalid Trustee Node pointer in a Directory Entry. SOLUTION: Apply DTRSTFIX NLM 1,384 12-19-95 7:43a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DUPFIX NLM ============ SYMPTOM: Duplexed drives report all mirrored drives were in sync after a hardware failure, yet they were not. SOLUTION: Apply DUPFIX NLM 1,513 12-19-95 7:54a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch fixes a problem in which a certain sequence of events would cause duplexed drives to report all mirrored drives were in sync after a hardware failure, yet they were not. DUPFIX.NLM must be loaded in memory at the time a hardware error occurs with the disk drive. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EAALLCFX NLM ============ SYMPTOM: Server will hang or abend when EAs are written to a large volume (>6 Gig.) that has a block size of > 4k Customer has an application (client based) that writes EAs. When this program is run the server will either hang or abend (multiple abends). The requirements for this to occur are 1) a volume that is greater than 1 gigabyte and 2) a block larger than 4k. The problem has been duplicated in-house as follows: 1) Ran a test program (TSTEA.EXE) that creates 50 test files. The program creates the files and then writes 8 1 megabyte EAs to each file. 2) The server starts to get "cache memory allocatorout of available memory" messages and then will simply hang. The server used is as follows: NetFrame 160 megabytes of memory 6 gigabyte volume block size set to 8k (also tried 16k) SET Maximum Alloc Short term memory = 33554432 SOLUTION: Apply EAALLCFX NLM 1,647 04-04-95 11:58a 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,368 03-28-94 8:46a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- EAERRFIX NLM ============ SYMPTOM: Invalid Semaphore ABEND which is initially caused by an ERR_EA_NOT_FOUND being returned in the Error Code on a Read Extended Attribute NCP reply. SOLUTION: Apply EAERRFIX NLM 1,020 7-19-96 8:44a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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 ABEND could be possible or seen, including GPPE'S. 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 lanalyzer. 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 1,465 12-21-94 12:36p 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- EAINFIX NLM ============ SYMPTOM: This patch fixes a problem with Extended Attributes when two or more work stations execute XCOPY multiple times. The result is that after about ten minutes the server will ABEND with the message: "Free called with a memory block that has an invalid resource tag.". SOLUTION: Apply EAINFIX NLM 2,250 12-19-95 8:02a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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 CD-ROM mounted volume. Sometimes after receiving these errors the connection to the File Server would be lost. SOLUTION: Apply EAREPLFX NLM 1,324 02-22-94 3:32p 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,393 11-09-93 11:07a 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. v4.10 is in 410ITx.EXE or 410PTx.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 968 07-26-94 8:20a 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,186 11-09-93 11:13a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- 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 1,049 07-26-94 8:25a 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EVENTFIX NLM ============ SYMPTOM: This patch is required by any NLM that needs object deletion notification. Symptoms of this bug will vary, depending on the NLM being run. It addresses a problem that occurs when a "delete bindery object" call is made to the OS. The OS reports the event after the object is already deleted, thus preventing the application from accessing information on the object when the event is reported. SOLUTION: Apply EVENTFIX NLM 2,498 12-19-95 8:05a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch fixes as described in the symptom; the bindery object is not deleted until after the event is reported. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EXTATTFX NLM ============ SYMPTOM: Attempt to mount a volume, could result with the error message: "Invalid extended attribute in directory". VREPAIR may not detect errors, or it may report the error condition: "Invalid score card error" several times. SOLUTION: Apply EXTATTFX NLM 2,442 01-19-94 3:51p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. EXTATTFX.NLM should be used on systems that have 2 or more name spaces on any single volume. This patch fixes a problem with extended attributes when using 2 or more name spaces on a single volume. If a certain code path is followed once these name spaces have been added, and the user attempts to mount the volume, the error message: "Invalid extended attribute in directory" is displayed. Running VREPAIR may not detect errors, or it may report the error condition: "Invalid score card error" several times. This patch corrects these errors, and allows correct functionality of 2 or more name spaces on a volume. 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 1,037 04-10-95 11:09a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- FATFIX NLM ============ SYMPTOM: Problem with TurboFAT and FAT corruption in general, when multiple workstations randomly access large database files SOLUTION: Apply FATFIX NLM 3,357 12-19-95 8:08a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch fixes a problem with TurboFAT and FAT corruption in general, when multiple workstations randomly access large database files. (The minimum size of a TurboFAT database file is, using a default 4k block size and 64 blocks as the TurboFAT, 64 * 4k = 256k. If a different block size is used then substitute that number.) *** IMPORTANT SPECIFIC INSTRUCTIONS FOR FATFIX.NLM *** It is important to note that the latest version of VREPAIR.NLM should be run before implementing this patch. FATFIX.NLM will prevent corruption of the FAT and TURBOFAT, but VREPAIR is required to correct previous corruption. The steps below should guide you through using FATFIX.NLM. In order to use this patch, first add the following two lines to your STARTUP.NCF file after the assignment of the "IPX INTERNAL NET" number (See page 150 of the NetWare v3.11 "Installation" manual for an example of this statement): LOAD PATCHMAN LOAD FATFIX It is important that these lines are added immediately after the assignment of the internal network number. After editing, be sure to save the file. After editing the AUTOEXEC.NCF file do the following things: -LOAD VREPAIR at the console. -Dismount the volumes. -Run VREPAIR on all volumes until there are no further errors reported (This make take one or more attempts). -Down the server. -Bring the server back up with the modified AUTOEXEC.NCF file. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- GETQFIX NLM ============ SYMPTOM: This patch fixes a problem which caused a large number of deleted .SRV files in the queue subdirectories in SYS:SYSTEM. SOLUTION: Apply GETQFIX NLM 1,130 12-20-95 1:58p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- GETRFIX NLM ============ SYMPTOM: An ABEND caused by a driver requesting a valid linked request, which has been changed by another process. SOLUTION: Apply GETRFIX NLM 1,311 12-19-95 9:42a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. A zero is now returned to the calling process instead of ABENDING the server. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- GETSEFIX NLM ============ SYMPTOM: A problem exist when more than 31 security equivalences for a user or group ID are set up. This can result in a system hang which may be accompanied by a message indicating a "multiple ABEND". SOLUTION: Apply GETSEFIX NLM 1,463 12-19-95 9:50a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,088 12-19-95 10:02a 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.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 2,509 12-19-95 10:08a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- HDUMP NLM ============ SYMPTOM: HDUMP.NLM v2.20 is a file server utility which allows system COREDUMPS to be routed to a file residing on the server's local DOS partition, instead of the customary floppy disk method (which is much more time consuming). SOLUTION: Apply HDUMP NLM 4,393 02-05-96 11:14a hdump.nlm Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. HDUMP.NLM v2.20 is a file server utility which allows system COREDUMPs to be routed to a file residing on the server's local DOS partition, instead of the customary floppy disk method (which is much more time consuming). HDUMP v2.20 is an enhancement utility intended for use with all user versions of NetWare v3.11. This version of HDUMP requires the patch manager PATCHMAN.NLM v2.20 be installed in order to load. If it is not already loaded, HDUMP will attempt to automatically load PATCHMAN. Once PATCHMAN is loaded, typing "DISPLAY PATCHES" at the server console will display all patches currently loaded. The HDUMP utility will be listed as a dynamic patch. Please note that a readme file is contained in \CHOP\*.* describing how to use it. The Chop utility allows you to put a memory dump on diskette from a network drive. Installation: To install HDUMP, simply place the HDUMP.NLM file in the same directory as the other NLM files (SYS:SYSTEM or DOS partition). From the file server console screen, type: load HDUMP If no destination path/filename is specified, HDUMP will use C:\COREDUMP.IMG as the default. HDUMP will attempt to create the destination directory if it does not already exist. The user will be warned if the destination file already exists, and given the option to overwrite the existing image file on the local drive or exit. If HDUMP must abort for any reason, the user will be given the option of writing the COREDUMP to floppy disk. If an ABEND occurs, or a COREDUMP is forced, HDUMP will automatically begin execution and will display the following: Writing diagnostic dump to: Reading memory range x of x. Dumping sector x of x. Upon successful completion, the message "Diagnostic dump complete" will be displayed. At this point, it may be useful to use the IMGCOPY.NLM and/or CHOP.EXE utilities to copy the file from the DOS partition. See their respective documentation for details. ----------------------------------------------------------------- HTFXFX NLM ============ SYMPTOM: Corruption of Data because of data being redirected by HOTFIX when using a volume block size is larger than 4k. SOLUTION: Apply HTFXFX NLM 1,036 12-19-95 10:44a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Corrects a problem when using disk block sizes larger than 4K and cache buffer sizes larger than 4K. If a block was read from the redirection area while copying a file in the above circumstance, it could cause the destination block to become corrupted. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- IMGCOPY NLM ============ SYMPTOM: IMGCOPY.NLM is a NetWare Loadable Module that is used to copy a COREDUMP image file residing on the file server's local drive to a network drive while the server is running. SOLUTION: Apply IMGCOPY NLM 4,775 09-04-91 8:35a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. IMGCOPY.NLM is a NetWare Loadable Module that is used to copy a COREDUMP image file residing on the file server's local drive to a network drive while the server is running. Normally, the image file will have been created using HDUMP, a COREDUMP image file generating utility. IMGCOPY reduces file server down time by copying the image file to a network drive as a background process, allowing the server to be used for normal activities. In order to use IMGCOPY, place the IMGCOPY.NLM file in the same directory as the other NLM'S (DOS partition or SYS:\SYSTEM directory). After an image file has been generated and the server brought back up, type the following at the file server console screen: LOAD IMGCOPY < > where: source path= Full path (including file name) of the image file which resides on the local hard drive. If no source path is specified, the default is C:\COREDUMP.IMG. If no parameters were specified with HDUMP when it was loaded, the default source path will be correct and need not be specified at the command line. destination path= The location on the network drive where the image file should be copied. This must be a complete NetWare path specification, including volume and file names. The default destination path is SYS:COREDUMP\COREDUMP.IMG. If the destination path does not already exist, IMGCOPY will attempt to create that directory on the network drive. If the file specified already exists, it will be overwritten without any warning to the user. priority= This parameter specifies what priority level is to be used when copying the image file. The valid options are LOW, MEDIUM, and HIGH. If no priority is given, MEDIUM is assumed. When running at LOW priority, IMGCOPY allows the file server to service user requests for longer intervals. LOW priority will exhibit the least amount of server degradation, but it will take much longer to complete the file transfer. At MEDIUM priority, there is no degradation of server functionality, although the transfer time is reduced considerably. At HIGH priority, the server will almost exclusively be processing transfer requests, thereby making it nearly impossible for the file server to perform other duties until the file has been transferred. This is the fastest transfer priority available. Note that all the above parameters are optional, and may be specified in any order. Once loaded, IMGCOPY will immediately begin to transfer the image file from the server's local DOS partition, to the network drive. A status screen will be displayed, showing the selected source and destination files, as well as the priority level. Also, a counter indicating the number of bytes successfully transferred will be display. The user can toggle out of the IMGCOPY screen by typing Alt + Esc. When the image file has been successfully transferred, IMGCOPY will display a message to the file server console and automatically unload itself. File server activity will then resume at normal operating levels. It is possible to abort the file transfer by unloading IMGCOPY while the transfer is taking place. A note about Real and Protected mode: During normal operation, the file server runs in protected mode. However, in order to access the local DOS partition to read the image file, the file server must switch to real mode each time a read request is processed. While in real mode, all normal file server activity ceases. Due to this frequent state switching, users may experience loss of keystrokes at the file server console if a key was pressed while the server was in real mode. These keystrokes are stored in a real mode buffer and will not be seen at the file server console. The higher the priority level, the more apparent this will become. At the MEDIUM and HIGH priority settings, users may not be able to toggle between screens easily or type anything at the server console. This condition will disappear as soon as the file has been transferred and IMGCOPY has been unloaded. ----------------------------------------------------------------- IPXRCVFX NLM ============ SYMPTOM: These patches fix a problem with receiving a GPPE ABEND because of the generation of an NCP request that IPX.386 did not handle correctly, thus causing an invalid fragment count. A problem has been encountered with the NetWare SFT III operating system that is produced by Running ARCServe 4.0 on one of the mirrored NetWare SFT III servers. If ARCServe is backing up a file to the tape and the secondary server restarts for any reason, upon re-synchronizing the memory the operating system will ABEND with a General Protection Processor Exception (GPPE) error. This error only occurs if a file is being copied to the tape at the time. If ARCServe is loaded but not in the process of copying a file to tape, then the problem is not apparent. CAUSE The problem is that an NCP request is generated that IPX.386 did not handle correctly, causing an invalid fragment count that would bring down the primary server. Because the primary server is being re-mirrored to the secondary server, the secondary server dies as well. SOLUTION: Apply IPXRCVFX NLM 979 02-04-94 8:33a 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF The patch needs to be loaded in both the MSEngine and IOEngine. 1. Copy the IIPXRCFX.NLM and PM311IO.NLM files to the NetWare boot directory. 2. Copy the IPXRCVFX.NLM and PATCHMAN.NLM files to the SYS:SYSTEM directory. 3. Edit the IOSTART.NCF file to load the PM311IO.NLM and IIPXRCFX.NLM files. 4. Edit the MSSTART.NCF file to load PATCHMAN.NLM and IPXRCVFX.NLM files. ----------------------------------------------------------------- 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 3,844 11-22-93 10:59a 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. v4.10 is in 410ITx.EXE or 410PTx.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. ----------------------------------------------------------------- ITABLEFX NLM ============ SYMPTOM: The server will sometimes abend with the "Alloc called with invalid resource tag" error message while mounting the volume. The particular code path that is being taken when mounting the volumes causes "StartDirectoryHandles" routine to run before initializing the NCPTableAllocTag. "StartDirectroyHandles" then calls SAlloc which compares the resource tag to the NCPTableAllocTag which is still null and therefore abends the server. SOLUTION: Apply ITABLEFX NLM 1,792 05-11-95 2:12p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MAXCDCFX NLM ============ SYMPTOM: SOLUTION: Apply MAXCDCFX NLM 962 12-19-95 11:22a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch changes the maximum limit for the Set Parameter "Maximum Concurrent Disk Cache Writes" from the old range of 10 to 100, to a new range, 10 to 1000. This change will be transparent to most users. The performance of some high throughput disk controller drivers is limited by the slower limit. You may want to load this NLM if your system uses high throughput EISA drives. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MFIXOPEN NLM ============ SYMPTOM: This patch is intended for all number-of-user versions of NetWare 386 v3.11 that are running the MAC gateway VAPS instead of the AFP NLM'S. This patch fixes the problem that MAC users have when trying to open files that are flagged Read Only. The user is unable to open the file, and receives the error message: "File not found." SOLUTION: Apply MFIXOPEN NLM 1,455 12-19-95 2:17p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF File: STARTUP.NCF ----------------------------------------------------------------- MIRRFIX NLM ============ SYMPTOM: The OS would get into a loop of abort/remirror attempts after certain failures involving mirrored drives. SOLUTION: Apply MIRRFIX NLM 1,242 08-06-93 4:53p Made change to CheckMirrorActiveFlag to set the correct partition structures bitmap table to -1's. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MKDIRFIX NLM ============ SYMPTOM: Invalid error codes returned by the "create directory" call when copying a file to an invalid path. Additionally, this fix changes error codes returned from "ERR_BAD_DIR_HANDLE-program aborted" to "ERR_INVALID_PATH" in the case where the server is scanning a directory path and a file name exists in the middle of that directory path. (For example: Makedir: dir1/dir2/dir3 where dir2 is a filename.) SOLUTION: Apply MKDIRFIX NLM 2,295 12-19-95 2:33p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. MKDIRFIX.NLM replaces and supersedes the previously released patch, DIRHFIX1.NLM. Since DIRHFIX1.NLM and MKDIRFIX.NLM patch some of the same areas, they cannot coexist. To run MKDIRFIX.NLM, DIRHFIX1.NLM must be removed from the system. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MPRPSFIX EXE ============ SYMPTOM: SOLUTION: This static patch allows one to have Maximum Physical Receive Packet Size up to 24682 instead of just 4202. Apply MPRPSFIX EXE 10,674 09-23-92 9:33a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: This is a static patch the executable file must be run aginst server.exe. ----------------------------------------------------------------- NCOMFIX NLM ============ SYMPTOM: ABEND: Resource tag link error detected in NCompleteRequest. ABEND: Invalid disk request passed to ReturnDiskRequest. SOLUTION: Apply NCOMFIX NLM 2,109 12-19-95 2:51p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- NCPCHKFX NLM ============ SYMPTOM: Application which performs an NCP 253 which abends the server with GPPE. SOLUTION: Apply NCPCHKFX NLM 1,150 04-05-95 11:45a 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- NCPEXTFX NLM ============ SYMPTOM: A patch is needed to support RegisterSpecificNCPExtension() on NetWare 3.11. SOLUTION: Apply NCPEXTFX NLM 1,688 05-09-94 11:27a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. While implementing SNMP over NCP extensions using our assigned well-known NCPX ID, we encountered the following problem: NetWare 4.x and 3.12 allow NCP extensions to be registered by ID but NetWare 3.11 only allows them to be registered by name. This implies that clients using NCPX must be able to register by both ID and name depending on the server OS version. Since we could have clients of all kinds, this is too much to expect from all our clients. A patch to NetWare 3.11 is needed to support the RegisterSpecificNCPExtension() function. This, in turn, will enable CLIB to support the needed function: NWRegisterNCPExtensionByID(). Installation Instructions: NOTE: THIS PATCH MUST LOAD BEFORE CLIB.NLM. NCF FILE: STARTUP.NCF ----------------------------------------------------------------- NCPFLTFX NLM ============ SYMPTOM: A problem exists with invalid connection number being passed in the data field when using an NCP request for connection information where the connection number field in the packets data has an invalid number. Resulting in a ABEND:GPPE. SOLUTION: Apply NCPFLTFX NLM 1,794 01-18-94 3:24p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF 1. Copy NCPFLTFX.NLM to the SYSTEM directory, or the NetWare boot directory. 2. Load the patch from the console by entering the command "LOAD NCPFLTFX". 3. This command may be added to either the STARTUP.NCF or the AUTOEXEC.NCF. This NCPFLTFX.NLM patch fixes a problem with receiving a GPPE ABEND when the server receives an NCP request for connection information where the connection number field in the packets data has an invalid number. This patch enables an error checking filter which will check the connection number for validity, thus avoiding the ABEND condition. ----------------------------------------------------------------- NCPSPFIX NLM ============ SYMPTOM: ABEND:GENERAL PROTECTION PROCESSOR EXCEPTION SOLUTION: Apply NCPSPFIX NLM 1,760 12-19-95 3:40p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch prevents a zero-length WriteToSpool NCP from being processed. This problem has been known to cause an ABEND:GPPE at server and corrupt an entire volume. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- NFSFIX NLM ============ SYMPTOM: This patch is intended for all number-of-user versions of NetWare v3.11 that run NFS.NLM v1.2. This patch adds a new parameter to the NameSpace call RemoveEntryName. This patch is also intended for users of earlier versions (before 1.2) of NFS.NLM if a hard link is created to a NetWare server using NetWare NFS. This patch fixes a server ABEND in the following situation: IF a Unix user creates a hard link to a directory in the NetWare server using NetWare NFS, and an attempt is made to remove this directory while the hard link still exists, the server ABEND. SOLUTION: Apply NFSFIX NLM 2,941 12-19-95 4:07p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NFS.NLM v2.10 will load this patch automatically. If installation is necessary for other versions of NFS.NLM, simply place the NFSFIX.NLM file in the same directory as the other NLM files (SYS:SYSTEM or DOS Partition), and type "LOAD NFSFIX." Once the patch has loaded, all changes are in effect until NFSFIX is unloaded. NCF FILE: STARTUP.NCF ----------------------------------------------------------------- OBPRGFIX NLM ============ SYMPTOM: ABEND "A string with too long a length was passed to the output formatter". SOLUTION: Apply OBPRGFIX NLM 1,640 12-19-95 3:58p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- OLDPASS NLM ============ SYMPTOM: If a user is required to have a unique password and is forced to change the password periodically in Syscon under Account restrictions, he will be allowed to have a non unique password. If he is not forced to change the password periodically then Setpass will work correctly and he will only be able to have a unique password. SOLUTION: Apply OLDPASS NLM 1,193 12-19-95 4:53p We have decided on two solutions to this problem. For the immediate customer's problem we will write a Patchman patch to change the number of days to wait to store an OLD_PASSWORD from four to one. In the future we will need to modify the OS to allow for the inclusion of a variable which sets the amount of time a user must wait before they are able to change their password. A grace opportunity to change password may be included in this interval. Without this additional variable, there will always be ways to reuse favorite passwords. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- OS2OPNFX NLM ============ SYMPTOM: This patch allows a user to use the "TYPE" command to view a file even though SCAN file rights have not been granted. Without this patch, if the user is granted all rights but the SUPERVISOR and SCAN file rights (including Read) the file still cannot be "TYPE"ed. SOLUTION: Apply OS2OPNFX NLM 1,385 12-19-95 4:52p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- PARSEFIX NLM ============ SYMPTOM: Parse parameters is only comparing 1st character In the NetWare OS when loading a LAN driver, each keyword requires a minimum of three characters like MEM. The OS is only checking that the first character matches and that there are at least three characters with the MEM parameter (others like INT work fine). In other words MFG would be interpreted as MEM by the ParseDriverParameters call. SOLUTION: Apply PARSEFIX NLM 1,176 02-12-96 2:16p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- PATCHMAN NLM ============ SYMPTOM: SOLUTION: Apply PATCHMAN NLM 15,591 01-22-96 11:22a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This version of PATCHMAN replaces any and all previous versions of PATCHMAN. PATCHMAN can only be used with NetWare v3.11+ (all number-of-user versions). NetWare v3.10a requires PATCHMAN v1.20b. *** PLEASE NOTE THE TECHNICAL BULLETIN ON THE 3.11 OPERATING SYSTEM PATCHES INCLUDED BELOW. PATCHMAN.NLM is the Patch Manager for which tracks and manages all official patches for NetWare 386 v3.10+. Patches for NetWare 386 v3.10+ consist of three types: DYNAMIC -- Dynamic patches are implemented as .NLM files that can be loaded/unloaded while the server is running. Unloading a dynamic patch will restore the Operating System to its original "un-patched" state. SEMI-STATIC -- Semi-static patches can also be loaded while the server is running, but they cannot be unloaded. It is not possible to undo the effects of a semi-static patch without first downing the server and bringing it back up without loading the semi-static patch. STATIC -- A static patch is a DOS executable program that modifies the SERVER.EXE file. This type of patch is applied once and its effects are permanent. It is suggested that a backup of the original SERVER.EXE file be made before applying a static patch. (In other words, do not patch the SERVER.EXE on your original distribution diskette!) Dynamic and semi-static patches modify the Operating System in memory, not on the disk. This means that dynamic and semi-static patches must be loaded each time the Operating System is brought up in order for any 'fixes' to take effect. It is recommended that the command "LOAD " be placed in the file server's AUTOEXEC.NCF file to ensure that the patch is always in effect as soon as the server is brought up. In order to see which patches are currently loaded on the system, type "PATCHES" at the file server command line. The patches will then be grouped and displayed according to their type (i.e. - STATIC, SEMI-STATIC, or DYNAMIC). Typing "MODULES" at the server console will show which dynamic patches have been loaded, but will not show semi-static or static patches. The Patch Manager (PATCHMAN.NLM) must be loaded before any dynamic or semi-static patches can be loaded. If PATCHMAN is not already loaded, the .NLM will attempt to locate PATCHMAN and, if found, will load it automatically. PATCHMAN only needs to be loaded once; all .NLM patches can then be loaded. PATCHMAN cannot be unloaded until all patches that rely on it are first unloaded. NOVELL TECHNICAL BULLETIN TITLE: Effects of v3.11 Serialization Changes on Patches and Fixes DOCUMENT ID#: TB.P.298 DATE: 4 December 1991 PRODUCT: NetWare PRODUCT REVISION: v3.11 SUPERSEDES: N/A SYMPTOM: Errors, such as "Unexpected code encountered in area to be patched" during implementation of patches and fixes. ISSUE/PROBLEM Because of the unanticipated success of NetWare v3.11, the available serialization range was exhausted. As a result, the v3.11 operating system has been modified to extend that serialization range. This modification has required a corresponding change to all v3.11 operating system patches, including those previously released. It does not affect any patches or fixes other than v3.11 operating system patches. When a user attempts to apply an unmodified NetWare v3.11 operating system patch to a v3.11 operating system with the extended serialization range, he or she may receive an error similar to the one above. SOLUTION The modified NetWare v3.11 operating system patches can be applied to any v3.11 operating system if the PATCHMAN.NLM (v2.20 or later) that accompanies them is loaded at the file server. PATCHMAN.NLM performs the application of a given patch to the v3.11 operating system as it resides in file server memory. Users should be aware of five important points: 1) PATCHMAN.NLM v2.20 (or later) must be loaded. 2) The modified patches, with PATCHMAN.NLM v2.20 (or later), will successfully load on NetWare v3.11 operating systems without the extended serialization range. 3) The re-released patches will not be successfully implemented if PATCHMAN NLM v2.20 (or later) is not loaded. 4) Unmodified v3.11 operating system patches will work successfully only on operating systems without the extended serialization range. They will not work on a newly modified operating system, nor on an operating system also running modified patches or PATCHMAN v2.20 (or later). 5) The re-released NetWare v3.11 operating system patches are dated October 1991 or later. ***************************************************************** DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. ***************************************************************** ----------------------------------------------------------------- PPCFIX NLM ============ SYMPTOM: A problem exist where an NLM being unloaded causes the server to ABEND because it fails to return a polling procedure resource. The server may ABEND after printing following message: "1.1.14 Module did not release 1 resource Module: NetWare 386 Print Server Resource: Print Server Polling Procedure Description: Poll Procedure Call-Backs" SOLUTION: Apply PPCFIX NLM 1,233 12-19-95 5:15p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- PRESFIX NLM ============ SYMPTOM: The LSL PreScan and default stack hooks in the 3.11 OS have two bugs in them. 1) When a LAN driver unloads, all protocol stacks bound to its logical board(s) are notified. PreScan and default stacks are not being notified. This needs to be corrected. 2) The LSL ReceiveEvent routine (which queues packets in the LSL and then processes them at ProcessEvents time) was passing the packets past the PreScan stacks before putting them on the receive queue. The PreScan stacks should see the packets only at ProcessEvents time. This only holds for the normal ReceiveEvent routine and not the FastReceive routine which does not queue anything in the LSL. SOLUTION: Apply PRESFIX NLM 1,302 12-19-95 3:47p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This Patch for v3.11 has been replaced by LSLENH.NLM. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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 1,609 08-10-94 4:19p 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- REMDEVFX NLM ============ SYMPTOM: Formatting removable devices through INSTALL.NLM would cause the Operating System to ABEND with the following message: "ABEND: Kernel detected a process switch during interrupt time." SOLUTION: Apply REMDEVFX NLM 1,086 12-19-95 2:58p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- REMFILFX NLM ============ SYMPTOM: ABEND "RemoveFile called with invalid file handle." SOLUTION: Apply REMFILFX NLM 1,279 12-19-95 2:46p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- RENDIRFX NLM ============ SYMPTOM: "RENDIR " will Abend a server with a GPPE. The client does not have to be logged in to abend the server. RENDIR in the LOGIN directory will do the same thing. SOLUTION: Apply RENDIRFX NLM 1,188 12-20-95 2:04p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.10, 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- RENFIX NLM ============ SYMPTOM: Rename of a file to a name of a subdirectory will move the file to that subdirectory. Details: Directory Structure: Sys:dir1\dir2 From dir1, if you rename a file to "dir2" the file will disappear from dir1 and you will find it with its original name in dir2. SOLUTION: Apply RENFIX NLM 1,374 12-19-95 11:14a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Wrote patch RENFIX.NLM to remove this feature according to the customer's desire. Now we Unlock the directory entry, place ERR_SOME_NAMES_EXIST (145) in code and jump to ExitRename. Fixed a problem in INWRenameEntry that would move a file into a subdirectory when an attempt was made to rename the file to the name of the subdirectory that was in the same directory as the file. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- REPLYFIX NLM ============ SYMPTOM: NCOPY drops the users connection. When a user is logged into a SFT 3 v3.11 server, his connection number is greater than 153, and runs NCOPY.EXE, the user's connection is dropped from the server. The error messages that he gets is server connection no longer valid. SOLUTION: Apply REPLYFIX NLM 1,145 06-29-93 7:47a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- REQFIX NLM ============ SYMPTOM: This patch re-initializes the number of requests made from a station each time a new user logs in. This problem was visible when looking at data returned by PAUDIT. If an individual workstation was used to Login for several different users, the "requests" value displayed in PAUDIT was not re-initialized for each user. SOLUTION: Apply REQFIX NLM 1,251 12-19-95 10:48a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- RPLENFX NLM ============ SYMPTOM: A problem has been found in which the server leaves files open. SOLUTION: Apply RPLENFX NLM 2,729 12-21-95 2:18p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch changes the length of the reply buffer in the StationControl structure. This patch has a command line parameter that allows for a configurable size. The default is 1024. Changing of the buffer size is accomplished at the time of loading the patch. To change the default buffer size, (to 2048, for example), type "load RPLENFX size 2048," at the console prompt. Installation Instructions: NCF FILE: STARTUP.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 1,943 12-21-95 7:42a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- SAPFX NLM ============ SYMPTOM: SOLUTION: Apply SAPFX NLM 2,380 12-19-95 7:43a 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. SAPFIX.NLM patch allows sapping devices with the same name to be advertised in different sap packets. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SEARCHFX NLM ============ SYMPTOM: Doing "SEARCH DEL 2" (or later number) on server console after removing all searches from that server cause abend. With usual configuration (only SYS:\SYSTEM is searched), doing "SEARCH DEL 1" then "SEARCH DEL 2" abends the server. SOLUTION: Apply SEARCHFX NLM 1,142 04-28-95 2:57p 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SERVHOPS NLM ============ SYMPTOM: This NLM is normally used when there is a mixture of 3.11 and SFT 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 1,852 05-10-93 11:36a 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- SHORTAFX NLM ============ SYMPTOM: NWSetDirectoryHandlePath() returns 0x89FF under NetWare 3.11 SOLUTION: Apply SHORTAFX NLM 1,010 04-05-95 11:41a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SPXACKFX NLM ============ This file has been removed. TID2914685 Symptoms There are two Native SPX issues that have come to our attention as of late: 1.) Btrieve applications running on Netware 3.11 servers experience status 95 errors (session no longer valid).. Also the SoftSolutions product was experiencing disconnected client as well. 2.) Rconsole on Netware servers running multiple windows using CSSTATUS (NWSAA utility), will "hang" other rconsole stations if one of the rconsole stations is rebooted. Solutions 1.) Unloading SPXACKFX.NLM from 311ptF.exe corrected this problem. We are investigating the problems with this patch. 2.) Unloading SPXTRMFX.NLM from 311ptF.exe corrected the second problem, as does exiting from the rconsole gracefully. We are very interested in recieving other information on these problems, traces, other facts, etc. ----------------------------------------------------------------- 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 1,151 01-23-96 2:39p 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. v4.10 is in 410ITx.EXE or 410PTx.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 ----------------------------------------------------------------- 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 1,727 01-23-96 2:41p 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. v4.10 is in 410ITx.EXE or 410PTx.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: STARTUP.NCF ----------------------------------------------------------------- SPXFSFIX NLM ============ SYMPTOM: Fix to a problem that results in a file server GPI in the SPXFindSession. This ABEND is known to occur when using Madge "Smart IPX" Token Ring drivers. SOLUTION: Apply SPXFSFIX NLM 1,155 12-19-95 7:29a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. The problem is caused by a connect request SPX packet which arrives at the server without the system bit being set. This causes the server to look up the session with ID = FFFF (session ID for system packets), but since the system bit isn't set, the server looks in the session table for a client with a corresponding ID. This causes SPXFindSession to look beyond the end of memory, resulting in a GPI ABEND. The patch adds a test to SPXFindSession to check for sessions beyond the end of the session table. With this patch, if a connect request SPX packet is sent without the system bit set, the packet will be discarded as invalid and the workstation that sent the invalid packet will hang. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SPXLISFX NLM ============ SYMPTOM: This fixes a problem with the SPXListenForConnectedPacket function that was not informing the connection partner when the window was reopened, after being closed. This caused terrible performance problems since the window would not open again until a WatchDog packet was generated about 3 seconds later. SOLUTION: Apply SPXLISFX NLM 1,016 12-19-95 7:13a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SPXMSFIX NLM ============ SYMPTOM: When trying to access the last slot of the spx session table, to open a new session, the server would hang in an infinite loop. SOLUTION: Apply SPXMSFIX NLM 988 01-23-96 2:45p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF File: STARTUP.NCF ----------------------------------------------------------------- SPXNSFIX NLM ============ SYMPTOM: If the session did not exist, SPX failed to interpret terminate ACKs as system packets. SOLUTION: Apply SPXNSFIX NLM 1,047 01-23-96 2:46p 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. v4.10 is in 410ITx.EXE or 410PTx.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 Acknowledgment packets on sessions that do not exist. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SPXTRMFX NLM ============ This file has been removed. TID2914685 Symptoms There are two Native SPX issues that have come to our attention as of late: 1.) Btrieve applications running on Netware 3.11 servers experience status 95 errors (session no longer valid).. Also the SoftSolutions product was experiencing disconnected client as well. 2.) Rconsole on Netware servers running multiple windows using CSSTATUS (NWSAA utility), will "hang" other rconsole stations if one of the rconsole stations is rebooted. Solutions 1.) Unloading SPXACKFX.NLM from 311ptF.exe corrected this problem. We are investigating the problems with this patch. 2.) Unloading SPXTRMFX.NLM from 311ptF.exe corrected the second problem, as does exiting from the rconsole gracefully. We are very interested in recieving other information on these problems, traces, other facts, etc. ----------------------------------------------------------------- STDIRHFX NLM ============ SYMPTOM: Unable to CD into LOGIN directory after loading client 32. SOLUTION: Fixed bug in StartDirectoryHandles where the usecount was not initialized correctly. Apply STDIRHFX NLM 1,119 09-23-96 1:41p 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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 SYNCTIME NLM 1,948 05-03-94 5:03p The SYNCTIME.NLM file in the SYNC3XFT.EXE patch file causes the server to update its' time periodically from the hardware clock. Installation Instructions: NCF FILE: AUTOEXEC.NCF 1. Copy the SYNCTIME.NLM file to the SYSTEM directory or the NetWare boot directory. 2. The appropriate PATCHMAN must first be loaded. (PM312.NLM of v3.11 PATCHMAN.NLM for 3.11 and PMIO311.NLM for 3.11 SFT3). 3 Then load the patch from the console for NetWare 3.11 and 3.12 or from the IOENGINE screen for 3.11 SFT3 NetWare, by entering the following command: LOAD SYNCTIME 4. You may also load the file in the IOSTART.NCF for 3.11 SFT3 or in the AUTOEXEC.NCF file for NetWare 3.11 and 3.12. ----------------------------------------------------------------- TRSTFIX NLM ============ SYMPTOM: This patch fixes a problem found when 9 or more trustee directory assignments for individual users or groups are made at the root level of the same volume (usually volumes other than the SYS: volume). Although the assignments are made as they should be, the 9th and above cannot be seen from SYSCON. (They do appear in FILER or TLIST.) SOLUTION: Apply TRSTFIX NLM 1,688 12-18-95 4:57p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This patch adds a check for the parent of the trustee node that contains the ninth trustee assignment; if the parent node is the root of the volume, it checks for trustee assignments. This patch also fixes a problem found when granting trustee rights to an existing group. The rights appear to be correct in SYSCON when viewed from user SUPERVISOR, but these new rights do not appear when viewed by the individual user. These rights are not actually in effect. When viewed as a group member, the user gets the error: "GetTrusteePaths returned error 242". Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- TTSFIX NLM ============ SYMPTOM: TTSFIX.NLM fixes a bug encountered when certain applications execute explicit TTS, and file locking is also used. This results in an application hang at the workstation, and a GPPE ABEND at the file server. SOLUTION: Apply TTSFIX NLM 1,227 12-18-95 4:49p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- UNKFIX NLM ============ SYMPTOM: This patch fixes a problem which was causes an ABEND on a 3.11 FILE SERVER. This is caused by entering a complete file name of a valid NetWare file at the file server console. This file may be located on any of the server's search paths. FOR EXAMPLE: typing "MONITOR.NLM" at the console instead of "LOAD MONITOR.NLM" will cause the above condition. Typing "MONITOR" without the .NLM extension will not cause the ABEND. If the named file is not an .NCF file the server will repeatedly display: "Unknown command" and "Invalid line in command file-line length exceeds 511 characters" until it eventually would ABEND with the message: "ABEND: General Protection Processor Exception running console command process." The Operating System is incorrectly attempting to open and read the NLM as if it were an .NCF file. SOLUTION: Apply UNKFIX NLM 955 12-18-95 4:33p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- UNLCKFIX NLM ============ SYMPTOM: This patch corrects a problem which causes a ABEND with the message: "UnlockDirectoryEntry called with entry that was already unlocked" This problems occurs when the system tries to read the primary directory table and fails. It then attempts to read the mirrored table and though it appears to read the table successfully, the information is corrupt and the system ABEND. SOLUTION: Apply UNLCKFIX NLM 1,049 7-19-96 8:14p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.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 1,756 12-21-94 12:43p 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- VOLWRFIX NLM ============ SYMPTOM: VolumeWriteAndWait Function does reads and not writes. VolumeWriteAndWait Function needs to have the disk request flag changed from READREQUEST to WRITEREQUEST. SOLUTION: Apply VOLWRFIX NLM 1,218 12-18-95 3:08p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- WORMROFX NLM ============ SYMPTOM: Currently, if a removable device is initially mounted read/write, and then the cartridge is removed and a new device is inserted that has the write disable tab set, the OS does not recognize that the device is now Read only. This patch fixes this problem. SOLUTION: Apply WORMROFX NLM 978 12-18-95 2: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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- WSDFIX NLM ============ SYMPTOM: This patch fixes a problem with APIs that allow users to access files on volumes where they have no rights. This patch generates a new handle so that rights are re-enumerated with each volume change. SOLUTION: Apply WSDFIX NLM 1,753 12-18-95 2:29p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- WTCHDGFX NLM ============ SYMPTOM: WatchDog cuts off active stations If you set the Delay Before First WatchDog Packet less than or equal to Delay Between WatchDog Packets, the server will blow away any station not making requests. How long it takes depends on the settings. Responder Notes: Patch WtchDgFx.NLM fixes problem for 3.11. SOLUTION: Apply WTCHDGFX NLM 1,465 12-18-95 2:13p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- XMDFIX NLM ============ SYMPTOM: This patch corrects a problem with utilities that use the SPX protocol to maintain communication with the server. Typically the client will loose the connection to the server and the following message will be displayed: "No more response buffers available" The most common occurrence is with a remote printer(RPRINTER.EXE) loosing it's connection to the print server(PSERVER.NLM), but it may happen with other utilities. This is happens when a call to SPXSendSequencedPacket()resets a session retransmit count which causes it to NOT abort the connection if the connection is broken in one direction and maintained in another. SOLUTION: Apply XMDFIX NLM 1,546 12-18-95 1:53p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11 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. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- ADDSRVFX NLM 1,341 12-18-95 1:13p ALERTFIX NLM 1,964 12-18-95 1:53p ASNCRDFX NLM 1,521 12-18-95 2:12p AUDITFIX NLM 1,049 04-17-95 10:59a BCKTTSFX NLM 1,648 07-15-94 8:18a BIGRFIX NLM 1,190 12-18-95 2:25p CLPHFIX NLM 1,238 12-18-95 3:10p DESLOTFX NLM 1,144 04-10-95 10:10a DEVRQFIX NLM 975 12-18-95 3:59p DHANDFX NLM 3,340 12-23-94 11:54a DIAGRFSX NLM 2,150 12-18-95 4:33p DIRLPFIX NLM 1,124 06-20-95 9:10a DIRSPCFX NLM 1,214 02-22-94 3:26p DIRSRCFX NLM 1,090 05-09-94 11:11a DOSUNFIX NLM 1,910 12-19-95 7:29a DOTFIX NLM 1,103 02-12-96 2:25p DTRSTFIX NLM 1,384 12-19-95 7:43a DUPFIX NLM 1,513 12-19-95 7:54a EAALLCFX NLM 1,647 04-04-95 11:58a EADATFIX NLM 1,368 03-28-94 8:46a EAERRFIX NLM 1,020 7-19-96 8:44a EAFLTFIX NLM 1,465 12-21-94 12:36p EAINFIX NLM 2,250 12-19-95 8:02a EAREPLFX NLM 1,324 02-22-94 3:32p EASCORFX NLM 1,393 11-09-93 11:07a EASUBFIX NLM 968 07-26-94 8:20a EAUNIQFX NLM 1,186 11-09-93 11:13a EAWRITFX NLM 1,049 07-26-94 8:25a EVENTFIX NLM 2,498 12-19-95 8:05a EXTATTFX NLM 2,442 01-19-94 3:51p EXTENDFX NLM 1,037 04-10-95 11:09a FATFIX NLM 3,357 12-19-95 8:08a GETQFIX NLM 1,130 12-20-95 1:58p GETRFIX NLM 1,311 12-19-95 9:42a GETSEFIX NLM 1,463 12-19-95 9:50a GLOCKFIX NLM 1,088 12-19-95 10:02a GNSFIX NLM 2,509 12-19-95 10:08a HDUMP NLM 4,393 02-05-96 11:14a HTFXFX NLM 1,036 12-19-95 10:44a IMGCOPY NLM 4,775 09-04-91 8:35a IPXRCVFX NLM 979 02-04-94 8:33a IPXSOCK NLM 3,844 11-22-93 10:59a ITABLEFX NLM 1,792 05-11-95 2:12p MAXCDCFX NLM 962 12-19-95 11:22a MFIXOPEN NLM 1,455 12-19-95 2:17p MIRRFIX NLM 1,242 08-06-93 4:53p MKDIRFIX NLM 2,295 12-19-95 2:33p NCOMFIX NLM 2,109 12-19-95 2:51p NCPCHKFX NLM 1,150 04-05-95 11:45a NCPEXTFX NLM 1,688 05-09-94 11:27a NCPFLTFX NLM 1,794 01-18-94 3:24p NCPSPFIX NLM 1,760 12-19-95 3:40p NFSFIX NLM 2,941 12-19-95 4:07p OBPRGFIX NLM 1,640 12-19-95 3:58p OLDPASS NLM 1,193 12-19-95 4:53p OS2OPNFX NLM 1,385 12-19-95 4:52p PARSEFIX NLM 1,176 02-12-96 2:16p PATCHMAN NLM 15,591 01-22-96 11:22a PPCFIX NLM 1,233 12-19-95 5:15p PRESFIX NLM 1,302 12-19-95 3:47p READQFIX NLM 1,609 08-10-94 4:19p REMDEVFX NLM 1,086 12-19-95 2:58p REMFILFX NLM 1,279 12-19-95 2:46p RENDIRFX NLM 1,188 12-20-95 2:04p RENFIX NLM 1,374 12-19-95 11:14a REPLYFIX NLM 1,145 06-29-93 7:47a REQFIX NLM 1,251 12-19-95 10:48a ROUTE NLM 5,045 01-30-96 4:56p RPLENFX NLM 2,729 12-21-95 2:18p RTRTIME NLM 1,943 12-21-95 7:42a SAPFX NLM 2,380 12-19-95 7:43a SEARCHFX NLM 1,142 04-28-95 2:57p SERVHOPS NLM 1,852 05-10-93 11:36a SHORTAFX NLM 1,010 04-05-95 11:41a SPXACKFX NLM 1,115 01-23-96 2:27p SPXDDFIX NLM 1,151 01-23-96 2:39p SPXFIX2 NLM 1,727 01-23-96 2:41p SPXFSFIX NLM 1,155 12-19-95 7:29a SPXLISFX NLM 1,016 12-19-95 7:13a SPXMSFIX NLM 988 01-23-96 2:45p SPXNSFIX NLM 1,047 01-23-96 2:46p SPXTRMFX NLM 1,058 01-23-96 2:48p SYNCTIME NLM 1,948 05-03-94 5:03p TRSTFIX NLM 1,688 12-18-95 4:57p TTSFIX NLM 1,227 12-18-95 4:49p UNKFIX NLM 955 12-18-95 4:33p UNLCKFIX NLM 1,049 7-19-96 8:14p UNLDIRFX NLM 1,756 12-21-94 12:43p VOLWRFIX NLM 1,218 12-18-95 3:08p WORMROFX NLM 978 12-18-95 2:39p WSDFIX NLM 1,753 12-18-95 2:29p WTCHDGFX NLM 1,465 12-18-95 2:13p XMDFIX NLM 1,546 12-18-95 1:53p