======================================================================== # # ## # ###### ##### # # #### ##### # # #### # # # # # # # # # # # # # # # # # ##### # # # # # # # #### #### # # # # # # ## # # # ##### # # # # ## # # ## ## # # # # # # # # # # ###### # # # #### # # # # #### ======================================================================== The easiest way to get PC-NFS up and running is to layer it on top of Microsoft's Windows for Workgroups v3.11 networking layer. Although I have not tried it yet, the following instructions should apply to Windows 95. For Windows 95, PC-NFS Pro is a better solution. For sure they will not work with Windows NT, for which Intergraph and Chameleon offer solutions. There are several reasons for adding PC-NFS on top of Windows networking: 1. PC-NFS direct hardware support is very limited. Most of the direct drivers they have are for currently obsolete hardware, were written 5-10 years ago and are very slow. 2. PC-NFS can be used with other drivers, like NDIS, but doing so is difficult at best. The problem is documentation, in that the PC-NFS manual tells you to consult the hardware vendors manual which tells you to consult the software vendor's manual... (you get the picture). 3. Microsoft has done an excellent job of providing lots of Network Interface Card (NIC) drivers, excellent hardware detection and configuration, and their drivers are for current hardware and they outperform the PC-NFS drivers by at least 2:1. 4. You'll be able to use PC-NFS under DOS and Windows to access TCP/IP networks and you'll also be able to access other PC machines (via NetBUI and Novel IPX/SPX) connected to the same network. 5. Once installed and setup, any future network changes are easily accomplished from the Windows Network Setup utility. Even so, adding PC-NFS on top of WFW networking is not exactly intuitive, but if you know the steps, it is straight forward. Here is a step by step approach to setting up a system: 1. If your system is already running PC-NFS, REM out all the PC-NFS stuff in CONFIG.SYS and AUTOEXEC.BAT. If PC-NFS is not already present, install the DOS portion now. You don't have to bother with configuring PC-NFS right now, you just need the files to be present on your hard disk, I'm assuming they are in the C:\NFS directory in this document. 2. If WFW is not installed, do so. If Windows is installed, you can also install the WFW Add-On for Windows. In either case, you do this by running the SETUP program on Disk 1 of the distribution. I'm assuming Windows is installed in the C:\WINDOWS directory in this document. 3. Setup and configure the WFW networking options. If installing WFW (or the add-on), you will automatically go to this step during SETUP. Otherwise, run the 'Network Setup' command, which is actually the 'WINSETUP' program with the '/Z' option. Initially, enable the 'Microsoft Windows Network' option (if it is not already on) and also make sure to check the 'No additional network' option, for now. 4. Then, select and configure a driver for your NIC. Network Setup does a very good job of detecting the type of NIC you have. You will probably automatically get the NetBUI and IPX/SPX protocols installed in addition. After this, Windows will probably reboot your machine to load the new drivers and when Windows starts up again, make sure the WFW networking starts up (it will compalin if it doesn't work right). 5. Now, run the Windows setup program (WINSTALL) on the PC-NFS Windows disk. This will place the PC-NFS support files into the Windows directory. Then re-run 'Network Setup' and enable 'Other' network and select PC-NFS from the list. The system will probably restart again to load the new drivers. At this point you are nearly ready to go on-line. Assuming you have an exisiting PC-NFS setup, you can skip over the next few steps. Otherwise, you need to tell the TCP/IP and NFS layers about your network. This is done in two DOS batch files in the PC-NFS directory (usually C:\NFS). You can do this either manually or with the PC-NFS configuration program. Whichever way you choose, stick with that method, because otherwise you could lose your configuration data. I will present the manual setup method, because that is what I am most comfortable with. C:\NFS\NETWORK.BAT - Network startup file. ------------------ C:\NFS\NET NISDOMAIN domain.sgi.com << Insert NIS domain here C:\NFS\NET START RDR machine * << Insert machine name here, i.e. etc/sys_id C:\NFS\NET SUBNET 255.255.255.0 << Enter as is C:\NFS\NET ROUTE [router] << Add router name if known C:\NFS\NET NISSET [nisserver] << Add NIS server if known C:\NFS\NET UMASK xyz << Add favorite permission mask, i.e. umask C:\NFS\NET BLIP on/off << On displays a network drive light (optional) C:\NFS\NET PCNFSD [server/*] << Add pcnfsd server, if applicable C:\NFS\NET LOGIN user << Add login name, if applicable C:\NFS\NET VERSION << Display current version (optional) C:\NFS\DRIVES.BAT - Mounted file systems. ----------------- C:\NFS\NET USE d: machine:/fs << Insert drive letter and file system C:\NFS\NET USE LPTx: machine:lp << Insert LPT and printer name C:\NFS\HOSTS - Host name-address database. ------------ 127.1 localhost nnn.nnn.nnn.nnn your.machine << Put a few IP addresses in this file mmm.mmm.mmm.mmm some.other.machine HINT: Once PC-NFS is up and running, grab a copy of /etc/hosts from some workstation, run it through UNIX2DOS and use that instead. NOTE: You need to specify unambiguous path names with running this networking configuration. As you will see later, some of the Windows and PC-NFS networking utilities have the same name but slightly different functions. Be sure to specify the correct ones. What I do to avoid confusion, is to place the PC-NFS directory in my search path and leave the Windows directory out of my path. This way, in all but the Windows directory, I will get PC-NFS tools when I enter the command name. In Windows, I will get Windows tools. Remember in DOS, the path is searched as follows, current directory first, BAT then COM then EXE, then the directories in the PATH are searched in order. Now, you are ready to put everything together. In your CONFIG.SYS file you will only have one driver associated with networking, that is: CONFIG.SYS ---------- ... DEVICE=C:\WINDOWS\IFSHLP.SYS ... If you had PC-NFS previously installed, you can take out all the old drivers, like PCNFS.SYS, SOCKDRV.SYS, etc. At this point, Windows networking will automatically turn on when you start Windows. However, PC-NFS will not be fully enabled. That is, it will be turned on to the point that you could use PING, RCP, or FTP inside of Windows, but you would have no file systems or printers mounted. To do this, you must turn on PC-NFS from DOS (before starting Windows). This is necessary in order to get the 'real-mode' redirector (\NFS\PRT) into DOS memory so that it can 'redirect' file and printer requests from DOS or Windows. However, before this can happen, you need to start the Windows network. AUTOEXEC.BAT ------------ ... C:\WINDOWS\NET START << Starts Windows networking C:\NFS\PRT * << Loads PC-NFS redirector CALL C:\NSF\NETWORK.BAT << Initializes the TCP/IP stack CALL C:\NFS\DRIVES.BAT << Mounts file systems and printers ... One final step remains if you now want to be able to directly access PC-NFS network utilities from inside Windows. This step is not required if you only wish to access mounted file systems and printers. To access PC-NFS from Windows, requires that the real mode interface be loaded. This can be done as follows: C:\NFS\RTM I usually put this in my Windows startup batch file (WIN.BAT). Here is an example: WIN.BAT - Starts up Windows ------- C:\NFS\RTM << Loads real-mode interface C:\WINDOWS\WIN.COM << Starts Windows loader C:\NFS\RTM -UO << Unloads real-mode interface =========================================================================== Roger Brown (rogerb@sgi.com) ===========================================================================