TITLE: NetWare 3.12 OS Patches DOCUMENT ID: DOCUMENT REVISION: A DATE: AUTHOR: Boyd Memmott ALERT STATUS: Yellow DISTRIBUTION: PUBLIC INFORMATION TYPE: Symptom Solution README FOR: 312PTx.EXE NOVELL PRODUCT and VERSION: ABSTRACT: This file contains the latest operating system test patches for NetWare 3.12. Included with this prerelease are all patches for all user-versions of NetWare 3.12. The patches included have been system tested by Novell. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ----------------------------------------------------------------- ADROUTFX NLM ============ SYMPTOM: 3.12 server on network with lots of sap/rip traffic hangs in router code. Is hanging in AgeRouters function. The NetList has a network node that has a 0 id and is not being removed from the list because it cannot find it in the hash table. The hop count is poison 0x10. Stuck in a while loop. SOLUTION: Apply ADROUTFX NLM 1,309 04-10-95 11:14a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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,046 04-17-95 10:54a 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,218 07-15-94 8:26a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- BHANDFIX NLM ============ SYMPTOM: SOLUTION: Apply BHANDFIX NLM 972 10-18-94 12:16p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. BHANDFIX (Bad Handle Fix) fixes a GPPE when proc InternalReadFile in fileio.386 receives a bad handle and jumps to label ReadInvalidHandle: The code at this label has been modified to not set the RALastReadStartOffset field of the fcb to -1. The label is also jumped to when the TNode field of the fcb is 0. Return from InternalReadFile with error code without trying to set field RALastReadStartOffset in FCB Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- CTRSTKFX NLM ============ SYMPTOM: Bug in LSLControlStackFilter functions NetWare v3.1x & v4.0x. SOLUTION: Apply CTRSTKFX NLM 972 12-21-94 12:48p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Problems found with NLA Requests to turn on Promiscuous Mode while HSL.NLM (Hub Support Layer) is loaded (NLA part of the NMS & RMON stuff) causes the server to hand (NW v3.x & NW v4.0x). Problem due to code in LSL function LSLControlStackFilter, at label , have after testing for entries in DefaultChainTable have which should be the line . Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- DAICCFIX NLM ============ SYMPTOM: This patch deals with applications that directly control hardware devices through NetWare (i.e. Jukeboxes, worms, tapes, etc.). If an error condition occurs such as reaching the end of a tape, an error code is returned to the calling application. The error code would be scrambled, resulting in the wrong error passed to the application. The result, as far as the Server (i.e. ABEND, hang, etc.) would depend on the specific application. The patch applies to applications which use a DAI interface to communicate with the server's hardware. Check with the vendor of the application to verify the use of the DAI interface and apply the patch if necessary. SOLUTION: Apply DAICCFIX NLM 1,076 12-18-95 3:04p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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,114 04-10-95 10:13a 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 ----------------------------------------------------------------- DFILTRFX NLM ============ SYMPTOM: Server Abend when loading server with Write Protected Tape in the Tape Driver Netware 3.12J server abend when try to load Server with Write Protected TAPE in the tape drive with following error Message: Abend : General Protection Processor Exception (Error Code 001C0000) OS version: Novell Netware v3.12 (250 User) 8/12/93 Running Process: Server 01 Process EIP 0017731C SOLUTION: Apply DFILTRFX NLM 1,054 02-27-95 10:53a A patch for the Media Manager called DFILTRFX.NLM was written to fix the problem. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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,650 12-23-94 12:04p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- DIRSPCFX NLM ============ SYMPTOM: Disk space can not be accounted for. SOLUTION: Apply DIRSPCFX NLM 1,212 04-26-94 9:06a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- EAACCFIX NLM ============ SYMPTOM: The following Error message: SYS0002 Access Denied is received when trying to copy a file with Extended Attributes from a NetWare v3.12 file server if the users only has Read and FileScan rights. SOLUTION: Apply EAACCFIX NLM 970 04-26-94 9:06a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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,627 04-04-95 12:05p 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,181 04-26-94 4:33p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- 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,309 12-21-94 12:59p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- 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,182 04-26-94 9:00a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- EASUBFIX NLM ============ SYMPTOM: When copying a long directory with EA's and only have R F rights the server returns 140 error. SOLUTION: Apply EASUBFIX NLM 965 07-26-94 7:44a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- 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,048 07-26-94 7:48a Change procedure OpenEAHandle to check for WriteExistingFileBit if the user does not have ModifyEntry rights. If the user does have WriteExistingFile rights he is granted Write and Read Privileges. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EAWRNFX NLM ============ SYMPTOM: The server was running out of allocated storage space for extended attributes without warning. SYMPTOM: The user is unable to manage extended attribute storage space in any given NetWare volume. SYMPTOM: There is a lack of extended attribute management functions. SOLUTION: Apply EAWRNFX NLM 4,518 02-12-96 11:57a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. EAWRNFX.NLM addresses issues with the management of EA's or Extended Attributes on a NetWare volume. Using this NLM will allow the user to control the amount of volume space allowed for EA storage on a volume. It will also alert users and the error log as to when space for EA storage is running low. After EAWRNFX is loaded two additional settings are available. To see these settings, type EA STATS at the server console prompt. The following information will be displayed: ----------------------------------------------------------- EA WARNING BROADCAST PERCENT = 85 EA WARNING BROADCAST INTERVAL = 1 min. VOLUME NAME % ALLOWED % USED OF ALLOWED [SYS] 30 1 [JUMBO] 30 45 ----------------------------------------------------------- EA WARNING BROADCAST PERCENT = 85 This statement depicts the level at which a warning would be broadcast. When 85 percent of the allotted volume space for EA's is utilized, a warning will be broadcast. To set this amount to 75 percent, you should typed the following at the console prompt or insert it in the AUTOEXEC.NCF file: EA WARNING BROADCAST PERCENT = 75 EA WARNING BROADCAST INTERVAL = 2 min. This statement depicts how often the warning broadcast will be sent to the network. To set this amount to 5 minutes the following would be type at the console prompt or inserted in the AUTOEXEC.NCF file: EA WARNING BROADCAST INTERVAL = 5 % ALLOWED The % ALLOWED statement to the right of the screen depicts the percentage of volume space allowed for EA storage. % USED OF ALLOWED The % USED OF ALLOWED depicts the percentage of the space allocated for EA storage that has been used. Additional information: The % USED OF ALLOWED field depicts a high water mark for EA storage on the volume in question. If, for example, this value hits 90 percent and half of these files are deleted, the value will remain at 90 percent until the volume is purged. After the volume is purged, the value would return to 45 percent. However, it is important to understand that EA's are stored as extended directory entries and after the space has been used for EA storage, it can never be reused for common file storage unless the volume is re-initialized. After EA related data has been purged, that purged area can be reused for EA storage in the future. Installation Instructions: NCF FILE: STARTUP.NCF 1. For this patch to function correctly, a patch by the name of DIRSPCFX.NLM must also be applied. DIRSPCFX.NLM corrects a problem in the directory entry table with extended attribute and directory usage on a NetWare volume. It is explained in detail in its own field test file. 2. For EAWRNFX.NLM to function correctly, all three files must be used! All three files should be copied to the DOS partition from where SERVER.EXE is booted. These files should be loaded from STARTUP.NCF, probably on the last three lines, in the following manner: LOAD PM312.NLM LOAD DIRSPCFX.NLM LOAD EAWRNFX.NLM PERCENT = 30 The PERCENT = 30 parameter can take the place of the SET MAXIMUM PERCENT OF VOLUME SPACE ALLOWED FOR EXTENDED ATTRIBUTES = 30 command that would be commonly found in the AUTOEXEC.NCF file. Setting this parameter in the STARTUP.NCF before the SYS: volume loads allows the SYS: volume to benefit from the setting. The value 30 is an arbitrary setting for this example. ----------------------------------------------------------------- ELEVFIX NLM ============ SYMPTOM: A window exist where two identical requests to access the same sector on the hard disk could get placed in the elevator queue at the same time resulting in a file server lock up. The file server may possibly hang when a system is in the process of re-mirroring and when there is extremely high I/O traffic on the bus. SOLUTION: Apply ELEVFIX NLM 1,717 04-26-94 9:08a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- EVNTRPFX NLM ============ SYMPTOM: Going to real mode an return from real mode events are not generated while the debugger is active. SOLUTION: Apply EVNTRPFX NLM 1,008 01-18-96 10:59p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- GETNSPFX NLM ============ SYMPTOM: GetOriginalNameSpace could not find the original name space errors on the server console. SOLUTION: Apply GETNSPFX NLM 1,317 02-13-96 8:30a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 02-12-96 11:20a 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 1,099 03-28-94 8:47a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- GTALLYFX NLM ============ SYMPTOM: Server ABEND when out of memory. SOLUTION: Apply GTALLYFX NLM 1,490 10-18-94 12:42p Set pointer to NULL when struct is allocated and the check for NULL before calling free. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- HFFIX NLM ============ SYMPTOM: The Server will hang if there is data lost after a HOTFIX. SOLUTION: Apply HFFIX NLM 1,054 05-26-94 11:46a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- IOHANDFX NLM ============ SYMPTOM: On releasing IO handles, the OS does not clean up the application link field. Do the following steps to reproduce the problem: 1. Load CDROM.NLM on a 3.12 server with a CD-ROM. 2. CD MOUNT # (to mount the CD). 3. CD CHANGE # ( to mount a different CD). 4. Take the CD out at the prompt and press any key to continue. 5. Unload CDROM.NLM. 6. Load CDROM.NLM. You can repeat steps 5 and 6 after putting a CD back into the device and the CD can no longer be seen until the disk driver is unloaded and loaded again. SOLUTION: Apply IOHANDFX NLM 1,070 05-26-94 11:41a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- IPXRCVFX NLM ============ SYMPTOM: These patches fix a problem with receiving a GPPE ABEND because of the generation of an NCP request that IPX.386 did not handle correctly, thus causing an invalid fragment count. A problem has been encountered with the NetWare SFT III operating system that is produced by Running ARCServe 4.0 on one of the mirrored NetWare SFT III servers. If ARCServe is backing up a file to the tape and the secondary server restarts for any reason, upon re-synchronizing the memory the operating system will ABEND with a General Protection Processor Exception (GPPE) error. This error only occurs if a file is being copied to the tape at the time. If ARCServe is loaded but not in the process of copying a file to tape, then the problem is not apparent. CAUSE The problem is that an NCP request is generated that IPX.386 did not handle correctly, causing an invalid fragment count that would bring down the primary server. Because the primary server is being re-mirrored to the secondary server, the secondary server dies as well. SOLUTION: Apply IPXRCVFX NLM 976 04-26-94 9:04a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V3.11 SFT III Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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,971 09-20-95 3:24p 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. ----------------------------------------------------------------- LSLUNBFX NLM ============ SYMPTOM: When unloading Madge driver, user receives error message: TCP - unrecognized parameter 'xxx' (where xxx is always three extended ASCII characters). ESI is expected to point to command line parameters for the Unbind command. This unbind results from the unload of the board and there are no command line parameters. However, ESI is not zero and TCPIP interprets the value as a pointer to the parameters. LSL is not clearing ESI, or is only clearing it when the first stack is unbound, when the unbind is caused by the unload of a board. ESI needs to be cleared before calling the protocol with unbind in this case. The problem is in the LSL call , the register ESI contains bogus values before the call to the Protocol Stack Control Entry point to UNBIND, ESI should point to a string or zero. ESI should be set to zero before making the call to the Protocol Stack, ie. . This fix has already been made in the NetWare v4.10 LSL code base. The same fix needs to be made to the NetWare v3.12 and v4.0x LSL code bases. SOLUTION: Apply LSLUNBFX NLM 1,035 12-21-94 1:19p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- LSTECBFX NLM ============ SYMPTOM: Lost ECB's when running endurance tests with packet signing. When running endurance tests with packet signing on, the IPX protocol stack will get into a state where ECB's will start to be lost. The problem occurs when two packets arrive at the same time. The second one will be lost. This problem is unique to 3.12. It was a result of some optimization that took place. The problem does not occur in 4.00 or later, nor does it happen in 3.11 with PBURST.NLM loaded. SOLUTION: Apply LSTECBFX NLM 1,302 07-26-94 7:51a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MACNMFX NLM ============ SYMPTOM: Mac File Move Results in Invalid DSubdirectory field in the Directory Handle. SOLUTION: Apply MACNMFX NLM 1,086 08-12-96 3:29a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MMACCFIX NLM ============ SYMPTOM: The workstation will hang while performing reads from the file server. High (100%) utilization at the server console. By typing "scan for new devices" at the console prompt the high utilization drops but will climb back up over time. SOLUTION: Apply MMACCFIX NLM 1,006 04-26-94 8:54a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. MMACCFIX.NLM fixes this condition by patching the media manager accelerator module of the NetWare 4.01 OS code. This patch is recommended for general application on all 4.01 NetWare servers. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- MMHANDFX NLM ============ SYMPTOM: The ability to mark a disk device as handicapped, thus causing reads to always go to the non-handicapped mirror does not work. SOLUTION: Apply MMHANDFX NLM 3,123 02-13-96 8:26a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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,147 04-05-95 11:48a 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 ----------------------------------------------------------------- NCPXTNFX NLM ============ SYMPTOM: Registration of NCP extensions does not work SOLUTION: Apply NCPXTNFX NLM 1,638 11-21-95 2:49p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- NPAPATCH NLM ============ SYMPTOM: The NPAPATCH.NLM is a patch module for NetWare 3.12. It patches the OS loader to accept .HAMs and .CDM. SOLUTION: Apply NPAPATCH NLM 2,516 08-12-96 1:50a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- PBWANFIX NLM ============ SYMPTOM: WAN links saturated with packets. SOLUTION: Apply PBWANFIX NLM 3,028 04-19-94 9:41a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Description of problem addressed by PBWANFIX.NLM. Due to the nature of packet burst, it is very easy to saturate WANS with packets that have already been sent and arrived correctly. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- PM312 NLM ============ SYMPTOM: SOLUTION: Apply PM312 NLM 14,825 02-05-96 11:19a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. This README file accompanies PM312.NLM. The following files are included for this revision: PM312.NLM replaces any and all previous versions of PM312.NLM. PM312.NLM is the Patch Manager which tracks and manages all official patches for NetWare 386 v3.12. Installation Instructions: NCF FILE: STARTUP.NCF Patches for NetWare 386 v3.12 consist of three types: DYNAMIC -- Dynamic patches are implemented as .NLM files that can be loaded/unloaded while the server is running. Unloading a dynamic patch will restore the Operating System to its original "un-patched" state. SEMI-STATIC -- Semi-static patches can also be loaded while the server is running, but they cannot be unloaded. It is not possible to undo the effects of a semi-static patch without first downing the server and bringing it back up without loading the semi-static patch. STATIC -- A static patch is a DOS executable program that modifies the SERVER.EXE file. This type of patch is applied once and its effects are permanent. It is suggested that a backup of the original SERVER.EXE file be made before applying a static patch. (In other words, do not patch the SERVER.EXE on your original distribution diskette!) Dynamic and semi-static patches modify the Operating System in memory, not on the disk. This means that dynamic and semi-static patches must be loaded each time the Operating System is brought up in order for any 'fixes' to take effect. It is recommended that the command "LOAD " be placed in the file server's AUTOEXEC.NCF file to ensure that the patch is always in effect as soon as the server is brought up. In order to see which patches are currently loaded on the system, type "PATCHES" at the file server command line. The patches will then be grouped and displayed according to their type (i.e. - STATIC, SEMI-STATIC, or DYNAMIC). Typing "MODULES" at the server console will show which dynamic patches have been loaded, but will not show semi-static or static patches. To install PM312.NLM, log into the server as supervisor or supervisor equivalent and copy PM312.NLM into the SYS:SYSTEM subdirectory. The Patch Manager (PM312.NLM) must be loaded before any dynamic or semi-static patches can be loaded. If PM312 is not already loaded, the .NLM will attempt to locate PM312 and, if found, will load it automatically. PM312 only needs to be loaded once; all NLM patches can then be loaded. PM312 cannot be unloaded until all patches that rely on it are first unloaded. ***************************************************************** DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. ***************************************************************** ----------------------------------------------------------------- READQFIX NLM ============ SYMPTOM: When a Queue is full, the File Server will get into an infinite loop trying to service Queue Management System (QMS) requests. Note that PCONSOLE makes QMS requests for building a list of jobs, inserting and deleting print jobs, as well as inserting and deleting print queues. Symptoms observed when this problem occurs include, but are not limited, to utilization up to 96 %, users loosing connections and Packet Receive Buffers count going high. SOLUTION: Apply READQFIX NLM 1,612 08-10-94 4:37p By applying READQFIX.NLM, the file server can correctly process a QMS request for a queue which is full. Note that if a queue is full prior to loading READQFIX, the following error message may appear on the console at any time after loading READQFIX. "WARNING: Error detected in Queue. ID=xxxxxxxx" If this happens the queue with the given ID number should be deleted and recreated. Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- REALMFIX NLM ============ SYMPTOM: This patch deals with applications that directly control hardware devices through NetWare (i.e. Jukeboxes, worms, tapes, etc.). If an error condition occurs such as reaching the end of a tape, an error code is returned to the calling application. The error code would be scrambled, resulting in the wrong error passed to the application. The result, as far as the Server (i.e. ABEND, hang, etc.) would depend on the specific application. The patch applies to applications which use a DAI interface to communicate with the server's hardware. Check with the vendor of the application to verify the use of the DAI interface and apply the patch if necessary. Application requests made to a device driver using the device IOCTL and DeviceBlockingIOCTL API's are aborted if NetWare is in the process of switching to real mode. Application requests made to a device driver using the DeviceIOCTL and DeviceBlockingIOCTL API's are aborted if NetWare is in the process of switching to real mode (i.e. the DOS Mode semaphore is set). The API's should instead delay the execution of the request. FIXED 2 DAI emulation bugs. Fixed the device IOCTL routine to return the driver specified error code instead of the media manager code. Fixed the IOCTL routines to postpone the execution of the IOCTL if the DOSDiskSemaphore is set instead of returning with an error. SOLUTION: Apply REALMFIX NLM 2,920 02-12-96 11:30a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- REGOBJFX NLM ============ SYMPTOM: Generic Info Valid bit not set for non-media objects Device, magazine, etc. objects don't set the valid bit in the status field. This causes an Media Manager application to loop forever waiting the in information be become "valid". SOLUTION: Apply REGOBJFX NLM 1,035 05-26-94 1:06p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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,134 09-05-95 10:19a 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 ----------------------------------------------------------------- RKIELFIX NLM ============ SYMPTOM: Message Correction for the following ABEND Message: "Richard Kiel memorial ABEND #27" SOLUTION: Apply RKIELFIX NLM 1,044 05-04-94 2:38p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. The new ABEND message is "Invalid entry in message list.". In the OS there is a process that checks the consistency of the message list. When this list is found to be invalid the OS will return this ABEND message. Follow the Guidelines for troubleshooting in the System Messages Manual Appendix "A". Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- RTCHGFIX NLM ============ SYMPTOM: This patch fixes a problem with packet signing after a switch over occurs on either an SFT III server or a router switch over (i.e. networks with redundant routes). When the switch over occurs the packet size would be renegotiated between the server and the workstation. The server in would send unsigned packets to the workstation during the renegotiation process. The workstation, expecting signed packets will discard all of the packets from the server attempting the renegotiation. The workstation would eventually timeout or appear to be hung. The key to the patch is that packet signing would have to be enabled or order for this problem to happen. SOLUTION: Apply RTCHGFIX NLM 984 12-18-95 2:41p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. 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 2,018 02-12-96 11:18a 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 1,970 12-18-95 1:50p 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 ============ SRCIOFIX NLM SRCMSFIX 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,145 04-28-95 3:03p 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,891 04-06-94 1:39p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- SHRRAMFX NLM ============ SYMPTOM: With many of the new ATM cards coming out, the one megabyte provided by the server will not be sufficient. Some of these new cards will need the ability to have 4 to 16 megaytes of shared memory. Now the number of Memory Mapped paragraphs for a LAN adapter can be the number of pages if the proper bit is set in the shared flags. This allows ATM and other memory hungry adapters to allocate very large mapped (shared) memory address ranges. SOLUTION: Apply SHRRAMFX NLM 3,432 01-08-96 11:41a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SIGLOGFX NLM ============ SYMPTOM: NWP_LOGIN when password has expired in bindery corrupts connection. SOLUTION: Apply SIGLOGFX NLM 1,159 12-21-94 1:06p Solutions Specifics: Servers 4.02 and 3.12 Signature level 1 Client VLMS dated 5-26-94 Signature level 2 Login 4.084 and 4.093 Login SPD 70145 Create user (TEST), assign a password and expire that password but have grace logins available. Login to user DS mode "LOGIN server/TEST" When asked to change password, reply N. Login to user bindery mode "Login server/TEST /B". You will get Abort, Retry, Fail error. All you can do is reply F. Then Login gets several 8801 errors, invalid connection. Server gets "Server 4.0-2506 AnNCP request with an invalid security signature was received from user TEST.... Possible intruder or network is corrupt." When the API calls VLM with NWP_LOGIN, everything after this fails. From CodeView, the VLM request is made, then CodeView is exited. The server gets several beeps and error messages then the dos prompt "invalid drive.." is displayed. Login works in this situation if NETX.EXE is used The problem we are seeing is that certain NCP packets do not function properly on the server side with signing turned on. In this case it is a PING FOR NDS packet. During a BINDERY Login to a 4.x server after the KEYED LOGIN NCP is sent and returned, a PING is sent with signing turned on. The server does one of two things in response: 1) It will either respond to the ping with no signing, in which case the client will fail the Login because signing is required; or 2) it will output intruder alert messages at the console and never respond to the ping. This happens using the 4.x LOGIN.EXE when doing a BINDERY emulation Login. Using a 3.x Login for BINDERY does not do the ping and therefore succeeds. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- 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.12 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 312pt9.exe corrected this problem. We are investigating the problems with this patch. 2.) Unloading SPXTRMFX.NLM from 312pt9.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,148 01-23-96 2:51p 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,035 01-23-96 2:52p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 ----------------------------------------------------------------- SPXNSFIX NLM ============ SYMPTOM: If the session did not exist, SPX failed to interpret terminate ACKs as system packets. SOLUTION: Apply SPXNSFIX NLM 1,044 01-23-96 2:55p 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.12 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 312pt9.exe corrected this problem. We are investigating the problems with this patch. 2.) Unloading SPXTRMFX.NLM from 312pt9.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,115 09-23-96 1:43p 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 ----------------------------------------------------------------- SYNCMFIX NLM ============ SYMPTOM: One drive off of one HBA is mirrored to two drives both of which are on the other HBA. (A total of 3 drives mirroring the same data). The single drive off of the first HBA is in sync and the other two drives off of the second HBA are mirrored to the first drive. The server is downed while the two secondary mirrored drives are still out of sync, (install NLM shows them still to be in the mirroring process). When SERVER.EXE is invoked, INSTALL.NLM shows the primary drive as In Sync and one of the secondary drives as In Sync and the other as Out Of Sync. The two secondary drives are the only ones showing disk activity as if they are mirroring each other and ignoring the actual in sync primary drive. SOLUTION: Apply SYNCMFIX NLM 1,025 04-26-94 8:58a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. The problem is resolved by loading the SYNCMFIX.NLM patch. You must load the patch manager and the SYNCMFIX.NLM in the STARTUP.NCF before the disk driver or move the disk driver load statements to the AUTOEXEC.NCF and have them loading after the patch manager and the SYNCMFIX.NLM patch. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- SYNCTIME NLM ============ SYMPTOM: The file server may gain or loose time, after a operating for a while. CAUSE: The FileServer time is by default taken from the software clock which is subject to lost timer ticks which may cause the server to loose time. SOLUTION: Apply 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: 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. ----------------------------------------------------------------- TRBUFFIX NLM ============ SYMPTOM: Transfer buffer sequence number are returned out of order-causing data corruption FIXED a problem in the elevator-off code where the requests were being serviced LIFO instead of FIFO. SOLUTION: Apply TRBUFFIX NLM 1,059 05-26-94 12:57p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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,971 12-21-94 1:24p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.11, V3.12, V4.01 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- UNLOADFX NLM ============ SYMPTOM: NLM'S dynamically importing can ABEND if not unloaded in same order. The OS needs a patch to check for a NULL pointer on unload. SOLUTION: Apply UNLOADFX NLM 992 12-18-95 1:38p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- VOLMTFIX NLM ============ SYMPTOM: If HD volumes and CDROM volumes mounted and if a HD volume is dismounted (must only be one volume per HD and a volume other than SYS), the HD volulme re-mount until the Cd volume is dismounted. The message is that reported to the console is: "SOME OR ALL VOLUME SEGMENTS COULD NOT BE FOUND". If the HD has more than one volume on it and only one volume is dismounted, then the volume will remount without a problem.. If however all the volumes are dismounted on the HD then the locked or reserved status changes and the volumes are then un-mountable. SOLUTION: Apply VOLMTFIX NLM 1,027 08-10-95 1:03p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. 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 1,061 04-10-95 11:11a 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 ----------------------------------------------------------------- WRLENFIX NLM ============ SYMPTOM: WRLENFIX.NLM (Write Length Fix) fixes an illegal NETX packet which requests to write over the 4 gig boundary (i.e. start offset = -1, bytes to write = 2). To stop the ABEND we truncate the length of the write just like the VLM's do so there is no wrap condition. SOLUTION: Apply WRLENFIX NLM 1,087 12-21-94 1:23p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.02 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- WSMSGFIX NLM ============ SYMPTOM: This patch fixes a problem with WS's when sending double byte broadcast messages. The double byte characters would get cut in half. To reproduce the problem: 1) Login from 2 workstations. 2) From one of the workstation send an double-byte message which is longer than 55 bytes to the other workstation. send "XXXXXXXXX..........." to STATION_ID XXXXXXXXXX.... is a double byte message longer than 55 bytes. 3) At the recipient workstation press Ctrl and ENTER key to clear the first part of the message. 4) The second part of the message appears on the recipient, but the message is collapsed. This is not a utility problem, but rather a server problem. When the message is too long to be displayed on the screen, the server divides the message without checking to see whether-or-not the character is double-byte. If the division takes place on the second half of a double-byte character, the characters displayed are changed. Double-byte characters must not be split. SOLUTION: Apply WSMSGFIX NLM 1,132 12-18-95 1:20p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- CON0PBFX NLM ============ SYMPTOM: Packets type 7777 with connection 0 will Abend the server. SOLUTION: Apply CON0PBFX NLM 1,158 04-09-96 10:43a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- LOADER EXE ============ SYMPTOM: 1) FIXED the defaultGlobalDataPDE so that the accessed bit will always be set. This fixes the problem where it does a TLB flush on every interrupt (VERY EXPENSIVE - over 1,000 clocks each on a pentium) 2) FIXED the HighResolutionTimer and the SuperHighResolutionTimer so that they use the RDTSC instruction if the CPU supports it and then converts the result to the desired granularity. This gets the clock counter from the CPU instead of going out on the bus to the external timer chip. 3) ADDED support for using the new BIOS call int 15 sub function E8 for memory detection on PCI machines and other ISA machines that have more that 64 Meg of memory. 4) FIXED the Pentium (TM) check code so that that interrupts are disabled. 5) FIXED the machine check exception so that it will be enabled at a later point. It is being turned on before installing the exception handler while the operating system is still in real mode. Also added a new command line parameter "-m" which will cause the OS to not turn on the machine check enable bit in CR4. This used to cause the machines to hang or reboot. Now they will at least get the exception message, and they can disable it by using the new "-m" command line option. 6) FIXED LDOSWrite so that it will do a movsd followed by a movsb. This should help the performance of coredumps. 7) FIXED the machine check exception handling so that now it will actually turn on the exception and see if a exception is returned immediately, if it does return a exeptiion, it is turned off and left off - so it will auto detect whether or not the machine can support having it on. The '-m' command line option is still supported. 8) ADDED a new table '_CPR' for CPR so that a loader can be linked to a specific version of the OS. Also linked a record onto the server's internal public list that will point to the loader's public list so that CPR can more easily patch the loader. 9) FIXED the reprogramming of the PIC so that we check for edge sensitive micro-channel machines. 10) FIXED problems with GetSharedMemoryLinearAddress where it was having problems dealing with shared memory addresses above 0xC8000000 - note that this is used by RegisterHardwareOptions which many LAN drivers call. The problems are: 1 - not handling multiple regions in the same IOConfig structure - it would return overlapping logical addresses. 2 - The logical address it would return would always be 4K aligned even if the physical address wasn't. And 3 - If the region crossed N number of pages, but the size rounded up to the nearest page size was (N - 1) pages, it would not reserve enough space - sometimes causing a page fault and always not reserving enough space. 11) ADDED support for calling through the PSM when a spurious interrupt is returned to the EIO on the APIC or whatever hardware may be tied into the PSM interface. 12) CHANGED the real mode interface so that it doesn't rely on the limit to GS being preserved while we are in real mode. Note that it was a problem when running on machines that were also running NIOS. 13) ADDED the new DoProtectedModeBIOSCall to the loader for use by ODI with new PCI device drivers. This API allows a driver to make protected mode calls to the BIOS. 14) CHANGED the makefile so that it will make a DOSV version JLOADER.EXE as well as the standard version LOADER.EXE. SOLUTION: Apply LOADER EXE 67,284 03-27-96 11:20a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.10 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. See LSWAP.NLM or LSWAP.EXE for installation intructions. ----------------------------------------------------------------- LSWAP NLM ============ SYMPTOM: SOLUTION: Apply LSWAP NLM 45,252 07-19-95 10:30a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.10 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 for LOADER.EXE: LOADER.EXE replaces the LOADER in both Native NetWare 4.10 as well as NetWare v4.10 SFT III. LOADER.EXE is a STATIC patch and should only be applied ONCE per SERVER.EXE or MSERVER.EXE. There are two utilities that will replace the LOADER (LSWAP.EXE or LSWAP.NLM). Use LSWAP.EXE if the server is down.. Use LSWAP.NLM if the server is up and running. To make LOADER.EXE active after running LSWAP.NLM, the server must be DOWNed , EXIT, and run SERVER.EXE. Both LSWAP.EXE and LSWAP.NLM use the same cammandline options. First option specifies the location to LOADER.EXE. (DEFAULT:C:\NWSERVER\LOADER.EXE). The second option spcecifies location to SERVER.EXE or MSERVER.EXE. (DEFAULT: C:\NWSERVER\SERVER.EXE). EXAMPLE: LSWAP C:\NWSERVER\LOADER.EXE C:\NWSERVER\SERVER.EXE DEFAULT:(C:\NWSERVER\LOADER.EXE) DEFAULT:(C:\NWSERVER\SERVER.EXE) or LOAD LSWAP C:\NWSERVER\LOADER.EXE C:\NWSERVER\SERVER.EXE DEFAULT:(C:\NWSERVER\LOADER.EXE) DEFAULT:(C:\NWSERVER\SERVER.EXE) NOTE: LOADER.EXE is a STATIC patch and should only be aplied once per SERVER.EXE or MSERVER.EXE ----------------------------------------------------------------- LSWAP EXE ============ SYMPTOM: SOLUTION: Apply LSWAP EXE 40,888 07-19-95 10:30a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.10 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 for LOADER.EXE: LOADER.EXE replaces the LOADER in both Native NetWare 4.10 as well as NetWare v4.10 SFT III. LOADER.EXE is a STATIC patch and should only be applied ONCE per SERVER.EXE or MSERVER.EXE. There are two utilities that will replace the LOADER (LSWAP.EXE or LSWAP.NLM). Use LSWAP.EXE if the server is down.. Use LSWAP.NLM if the server is up and running. To make LOADER.EXE active after running LSWAP.NLM, the server must be DOWNed , EXIT, and run SERVER.EXE. Both LSWAP.EXE and LSWAP.NLM use the same cammandline options. First option specifies the location to LOADER.EXE. (DEFAULT:C:\NWSERVER\LOADER.EXE). The second option spcecifies location to SERVER.EXE or MSERVER.EXE. (DEFAULT: C:\NWSERVER\SERVER.EXE). EXAMPLE: LSWAP C:\NWSERVER\LOADER.EXE C:\NWSERVER\SERVER.EXE DEFAULT:(C:\NWSERVER\LOADER.EXE) DEFAULT:(C:\NWSERVER\SERVER.EXE) or LOAD LSWAP C:\NWSERVER\LOADER.EXE C:\NWSERVER\SERVER.EXE DEFAULT:(C:\NWSERVER\LOADER.EXE) DEFAULT:(C:\NWSERVER\SERVER.EXE) NOTE: LOADER.EXE is a STATIC patch and should only be aplied once per SERVER.EXE or MSERVER.EXE ----------------------------------------------------------------- MMMIRRFX NLM ============ SYMPTOM: OS tries to abort/remirror repeatedly when drive #0 fails, instead of still being operational. When drive #0 fails due to bad cable/disk the OS goes into a loop trying to remirror partition #0 and then aborts the remirror of partition #0. SOLUTION: Apply MMMIRRFX NLM 1,075 03-19-96 3:07p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.10 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 ----------------------------------------------------------------- ZEROBFIX NLM ============ SYMPTOM: The NETWARE_312 cd is mounted on the server. If you search all documents twice the server no longer broadcasts the 1.1.44 error writing to FAT message but it will abend the file server. The Abend message is: Abend: AllocateDiskBlock allocated a block that was not really available SOLUTION: Apply ZEROBFIX NLM 1,054 03-18-96 7:44p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12 Example: v3.11 is in 311ITx.EXE or 311PTx.EXE, v3.12 is in 312ITx.EXE or 312PTx.EXE, v4.01 is in 401ITx.EXE or 401PTx.EXE, v4.02 is in 402ITx.EXE or 402PTx.EXE. v4.10 is in 410ITx.EXE or 410PTx.EXE. v3.11 SFT is in SFTITx.EXE. Installation Instructions: NCF FILE: STARTUP.NCF ----------------------------------------------------------------- ADROUTFX NLM 1,309 04-10-95 11:14a AUDITFIX NLM 1,046 04-17-95 10:54a BCKTTSFX NLM 1,218 07-15-94 8:26a BHANDFIX NLM 972 10-18-94 12:16p CON0PBFX NLM 1,158 04-09-96 10:43a CTRSTKFX NLM 972 12-21-94 12:48p DAICCFIX NLM 1,076 12-18-95 3:04p DESLOTFX NLM 1,114 04-10-95 10:13a DFILTRFX NLM 1,054 02-27-95 10:53a DHANDFX NLM 3,650 12-23-94 12:04p DIRSPCFX NLM 1,212 04-26-94 9:06a EAACCFIX NLM 970 04-26-94 9:06a EAALLCFX NLM 1,627 04-04-95 12:05p EADATFIX NLM 1,181 04-26-94 4:33p EAFLTFIX NLM 1,309 12-21-94 12:59p EAREPLFX NLM 1,182 04-26-94 9:00a EASUBFIX NLM 965 07-26-94 7:44a EAWRITFX NLM 1,048 07-26-94 7:48a EAWRNFX NLM 4,518 02-12-96 11:57a ELEVFIX NLM 1,717 04-26-94 9:08a EVNTRPFX NLM 1,008 01-18-96 10:59p GETNSPFX NLM 1,317 02-13-96 8:30a GLOCKFIX NLM 1,088 02-12-96 11:20a GNSFIX NLM 1,099 03-28-94 8:47a GTALLYFX NLM 1,490 10-18-94 12:42p HFFIX NLM 1,054 05-26-94 11:46a IOHANDFX NLM 1,070 05-26-94 11:41a IPXRCVFX NLM 976 04-26-94 9:04a IPXSOCK NLM 3,971 09-20-95 3:24p LOADER EXE 67,284 03-27-96 11:20a LSLUNBFX NLM 1,035 12-21-94 1:19p LSTECBFX NLM 1,302 07-26-94 7:51a LSWAP NLM 45,252 07-19-95 10:30a LSWAP EXE 40,888 07-19-95 10:30a MACNMFX NLM 1,086 08-12-96 3:29p MMACCFIX NLM 1,006 04-26-94 8:54a MMHANDFX NLM 3,123 02-13-96 8:26a MMMIRRFX NLM 1,075 03-19-96 3:07p NCPCHKFX NLM 1,147 04-05-95 11:48a NCPXTNFX NLM 1,638 11-21-95 2:49p NPAPATCH NLM 2,516 08-12-96 1:50a PBWANFIX NLM 3,028 04-19-94 9:41a PM312 NLM 14,825 02-05-96 11:19a READQFIX NLM 1,612 08-10-94 4:37p REALMFIX NLM 2,920 02-12-96 11:30a REGOBJFX NLM 1,035 05-26-94 1:06p RENDIRFX NLM 1,134 09-05-95 10:19a RKIELFIX NLM 1,044 05-04-94 2:38p RTCHGFIX NLM 984 12-18-95 2:41p RTRTIME NLM 2,018 02-12-96 11:18a SAPFX NLM 1,970 12-18-95 1:50p SEARCHFX NLM 1,145 04-28-95 3:03p SERVHOPS NLM 1,891 04-06-94 1:39p SHRRAMFX NLM 3,432 01-08-96 11:41a SIGLOGFX NLM 1,159 12-21-94 1:06p SPXACKFX NLM 1,112 01-23-96 2:48p SPXDDFIX NLM 1,148 01-23-96 2:51p SPXFIX2 NLM 1,035 01-23-96 2:52p SPXNSFIX NLM 1,044 01-23-96 2:55p SPXTRMFX NLM 1,055 01-23-96 2:49p SYNCMFIX NLM 1,025 04-26-94 8:58a SYNCTIME NLM 1,948 05-03-94 5:03p TRBUFFIX NLM 1,059 05-26-94 12:57p UNLDIRFX NLM 1,971 12-21-94 1:24p UNLOADFX NLM 992 12-18-95 1:38p VOLMTFIX NLM 1,027 08-10-95 1:03p WORMROFX NLM 1,061 04-10-95 11:11a WRLENFIX NLM 1,087 12-21-94 1:23p WSMSGFIX NLM 1,132 12-18-95 1:20p ZEROBFIX NLM 1,054 07-18-96 7:44p