# @(#)sample.txt.u	1.4 91/07/11 SMI




(The following text is for use by ISVs who write and distribute
applications written with the PC-NFS Programmer's Toolkit 2.0. Along with
their application, ISVs must distribute three resident module files
(RTM.EXE, RNMNIS.EXE, and RNMFILE.EXE), two utilities (RTMREM.EXE and
RNMREM.EXE), and one database file (NETCONF). The information below
will be needed by the end-user of a Toolkit application. It explains
how to install the resident modules and NETCONF. ISVs can adapt this
text for the documentation they produce for their applications.)

======== Cut Here ==============

Installing Files Needed by the XYZ (name of application) Program.

To install the auxiliary files needed to run XYZ (the files called the
resident modules) you simply copy them from the distribution disk onto
your hard disk. The best location for the files is the directory where
PC-NFS is stored.

For example, to copy the files into the directory named \nfs, type

copy a:*.exe c:\nfs

copy a:netconf c:\nfs 

Once these files reside on your hard disk, you may choose to use one of
two name-service modules with your application. Use RNMNIS.EXE if your
network uses NIS. Otherwise, use RNMFILE.EXE to access the
local-machine's PC-NFS databases. The NETCONF database can make this
choice for you in most circumstances.

The NETCONF file shipped with the Toolkit contains the following lines:

udp tpi_clts	  v	 inet udp \rtm\udp  rnmnis.exe,rnmfile.exe
tcp tpi_cots_ord  v	 inet tcp \rtm\tcp  rnmnis.exe,rnmfile.exe

The name-service module used by the application will be the first one
listed in NETCONF. You will need to edit NETCONF only if your network
has NIS available but you prefer to use local-machine network
databases. In this case, you will need to remove RNMNIS.EXE from
NETCONF. Use a text editor to delete the references to RNMNIS.EXE.

NOTE: Save the existing NETCONF file with a .OLD extension before
making this change.
