OBSOLETE Patch-ID# 103324-03 Keywords: PC-NFS 5.1c update 5.1 cdrom switch net use /cdrom /cd /os2 Synopsis: OBSOLETED by 103519 Date: May/02/96 Solaris Release: SunOS Release: Unbundled Product: PC-NFS Unbundled Release: 5.1 5.1a Relevant Architectures: PC BugId's fixed with this patch: 1206973 1226757 1208025 1171233 1091463 1219216 1180108 1220559 1183333 1220000 1201775 1206005 1225178 1186009 1170371 1220545 1177425 1174351 1172091 1171610 1193249 1178273 1214069 1187504 1224208 1246614 Changes incorporated in this version: 1246614 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: 102068-01 for release 5.1 Obsoleted by: 103519 Files included with this patch: RTM.EXE RNMFILE.EXE RNMNIS.EXE RNMDNS.EXE RNMFILE.DLL RNMNIS.DLL RNMDNS.DLL TKLIB.DLL WINSOCK.DLL WSHELPER.EXE PCNFS.SYS PPP.SYS NFSODI.SYS NET.EXE NFSCONF.EXE PPPMGR.EXE NET.MO CONFIG.MO CONFIG2.MO PPPMSG.MO TELNET.EXE FTP.EXE RDATE.EXE RSH.EXE LPR.EXE PCNFS.386 PCNFSPPP.386 DNET.DLL PCNFS.DRV CMESSAGE.EXE FTPW.EXE LOG.EXE LPRW.EXE NISLOOK.EXE PINGW.EXE RPCINFOW.EXE STATW.EXE TELNETW.EXE MODEMS LIVPORT.SCR MORNSTAR.SCR PPPCONN.SCR PPPDIAL.SCR PPPDISC.SCR PPPHUP.SCR SOLARIS.SCR PPPDOC.PS PPPDOC.TXT Problem Description: BugID Description ----------------------------------------------------------------------- 1206973 PC-NFS 5.1a gets Btrieve errors with REGISTRAR app 1226757 File sharing between WABI and PC-NFS incorrect 1208025 cannot mount a homedir using NIS auto.home 1171233 PC-NFS 5.1 corrupts data saving Excel workbook on networked disk 1091463 PC-NFS DLL's version numbers 1219216 WINSOCK recv function fails to respond 1180108 fully qualified DNS names with WINSOCK fails 1220559 PC-NFS token ring: cannot access server on same net 1183333 Input errors when using "NETSTAT -I" 1220000 after NET LOGIN, PC-NFS checks first alias in hosts file 1201775 Redundant options with NET USE 1206005 LPR command print output garbled on HP plot files 1225178 FTP has only 16 character field for login and passwd 1186009 FTPW does NOT supply fully qualified name as passwd for anon. user 1170371 TELNET will not remap F10 key 1220545 TELNET does not handle DESCL seq correctly 1177425 TELNETW GPF when Shift-Z used 1174351 TELNETW: SET TERMINAL command line option does not work 1172091 TELNETW problems with VT220 emulation 1171610 TELNETW Swedish keyboard bugs 1193249 TELNETW vi does not work properly 1178273 RDATE does not work with non-US daylight savings * 1214069 PING -S reboots or hangs PC with ODI drivers 1187504 RSH to Solaris 2.3 server times out back to C:> prompt 1224208 PC-NFS Toolkit: Timer-Tick TSR does not preserve interrupt context 1246614 PC-NFS V5.1c NET USE drive: mount /cdrom fails PATCH INSTALLATION INSTRUCTIONS: ------------------------------- NOTE: This update should NOT be installed on a PC-ADMIN client! Doing so will prevent PC-ADMIN from working properly. This update kit is composed of four (4) files: README.51C (this file) INSTALL.BAT (installation batch procedure) PCNFS.SY_ (PC-NFS v5.1c driver) PCNFS51C.EXE (self-extracting archive of PC-NFS v5.1c files) First, verify that you have the proper version of PC-NFS installed on your system. At the DOS prompt, type the command "NET VERSION". If the system responds with a version of 5.1a or 5.1b, then you may safely proceed to install this patch. If the system responds with a version of 5.1, you must first obtain the version 5.1a jumbo patch (102068-01), and install it, before you can proceed with the installation of this patch. This kit should be installed from a clean directory on your PC's local hard disk drive. You will temporarily need about 8 megabytes of available disk storage to get through the installation procedure. About 5 megabytes of this can be immediately freed back up by purging the directory from which you perform the install. Much of the remainder of the disk usage is attributed to the fact that backup copies of the original software are created as part of the install procedure. We suggest that you retain the backup copies for a while, until you are satisfied that you have safely transitioned to this new version. Using the directory C:\TEMP-KIT as an example, the following should be done from the DOS prompt (but NOT from a DOS session under Microsoft Windows): C: MKDIR \TEMP-KIT CD \TEMP-KIT Copy the four files listed above into the C:\TEMP-KIT directory. This may be accomplished via the COPY command from a network drive or floppy disk media, or via an FTP transfer into this directory. If NFSPATH is defined, run INSTALL If NFSPATH is not defined, run INSTALL During the course of the install, there may appear a warning regarding the transfer of the serial number from the pre-existing PCNFS.SYS file to the update version. If you see the text: WARNING: the target file is NOT unserialized. It has the serial number PC-NFS....... Press Y to continue, any other key to quit Answer Y to this prompt. Additional note to Windows for Workgroups users: if you have installed Windows for Workgroups to a location other than the C:\WINDOWS directory, and you have your PC configured to run Windows networking as a primary network and PC-NFS as a secondary network, then you need to manually copy the updated PCNFS.SYS file from the NFS directory to the Windows directory, at the completion of the install procedure. After the program files are copied to the NFS directory, you will be asked which, if any, of the PPP documentation files, you wish to have copied as well. Answer: 1 for the text version "pppdoc.txt" 2 for the PostScript version "pppdoc.ps" 3 for both of the above 4 neither of the above At the conclusion of the install, you may erase the contents and remove the directory from which you installed, e.g. C:\TEMP-KIT. OPERATIONAL NOTES: ----------------- CONFIGURING PPP --------------- Instructions for configuring and using PC-NFS PPP are contained in the "Point-to-Point Protocol Guide." This guide is provided in both postscript (PPPDOC.PS) and text (PPPDOC.TXT) formats. Please print either file and use it to get started with PPP. KNOWN PROBLEMS WITH PPP ----------------------- 1. A new version of WSHELPER.EXE, included in the PPP files, enables Winsock applications to run at higher baud rates. To take advantage of it, edit PCNFS.INI in your windows directory to contain the following lines: [Config] SelectWaitEnable=Always SelectWaitLen=2 If you are using DNS, you may be able to use the following lines, instead: [Config] SelectWaitEnable=Manual SelectWaitLen=2 2. If you experience GPFs when running NetScape 1.0 with DNS as your name service, try to fix it by editing the NETSCAPE.INI file to contain the following in the [Network] section: Use Async DNS=no 3. While you can set the baud rate at up to 115,200 bits per second (bps), the maximum rate currently supported is 38,400 bps. If you experience problems at higher baud rates, drop the baud rate to 38,400, or lower. 4. Windows for Workgroups allows you to run multiple stacks over MAC drivers such as NDIS and ODI. PPP for PC-NFS does not support the NDIS or ODI MAC layer and is not designed for running multiple stacks such as Novell IPX, LAN MAN, etc with PC-NFS. Due to this, you must configure PC-NFS as the the primary network. PPP for PC-NFS does not support a secondary network. NOTE: You can run NetBIOS applications over TCP/IP within the single stack supported by PPP using the PC-NFS NB.EXE component.