Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!NCSA.UIUC.EDU!timk
From: timk@NCSA.UIUC.EDU (Tim Krauskopf)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Public Domain drivers for Ethernet cards
Message-ID: <8906112302.AA01202@zaphod.ncsa.uiuc.edu>
Date: 11 Jun 89 23:02:19 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 38


	From: James Van Bokkelen <jbvb@vax.ftp.com>
	To: ccicpg!swonk
	Cc: pcip@TWG.COM
	In-Reply-To: Glen Swonk's message of 24 May 89 23:40:18 
	Subject: Re: Public Domain drivers for Ethernet cards

	Assuming you want something copyrighted such that you can use it in a product:

	NCSA Telnet/FTP is available in source form, has a driver for the
	3C501, but the only way it can use a WD8003 is via the Clarkson Packet
	Driver, which has a no-commercial-use copyright.  NCSA puts the
	application and the protocol stack in the same .EXE file, and I don't
	think the programming interface looks much like sockets (I am not sure
	how well the interface is defined, either).


Let me fill in:

NCSA Telnet supports several boards in our public domain implementation:
3C501,WD8003E,UB PC/NIC,NI5210,3C523 and UB NIC/PS2.  You don't need
the packet driver implementation for these boards, they are supported
in version 2.2.  V2.3 this summer will add 3C503 and LocalTalk support.

We do put the application and TCP/IP in the same .EXE file so there is
NO memory overhead when the program is not running.  Our socket interface
is reasonably (I hesitate to say "fully") documented.  It supports 
multiple streams and is the same on the PC and the Macintosh.  It is
NOT, however, compatible with Berkeley sockets which is why I didn't
respond to the earlier message.  He was quite BSD-oriented.

Anonymous FTP from ftp.ncsa.uiuc.edu (128.174.20.50).


Tim Krauskopf                timk@ncsa.uiuc.edu (ARPA)

National Center for Supercomputing Applications (NCSA) 
University of Illinois, Urbana-Champaign