|
Self-Extracting File Name: 310PT1.EXE Revision: A
Files Included Size Date Time
\
310PT1.TXT (This File)
BELOW16.DSK 2788 04-08-91 1:19p
CACHEFIX.NLM 1189 10-29-90 5:05p
DELDIRFX.NLM 1773 10-29-90 10:05a
DELFIX.NLM 1872 10-29-90 5:53p
DIRLPFX.NLM 757 04-09-91 09:23a
DTTMFIX.NLM 2563 12-07-90 08:46a
DUPDSKFX.NLM 1207 12-21-90 12:44p
FIXDUMP.NLM 2123 10-29-90 6:03p
FIXOPEN.NLM 2723 10-29-90 6:09p
FREEFIX.NLM 2587 02-25-91 3:53p
IPXINCOM.NLM 1279 10-11-90 5:03p
LGHOTFIX.NLM 1374 12-20-90 09:28a
LIMBOFIX.NLM 575 03-04-91 10:10a
MAXNCP.NLM 1581 10-17-90 3:39p
MONITOR.NLM 100451 07-20-90 4:51p
NAMEFIX.EXE 8456 07-26-90 2:09p
PASSFIX.NLM 2519 01-03-91 09:00a
PATCH31.NLM 46757 02-14-91 1:18p
PATCHMAN.DOC 3752 04-17-92 2:48p
PATCHMAN.NLM 6550 02-05-91 10:16a
PTFIX.NLM 1932 12-05-90 09:18a
QFIX.NLM 3224 12-18-90 12:42p
READFIX.NLM 721 02-05-91 09:58a
RTAGFIX.EXE 11860 11-13-90 1:02p
SCANBFIX.NLM 1764 01-14-91 11:23a
TTSFIX.NLM 1938 12-05-90 08:58a
WDOGFIX.NLM 1182 10-29-90 6:17p
\NCPLIM\
NCPLIMIT.DOC 18591 12-17-90 11:52a
NCPLIMIT.MAP 4438 12-12-90 09:25a
NCPLIMIT.NLM 1980 12-12-90 09:25a
NCPLIMIT.TXT 3962 12-17-90 11:53a
\VRP310\
VREPAIR.NLM 86330 01-09-91 11:29a
VREPAIR.TXT 2191 03-07-91 3:46p
VRSHIM.NLM 699 01-11-91 3:52p
V_MAC.NLM 4914 12-10-90 07:06a
WARNG!.TXT 121 02-07-91 09:18a
README FILE FOR 310PT1.EXE
This file contains the latest release of NetWare v3.10 Operating System Patches and server console utilities. These patches are NOT intended to run on versions of NetWare other than v3.10.
It is recommended that every v3.10 NetWare system install CACHEFIX.NLM, DELDIRFX.NLM, DELFIX.NLM, DUPDSKFX.NLM, FIXOPEN.NLM, PASSFIX.NLM, and WDOGFIX.NLM. All other patches should be installed at the discretion of the network supervisor as needed.
*****************
BELOW16.DSK
2788 04-08-91 1:19p This file is a Static path and is for use with DMA LAN adapters and Disk Controllers with 24 bit address lines that require memory allocation below 16 MB. This module provides developers with two function calls under NetWare v3.10 to guarantee allocation of memory under 16 Mb.
Installing issues:
1. BELOW16.DSK must be loaded before any other module.
2. By default BELOW16 allocates 8 buffers (the default buffer size is 4096 bytes as defined in "Cache Buffer Size"). To over-ride the number of buffers, the following syntax may be used in STARTUP.NCF,"LOAD BELOW16 number",where "number" is the number of buffers. Changes to the number of buffers allocated should only be made at the recommendation of the manufacturer.
CACHEFIX NLM
1189 10-29-90 5:05p CACHEFIX is a semi-static patch which is loaded at the file server console as a NetWare Loadable Module. Under heavy usage when data is read immediately after it is written to cache, the data read could result in the return of erroneous data. If cached data is read and rewritten to cache, the corruption would be saved to disk. If the data is not changed in cache, the data will be saved correctly. This problem exists primarily with random access applications (for example, database servers).
DELDIRFX NLM
1773 10-29-90 10:05a DELDIRFX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a bug in NetWare 386 V3.10a that would cause the server to ABEND with the message: "DeleteDirectory found invalid phantom list." Whenever an attempt was made to delete a directory which contained a certain number of trustees assigned to it. The number of trustees had to be greater than eight and the binary representation for that number had to have the number two bit set. For example, the binary representation of 10 trustees is 1010; the second bit is set in this binary number.
DELFIX NLM
1872 10-29-90 5:53p DELFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a bug in NetWare 386 V3.10a that would cause the server to ABEND with the message, "DeleteFileCompletely found an invalid TNode", whenever an attempt was made to delete a file which had more than seven trustees assigned to it and Immediate Purge Of Deleted Files was set to ON.
DIRLPFX.NLM
757 4-09-91 9:23a DIRLPFX0 is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 v3.10 that results in an infinite loop when the DOS DIR command is used in a subdirectory where more than 65,535 files exist. This loop will also occur with the FindFirst and FindNext DOS function calls.
DTTMFIX NLM
2563 12-07-90 8:46a DTTMFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes two problems in NetWare 386 V3.10a.
One would not allow a file's date/time to be set to 0. Some applications known to set the date/time to 0 are Borland's Turbo C++ and Turbo Pascal products.
The compiler's "Build All" option within the integrated environment sets the date/time to 0's in order to force a full recompile of all source files. Without this patch installed, the file's date/time remained unchanged. Other applications may also set the date/time to 0. DTTMFIX also corrects a problem that would sometimes cause copied files to be stamped with incorrect date/time information. This problem occurs most often when copying files from a Macintosh workstation.
**NOTE: Due to the implementation of this patch, attempting to set the date/time to FF's will result in the date/time remaining unchanged.
DUPDSKFX NLM
1207 12-21-90 12:44p DUPDSKFX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a when using the Core driver certified for 3.0 resulting in the message, "Abend: Invalid System ID passed to NPUTIOCTL". DUPDSKFX.NLM also solves problems with systems hanging, then upon rebooting the system, the error: "Fat Chain Overlaps Onto Itself" was reported.This patch is also recommended by Storage Dimensions when mirroring or duplexing on their systems.
FIXDUMP.NLM
2123 10-29-90 6:03p FIXDUMP is a dynamic patch that is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 v3.10a where memory above 16MB was not being dumped during a diagnostic image dump. (Servers with less than 16MB are not affected by this problem.)
FIXOPEN NLM
2723 10-29-90 6:09p FIXOPEN is a dynamic patch that is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 v3.10a that would not allow files that were flagged RO to be opened with RW rights when the Read Only Compatibility mode of the shell was on. This problem was seen in an application as an error: "File not found" or "Access denied."
Read Only Compatibility = Off is the normal mode of operation and requires RW rights for applications which open in RW mode. The Read Only Compatibility parameter in the shell is intended to allow such applications to open a file when the user only has RO rights.
FREEFIX.NLM
2587 02-25-91 3:53p FREEFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 v3.10 that results in the fatal error, "ABEND:Freeable procedure found an invalid deleted file".This ABEND can occur when mounting a volume or while running VREPAIR or while running heavy I/O on the server.
FREEFIX fixes bugs in the HotFix code; in the case where HotFix discovered a bad block, it was asking the OS to search its cache buffers for the data for this block, but passed the wrong block number to the cache code.
***NOTE: FREEFIX.NLM will not run with another patch by the name of LIMBOFIX.NLM and should not be loaded with it.
IPXINCOM NLM
1279 10-11-90 5:03p IPXINCOM is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a resulting in the error "IPX received incomplete packet". This patch will quell the error message that is reported to the screen and the error log of the server. It is to be used in conjunction with OEM and 3rd party drivers until the drivers are fixed. The offending driver can be in any client, bridge or server. Old Client Ne/2 and old Host NE2000 drivers are known to cause this problem and should be updated to currently released drivers.
LGHOTFIX.NLM
1374 12-20-90 9:28a LGHOTFIX is a semi-static patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a that would cause INSTALL.NLM to not recognize any partitions that were initialized with a redirection (hotfix) area that was greater than 8000 blocks.
**NOTE LGHOTFIX must be loaded before any attempt is made to create a volume on a partition that has more than 8000 redirection blocks.
LIMBOFIX NLM
575 03-04-91 10:10a This is a semi-static patch and is to be considered a temporary fix to the problem associated with the error, "ABEND: FreeALimboFile".
** NOTE: LIMBOFIX.NLM should not be used with another patch by the name of FREEFIX.NLM.
MAXNCP.NLM
1581 10-17-90 3:39p This is a semi-static patch which must be loaded as a NetWare loadable module at the console. If a user has an application that uses all that is available of the NCP search table, this patch is a good work around until you go to 3.11 or get a later revision of the application.Loading MAXNCP.NLM will increase the upper limit of NCP searches from 1000 to 5000. After loading the NLM, use the SET command to increase the NCP search limit variable.
**WARNING!:Increasing the number of NCP searches will decrease the amount of RAM available to NetWare. Using this patch will either decrease your number of connections to less than 100 or require that additional RAM be added. The following formula will help in determining how much additional RAM will be needed to maintain the same amount of working RAM on your server:
24000 x (Maximum Outstanding NCP Searches / 1000) x Number of Stations
EXAMPLE: For 100 stations and 5000 NCP Searches, the additional RAM would be: 24000 x (5000 / 1000) x 100 = 12 Meg of RAM
MONITOR NLM
100451 07-20-90 4:51p This version of MONITOR corrects a problem where the server may hang when clearing connections. It also corrects a problem where resources may not be released when exiting MONITOR.
To install this utility:
1) Copy MONITOR.NLM to the same directory as the other NLM files on your system (SYS:SYSTEM is suggested).
2) After the system is brought up, type LOAD MONITOR.
NAMEFIX EXE
8456 07-26-90 2:09p NAMEFIX is a static patch utility that removes the erroneous message"Novell In House Version" from the Console sign-on screen of shipping versions of NetWare 386 v3.10 Rev. A.
NCPLIM EXE
9485 12-17-90 4:21p NCPLIMIT is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module.
This EXE file contains the following files:
NCPLIMIT.MAP 4,438 12-12-90 9:25a
NCPLIMIT.NLM 1,980 12-12-90 9:25a
NCPLIMIT.DOC 4,972 12-17-90 11:52a
NCPLIMIT.TXT 1,858 12-17-90 11:53a
This patch provides for better management of file searches done on a NetWare 386 V3.10a server.
This patch adjusts to applications written using the findfirst function. If the findfirst search function is not completed correctly, NetWare 386 will generate the warning message "You exceeded your outstanding NCP directory search limit." If loading this NLM does not eliminate the warning message, the application will need to be rewritten according to the recommendations described in NCPLIMIT.DOC. For more information, please refer to that document.
PASSFIX.NLM
2519 1-03-91 9:00a PASSFIX is a dynamic patch that is loaded at the file server console as a NetWare Loadable Module. This patch fixes a password problem in NetWare 386 v3.10a. A very rare security shortcoming has been identified by Novell. It has been fixed with this patch. For most Novell customers who have intruder detection set on - this security weakness will not pose a problem. Novell recommends that all customers turn intruder detection on and if the customer has greater concerns for security, they should apply this corrective patch.
PATCH31.NLM
46757 2-14-91 1:18p PATCH31.NLM is a dynamic patch. This NLM patches several functions in CLib v3.10. See patch31.doc for a list of functions that are replaced by the PATCH31 NLM.
**WARNING: Do not unload 'PATCH31.NLM' while the CLib is being used by other NLMs.
PTFIX NLM
1932 12-05-90 9:18a PTFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a that would cause the server to ABEND with the message: "Abend: PurgeTrustee found an entry it couldn't deal with."
QFIX NLM
3224 12-18-90 12:42p This is a semi-static patch and is provided as a temporary fix. It is intended to resolve a problem with NetWare v3.10 where print jobs would be lost from print queues.
READFIX.NLM
721 2-5-91 9:58am READFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a that could cause an invalid error code to be returned to an application making a file READ operation. This problem was first noticed using the BTRIEVE NLM.
RTAGFIX EXE
11860 11-13-90 1:02p RTAGFIX is a static patch that corrects the error "Abend: Bad resource tag passed to AES process."
SCANBFIX NLM
1764 01-14-91 11:23a SCANBFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a. The API function call ScanBinderyObject fails to properly recognize "?" as a wild card. The failure was related to the size of the bindery name being searched for and the number of "?" wild card characters (if greater than 12) entered in the search string. Although those most likely to see this problem are application developers using the ScanBinderyObject call, users of applications developed with this call may see the error message: "Object could not be found".
TTSFIX NLM
1938 12-05-90 8:58a TTSFIX is a dynamic patch which is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a that would cause the server to ABEND with the following message, "Abend: TTSAbortTransaction detected a bad TTS file"
**NOTE IT IS HIGHLY ADVISABLE TO RUN THE CACHEFIX PATCH IN CONJUNCTION WITH TTSFIX.
(VRP310)
VREPAIR NLM
86330 01-09-91 11:29a This version of VREPAIR corrects problems with FAT chain overlap, unrecoverable read errors, VREPAIR changes not written to disk, and problems when both Primary and Secondary mirrored FATs contain an invalid link value. This version will also correct some problems experienced when using the ERASEFIX patch previously distributed on NetWire.
VRSHIM NLM
699 01-11-91 3:52p
V_MAC NLM
4914 12-10-90 7:06a
**WARNING!:This version of VREPAIR can cause data loss if used in conjunction with the PS2SCSI.DSK driver.
To install this version of VREPAIR:
1) Copy VREPAIR.NLM and VRSHIM.NLM to the same directory as the other NLM files on your system (SYS:SYSTEM is suggested).
2) Type LOAD VRSHIM and then LOAD VREPAIR. VRSHIM must be loaded before VREPAIR.
**NOTE: If you are using a MACINTOSH NAME SPACE on your system, you will need to ALSO LOAD V_MAC.NLM. After loading VRSHIM and VREPAIR: Toggle out of VREPAIR (<Alt> <Esc>), then type LOAD V_MAC. Toggle back in VREPAIR and repair the volume.
WDOGFIX NLM
1182 10-29-90 6:17p WDOGFIX.NLM is a SEMI-STATIC patch that is loaded at the file server console as a NetWare Loadable Module. This patch fixes a problem in NetWare 386 V3.10a that would cause the file server to ABEND with the message, "Abend: Total sprintf string length was too long (Error code 00000000)" This ABEND could occur at any time, but would occur more frequently if the console parameter "Console display watchdog logouts = ON" was set. This patch also fixes a problem that displayed invalid characters or user names on the console screen when the watchdog cleared a user's connection.
****************
TYPES OF PATCHES FOR NETWARE 386 V3.10
There are three types of patches for NetWare v3.10: dynamic, semi-static, and static. Dynamic patches are .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 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. A static patch is a DOS executable program that makes changes to the SERVER.EXE file. This type of patch is applied once and its effects are permanent. It is suggested that static patches be applied to a copy of the SERVER.EXE file, not the original file.
DYNAMIC and SEMI-STATIC patches modify the Operating System in memory, not on the disk. and require PATCHMAN.NLM in order to load. 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 <patch>" be placed in the file server's AUTOEXEC.NCF file to ensure that the patch is always in effect when the server is initially brought up. Typing MODULES at the server console will show which dynamic patches have been loaded, but will not show semi-static or static patches.
The Patch Manager (PATCHMAN.NLM) must be loaded before any dynamic or semi-static patches can be loaded. If PATCHMAN is not already loaded, the <patch>.NLM will attempt to locate PATCHMAN and, if found, will load it automatically. PATCHMAN only needs to be loaded once; all .NLM patches can then be loaded. PATCHMAN cannot be unloaded until all patches that rely on it are first unloaded.
To implement a SEMI-STATIC OR DYNAMIC patch:
1) Copy PATCHMAN.NLM and the patch .NLM file to the same directory as the other NLM files on your system (SYS:SYSTEM is suggested).
2) After the system is brought up, type LOAD PATCHMAN at the console.
3) LOAD the patch .NLM file.
NOTE: These patches and PATCHMAN.NLM will only operate on NetWare 386 v3.10a. Future versions of NetWare 386 will require a version of PATCHMAN specific to that release.
STATIC patches are run against the SERVER.EXE file and may not be compatible with other static patches. If you are running other static patches and have questions regarding their compatibility, contact your NetWare Service Provider.
To implement a STATIC patch: (Ensure a backup copy of SERVER.EXE has been made and is kept in a safe place)
1) Copy RTAGFIX.EXE into the same directory as SERVER.EXE.
2) Type RTAGFIX. The program will patch the file and notify you when finished.
|
