Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: info on clarkson tcp Message-ID: Date: 18 Jan 91 22:33:00 GMT References: <1067@rna.UUCP> Sender: @grape.ecs.clarkson.edu Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) Organization: Clarkson University, Potsdam NY Lines: 29 In-Reply-To: kc@rna.UUCP's message of 16 Jan 91 17:22:58 GMT In article <1067@rna.UUCP> kc@rna.UUCP (Kaare Christian) writes: Does anyone have any pointers for learning about the clarkson tcp package? I browsed around the pub directories on both omnigate and sun.soe but didn't encounter anything more than a readme. Seems there must be a more comprehensive doc somewhere, but where? Look IN drivers.arc. The pub/ka9q directory on sun.soe.clarkson.edu has a skidillion drivers, but I don't know what they are. Look at read.me in drivers.arc. I'm particularly interested in the ne2000 board, and there is a ne2000.com, but is this really the driver? (I would have expected ne2000.sys plus some doc file.) The packet drivers are written as TSR programs. You run them like any other program, and they Terminate and Stay Resident. D-Link has modified their Clarkson-derived drivers to work as device drivers, and they are sending me their sources. So, I may include an option to make the packet drivers as device drivers. There is, however, no real advantage to doing so... -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) FAX 315-268-7600 It's better to get mugged than to live a life of fear -- Freeman Dyson I joined the League for Programming Freedom, and I hope you'll join too.