----------------------------------------------------------------- ----------------------------------------------------------------- ACTMDLFX NLM ============ SYMPTOM: Concurrent loading of multiple load NLM fails. SOLUTION: Apply ACTMDLFX NLM 1,195 09-23-96 12:44p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- AUDCONFX NLM ============ SYMPTOM: Audit records continue to be logged after overflow if the Disable Event Record is selected. SOLUTION: Apply AUDCONFX NLM 1,066 10-02-96 2:24p Solution Specifics: Added a patch which checks if the volume is in overflow and the Discard Record Option is active. If the check passes then the patch returns to the exit in WriteAuditDataRecord. Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- AUDDELFX NLM ============ SYMPTOM: Only the directory path is reported by Auditcon for the Delete File audit records. SOLUTION: Corrected the audit record generation for A_EVENT_DELETE_DIRECTORY, A_EVENT_DELETE_FILE, A_EVENT_SALVAGE_FILE, and A_EVENT_PURGE_FILE to NOT null terminate the directory string before appending the filename. Apply AUDDELFX NLM 1,121 10-02-96 1:50p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- AUDOVFFX NLM ============ SYMPTOM: Audit records continue to be logged after overflow if the Disable Event Record is selected. _ SOLUTION: Added a patch which checks if the volume is in overflow and the Discard Record Option is active. If the check passes then the patch returns to the exit in WriteAuditDataRecord. _ Apply AUDOVFFX NLM 1,143 10-02-96 2:11p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- AUDRESFX NLM ============ SYMPTOM: The patch fixes a problem in certain situations the overflow portion of audit file was not getting truncated during reset. This causes Auditcon to hang and/or GPF when viewing the old audit file. SOLUTION: The patch removed the audit file header "mashing" and the truncation of the audit file (the truncation truncates the unused portion of the pre-allocated overflow file) from ResetAuditDataFile. The routines which call ResetAuditDataFile (EnableVolumeAuditing and ResetAuditFile) were changed to save the oldAuditFileSize in a local variable and call a new routine TruncateOldAuditFile just befor the old audit file is closed. Apply AUDRESFX NLM 1,899 11-11-96 12:48p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- DFSCCHFX NLM ============ SYMPTOM: A problem occurs when a DFS file size is increased and the newly acquired block was recovered from a recently deleted file still being represented in the NetWare disk cache and is marked as dirty (or needs to be written to disk), and the cache block is written to by DFS before the cache subsystem performs it's periodic update. The effect is that if the newly expanded DFS file area is written to and then read back, the read data will not match the written data. Opening a file in DFS mode evacuates that file from NetWare cache. New disk blocks are acquired as the DFS file size is increased. New disk blocks are acquired from a list of free blocks. The disk blocks on the free block list either never been assigned to any file, or they are recovered from deleted files. Blocks from recently deleted files may still be represented in cache. SOLUTION: This has been fixed by having DFS verify that newly acquired blocks, obtained while expanding a file, are evacuated from the NetWare disk cache. SYMPTOM: A problem occurs when a DFS file size is increased and written to in a non-sequential mode, causing the formation of a sparse file. The effect is that data previously written to the to the DFS file might be zeroed out by subsequent writes to adjacent blocks. It is possible write to a file in DFS mode in a manner that causes the file to become a NetWare sparse file (ether by creating a new file or extending an existing file). As a security measure, the newly acquired disk blocks are zeroed out before use. SOLUTION: This problem has been fixed by changing the method of zeroing out the newly acquired disk blocks. ********************************************************** Technology Background: ********************************************************** NetWare Disk Caching Subsystem Description NetWare's disk caching subsystem technology decreases data access time for frequently accessed disk data. The technology involves storing a representation of disk in the (RAM) memory of the NetWare file server. When a client reads and writes files that are stored on a NetWare file server, the data does not interface directly with the server's disk storage hardware, it is accessed in the file server's memory cache (RAM). NetWare periodically updates the disk storage hardware as needed. NetWare Direct File System The Direct File System (DFS) allows an application to bypass the NetWare Disk Cache and Transaction Tracking Systems. DFS is necessary for some database applications that provide their own caching and transaction tracking facilities. Backup applications often access large amounts of data not being accessed by other applications. If these accesses are made through the cache, the cache becomes non-relevant for all other accesses, and general server performance suffers from other users. Some utilities may also require the ability to specify exactly where files are placed, so that volumes can be de-fragmented and optimal file access can be made. NetWare does not allow a file to be opened in both the cache and DFS modes simultaneously. DFS file open requests can only be made by an NLM application, and fails if the specified file is already open by any other (NLM or NetWare client) entity. While a particular file is opened in DFS mode, NetWare will deny all other open requests (for both DFS and cache modes) for that file. Files opened in DFS mode must not have any portion represented in NetWare cache. Therefore, as the file is opened in DFS mode, NetWare searches all cache for blocks that belong to the file. If a cache block belonging to the file being opened is encountered, the cache block content is written to the server's disk storage hardware (if required), and the cache block is disassociated from the file being opened. This process may take considerable time, depending on the size of the file being opened in DFS mode, and the total number of cache blocks in server RAM. NetWare Sparse Files The NetWare file system allows the creation of what Novell calls "sparse files." A sparse file is a file which has "holes" or areas which have not been yet been written to. A sparse file is formed by opening a new file writing to it non-sequentially. An example of a sparse file is one where the file is opened, and data is written to the file starting at offset 1000 and then closing the file. In this state, the file offsets 1 through 999 have not been written to and represents a hole in the data of the file. If an attempt is made to read from offset 1 through 999, NetWare returns zeros as the data. NetWare only allocates disk blocks to portions of a sparse file that have been written to. NetWare does not allocate disk blocks to a sparse file's holes. Apply DFSCCHFX NLM 2,270 09-23-96 1:06p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.10, V4.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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- DFSSETFX NLM ============ SYMPTOM: A problem occurs when a DFS file size is increased and the newly acquired block was recovered from a recently deleted file still being represented in the NetWare disk cache and is marked as dirty (or needs to be written to disk), and the cache block is written to by DFS before the cache subsystem performs it's periodic update. The effect is that if the newly expanded DFS file area is written to and then read back, the read data will not match the written data. Opening a file in DFS mode evacuates that file from NetWare cache. New disk blocks are acquired as the DFS file size is increased. New disk blocks are acquired from a list of free blocks. The disk blocks on the free block list either never been assigned to any file, or they are recovered from deleted files. Blocks from recently deleted files may still be represented in cache. SOLUTION: This has been fixed by having DFS verify that newly acquired blocks, obtained while expanding a file, are evacuated from the NetWare disk cache. SYMPTOM: A problem occurs when a DFS file size is increased and written to in a non-sequential mode, causing the formation of a sparse file. The effect is that data previously written to the to the DFS file might be zeroed out by subsequent writes to adjacent blocks. It is possible write to a file in DFS mode in a manner that causes the file to become a NetWare sparse file (ether by creating a new file or extending an existing file). As a security measure, the newly acquired disk blocks are zeroed out before use. SOLUTION: This problem has been fixed by changing the method of zeroing out the newly acquired disk blocks. ********************************************************** Technology Background: ********************************************************** NetWare Disk Caching Subsystem Description NetWare's disk caching subsystem technology decreases data access time for frequently accessed disk data. The technology involves storing a representation of disk in the (RAM) memory of the NetWare file server. When a client reads and writes files that are stored on a NetWare file server, the data does not interface directly with the server's disk storage hardware, it is accessed in the file server's memory cache (RAM). NetWare periodically updates the disk storage hardware as needed. NetWare Direct File System The Direct File System (DFS) allows an application to bypass the NetWare Disk Cache and Transaction Tracking Systems. DFS is necessary for some database applications that provide their own caching and transaction tracking facilities. Backup applications often access large amounts of data not being accessed by other applications. If these accesses are made through the cache, the cache becomes non-relevant for all other accesses, and general server performance suffers from other users. Some utilities may also require the ability to specify exactly where files are placed, so that volumes can be de-fragmented and optimal file access can be made. NetWare does not allow a file to be opened in both the cache and DFS modes simultaneously. DFS file open requests can only be made by an NLM application, and fails if the specified file is already open by any other (NLM or NetWare client) entity. While a particular file is opened in DFS mode, NetWare will deny all other open requests (for both DFS and cache modes) for that file. Files opened in DFS mode must not have any portion represented in NetWare cache. Therefore, as the file is opened in DFS mode, NetWare searches all cache for blocks that belong to the file. If a cache block belonging to the file being opened is encountered, the cache block content is written to the server's disk storage hardware (if required), and the cache block is disassociated from the file being opened. This process may take considerable time, depending on the size of the file being opened in DFS mode, and the total number of cache blocks in server RAM. NetWare Sparse Files The NetWare file system allows the creation of what Novell calls "sparse files." A sparse file is a file which has "holes" or areas which have not been yet been written to. A sparse file is formed by opening a new file writing to it non-sequentially. An example of a sparse file is one where the file is opened, and data is written to the file starting at offset 1000 and then closing the file. In this state, the file offsets 1 through 999 have not been written to and represents a hole in the data of the file. If an attempt is made to read from offset 1 through 999, NetWare returns zeros as the data. NetWare only allocates disk blocks to portions of a sparse file that have been written to. NetWare does not allocate disk blocks to a sparse file's holes. Apply DFSSETFX NLM 5,779 09-23-96 1:10p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.10, V4.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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- GETSTSFX NLM ============ SYMPTOM: ManageWise will cause the secondary machine to Abend. SOLUTION: Apply GETSTSFX NLM 2,388 09-23-96 12:51p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.10, V4.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: NetWare SFTIII: IOSTART.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- LOADER EXE ============ SYMPTOM: 1) This is a loader.exe with fixes for SFTIII and for SPD # 136329. This is a Green River patched loader. It has been tested and appears to work fine. This patch is only useful if the stwintfx.nlm patch is applied at the same time. 2) Added new code to prelude1.386 to make the new int 15 E820 calls to discover physically fragmented memory in larger than 64M segments. 3) FIXED a problem that would caused bizarre behavior in various places. This was found by Compaq. It dealt with global paging. 4) FIXED a problem in the memory detection code where it would have trouble registering memory if the block it was trying to register overlapped a previously registered block; the part that didn't overlap never got registered. In one case it was leaving out over 400MB when all of high memory showed up in one chunk. 5) FIXED a problem when there is more than 0xC8000000 of physical memory; it just doesn't work. Now you can have more than than on the machine and the OS just won't use it. 6) OPTIMIZED "MapDataOffsetToAbsoluteAddress()" because it is taking up too much time to translate the addresses and causing performance problems for fast ethernet drivers. 7) CHANGED the LoaderRevisionNumber so that LSWAP.EXE won't complain about the version being the same. 8) FIXED the new E820 memory registration code so that it will honor the flag to not register memory above 16 meg. Also bumped the loader revision number. 9) FIXED a problem that was causing fragmentation in systems with more than 2 GB of memory that support the E820 bois call. This was done by increasing the size of the add memory list. 10) FIXED GetSharedMemoryLinearAddress to address a problem COMPAQ has when a device has shared memory near but below the 0xC8000000 region. They were having the problem where the memory would get assigned to the APIC, and then when their device driver would register for that physical address, it would map the devices memory in at that address and unmap the APIC causing future APIC referenced to fail. Also changed the revision in LSTART so LSWAP wont complain. 11) FIXED a bug in the E820 bios function. The problem happened when we got a piece of memory back from the E820 call that was larger than 64M before adjusting for the fact that the memory started before 16M. After the adjustment it was smaller than 64 M and when I decrimented the value it would go negative. 12) FIXED a bug where the EISA memory detection code was not working when there was more than 64MB of memory on the machine. This bug was introduced by fix #4. 13) FIXED a problem where SFT III mirroring would bread if it tried to mirror a memory segment that was not 4K aligned; so when the BIOS returns a non-aligned memory segment we need to make sure we 4k align it before registering it with the OS. 14) FIXED 2 problems where MP configurations would blow up after shutting down the secondary processors. To resolve the problems we need to switch a processor to real mode before doing a halt, and we also need to deal with the case where the processor will be restarted by an SMI interrupt and then improperly return to the next instruction minus one byte. These changes are handled by a new public procedure DoRealModeHalt(). SOLUTION: Apply LOADER EXE 144,0555 01-21-97 3:51p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V3.12, V4.10, V4.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. See LSWAP.NLM or LSWAP.EXE for installation intructions. ----------------------------------------------------------------- LSWAP EXE ============ SYMPTOM: SOLUTION: Apply LSWAP EXE 55,597 05-28-96 1:51p 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 specifies 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 applied once per SERVER.EXE or MSERVER.EXE ----------------------------------------------------------------- LSWAP NLM ============ SYMPTOM: SOLUTION: Apply LSWAP NLM 46,534 05-28-96 1:52p 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 specifies 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 applied once per SERVER.EXE or MSERVER.EXE ----------------------------------------------------------------- MACCONFX NLM ============ SYMPTOM: The MAC_STATION is getting set if the volume does not support the MAC namespace. SOLUTION: Fixed case 10 of MacintoshRequest to only set the connection status MAC_STATIO bit only if the call to MacEnumerate returned successfully. Apply MACCONFX NLM 1,236 10-02-96 2:26p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- MIGPRGFX NLM ============ SYMPTOM: Cannot delete demigrated file with savekey. SOLUTION: Apply MIGPRGFX NLM 2,023 09-23-96 12:39p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- MSGFREFX NLM ============ SYMPTOM: Only the directory path is reported by Auditcon for the Delete File audit records. SOLUTION: Corrected the audit record generation for A_EVENT_DELETE_DIRECTORY, A_EVENT_DELETE_FILE, A_EVENT_SALVAGE_FILE, and A_EVENT_PURGE_FILE to NOT null terminate the directory string before appending the filename. Apply MSGFREFX NLM 1,074 10-02-96 2:23p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- PK411 NLM ============ PK411.NLM IS (PM411.NLM + PMB411.NLM + PATCHES). PK411.NLM has been developed to simplify the patch prcess for SERVER.EXE and MSERVER.EXE ----------------------------------------------------------------- PM411 NLM PMB411 NLM ============ SYMPTOM: SOLUTION: Apply PK411 NLM 74,396 01-07-97 4:09p PM411 NLM 1,607 10-07-96 9:38a PMB411 NLM 28,910 10-07-96 9:39a Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF NetWare SFTIII: IOSTART.NCF This README file accompanies PM411.NLM (patch manager for NetWare V4.11). PM411.NLM is the Patch Manager which tracks and manages all official patches for NetWare V4.11 including SFT3. Patches for NetWare V4.11 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. 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!) 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 (PM411.NLM) must be loaded before any dynamic or semi-static=patches can be loaded. If PM411.NLM is not already loaded, the .NLM will attempt to locate PM411.NLM and, if found, will load it automatically. PM411.NLM only needs to be loaded once; all NLM patches can then be loaded. PM411.NLM cannot be unloaded until all patches that rely on it are first unloaded. ----------------------------------------------------------------- RECALCFX NLM ============ SYMPTOM: Bug in SetTimeFromVector doing a RecalculateDST call. SOLUTION: Apply RECALCFX NLM 2,379 11-25-96 4:14p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- RENENTFX NLM ============ SYMPTOM: Files in the _NetWare directory can be renamed. SOLUTION: Changed the routine INWRenameEntry to return ERR_INVALID_PATH if the IFlags returned from FindDirectoryEntry for the source contains the _NETWARE bit and the connection is not connection 0. Apply RENENTFX NLM 1,199 10-02-96 2:25p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: 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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- STDIRHFX NLM ============ SYMPTOM: Unable to CD into LOGIN directory after loading client 32. SOLUTION: Apply STDIRHFX NLM 1,099 09-23-96 1:02p Solution Specifics: Different versions of this patch are available for the following NetWare Operating System's: V4.10, V4.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: Native NetWare: STARTUP.NCF NetWare for OS/2: STARTUP.NCF NetWare SFTIII: MSSTART.NCF ----------------------------------------------------------------- SWTINTFX NLM ============ SYMPTOM: SFT III servers experience different outputs aBENDS Solution: Apply: SWTINTFX NLM 1,582 09-23-96 12:59p Solution Specifics: Use a interrupt gate so stacks are kept the same. Different versions of this patch are available for the following NetWare Operating System's: 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: NetWare SFTIII: IOSTART.NCF ----------------------------------------------------------------- ----------------------------------------------------------------- ACTMDLFX NLM 1,195 09-23-96 12:44p AUDCONFX NLM 1,066 10-02-96 2:24p AUDDELFX NLM 1,121 10-02-96 1:50p AUDOVFFX NLM 1,143 10-02-96 2:11p AUDRESFX NLM 1,899 11-11-96 12:48p DFSCCHFX NLM 2,270 09-23-96 1:06p DFSSETFX NLM 5,779 09-23-96 1:10p GETSTSFX NLM 2,388 09-23-96 12:51p MACCONFX NLM 1,236 10-02-96 2:26p MIGPRGFX NLM 2,023 09-23-96 12:39p MSGFREFX NLM 1,074 10-02-96 2:23p PK411 NLM 74,396 01-07-97 4:09p PM411 NLM 1,607 10-07-96 9:38a PMB411 NLM 28,910 10-07-96 9:39a RECALCFX NLM 2,379 11-25-96 4:14p RENENTFX NLM 1,199 10-02-96 2:25p STDIRHFX NLM 1,099 09-23-96 1:02p SWTINTFX NLM 1,582 09-23-96 12:59p ----------------------------------------------------------------- -----------------------------------------------------------------