Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!dsac.dla.mil!dsacg3.dsac.dla.mil!dsacg2.dsac.dla.mil!nol2321
From: nol2321@dsacg2.dsac.dla.mil (Jim Dunn)
Newsgroups: comp.protocols.nfs
Subject: PCNFS(tm) and Clarkson Drivers
Message-ID: <3267@dsacg2.dsac.dla.mil>
Date: 4 Jun 91 15:11:23 GMT
Organization: Defense Logistics Agency Systems Automation Center, Columbus
Lines: 113


     In regards to the various questions concerning PCNFS(tm) and the Clarkson
     Packet Drivers, I have written the following document.  Note that I am not
     associated with either Sun Microsystems or Clarkson University, therefore
     this document is provided as is, no warranty is expressed or implied.

     You have several alternatives as to the configuration of your
     pc when it comes to the Ethernet LAN.  Some are:

     a)  PCNFS(tm) drivers only.
     b)  PCNFS(tm) drivers mixed with Clarkson Drivers. (after NFSRUN)
- - - - - -
     c)  PCNFS(tm) drivers mixed with Clarkson Drivers. (before NFSRUN)
     d)  Clarkson Drivers Only.

Note:
     The "A" and "B" setups are seemingly identical, as are the "C" and
     "D" setups.  Notice the line drawn between the two sets of setups.

     The "A" setup allows you to run all programs compiled with the
     PCNFS(tm) Toolkit using the NFS TCP/IP packet protocol.  Also, you
     have "mounted drive" capabilities.

     The "B" and "C" setup uses the Clarkson drivers to replace some of
     the Sun drivers, allowing you to use the network before and after
     you run the PRT.EXE or NFSRUN.EXE programs.

     The "B" setup is an "emulated A" setup, allowing all of the same
     functions as the "A" setup.  (however, I have noticed that some
     programs will lock up the pc if you forget to run PKTMODE)

     The "C" setup is a "half way into the A" setup, allowing you to
     run all the Clarkson Packet Driver Protocol programs such as KA9Q,
     NCSA Telnet, CUT/CP-REV-D, etc.  The downside is that in this half
     way state, you cannot run PCNFS(tm) Toolkit programs or access the
     PCNFS(tm) Mounted Drive.

     The "D" setup is the simplest, using only the Clarkson Packet
     drivers to allow the same access as the "C" setup.

Recommendation:
     If you need PCNFS(tm) Mounted Drive or toolkit apps, use the "A"
     setup, else, use the "D" setup.

Appendix of configuration files: (for a 3C503 card)

     ---"A" config.sys---
     device=c:\nfs\pcnfs.sys /f20
     device=c:\nfs\sockdrv.sys
     device=c:\drivers\vecie6.sys /i5
     device=c:\nfs\nfsvec.sys
     lastdrive=v
     ---eof config.sys---

     ---"A" autoexec.bat---
     set tz=EST5EDT
     set path=c:\nfs
     set NFSDRIVE=c
     prt -T25 *
     nfsrun
     ---eof autoexec.bat---


     ---"B" config.sys---
     device=c:\nfs\pcnfs.sys /f20
     device=c:\nfs\sockdrv.sys
     device=c:\LAN\pktd.sys
     lastdrive=v
     ---eof config.sys---

     ---"B" autoexec.bat---
     set tz=EST5EDT
     set path=c:\nfs
     set NFSDRIVE=c
     C:\LAN\3c503.com 0x7e 5 0x300
     prt -T25 *
     nfsrun
     ---eof autoexec.bat---

     ---"C" config.sys---
     device=c:\nfs\pcnfs.sys /f20
     device=c:\nfs\sockdrv.sys
     device=c:\LAN\pktd.sys
     lastdrive=v
     ---eof config.sys---

     ---"C" autoexec.bat---
     set tz=EST5EDT
     set path=c:\nfs
     set NFSDRIVE=c
     C:\LAN\3c503.com 0x7e 5 0x300
     ---eof autoexec.bat---

     ---"C" nfs.bat---                      NOTE:  nfs.bat is executed whenever
     prt -T25 *                                    you want to change your setup
     nfsrun                                        to "B".  A reboot is required
     ---eof nfs.bat---                             to get back to setup "C".


     ---"D" config.sys---
     ---eof config.sys---

     ---"D" autoexec.bat---
     set tz=EST5EDT
     C:\LAN\3c503.com 0x7e 5 0x300
     ---eof autoexec.bat---

Dumb Answer:

     There may be some who will ask, "Why bother with setup B or C anyway?"
     Well, you may wish to have multiple copies of your autoexec.bat and
     config.sys that, when renamed, would allow you to reboot under a
     different configuration "umbrella," thus you are more flexible...