Xref: utzoo comp.sys.ibm.pc:10410 comp.dcom.lans:928
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!bloom-beacon!gatech!mcnc!decvax!decwrl!pyramid!voder!kontron!optilink!cramer
From: cramer@optilink.UUCP (Clayton Cramer)
Newsgroups: comp.sys.ibm.pc,comp.dcom.lans
Subject: Re: Need help writing 3COM 3C501 driver for PC-AT (long)
Message-ID: <1847@optilink.UUCP>
Date: 14 Jan 88 19:20:21 GMT
References: <3393@bcsaic.UUCP> <1437@phoenix.Princeton.EDU> <38764@sun.uucp>
Organization: Optilink Corporation, Petaluma, CA
Lines: 40

> > There are a number of fairly complete implementations of TCP/IP for IBM
> > PC's (XT, AT also).
> 
> The glossy for the Sun PC-NFS Release 2.0 claims that it supports TCP and UDP,
> which is probably true as NFS uses Sun RPC on top of UDP and TELNET, FTP,
> "rsh", and "rcp" (which come with PC-NFS) use TCP.  It also claims that it
> supports ICMP - I don't know what level of support is provided - ARP and RARP
> (RARP client, one would presume).  I seem to remember a claim from somebody
> here that it provides interfaces to TCP and UDP that users can use for
> applications; they probably look like 4BSD socket calls, if they exist.  It
> definitely provides an RPC/XDR implementation that applications can use.
> 
> The glossy also claims that it prvides FTP, a printer interface (which probably
> permits a PC to spool to the 4.[23]BSD print spooler), and "rsh" and "rcp" in
> some form.
> 
> According to the glossy, PC-NFS 2.0 includes drivers for the 3C501 as well as
> the Ungermann-Bass NIC and the Micom-Interlan NI5010.
> 
> 	Guy Harris
> 	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy

We are using PC-NFS Release 2.0 here, and all the glossies are substantially
correct.  We've had a few problems, though to be fair, Sun Tech Support has
worked very hard to help us resolve the problems.  (Also, to be fair, we have
a truly unique arrangement -- two Ethernet legs off a Sun, then a gateway
from Ethernet to Appletalk).

One bug we've found with PC-NFS that is *truly subtle* is that we used the
DOS APPEND command in our AUTOEXEC.BAT files.  When we printed to the
network printer interface from Microsoft Word, then exited, our PCs would
lock up, requiring power off.

I suspect the bug is that PC-NFS is picking up a pointer to the PATH 
environment variable, and that APPEND moves the location of PATH after
APPEND has been executed.

Over all, PC-NFS has been pretty solid.

Clayton E. Cramer