-------------------------------------------------------------------------
			         READ ME
			 InterDrive(R) 95 Version 1.0 
		   
-------------------------------------------------------------------------

This file describes last-minute changes, bug fixes, and enhancements that
do not appear in other printed or online documentation. This file also 
describes some known problems and suggested solutions.

				 CONTENTS

        1. Installing InterDrive 95
           1.1 Upgrading from a Previous Beta of InterDrive 95
           1.2 Installing the InterDrive 95 Software
           1.3 Files Added by the Installation
        2. Supported Features in This Release
        3. Documentation Changes
        4. Known Problems
        5. Case Sensitivity of Login Names
        6. Case Sensitivity of Filenames in Windows 95
        7. Connecting from Network Neighborhood with No PCNFSD Available
        8. Using InterDrive 95 and Microsoft Clients on the Same System
        9. Connecting to Print Servers That Support Both LPD and NFS        
       10. Finding Files and Folders on Network Drives
       11. Opening and Saving files through Network Neighborhood Browsing
-----------------------------
1.  Installing InterDrive 95
-----------------------------

This section describes InterDrive 95 installation considerations
and lists the files that are added as a result of installation. For
complete details, refer to the "Installing InterDrive 95" card that
accompanies your software.

1.1  Upgrading from a Previous Beta of InterDrive 95
----------------------------------------------------

If you are currently running a Beta version of InterDrive 95, you
must remove it before installing the FCS version.

To remove the current version,

1. Right-click the Network Neighborhood icon, and, in the menu that
   appears, click Properties.

2. In the Configuration property sheet of the Network dialog box that
   appears, select FTP Software NFS Client (InterDrive 95); then click Remove.

3. Click OK.

4. Restart your PC.


1.2  Installing the InterDrive 95 Software
------------------------------------------

InterDrive 95 is supported on any system that is running a released version
of Windows 95. InterDrive 95 is no longer supported on the Beta version of 
Windows 95.

To prepare for using InterDrive 95:

o Verify that a network card or modem is installed in your PC.

o Install and configure TCP/IP protocol support, if you have not done 
  so already. Use property sheets available through the Network Neighborhood
  or the Network Control icon to configure at least the following information:
    - Your system's hostname and IP (Internet Protocol) address
    - Your system's subnet mask
    - The address of at least one gateway system for communicating with
      systems beyond your local area network (LAN)

  In addition, you should configure a service for mapping hostnames to
  IP addresses. This service can be in the form of a Domain Name System
  (DNS) server, or a HOSTS file in the directory where your Windows 95
  files are installed. Without a name service, you can connect to a
  network server only if you specify its complete IP address (instead of 
  the hostname).

  See your Windows 95 documentation for details on installing and
  configuring TCP/IP.

Before you install InterDrive 95:

You need to copy an updated version of the NETFTP.INF file from the
FTP Software NFS Client installation disk into the \INF directory beneath 
the directory where your Windows 95 files are installed. Note that by 
default, the \INF directory is hidden, and so is the NETFTP.INF file. You 
can make the \INF directory your current directory or copy files into it 
even if it is hidden.

For details on this and other InterDrive 95 installation steps,
see the "Installing InterDrive 95" card that accompanies your software.

After you install InterDrive 95:

o It is recommended that you configure the names of NFS servers that
  you want to be able to browse in Network Neighborhood. InterDrive 95
  adds server names automatically to the NFS Servers group after you connect to
  them, but you can preconfigure server names in the group if you want
  to be able to browse those servers immediately. See the "Installing
  InterDrive 95" card or Chapter 3 of the InterDrive 95 "User's Guide" for
  details.

o Verify that the daemons (software components) required to support NFS
  file and printer sharing are configured and running on each host whose 
  resources you want to use. In particular, InterDrive 95 needs to contact 
  an authentication server to verify your username and password when you 
  attempt to connect to network folders and printers. An authentication 
  server (typically called PCNFSD) is usually a built-in component of the 
  NFS server system.

  If no authentication server is running on the system whose resources you
  are trying to use, you can do either of the following:

    o Configure a single, centralized authentication server to verify
      all connection requests in your network. 
  
    o Log in as user "nobody" with no password.

    See the InterDrive 95 "User's Guide" for details.


1.3  Files Added by the Installation
------------------------------------

Installing InterDrive 95 adds the following files to your Windows 95
system:

   File                      Function
   -------------             ------------------------------------------

   NETFTP.INF                Contains information that Windows 95 uses
                             to install and configure InterDrive 95. You
                             must copy this file manually.

   VIDRIVE.386               NFS redirector VxD.

   IDHELPER.EXE              Program that assists print redirection.

   IDNP32.DLL                The NFS network provider DLL.

   IDNPEXT.DLL               DLL that supports configuring of
                             properties for individual mapped drives
                             and permissions for files and folders
                             within mapped drives.

   IDNPNDI.DLL               DLL that supports configuring of 
                             InterDrive 95 properties.

   IDPP32.DLL                The print provider DLL.

   IDPPLPR.DLL               DLL that supports print redirection to
                             LPD servers.

   IDRIVE95.HLP              Context-sensitive help for InterDrive 95
                             property sheets.

   RPC4W32.DLL               Remote Procedure Call library DLL.


-------------------------------------
2. Supported Features in This Release
-------------------------------------

This section summarizes the features that are available in InterDrive 95.
You can
  
   o Run InterDrive 95 over the Microsoft TCP/IP protocol stack, 
     or over the TCP/IP kernel available in FTP Software(R) 
     OnNet (TM) for Windows Version 2.0.
   o Use an InterDrive 95 property sheet to configure hostnames 
     in the NFS Servers group in Network Neighborhood.
   o Browse the available resources in the NFS Servers group, use the
     resources, and optionally configure persistent connections to them. 
   o Configure connections that you want to use regularly by mapping
     a folder to a network drive or configuring a network printer.
   o Print to a network printer managed by an LPD or NFS print server.
   o Disconnect file systems and printers that you no longer use.
   o Use InterDrive 95 property sheets to change basic security, file 
     management, caching, tuning, and printing properties.
   o User folder-specific property sheets to view and change the properties
     of a mapped drive, overriding global InterDrive 95 properties
     for that drive. View and change permissions for files and folders
     within a mapped drive, if you have the appropriate access. 
   o View context-sensitive help for InterDrive 95 property sheets.

For details on using InterDrive 95, see the InterDrive 95 "User's
Guide." 

------------------------
3. Documentation Changes
------------------------

The following features were added to the software after the documentation
went to print:

3.1 Changing Properties for Mapped Network Drives
-------------------------------------------------

In addition to specifying global properties, which affect all network
folders that you use through InterDrive 95, you can view and set
certain properties for individual mapped drives.

To view or change the properties of a mapped drive, right-click its
icon; then, in the menu that appears, click Properties.

     Click this tab     To do this
     --------------     --------------------------------------------------

     Drive Options      Change properties such as symbolic link processing,
                        lowercase name mapping, and tuning values. 

     NFS Attributes     Change the default permissions applied to all
                        new files and directories created on the mapped drive.
                        You can also view the user ID and group ID associated 
                        with the mapped drive, and optionally change the 
                        group ID, if you are a member of multiple groups, and 
                        if the NFS server supports multiple groups. 

    Disk Quota          View the amount of disk space available to you on
			the network drive.

If you set a drive property that is different from the global
setting for that property, the drive property overrides the global
property for that drive.

3.2 Viewing NFS Attributes of Folders and Files on a Network Drive
------------------------------------------------------------------

You can also view the current NFS attributes of any folder or file on
a network drive. Right-click the folder or file icon; then, in the
menu that appears, click Properties. Click the NFS Attributes tab to
view the user ID, group ID, and permissions associated with the
selected folder or file. If you own the folder or file (ownership is
determined by user ID and group ID), you can change its permissions.

-----------------
4. Known Problems
-----------------

The following is a list of known problems with using InterDrive 95:

o The net use command does not successfully mount folders
  with mixed-case paths.

o The DOS and Windows NFS servers from the FTP Software Services OnNet
  package for DOS/Windows do not support the use of long filenames.
  If you use InterDrive 95 to connect to resources shared by these
  servers, do not use long filenames in Windows 95.

o When InterDrive 95 is running with FTP's OnNet 2.0 Kernel, the Windows
  95 System Monitor inaccurately indicates 100 percent CPU usage. This 
  does not affect your system performance. It reflects the fact that 
  the 32bit winsock blocks its own threads at the kernel level while in a 
  waiting state.  The System Monitor incorrectly interprets this behavior 
  as CPU usage.  This problom will occure with all 32 bit applications that
  work with winsock.  A workaround will be available in a later patch release.
 
o The value displayed for Disk Quotas under the Mapped Network Drives
  property sheets does not represent the user's disk usage and limits as
  presented by the "quota" command on Unix servers.  The value displayed
  is all available space on the disk minus the space reserved for system
  allocation routines.
----------------------------------
5. Case Sensitivity of Login Names
----------------------------------

Unlike in Windows 95, NFS login usernames and passwords are case 
sensitive. For example, to an NFS authentication server, the name 
Bob and the name BOB are two different usernames. When you restart 
Windows 95, the login dialog box might display the current default username 
in all uppercase letters. If necessary, type the username again in the 
appropriate case to ensure that authentication works when you try
to use shared folders on an NFS server.

-----------------------------------------------
6. Case Sensitivity of Filenames in Windows 95
-----------------------------------------------

Windows Explorer does not support the use of more than one 
directory with the same name but different case. 

When you create a file, Windows 95 maintains the case of the filename
as you enter it. However, on subsequent attempts to open or use a
file, Windows Explorer converts anything that you type to lowercase before
trying to find the file. So, for example, you could create a folder
named test and a folder named TEST. However, no matter what case you
use subsequently to access the folder, Windows Explorer opens the folder
named test.  Because of this limitation, if you use InterDrive 95 to
connect to folders that have the same name but different case, you
cannot use Windows Explorer to access those folders or the files in them.

Also, not all Windows 95 applications support case preservation in
the same way. For example, if you use the DOS copy command without
specifying a destination filename, the system creates a file with all
uppercase letters when the long filename for the source file is in
all uppercase. Because InterDrive 95 cannot assume that all
applications pass it filenames in their original correct case, it
creates new filenames in all lowercase. If you want to change this
default InterDrive 95 behavior so that the case of all filenames
is preserved, you can specify a value of 1 for the Registry parameter
HKEY_LOCAL_MACHINE -> System -> CurrentControlSet -> Services ->
FTPNFS -> IdriveConfig -> keep-create-case. Restart your system
for the parameter change to take effect.

----------------------------------------------------------------
7. Connecting from Network Neighborhood with No PCNFSD Available
----------------------------------------------------------------

If you can browse folders in the NFS Servers group in Network
Neighborhood, but you get the message "Invalid Network Resource" when
you try to connect, the reason might be that there is no
authentication daemon (PCNFSD) running on the NFS server.

When InterDrive 95 cannot communicate with a PCNFSD, it is unable to
verify that the host is an NFS server, so it passes the request to
the Windows 95 multiple provider router. Windows 95 generates the
"Invalid Network Resource" message if no other network provider can
recognize the shared folder and make the connection.

---------------------------------------------------------------
8. Using InterDrive 95 and Microsoft Clients on the Same System
---------------------------------------------------------------

In Windows 95, multiple network providers can be installed
and running at the same time on your system. If you run 
InterDrive 95 and the Client for Microsoft Networks or the Microsoft
Client for NetWare Networks simultaneously, attempts to
map a network drive or connect to a network printer can produce 
unpredictable or unapparent results, due to the order in which 
the multiple provider router (MPR) calls network providers, and
the varying information that each provider returns to the MPR.

If the Microsoft network provider and InterDrive 95 both recognize
the same network resource (if the name by which the resource is
shared under LAN Manager is the same as the exported file system path
that InterDrive uses), it is not always apparent which network
provider makes the connection.

Also note that if an attempt by a Microsoft network provider to map a
network drive fails because the server denies access, the MPR does
not pass the request on to any other network provider, even if the
user has access to the same folder through InterDrive 95. 

For this reason, hosts running both LAN Manager and NFS servers 
concurrently should share resources under the exact same names through both
services. Also, file permissions should be assigned exactly the same
way for a LAN Manager folder and an NFS folder of the same name.

-------------------------------------------------------------
9.  Connecting to Print Servers That Support Both LPD and NFS
-------------------------------------------------------------

InterDrive 95 supports printing to both NFS servers and Berkeley
UNIX-style LPD servers. The standard network printer path
(\\host\queue) gives InterDrive 95 no indication of what protocol to
use. By default, InterDrive 95 attempts to connect to the printer
using the LPR protocol first. If that fails, InterDrive 95 attempts
to connect using the NFS protocol. 

To ensure success when connecting to a print server that supports
both NFS and LPR protocols, the print queues should be assigned the
exact same names under both services. Otherwise, use of a queue name
that is valid for only one protocol might result in a print failure
when InterDrive 95 tries the other protocol.

Note that you can change the default order of which protocol 
InterDrive 95 tries first. For details, see Chapter 2 of the 
InterDrive 95 "User's Guide."

Note also that when you browse for and connect to a printer using the
NFS protocol, InterDrive 95 inserts a forward slash into the printer
name (for example, \\host\/queue) before storing it. You might see
this type of path in displays. The forward slash simply indicates to
InterDrive 95 that the printer to connect to is an NFS printer. This
syntax should not affect your ability to connect to and use the
network printer, and it does not change the standard way in which you
can enter network printer names in the format \\host\queue.

------------------------------------------------------------------
10. Finding Files and Folders on Network Drives
------------------------------------------------------------------

If you use the Windows 95 Find Files and Folders utility with network
drives, note the following guidelines and restrictions:

  o The utility is case sensitive.

  o The host that you are searching must already exist in the NFS Servers
    group in Network Neighborhood.

  o Searching works reliably for shared folder names that are
    one level deep only.

  o To specify path portions beyond the shared folder name, use a 
    backslash.

------------------------------------------------------------------
11. Opening and Saving files through Network Neighborhood Browsing
------------------------------------------------------------------

If you use the Windows 95 Browse Network Neighborhood Browse facility
in a windows application to Open or Save a file to an NFS server, you 
will receive an invalid filename error.  This is because the Microsoft's
Network Provider does not process the "/" in the path name correctly.
You may still open or save a file using the UNC facility by typing in the
pathname and using the "\" as the delimiter in the pathname.





