NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Patch Kit for NetWare 386 v3.00 DOCUMENT ID: TID000014 DOCUMENT REVISION: A DATE: 01JUL93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: 300PT1.EXE NOVELL PRODUCT and VERSION: NetWare Pre 3.11 and 2.2 ABSTRACT: This file contains the operating system patches for NetWare v3.0. These patches are intended for NetWare v3.0 only. This file contains the following files: BWFIX.EXE CDFIX.EXE CONFX2.EXE CRTFIX.EXE LOADFX.EXE OPENFX.EXE _________________________________________________________________ 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. _________________________________________________________________ Self-Extracting File Name: 300PT1.EXE Files Included Size Date Time 300PT1.TXT (This File) BWAREFIX.EXE 13157 1-18-90 3:39p CHDIRFIX.EXE 13204 6-11-90 9:52a CONNFIX2.EXE 8990 6-01-90 9:11a CREATFIX.EXE 8772 12-18-89 12:24a LOADFIX.EXE 11757 8-25-89 11:32a OPENFIX.EXE 8746 11-28-89 8:43a README FILE FOR 300PT1.EXE These patches are intended for 386 NetWare v3.0 only. ****NOTE: It is recommended that CONNFIX2.EXE, CREATFIX.EXE, LOADFIX.EXE, and OPENFIX.EXE be installed in every 3.0 system. BWAREFIX.EXE and CHDIRFIX.EXE should be installed ONLY on an as-needed basis. ***Note that the files included in this release are "static" patches which means that they are individual programs that are run against the SERVER.EXE FILE and change the file permanently. This is unlike the majority of patches for releases of NetWare subsequent to V3.00 that are patched in memory. The patches listed below are therefore only for NetWare 386 V3.00. It is strongly recommended that you BACKUP SERVER.EXE BEFORE APPLYING THIS PATCH! This file (300PT1.EXE) contains the following files that were previously released on NetWire, Library 4: 1. BWFIX.EXE 2. CDFIX.EXE 3. CONFX2.EXE 4. CRTFIX.EXE 5. LOADFX.EXE 6. OPENFX.EXE BWAREFIX EXE 13157 1-18-90 3:39p BWAREFIX.EXE performs the patch mentioned in the January, 1990, issue of LanTimes (pp. 13,14), as well as in BootWare Bulletin #19 from LANWORKS Technologies Inc. This patch will enable any 2.1x bootprom to work with NetWare 386 v3.00. CHDIRFIX.EXE 13204 06-11-90 9:52a CHDIRFIX.EXE addresses an issue with using periods when in accessing directories. DOS allows a user to specify a directory name by ending the name with a period. This period is ignored by DOS, but not by NetWare. For example: if a user had a directory named "TEMP", DOS would allow the user to type "CD TEMP" or "CD TEMP." to change directories. Under NetWare 386 v3.0, the latter command would generate an "Invalid directory" error message. Although this should rarely be a problem, some applications append the period character to the end of a directory name before searching for the existence of the directory. Directory names which have a period character embedded in them will not be affected by this patch (EXAMPLE: "TEST.DAT"). NetWare 386 already treats these directories the same as DOS. CONNFIX2.EXE 8990 06-01-90 9:11a CONNFIX2.EXE corrects a problem with some applications which use an older NetWare function call to map a user to a connection list and caused confusion between nearly identical user names. These are names which are identical with the exception of the last character (for example: SAMS and SAMR). CONNFIX2 also corrects an anomaly in CONNFIX which causes a General Protection Interrupt when some applications are run. ** Note: CONNFIX2 replaces the previous version of CONNFIX. If you have already run CONNFIX, CONNFIX2 will fix the GPI problem caused by CONNFIX. If CONNFIX has not been run previously, CONNFIX2 will make all the necessary adjustments to SERVER.EXE. CREATFIX EXE 8772 12-18-89 12:24p Some applications attempt to create a file by using the DOS INT 21 call "CREATE NEW FILE" (function 5B). This call will only succeed in creating the specified file if it does not already exist. If the file does exist, function 5B returns an error code indicating the existence of the file. NetWare 386 erroneously returns an ACCESS DENIED error if function 5B is called to create a file which already exists. This may confuse certain applications, leading to unpredictable results. CREATFIX corrects this problem and causes the correct error code to be returned to the application. LOADFIX EXE 11757 8-25-89 11:32a Some 386 clone machines hang when loading NetWare 386 v3.0. The hardware in these machines does not handle the switch into 386 protected mode fast enough for SERVER.EXE to load normally. This may cause the machine to "hang" during boot-up, or continually reset itself. This patch injects wait loops to allow the hardware time to make the switch into 386 protected mode. OPENFIX EXE 8746 11-28-89 8:43a Some applications open the same file more than once within the program. If the application opens the file with different access rights (or fewer access rights) the next time, the rights granted during the latest OPEN will overwrite the previous access rights. For example, if a file is opened with Read\Write access rights the first time, then is opened again with only the Read access right, the file opened first will no longer have the Write access right when the second file is closed. This problem only occurs if the same file is being opened a second time without closing it the first time. Applications that receive the resulting ACCESS DENIED error from NetWare may interpret this differently and give the user inaccurate error messages. The AccPac software by Computer Associates, for example, returns a DISK FULL error when this occurs. Other applications may return different error messages. **************************************************************** Future versions of NetWare 386 will already have these fixes implemented. These patches will only work for NetWare 386 v3.0. Instructions for use: Copy the .EXE into the same directory as SERVER.EXE and type the patch name. The program will patch the file and notify the user when finished. Reboot your file server using the patched SERVER.EXE. ÿ