ReadMe File         NFS Client for LAN WorkPlace v3.0c              12/8/93
===========================================================================

What is in this file?
=====================
     1.  Configuring the NFS Client to run with the NetWare DOS
         Requester v1.1 and LAN WorkPlace v4.1.
     2.  Running the NFS Client with LAN WorkGroup.
     3.  Name Service Support.
     4.  Using the Compiled LWPNFSD Daemons in NFSCLNT\UTILITY.


1. Configuring the NFS Client to Run with the NetWare DOS Requester v1.1
   and LAN WorkPlace v4.1.
===========================================================================

     Configuration Prerequisites:
     ----------------------------
          a.  You must have the NetWare DOS Requester v1.1 (available on
              NetWire).
          b.  You must have the NFS Client for LAN WorkPlace v3.0c.
          
     Quick Configuration Instructions:
     ---------------------------------
     
     Modify the files:
          
     AUTOEXEC.BAT
     STARTNET.BAT
     LANWP.BAT
          
     so that the NW Client, LWP TCPIP stack, and NFS Client redirector load
     in the following order:
     
     LSL.COM
     NE2000.COM                         <-or whatever MLID you have to load
     TCPIP.EXE                          <-LAN WorkPlace TCPIP Stack
     LWPRPC                             <-NFS Client Redirector
     LWPNFS pcname /r:9096 /w:4096      <-NFS Client Redirector
     IPXODI.COM
     VLM.EXE
          
     IMPORTANT NOTE:  This load order works only when used with the NW
     Client v1.1.  If you use the NetWare Shell (NETX.EXE) the normal
     installation of the NFS Client must be used, that is IPXODI.COM and
     NETX.EXE must load before the LWP TCPIP stack and NFS Client
     redirector.
     
     
     Modifying Your System Files:
     ----------------------------
     The NetWare DOS Requester (or NetWare Client v4.x) installs and
     creates the file STARTNET.BAT.  This is the initialization or startup
     batch file for the NetWare Client software and resides in your
     NWCLIENT installation directory.  Next there is the startup batch file
     for LAN WorkPlace v4.1 called LANWP.BAT which is located in your
     NET\BIN (or <lwp_install_dir>\BIN) directory.  Lastly, there is your
     AUTOEXEC.BAT file typically in the root directory of your boot drive.
     These three files may require modification to run the NFS Client with
     the NetWare DOS Requester v1.1 and LAN WorkPlace v4.1.   Below are
     typical sample files which can provide some guidance in modifying your
     files to support the NFS Client:
          
     
     
     
     
     
     System (startup) files BEFORE Modification:
     ===========================================
     
     
     Typical AUTOEXEC.BAT File Running with NetWare Client Before
     Modification
     ====================================================================
     @echo off
     @CALL C:\NWCLIENT\STARTNET.BAT
     SET YPDOMAIN=company.com/192.57.5.111
     PATH C:\DOS;C:\;C:\BIN;F:\NWCLIENT;C:\BAT;C:\WINDOWS
     prompt $p$g
     CALL LANWP.BAT
     F:\NFSCLNT\lwprpc
     F:\NFSCLNT\lwpnfs pcname /r:4096 /w:4096
     
     Typical STARTNET.BAT File Running with NW Client Before Modification
     ====================================================================
     @echo off
     F:
     CD \NWCLIENT
     SET NWLANGUAGE=ENGLISH
     LSL
     NE2000.COM
     IPXODI
     VLM
     CD \
     
     Typical  LANWP.BAT File Running with NW Client Before Modification
     ==================================================================
     C:\yesno "Do you want to load the networking software[y/n]?"
     if errorlevel 1 goto noload
     PATH C:\NET\BIN;%path%
     L:login nds-server/user1
     tcpip.exe
     :noload
     
     
     System (startup) files AFTER Modification
     =========================================
     
     
     Typical AUTOEXEC.BAT File Running with NW Client after Modification
     ===================================================================
     echo off
     @CALL C:\NWCLIENT\STARTNET.BAT
     SET YPDOMAIN=company.com/192.57.5.111
     PATH C:\DOS;C:\;C:\BIN;F:\NWCLIENT;C:\BAT;C:\WINDOWS
     prompt $p$g
     rem   -------------------------------------------------------
     rem   lines below have been modified from original
     rem   -------------------------------------------------------
     rem   CALL LANWP.BAT                             <-or delete
     rem   F:\NFSCLNT\lwprpc                          <-or delete 
     rem   F:\NFSCLNT\lwpnfs pcname  /r:4096 /w:4096  <-or delete	 												    placing in LANWP.BAT
     
     
     Typical STARTNET.BAT File Running with NW Client After Modification
     ===================================================================
     @echo off
     F:
     CD \NWCLIENT
     SET NWLANGUAGE=ENGLISH
     LSL
     NE2000.COM
     rem   --------------------------------------------------------------
     rem   line below has been added from AUTOEXEC.BAT
     rem   --------------------------------------------------------------
     @CALL LANWP.BAT   <-this line inserted to load the LWP TCPIP stack 
                         and NFS Client IPXODI
     VLM
     CD \
     rem  ------------------------------------------------------------
     rem  lines below have been added from LANWP.BAT
     rem  ------------------------------------------------------------
     L:
     L:login nds-server/user1
     
     
     Typical  LANWP.BAT File Running with NW Client After Modification
     =================================================================
     C:\yesno "Do you want to load the networking software[y/n]?"
     if errorlevel 1 goto noload
     PATH C:\NET\BIN;%path%
     rem  L:login nds-server/user1    <- or delete
     tcpip.exe
     rem  ----------------------------------------------------------
     rem  lines below have been added from AUTOEXEC.BAT
     rem  ----------------------------------------------------------
     F:\NFSCLNT\lwprpc
     F:\NFSCLNT\lwpnfs pcname  /r:4096 /w:4096
     :noload
     
     
2. Running the NFS Client with LAN WorkGroup.
=============================================
When installing the NFS Client with LAN WorkGroup (LWG) v4.1, you can use
the normal installation for the NFS Client.  However, if you intend to run
the NFS Client with the NetWare DOS Requester,  you can use the
modifications shown in section 1 for LAN WorkPlace for DOS.  Please note
that with LWG the LANWP.BAT file is LANWG.BAT located in net\bin on your
WorkGroup client.


3. Name Service Support
=======================
The NFS Client now supports Domain Name Service (DNS) in addition to
Network Information Service that was provided in v2.30 of the NFS Client.
DNS is provided via the LAN WorkPlace TCPIP stack and must have been set up
during installation of the LAN WorkPlace product.


4.  Using the Compiled LWPNFSD Daemons Located in NFSCLNT\UTILITY
=================================================================
In an effort the assist customers with UNIX hosts that do not have
development tools to compile the authentication daemon,  we have included
copies of the compiled daemons in the installed directory tree.

For example,  if you would like a compiled version of the authentication
daemon for SunOS you can use FTP to PUT \NFSCLNT\UTILITY\SUNOS\LWPNFSD  to
your UNIX host.

Example FTP Session:  c:\>  FTP <unix_host_name>
                      ftp>  mkdir LWPNFS
                      ftp>  cd LWPNFS
                      ftp>  put C:\NFSCLNT\UTILITY\SUNOS\LWPNFSD.SUN LWPNFSD
                      ftp>  bye
                      c:\>


Refer to page 2-7 of the NFS Client User's Guide for details on how to
install and start the daemon.  There are compiled daemons and accompanying
readme file for each of the following platforms.

      Vendor                  OS                Directory
     ----------------------------------------------------------------------
     Sun Microsystems         SunOS v4.2        \NFSCLNT\UTILITY\SUNOS
     Sun Microsystems         Solaris v2.1      \NFSCLNT\UTILITY\SOLARIS
     Novell                   UNIXWARE v1.x     \NFSCLNT\UTILITY\UNIXWARE
     Hewlett Packard          UX  v8.07         \NFSCLNT\UTILITY\HPUX
     DEC                      ULTRIX  v4.3      \NFSCLNT\UTILITY\ULTRIX
     IBM                      AIX  v3.2         \NFSCLNT\UTILITY\AIX
     SCO                      ODT v3.0          \NFSCLNT\UTILITY\SCO
     
Please note the platform versions on which these daemons were compiled.
While we have made every effort to provide the authentication daemons with
the product, we cannot guarantee that the daemon runs correctly on every
version of each platform.  If you have trouble starting the daemon on your
system, you may have to get the development tools for your system and
compile the daemon yourself, or use the PCNFSD or BWNFSD daemon (consult
the user's guide for more information on other authentication daemons that
work with the NFS Client).


Known Problems with SCO
=======================
We have provided the compiled LWPNFSD for SCO ODT v3.0 since we have
discovered that the SCO development system does not ship with serveral
libraries required to compile and run the daemon successfully.  




