kc@rna.UUCP (Kaare Christian) (01/17/91)
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? The pub/ka9q directory on sun.soe.clarkson.edu has a skidillion drivers, but I don't know what they are. 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.) Seems like I must be missing some major piece of the puzzle. Any suggestions are welcome. Kaare Christian kc@rna.rockefeller.edu
nelson@sun.soe.clarkson.edu (Russ Nelson) (01/19/91)
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.cnolan@mee.tcd.ie (01/28/91)
In article <NELSON.91Jan18163300@sun.clarkson.edu>, nelson@sun.soe.clarkson.edu (Russ Nelson) writes: > > 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... > We use D-Link's DE-100 card here, are the D-Link drivers fuctionally different to the Clarkson drivers? How does one get hold of D-Link's driver? =============================================================================== Conor Nolan Phone: 772941 (X1741) Snr. Technician Fax: 772442 Microelectronics Dept. Trinity College Dublin 2 cnolan@mee.tcd.ie IRELAND ===============================================================================
nelson@sun.soe.clarkson.edu (Russ Nelson) (01/30/91)
In article <1991Jan28.130207.1@mee.tcd.ie> cnolan@mee.tcd.ie writes:
We use D-Link's DE-100 card here, are the D-Link drivers
fuctionally different to the Clarkson drivers? How does one get
hold of D-Link's driver?
I haven't seen their skeleton (they're sending their source to me,
supposedly by next-day air), so I can't say. Their drivers are in the
pctcp directory on the drivers disk that they ship with their boards.
--
--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.