Patch-ID# 103519-03
Keywords: update 5.1D 5.1C 5.1B 5.1A
Synopsis: PC-NFS 5.1: Patch to update to 5.1D
Date: Jan/23/97

Solaris Release:  

SunOS Release: 

Unbundled Product: PC-NFS

Unbundled Release: 5.1

Relevant Architectures: i386
NOTE:PC

BugId's fixed with this patch: 1206973 1226757 1208025 1171233 1091463 1219216 1180108 1201047 1220559 1183333 1220000 1201775 1206005 1225178 1186009	1170371	1220545	1177425	1174351 1172091	1171610	1193249	1178273	1214069	1187504 1224208 1148284 1207053 1207651 1201715 1100477 1094176 1179192 1201732 1216356 1178273 1201744 1224175 1202254 1202166 1202803 1106768 1175164 1180841 1169390 1243605 1231494 1201740 1221514 1203059 1201731 1202701 1228148 1237472 1206682 1202256 1202712 1181051 1201757 1257386 4006684

Changes incorporated in this version: 1257386 4006684

Patches accumulated and obsoleted by this patch: 103324-03 103519-01

Patches which conflict with this patch:  

Patches required with this patch: 102068-01 
                           NOTE:  for revision 5.1 only

Obsoleted by: 

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
PRT.COM
NET.EXE
NFSCONF.EXE
PPPMGR.EXE
NET.MO
CONFIG.MO
CONFIG2.MO
PPPMSG.MO
RDATE.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
LS.EXE


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
1201047 file corruption on Solaris 2.x (pcn4883)
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
1148284 sockets, Cannot connect > 7 sockets SDR# pcn3766
1207053 FTPW fails to cope with VMS directory structure
1207651 protected mode toolkit app returns bad descriptor
1201715 Quirks unmounting network printer
1100477 Printing from WP is done with no respect to the timeout
1094176 Problems accessing long file paths
1179192 pcnfs lpr client spool area to be configurable
1201732 nfsconf hangs when slipconf.db is incomplete
1216356 pc-nfs gives error when install to HD after booting off floppy
1178273 RDATE does not work with non-US daylight savings (improved over 5.1c)
1201744 Specific route fails
1224175 Accessing vecie6.sys driver from PCNFS using toolkit locks PC
1202254 Net route entries use subnet
1202166 Delete key not working - net login
1202803 No win utils, but get pcnfs.grp anyway
1106768 DOS FindFirst/FindNext returns invalid err codes
1175164 incorrect license violation detection error
1180841 support out-of-sequence packet reordering
1169390 getpwuid can't handle uids > 32767
1243605 mounting from PC-NFSpro NFS server fails to get correct pwd
1231494 PC-NFS locks windows global heap permanently
1201740 wfw 2nd net ndis in config.sys
1221514 NFS 1.5 client to NFS client 2.0 does not work with WFW
1203059 netmask not deleted from network.bat
1201731 senddgram buf size 1-512 only
1202701 change adapter gives bogus msg for WFW 3.11
1228148 Z-Mail and RDM from Interleaf doesn't work together
1237472 PCNFS does not free up its sockets when using NIS
1206682 telnetw doesn't recover from execution of DOS commands
1202256 can't enter hexadecimal subnet mask
1202712 user not told win files updated
1181051 When UID > 32000, the ls command shows UID as negative number
1201757 ODI stress testing fails
1257386 Add clipboard support to WSHELPER.EXE
4006684 PC-NFS V5.1d NLM unshare posts unsupported messages


Patch Installation Instructions: 
-------------------------------- 
NOTE: This update should NOT be installed in a PC-ADMIN client! Doing so will
prevent PC-ADMIN from working properly.

To make downloading this update kit easier this kit is composed of two (2) 
files:
 
        NFS51D.EXE   (self-extracting archive of PC-NFS v5.1d files)
        README       (this file)
 
After downloading the two files listed above, execute the NFS51D.EXE file.
This will produce the four (4) files listed below. The files listed below are
sized such that they can be transported on 1.4 Mbyte floppies if necessary.

	README.51D   (install instructions and release notes)
	INSTALL.BAT  (installation batch procedure)
	NFS51D-1.EXE (self-extracting archive of PC-NFS v5.1d files)
	NFS51D-2.EXE (self-extracting archive of PC-NFS v5.1d 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, 5.1b, or 5.1c, then you may safely proceed 
to install this patch.  If the system responds with a version of 5.1, you 
first must obtain the version 5.1a jumbo patch (102068-01), and install it, 
before you can proceed with the installation of this patch.

The 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 <NFS directory>

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.

Installation Notes:
All drive letter and directory name references are PC-NFS defaults. If 
you have installed PC-NFS or the patch file on a different drive, or in 
a different directory, substitute your drive and directory names in the 
example commands above.
 

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.


----------------------------------------------------------------------------

CHANGES IN PROGRAM USAGE
------------------------

1. RDATE utility.  The version of RDATE.EXE included with this update now
   accepts a -d command-line option before the hostname.  This switches
   the program to use the DAYTIME protocol instead of the default TIME
   protocol.  The DAYTIME protocol has the advantage of working more
   reliably in non-US time zones where daylight savings time is used.
   The restriction on the use of the DAYTIME protocol is that it must only
   be used when the PC and the server are located within the same time zone.


2. LPR Windows utility.  To override the default spool directory, set the
   SpoolPath in the QueueOptions section of lprw.ini.  For example, to set
   the SpoolPath to the directory "mysppath" in the root directory on drive
   C, use the following:

	[QueueOptions]
	SpoolPath=c:\mysppath


3. PC-NFS Broadcast option.  An option has been added to change how
   PCNFS.SYS handles broadcast packets. The default action is to send
   broadcast packets that contain the subnet mask.  Certain routers can't
   handle these packets properly, as evidenced by bug #1175164.

   The /t command line option causes PCNFS.SYS to use the global
   (255.255.255.255) broadcast address.

   The /t option is added to the end of the "device=[path] PCNFS.SYS"
   line of config.sys if PC-NFS is the primary network.  When PC-NFS is the
   secondary network under Windows for Workgroups the modification
   is made in the system.ini file in the [network drivers] section.

   Example of file config.sys:

	DEVICE=C:\NFS\PCNFS.SYS /t

   Example of file system.ini:

	[network drivers]
	transport=ndishlp.sys,c:\nfs\pcnfs.sys,  .   .   .   .
	c:\nfs\pcnfs.sys='/t'

   This option should not be used unless it is determined to be
   necessary.  Use of this option increases network activity beyond
   the scope of the subnet.

   Please note that presently there is no way to set this option from
   the nfsconf utility.


4. PC-NFS new 'current working directory' algorithm option.  An option
   has been added to change how PCNFS.SYS determines its current working
   directory on an NFS-mounted drive.  Because the method of determining
   the current working directory breaks down when using a file system
   exported from a PC-NFSpro NFS server (see bug #1243605), an alternative
   method has been developed.

   The /w command line option causes PCNFS.SYS to activate this new method.
   The default is to use the existing method.

   The /w option is added to the end of the "device=[path] PCNFS.SYS"
   line of config.sys if PC-NFS is the primary network.  When PC-NFS is the
   secondary network under Windows for Workgroups the modification
   is made in the system.ini file in the [network drivers] section.

   Example of file config.sys:

	DEVICE=C:\NFS\PCNFS.SYS /w

   Example of file system.ini:

	[network drivers]
	transport=ndishlp.sys,c:\nfs\pcnfs.sys,  .   .   .   .
	c:\nfs\pcnfs.sys='/w'

   Please note that presently there is no way to set this option from
   the nfsconf utility.

5. PC-NFS lock retry option.  This option has been present in PCNFS.SYS
   since version 5.1, but has been heretofore undocumented.

   Users wishing to implement a timeout feature for file- or record-locking
   of network files, may use the /kn command-line option of PCNFS.SYS,
   where 'n' is any integer value which specifies the number of times to
   retry the lock.  When the number of specified retries is reached,  PC-NFS
   will fail the locking call and return.  This curtails the behavior of
   polling ad infinitum in search of a successful locking call.

   The /kn option is added to the end of the "device=[path] PCNFS.SYS"
   line of config.sys if PC-NFS is the primary network.  When PC-NFS is the
   secondary network under Windows for Workgroups the modification
   is made in the system.ini file in the [network drivers] section.

   Example of file config.sys:

        DEVICE=C:\NFS\PCNFS.SYS /k5              (sets for 5 lock retries)

   Example of file system.ini:

	[network drivers]
	transport=ndishlp.sys,c:\nfs\pcnfs.sys,  .   .   .   .
        c:\nfs\pcnfs.sys='/k5'

   Please note that presently there is no way to set this option from
   the nfsconf utility.

6. In ODI environment, if remote connections are droped for unexplained
   reasons, this could be due to Media Access Card may not be able
   to cope up with transmit traffic generated from PC-NFS ODI shim (NFSODI.SYS)
   This can be now verified by `Outgoing packet error' count in NETSTAT;
   e.g. NETSTAT -i will show `Oerrs' to be non zero.

   Also /Wn option allows user to change the amount of time ODI shim
   will wait before deciding to drop the packet. 
   Default value is n=5 PC-ticks. Each PC-tick is 18.5 milliseconds

   The /Wn option is added to the end of the "device=[path] NFSODI.SYS"
   line of config.sys.

   Example of file config.sys:

   DEVICE=C:\NFS\NFSODI.SYS /W4
       -or- if using /B switch for board number to use.
   DEVICE=C:\NFS\NFSODI.SYS /B1 /W4
       This will set ODI shim to wait for 4 PC-ticks(74ms approx.) before
       deciding to drop the packet.

   Please note that presently there is no way to set this option from
   the nfsconf utility.

7.  File locking and Interoperatibility issue:
	If your site uses different NFS clients from Sun (e.g. PC-NFS,
	PC-NFSpro, Wabi, SunPC, or PC-Admin), proper file locking behavior
	among these clients is guaranteed only if you use compatible versions
	of these clients together. See the tables below.

	File locking functionality is used by many programs (such as MS Word
	and Ms Excel) to guarantee exclusive access to certain portions of a
	file. PC-NFS supports file locking on drives mounted with /ms - must
	share option. Other NFS client from Sun also support file locking, such
	as PC-NFSpro, Wabi, SunPC, and PC-Admin, but different incompatible
	implementations have evolved over time. If NFS clients with
	incompatible (i.e. different) locking mechanisms are used to access the
	same file, unexpected behavior may result.

	PC-NFS 5.1.D is known to be compatiable with:
		PC-NFS 5.1
		PC-NFS 5.1.A
		PC-NFS Pro 1.1.1.0
		PC-NFS Pro 2.0
		PC-Admin 1.0 and 1.5
		Wabi 2.1B and above.
		SunPC 4.1 + patch 102924-04 (Solaris 2).

	PC-NFS 5.1.D is known to be incompatiable with this older versions:
		PC-NFS 5.0
		PC-NFS 5.1.C
		PC-NFS Pro 1.1.0.0
		Versions of Wabi before 2.1B
		SunPC 3.1b (Solaris 1)

	If you have PC running PC-NFS 5.0 upgrade it to PC-NFS 5.1
	If you have PC running PC-NFS 5.1.C update it to PC-NFS 5.1.D

----------------------------------------------------------------------------

PCNFSD DAEMON CHANGES
---------------------

The following bugs have been fixed in the PCNFSD daemon (rpc.pcnfsd):

BugID		Description
------- ---------------------------------------------------------------
1226593 panic: data fault: pcnfsd under Solaris 2.4
1230808 security hole: rpc.pcnfsd can be used to chmod 777 secure files
1228158 rpc.pcnfsd under SunOS 4.1.4 dies under heavy load

These fixes are included in general Solaris/SunOS patch numbers 103095-02 
and 103096-02 (not included in this patch kit) which can be downloaded from 
Sun's Web site http://access1.sun.com.  

To download the daemon patches, connect to http://access1.sun.com using a Web
browser.  Click on the "search" button to enter the search screen.  Select
"patches" under "unbundled" products, enter the patch number (e.g. 103095-02)
to search for, and then click on the "search" button.  Click on the associated
readme file for the patch to access patch info and download instructions.


Special Install Instructions: 
-----------------------------
None.
