
-------------------
Version Information
-------------------------------------------------------------------------------
Product:        DiskAccess        DiskAccess Installation
Number:         SSBY897AC-0100A
Version:        01.01.00.33
Date:           25-JUL-1996
Description:	Intergraph DiskAccess is a kernel-based network file 
                system (NFS) client that enables a Windows 95 system
		to mount file systems located on UNIX and other NFS
                server systems. 

NOTE:           Windows 95.
------------------------------------------------------------------------------- 
End of Version Information                                                      
--------------------------                                                      

-----------------
Installation Help
-----------------
NOTE:  The DiskAccess delivery structure has changed slightly from
previous releases.  You may install this release without removing
a previously installed release.  However, if you should later decide 
to remove DiskAccess, some files from the previous release will not be 
deleted.  If you plan to remove DiskAccess in the future and you want 
files from all releases to be automatically deleted, you should remove 
the previously installed release before installing this one.

The DiskAccess product consists of a set of drivers, dynamic link
libraries, executables, and related documentation files.  By default,
the setup procedure installs all but the utility and documentation files 
into %SystemRoot%\SYSTEM, and all files into the product directory. The 
system root directory is the one in which Windows 95 is installed, typically
C:\WINDOWS.

Setup prompts for an installation path for the utility and documentation 
files.  The default is C:\Program Files\DiskAccess.  If the product already 
exists in the specified directory, setup prompts to verify overwriting of 
this directory.

After installing all files, setup updates all necessary data in the registry 
and adds DiskAccess as a common program group in the Start Menu.  Because 
DiskAccess cannot be started until the system reboots, setup provides the 
option to immediately reboot the system.

------------------------ 
End of Installation Help 
------------------------ 


---------------                           
Getting Started                           
---------------                           
After installation, the system must be rebooted before DiskAccess can
be started.  Certain default mount options are preset at the factory.  
To modify the factory settings and establish your own defaults, run
the DiskAccess Configuration utility from the Control Panel.

NOTE: The first time a user logs in after installing DiskAccess, the NFS
login may fail and the user will be prompted to log in and configure
DiskAccess.  These settings will then be used as the default for that user.
Please see the New Features section for more details.

----------------------                    
End of Getting Started                    
----------------------                    
                                          
-------------                             
Documentation                             
-------------                             
On-line help is available by selecting the Help button on the DiskAccess
configuration dialog, which is accessed from the Control Panel.  You may
also directly access the file daccess.hlp in the product directory.

--------------------                      
End of Documentation                      
--------------------                      
                                          
--------                                  
Training                                  
--------                                  
No training is currently available for this product.

---------------                           
End of Training                           
---------------                           
                                          
----------------                          
Product Sections                          
----------------                          
-----------------------                   
End of Product Sections                   
-----------------------                   
                                      
---------                                 
New Fixes                                 
---------

----------------                          
End of New Fixes                          
----------------                          
                                          
------------        
New Features        
------------  
Version 01.01.00.32

A new version of the Windowed Telnet application is included 
in this version of DiskAccess.  Please see wtelnet\readme.txt 
in the product directory for more information.

Version 01.01.00.25

Due to numerous customer requests, DiskAccess defaults are now
saved per current user instead of per system.  Please note that
if Windows 95 is configured such that all users have the same
user profile, then all users will continue to have the same
DiskAccess defaults.  However, if Windows 95 is configured such
that users have individual profiles, then each user will have his
own DiskAccess defaults.  As a result, when a user logs in for 
the first time after installing DiskAccess, the NFS authentication 
may fail and the user will be prompted to retry the login and thus 
configure the defaults.  DiskAccess can be configured not to attempt 
authentication at login.  Refer to answers.wri in the product directory
for instructions.

Because of potential security problems with persistent connections,
DiskAccess has been modified to cancel all NFS connections when a
user logs off.  When another user logs in, any persistent connections
in the current profile will be attempted.  By default, these connections
will continue to be made as in the past, i.e. NFS authentication is
attempted using the defaults for that connection without prompting
the user for a password.  However, the system can be configured to force 
the user to enter a password for authentication at reconnection if the 
user who is currently logged in is different from the user who created 
the persistent connection.  Refer to answers.wri in the product directory 
for instructions on enabling this feature.

------------------- 
End of New Features 
------------------- 
                    
-------------       
Open Problems       
-------------       
Windowed FTP File Transfer Failures
-----------------------------------
When using Windowed FTP to transfer a file with a filename that begins
with a space or tab, the error "no such file or directory" will be
returned from certain servers, among them Windows NT 3.5 and Windows NT 3.51.
This has been reported to Microsoft as a bug, and to other vendors
with whom the problem has been seen.

System hang - Intergraph TR #289503524
-----------
It is possible to hang the system by starting a batch file that continuously
mounts and unmounts NFS shares and then using the Explorer Map Network Drive
to mount an NFS share.  The share name specified in the Explorer dialog must
be in the UNC name format (\\server\share) to reproduce this condition.  This
problem may be avoided by specifying the share name in the NFS colon format
(server:/share).

When the UNC name format is specified, LAN Manager must determine if it should
perform the connection.  Apparently, LAN Manager becomes deadlocked with the
NFS mount requests generated by the batch file.  By using the NFS colon format,
LAN Manager immediately determines that it should not perform the connection
and passes the request to NFS.

Remote NFS share name specification for explorer /e, /root, - Intergraph TR
-----------------------------------------------------------   #289503525
The explorer may be started from the command line.  The syntax is
explorer /e, /root, <pathname>

When specifying the path to an NFS share or directory do not use UNC
style names.  UNC names produce inconsistent results.  For the best
results first map the remote NFS share to a local drive letter by using
the explorer or the net use command.  Specify the NFS pathname as a drive
letter based name.

For example:

	explorer /e, /root, f:\usr\tmp
	explorer /e, /root, f:\

Note that a backslash must be specified after the drive letter to display
the share root directory.

Property Sheet inconsistencies
------------------------------
Inconsistencies can occur if file attributes are set from either the NFS
Attributes property sheet or the General property sheet for a file.  A
Windows 95 bug prevents the General property sheet from correctly handling
file attributes set from the NFS Attributes property sheet.  This bug has
been reported to Microsoft.  As a workaround, use either the Apply button 
or the OK button - but not both - to change the attributes.  If you use
Apply, use the Cancel button to dismiss the dialog.

Long delays with eventual timeouts
----------------------------------
If Windows 95 has been installed with DNS disabled and there is
no hosts file, TCPIP broadcasts for a DNS server any time a TCPIP
connection is attempted.  For DiskAccess, this means that PCNFSD
authentication and network browsing will timeout after a long
delay.  This is a Windows 95 implementation issue which cannot
be remedied by DiskAccess.  The only way to avoid the delay is 
to either configure a DNS server or create a valid hosts file on 
the system.  

NET USE syntax for mounting NFS shares
--------------------------------------
The Windows 95 NET USE command for mounting shares from the command line
does not allow mounting share names longer than servername and a single
sharename element.  Refer to answers.wri in the product directory for
possible workaround solutions.

Sharename Limitations for Mapping Network Drives
------------------------------------------------
The Windows 95 OS (MPR and the IFS Manager) limits the sharename that may be
specified when mapping network drives.  The last element of the sharename path
cannot exceed eight characters. (Although the connection may succeed, it
will fail on reconnection of persistent connections.)  Also, NET USE does not 
maintain case on sharenames, so all NFS mount sharenames are forced to lowercase.  
These have been reported to Microsoft as OS bugs.

Connecting to a server that supports both NFS and LAN Manager
-------------------------------------------------------------
There is a problem with the way Windows 95 handles connecting to servers
that support more than one protocol understood by the client.  Once Windows 95
determines that the server supports Windows LAN Manager networking, the OS 
will never again try to access the server using NFS until the client is 
rebooted.  This occurs with any Windows 95 client connecting to a server 
that supports multiple protocols along with LAN Manager, not just NFS.
Windows 95 may make IPC (InterProcess Communication) connections to LAN
Manager servers from time to time unrelated to Map Network Drive attempts
that will block NFS access to multiple protocol servers.

Windows 95 will never timeout its cache of servername to protocol once it
determines a protocol the server supports on an access.  This may also
prevent LAN Manager access to the specific multiple protocol server once 
an NFS connection has been established.  This has been identified by 
Microsoft as an OS bug.

Deleting a DOS supported NFS network printer
--------------------------------------------
If you have another LanMan network printer which is configured to
support DOS printing, the CancelConnection request goes to the LanMan
network provider instead of NFS network provider, and thus it fails to
delete the network printer from the Persistent registry key.  You can
manually end the printer port capture by going to the property sheet of
any printer.  Within the property sheet, there is Details folder and
click on End Capture.  It will list all the ports captured.  Select the
one that you would like to delete and click OK.  Or you can delete the
registry key \\HKEY_CURRENT_USER\Network\Persistent\LPT# and reboot the
system.  This has been filed to Micorsoft as a bug.

--------------------
End of Open Problems
--------------------
