All Rights Reserved
This product and related documentation are protected by copyright
and distributed under licenses restricting its use, copying, distribution,
and decompilation.  No part of this product or related documentation
may be reproduced in any form by any means without prior written
authorization of Sun and its licensors, if any.


RESTRICTED RIGHTS LEGENDS

Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of The Rights
in Technical Data and Computer Software clause at DFARS 252.227-7013
or subparagraphs (c) (1) and (2) of Commercial Computer Software --
Restricted Rights at 48 CFR 52.227-19, as applicable.

Unpublished -- rights reserved under the Copyright Laws of the
United States.


TRADEMARKS
Sun, Sun Microsystems, SunSelect, the Sun logo, the SunSelect logo, NFS,
and PC-NFS are trademarks or registered trademarks of Sun Microsystems,
Inc. Unix and OPEN LOOK are registered trademarks of Unix System
Laboratories, Inc.

Intergraph is a registered trademark of Intergraph Corporation.

Microsoft is a registered trademark and Windows NT is a trademark of
Microsoft Corporation.  All other product names mentioned herein are
the trademarks of their respective owners.


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

-------------------
Version Information
-----------------------------------------------------------------------------

Product:	PC-NFS for Windows NT 
Number:		SSBY534AC-0201A (Intel)
		SSCB534AC-0201A (Alpha)
		SSCJ534AC-0201A (Mips)
		SSCK534AC-0201A (Power PC)
Version:	02.01.06.00
Date:		07-JUN-1995
Description:	PC-NFS for Windows NT is a kernel-based network file system,
		NFS, client that enables Windows NT system to gain access to 
		any system running as an NFS server.  The product also 
		contains a Network Time Protocol client/server, Rsh server,
		windowed ftp, windowed telnet, windowed telnet3270,
		showmount, and rpcinfo. 
-----------------------------------------------------------------------------
End of Version Information
-------------------------- 



-----------------
Installation Help
-----------------------------------------------------------------------------

The product can be loaded by disk or across the network if the contents of the 
disks have been copied to a shared network drive.  In either case, execute the 
command, setup.exe, from either a DOS command window or through the File 
Manager.  The setup utility will make sure your system has enough disk space
to load the product.  If there is not enough disk space, the setup utility 
will warn the user about insufficient disk space and will stop the installation.
Upon completion of the space verification, the user will be prompted to 
enter their name, company name, and serial number.  The serial number must be
typed in as printed on ther serial number sheet that comes with the kit.  The 
serial number will uniquely identify the user.  The serial number is also used 
to brand the product's programs.  After the user information is registered,
the user will be requested to provide the location for the product to download.
After the product downloads, the user will be prompted to reboot the system. 
The system must be rebooted in order to start the NFS drivers and utilities.
------------------------------------------------------------------------------
End of Installation Help
------------------------



---------------
Getting Started
------------------------------------------------------------------------------

Please see the online help for PC-NFS:        ntnfs.hlp
			       Telnet3270:    gr3270.hlp
			       FTP:	      wftp.hlp
			       Telnet:	      telnetw.hlp
			       RPC utilities: rpcinfo.hlp
------------------------------------------------------------------------------
End of Getting Started
----------------------


-------------
Documentation
------------------------------------------------------------------------------

Documentation is provided in the form of WinHelp files.  Please see the section
"Getting Started" for the list of WinHelp files.

------------------------------------------------------------------------------
End of Documentation
--------------------



--------
Training
------------------------------------------------------------------------------

No training is available for this product.

------------------------------------------------------------------------------
End of Training
---------------



-------
Support
------------------------------------------------------------------------------

If the product has been purchased directly from Intergraph Corporation, you 
may call 1-800-633-7248 for product support.  

------------------------------------------------------------------------------
End of Support
--------------

-----
Fixes
-----

The following problems have been fixed in this or past releases:

[TR #289501060]
    The print to command feature would not work.

[TR #289501054]
    The '&' key was incorrectly displayed.

[TR #289501060]
    The PF10 key was not being sent to the terminal emulator.

[TR #289501177]
    Alternate font was not being displayed for models with 132 columns.

[No TR]
    Attempts to run a 16bit application would hang.  In addition, if the a:
    drive is double clicked on in File Manager, File Manager would hang. 
    These problems are only seen with pre pcnfs for windows nt version 2.1.2
    and windows nt 3.51 pre build 1050.

[TR #289501458]
    Wftp; when local commands fail, such as goto or remove directory, there 
    isn't any error message stating the command fails.  It appears the command
    was successful.  

[TR #289408379]
    The user name in nfslogin was limited to 9 characters.  The new limit is 
    now 28.  A limit of 28 should take care of most servers.

[TR #289500177]
    The share/lock owner handle were different. This would confuse
    some servers.  They are now transmitted as the same.

[TR #289409743]
    The nfslogin dialog box would pop up after a user logs into NT even
    though the "User NT username/password" option was chosen and the 
    pcnfsd server was active.

[TR #289409267]
    Unable to compile a simple program with VC++ 2.0 on version 3.5 of the 
    OS and user belonged to more than 8 secondary groups.

[TR #289408350]
    Unable to delete very large directories that reside on NFS mounted drives.

[TR #289409617]
    Under version 3.1 of the OS, the FileManager would die with a Dr. Watson 
    error after only a few NFS drives where mounted.

[TR #289409468]
   After the second WNETEnumResource(), winsock is disabled if PC-NFS is 
   loaded to the system. 

[TR #289409544]
    Would get the error message that the Pc-NFS driver had not started but was
    able to start the driver after the system came up and the user logged in.

[TR #289409219]
    If EtherLink II cards are being used in a system running version 3.5 of the
    OS, the default 4k read buffer was not occuring.  Users had to manually
    set the read buffer. 
  
[TR #289409269]
    Linking with Microsoft C++ would sometimes cause the link to fail.  Often
    resulting files would be 2meg in size regardless of amount of source code 
    that is was being compiled and linked.
 
[No TR]
    While attempting to load PC-NFS for Windows NT to a new system, the setup
    procedure would pop up an error box stating, "While Registering with 
    OLE-Server Setup had a problem with reg.dat, shell.dat or diskspace.

[TR #289500823]
    Telnetw would report that it could not find the file dcsfonth.fon. 

[TR #289409737]
    Telnetw had several references to hard documentation that was not in the 
    on line help.

[TR #289409456]
    Unable to write a file that is greater than 8k in size and locking is 
    enabled on the NFS drive.  

[TR 289408924]
    GR3270 will fail to start on a Windows NT 3.5 system that has been 
    configured to use large fonts from the Display Control Panel applet.

[TR #289500943]
    wftp would not display files and "directories" when attached to a IBM OS/MVS
    system.

[No TR]
    wftp would display symbolicly linked files only in the remote directory 
    window.

[TR #289501492]
    The rcp server would hang while trying to recieve files to invalid paths.


------------
End of Fixes
------------

-------------
Open Problems
-----------------------------------------------------------------------------

The following is a list of known problems that will be addressed in future 
releases.

[No TR]
    Under Windows NT 3.51, if the Microsoft NetWare network provider is 
    loaded in conjunction with PC-NFS for Windows NT, then the "showmount"
    functionality in FileManager only works correctly for NFS servers if the 
    NFS server's name that is entered in the Path field is proceeded with a
    colon ":".   If the colon ":" does not proceed the name, the server's name
    will be placed under the first network provider heading in the the Shared
    Directories box. 

[TR #289408292]
    If a directory is set to read only any attempt to copy that directory
    to a nfs mounted file system with umask set to octal 000 will fail.
    The write attribute on the unix side does not get set so the copy
    indicates a permission violation.

[TR #289408283]
    TELNETW:  Cannot send files using Xmodem

[TR #289408276]
    TELNETW:  Cannot receive file using Xmodem.

[TR #289408275]
    TELNETW:  Cannot successfully transfer large file from pc to server.
    One was sent ascii type that was about 1.4Mbytes and after about 24%
    was transferred, it just stopped.  Could not access network and have
    to powercycle sytem after hang.

[TR #289408269]
    TELNETW:  if you try to receive a file in ASCII the system hangs.

[TR #289407686]
    This is a problem under 528 and 683.
    If the NFS server returns a zero for a cookie value for "." and/or
    zero as a file id for "..", then the client is stuck in an
    infinite loop of "lookups on .".  The server does return on each
    lookup on ".".  Though a zero cookie value violates the protocol specs, 
    the client must be able to gracefully handle this case.                                         

[TR #289407415]
    NTPD currently writes the NTP drift value to the registry every four
    seconds.  This makes the registry editor difficult to navigate because
    the database is constantly updating.  Data which is that transient
    should be maintained in a file.


[TR #289405868]
    DATE:  14 April 1994
    PROBLEM:  If you disable the TCP/IP Bindings and reboot, doing
    equivalent 'net view' type command with in File Manager takes 3
    minutes to complete.  Disabling the NFS Client completely improves
    the response time to 5 seconds.


[TR #289405614]
    In version 1.0 if you copy a file from the NT node to a CLix node doesn't 
    retain the original time stamp on the file, it changes it to the current 
    time/date. Moving a file across the mount in the same direction retains 
    the time/date. PC-NFS on DOS retains the time/date on a copy and so does 
    Clix to Clix and Clix to NT copies. This was verified using FAT file 
    systems on DOS and NT.

[TR #289501951]
    The RshSvc Service fails to execute 16bit non-graphic DOS binaries
    properly. Under NT35 the process hangs. Entering an interrupt will
    return the remote rsh/rcmd to the prompt. Under NT3.51 the process
    fails and does nothing.

[ No TR ]
    In NT version 3.5, applications will not be allowed to interact with the 
    Desktop from the RshSvc Service (calc, word, notepad, etc...), even if the
    'Allow Service To Interact with Desktop'  is checked. This seems to be a 
    problem with  NT 3.5.  The  problem goes  away after  loading NT 3.51, a
    possible work around is to try to "rcmd nt_node 'cmd /c notepad'". 

[No TR]
    Files prefixed with com, con, nul, prn, aux, lpt1 or lpt2 (eg 'aux.txt'),
    will not be copied. These are reserved device names under NT.
