Xref: utzoo comp.protocols.tcp-ip.ibmpc:4191 comp.dcom.lans:6494
Path: utzoo!attcan!uunet!mcsun!ukc!tcdcs!swift.cs.tcd.ie!vax1.tcd.ie!cnolan
From: cnolan@vax1.tcd.ie
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.dcom.lans
Subject: Re: Status of, and mailing list for Clarkson packet drivers
Message-ID: <7245.273de4ef@vax1.tcd.ie>
Date: 11 Nov 90 23:55:26 GMT
References: <9011090510.AA09890@image.soe.clarkson.edu>
Organization: Trinity College Dublin
Lines: 32

In article <9011090510.AA09890@image.soe.clarkson.edu>, nelson@image.soe.clarkson.edu (Russ Nelson) writes:> Hi.  This is just a note to keep you all up to date on the packet
	stuff deleted ...

> Useful projects I don't see myself finding the time for:
> 
>   o A real but small program written in C that uses the packet driver, with
>     source code for study and modification.
>   o A program or programs that exercise the packet drivers.  For example,
>     a ping client that loops through all possible packet sizes would be
>     handy.  Perhaps the PC-IP ping client could be modified to do this?
>   o Genericize the three LANCE-based drivers, the ni6510, the nti16, and
>     the (unreleased) isolink.
>   o Write an article on the packet drivers for a PC programmer's magazine
>     such a Programmer's Journal, or suchlike.
> 
> -russ

I would be really interested in the latter.  Has any one else done similar
aticles from both a programming and a explanatory point of view?

-- 
===============================================================================

             
       	 	Conor Nolan			Phone:	772941 (X1741)
           	Microelectronics Dept.		Fax:	772442
            	Trinity College			
	      	Dublin 2			cnolan@mee.tcd.ie
  	     	IRELAND				ampere::cnolan
            

===============================================================================