Patch-ID# 100162-01 Keywords: pc pc-nfs Synopsis: PC-NFS 3.0.1: Jumbo patch Date: Nov/14/90 Solaris Release: SunOS Release: 4.0.3 4.1 Unbundled Product: PC-NFS Unbundled Release: 3.0.1 BugId's fixed with this patch: 1028791 Changes incorporated in this version: Relevant Architectures: i386 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: PC-NFS 3.0.2 Problem Description: CO-EXISTENCE WITH 3COM SOFTWARE When PC-NFS and 3Com software are both installed in a PC, and users attempt to access remote files provided by either system, the 3Com software fails. It usually displays the message "Redirector error 5". See APPENDIX A for a full description of installing co-existant software. LARGE FILES You are unable to create, read or write correctly network files whose size is 64 Megabytes (67108864 bytes) or larger.This may occur when using either an application, or DOS commands, when the file is located on a network drive. ONLY THE OWNER OF A FILE CAN SHRINK IT You have a file with read-write permission for all users. You are a user who is not the owner (creator) of the file. You edit the file using an application which rewrites the file in-place [which many editors do not do]. During this edit, you deletes data from the file so that it should be shorter. When you display the file it has not been truncated; there is excess data left at the end of the file. With 301b, the file is correctly reduced in size. INCORRECT MESSAGE - NO DISK SPACE DOS applications report that there is no space available on a network drive when you try to save. However, there actually is space available. With this fix, applications will not misconstrue how much space is available. PC-NFS PROGRAMMER'S TOOLKIT APPLICATIONS CLOSE CONNECTION You are using an application that is built with the PC-NFS Programmer's Toolkit. When you are within the application, pressing Control-Break causes the connection to disconnect. With this fix, this will no longer occur, unless the application deliberately closes the connection when it receives a Control- Break. SLOW RESPONSE DUE TO SPURIOUS RARP PACKETS When you use PC-NFS in Class 'A' networks you experience delays in response of 3 to 15 seconds. Traces of the network traffic (Sniffer traces) indicate that spurious RARP packets are generated, seemingly at random. This happens even if RARP option is turned off. NOTE: This fix is quite specific to the generation of extra RARP packets. If you are experiencings delays in response, there can be a wide range of reasons unrelated to this problem. UNABLE TO FIND A YP SERVER A NET YPSET * command (usually in your startup procedure) will frequently cause your system to hang without finding a YP server or printing a message. This occurs even if there are valid YP servers available in your network. This problem is most likely to occur in subnetted networks. It is corrected with this fix. UNABLE TO MOUNT A DRIVE IN VMS You are unable to mount a remote drive on a VMS system, even though you have access rights. You probably received the message: NFS038F : Access to file system denied by server. You will now be able to mount the drive. STALE FILE HANDLES Stale file handles resulting from opening the same file under different descriptors will no longer occur after the file descriptor is closed. SECONDARY GROUP PERMISSIONS NOT RECOGNIZED You are unable to mount a remote drive to a filesystem when you have permissions only through a secondary group. That is, you not do not have permission either through your user id or through your primary group to that filesystem. You are using YP services. Secondary groups are recognized in NET USE commands with this fix. NET COMMAND HANGS You issue a NET command that specifies a hostname, and hang. YP services are enabled. NCR CASH REGISTER INSTALLATION. Your PC hangs when the first NET command which causes network traffic is executed. For example, with the NETWORK.BAT file: NET YPDOMAIN foo NET START RDR bar * NET YPSET bletch the NET YPSET is the first command that actually causes network traffic. This is caused by the link level driver (such as \NFS\3C501.SYS) is loaded too high in memory for PC-NFS to find it. This can be also caused by a unusual DOS or by device drivers which reserve too much memory loaded before the link level driver. This problem first occurred with an NCR Point-of-sale PC, but could be found with other unusual configurations. INCORRECT VIDEO ATTRIBUTE HANDLING IN TELNET You run Telnet to access a server. The application that you run via Telnet uses VT-100 screen attributes to display fields in various formats. When the screen scrolls, the new line at the bottom or top of the screen is shown in reverse video. (Other incorrect modes are possible.) This is corrected in 3.0.1b. OVERWRITING DATA WHEN MULTIPLE USERS SIMULTANEOUSLY APPEND A DATA BASE Multiuser data base packages such as Clipper may encounter corrupted data when multiple uses simultaneous append to a data base on a network drive. FTP IS SLOW DUE TO SMALL PACKETS When using FTP to transfer files, the performance is very slow. Traces of network traffic (Sniffer traces) show that the data is being broken into increasingly smaller packets. READ/WRITE ERRORS WHEN ACESSING FILES ACROSS A GATEWAY If DOS errors occur when accessing an NFS file system across an gateway which performs IP fragmentation you may need to install 3.0.1b. Earlier version of PC-NFS had a problem reassembling odd bye packets. SLIP DROPPING PACKETS You use SLIP to connect a PC running PC-NFS to a Sun server running SunOS 4.0 or later, and you see the following messages on the Sun server's console: : q full -- dropping packets : sloutput restart If you use the new slipd40.tar you may get page faults depending on which version of the SunOS and server type you are running: SunOS Platform Page Fault Frequency --------------------------------------------------- 4.0 Sun3, Sun386i, Sun4 rarely 4.0.1 Sun386i rarely 4.0.2 Sun386i never 4.0.3 Sun3, Sun4 rarely Patch Installation Instructions: -------------------------------- The following instructions refere to "diskette" format of this patch. You may have to modify path names if you received this patch in some other form. All files noted below are in the sub directory called diskette. INTRODUCTION This diskette contains fixes for certain problems which occur when using PC-NFS version 3.0.1. It contains several new PC-NFS executables and several server executables. You many only need some of these executables. There are two sets of changes available, and two corresponding Installation Instructions which describe how to install each set of changes. Use the descriptions below to help you decide what set(s) of changes you need. WARNINGS o DO NOT directly copy any changes into your \NFS directory. If you do, you will encounter problems with your software's serial number upon reboot of your system. o These patches should be installed ONLY with PC-NFS VERSION 3.0.1. DO NOT install them with any other verion of PC-NFS. DO I NEED THESE FIXES? You will need these fixes if you have encountered any of the problems described below. If you have not experienced any of these problems, these patches will not cause any problems, but will probably not help any other problem you may be experiencing. If you have any questions, please contact the person from whom you received the patch. SET 1: USE THE 301A INSTALLATION -------------------------------- If you have encountered any of the following problems, use the Installation Instructions titled TO INSTALL THE 301A PATCHES. PROBLEM DESCRIPTIONS CO-EXISTENCE WITH 3COM SOFTWARE LARGE FILES ONLY THE OWNER OF A FILE CAN SHRINK IT INCORRECT MESSAGE - NO DISK SPACE PC-NFS PROGRAMMER'S TOOLKIT APPLICATIONS CLOSE CONNECTION SLOW RESPONSE DUE TO SPURIOUS RARP PACKETS UNABLE TO FIND A YP SERVER UNABLE TO MOUNT A DRIVE IN VMS STALE FILE HANDLES SECONDARY GROUP PERMISSIONS NOT RECOGNIZED NET COMMAND HANGS NCR CASH REGISTER INSTALLATION. INCORRECT VIDEO ATTRIBUTE HANDLING IN TELNET OVERWRITING DATA WHEN MULTIPLE USERS SIMULTANEOUSLY APPEND A DATA BASE FTP IS SLOW DUE TO SMALL PACKETS READ/WRITE ERRORS WHEN ACESSING FILES ACROSS A GATEWAY SET 2: CHANGE YOUR SLIP DRIVER --------------------------------- If you have encountered the following problem, follow the Installation instructions titled INSTALLING A NEW SLIP DRIVER. You DO NOT need to to do the installation described in USE THE 301A INSTALLATION. SLIP DROPPING PACKETS INSTALLATION DOCUMENTATION ---------------------------- FILES IN THE SUBDIRECTORY DISKETTE 301.BAT A batch file to install changes COPYSER.EXE A utility to move serial numbers README.TXT A description of the contents of this patch PCNFS.SYS The PC-NFS driver NET.EXE Net command NFSCONF.EXE PC-NFS Configuration command EM.COM Part of Telnet FTP.EXE File Transfer program \SLIP\SLIPD40.TAR Serial Distribution for SunOS4 TO INSTALL THE 301A PATCHES (1) Create an empty directory on an NFS mounted drive with at least 600 kilobytes of free space. The example uses Drive G:. For example: net use g: \\server1\platypus g: mkdir \301b.nfs (2) Insert the patch diskette in a 1.2MB diskette drive (typically A:) and type COPY A:\*.* G:\subdirectory /v. For example COPY A:\*.* G:\301b.nfs /v (3) On each PC to be upgraded, mount this directory as drive G: (preferably read-only) and type: G: cd \301b.nfs 301b C where C is the drive on which you installed PC-NFS 3.0.1. Note that thereis no colon after the drive name. If you are not sure where PC- NFS is installed, type your autoexec.bat. It should have a statement NFSDRIVE = C Use the drive named there. 4) The procedure 301b is a batch file that copies the patch fixes in to your NFS directory, and updates the file pcnfs.sys with the appropriate serial number. After the procedure is complete, reboot your machine, and verify that PC-NFS loads correctly. INSTALLING SLIP DRIVER To install the slip driver, follow the instructions on p.16 through 18 of the PC-NFS Serial Communications guide. The file slipd40.tar is on the patch diskette in the subdirectory \slip. When running the addslip.csh installation script, anwser the following question YES: Do you want to remove SLIP? Yes You may save your old SLIP source code. If you do, be sure to anwser Do you want to copy the SLIP source files? Yes You should also install the latest upgrade to the SunOS kernel. APPENDIX A - ESTABLISHING CO-EXISTANCE BETWEEN PC-NFS AND 3COM 3+ SOFTWARE If you use an EtherLink Plus (3C505) from 3Com, you can run PC-NFS and 3Com 3+ software simultaneously. by following the procedure outlined below. Co-Existance may be achieved using the 3c505 board only. We are working wiht 3COM to address problems with the EtherLink II (3c503) and Etherlink/MC (3c523) boards. Note: For the EtherLink Plus (3C505) board, a minimum of 384K of on- board memory and the LinkPlus Optimizer software is required. The board should be at revision level M or higher. Installation Procedure 1. Install the 3Com 3+ User software following the installation procedure provided with the software. 2. Install the 3Com LinkPlus Optimizer software. 3. Install PC-NFS following the instructions outlined in the Installing PC-NFS manual. If installing for the first time, complete the installation and run the program NFSCONF to create a configuration. When you finish running NFSCONF, DO NOT reboot your system. Exit to DOS and follow the steps below. If this is an upgrade installation, press ESC to exit the install program and follow the steps below; DO NOT reboot your system. 4. Copy the file ETHVEC.SYS from the PC-NFS Connections diskette into the \DRIVERS directory. 5. Modify CONFIG.SYS as listed below. Note that in every case, the line listing pcnfs.sys has the /y flag on it; this is required for successful coexistance. Note: The order of these lines in your files is critical. The case of names (upper- or lower-) is not, since DOS is case insensitive. Sample CONFIG.SYS file: For EtherLink Plus (3C505) using Link Plus Optimizer, for Interrupt 5, i/o address 310, DMA interrupt 5: device=ansi.sys device=psh.sys 05 310 5 device=pth.sys device=\nfs\3c505.sys device=\nfs\pcnfs.sys /y device=\nfs\sockdrv.sys buffers=20 files=20 lastdrive=m PC-NFS 301b Patch July 19, 1990 Page 8 6. Modify the ldr.cfg file as follows: driver=\drivers\proa.sys 32 1 50 driver=buf.sys driver=\drivers\vecie3.sys driver=\nfs\3c505dx.sys driver=\drivers\ethvec.sys driver=idp.sys driver=spp.sys driver=lgl.sys program=nba.exe /s32 /n32 /r6 /t7 /d3 /i8 /l8 program=pta.exe 7. Now reboot your PC. Notes on PC-NFS and 3Com 3+ Coexistance If you attempt to use the 3+ commands before issuing a 3F LINK command, a "transmission error" will occur. Workaround: execute a valid 3F LINK command before performing any other 3+ functions. If you link (3+ 3f link) and mount (PC-NFS net use) specifying the same DOS drive letter (e.g. f:) the last command issued determines which server the drive is mapped to. Workaround: be sure to link one DOS drive to exactly one server. If in your autoexec.bat file, nfsrun (PC-NFS) is executed before minses and msredir (3Com 3+), 3+ fails. Workaround: Move nfsrun after minses and msredir in your autoexec.bat file. Special Install Instructions: ----------------------------- None.