Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!pdn!gumby!dixon
From: dixon@gumby.paradyne.com (0000-Tom Dixon(0000))
Newsgroups: comp.dcom.lans
Subject: PC/IP and the Packet Driver.
Keywords: TCP/IP, packet driver
Message-ID: <6646@pdn.paradyne.com>
Date: 12 Oct 89 19:13:01 GMT
References: <489@excelan.COM> <6635@pdn.paradyne.com> <736@ftp.COM>
Sender: usenet@pdn.paradyne.com
Reply-To: dixon@gumby.paradyne.com (0000-Tom Dixon)
Organization: AT&T Paradyne, Largo, Florida
Lines: 30

In article <736@ftp.COM> jbvb@ftp.COM (James Van Bokkelen) writes:
> As of this moment, the following TCP/IPs for DOS support the Packet Driver
>and interface-sharing with BYU Netware (in order of introduction):
>
>FTP's PC/TCP (commercial)
>CMU version of PC-IP (public-domain; Karl Auerbach's TRW driver was the first)
>Phil Karn's KA9Q (no-commercial-use copyright)
>Clarkson version of NCSA (public-domain)
>WIN/PC from Wollongong (I'm not sure if this is commercially available yet).
>PC/NFS from Sun (not supported by Sun, but available via Clarkson).

A couple of questions:  
We have never tried this but have always wondered it. Can you use
the packet driver with multiple TCP/IP applications?  Say for example
NCSA Telnet and PC-NFS.  Or would the packet driver get really confused?


>If there weren't at least some people out there who think they're getting what
>they pay for, I'd be in another line of work.-- 

Good point.  Quality is worth something.  But sometimes, its sweat and not
cash.


>James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
>FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

Tom Dixon
AT&T Paradyne, Largo, Flj
uunet!pdn!dixon