Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!bbn!bbn.com!clements
From: clements@bbn.com (Bob Clements)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: 3Com 503
Message-ID: <48299@bbn.COM>
Date: 15 Nov 89 22:50:13 GMT
Article-I.D.: bbn.48299
References: <8911091338.aa14138@louie.udel.edu> <3560@mace.cc.purdue.edu>
Sender: news@bbn.COM
Reply-To: clements@BBN.COM (Bob Clements)
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 20

In article <3560@mace.cc.purdue.edu> ajt@mace.cc.purdue.edu (Andy Thomas) writes:
> [...] I had version 3.1 of the 3C503
>packet driver.  It would not work with NCSA telnet program.  After looking
>at the source, I found that the packet driver initialization is assuming
>thin ethernet.  I was using thick ethernet.
> [and gives a binary patch]

Yes, that was a serious boo-boo on my part, not allowing for thick-net.
I based the driver on my earlier WD8003E driver where the transceiver
type is selected by a jumper.  In the 3C503 it is selected by software,
and I forgot to deal with that.

The current release of the driver (get it from Clarkson) has a command-line
option to select thick versus thin.

>Andy Thomas
>ajt@bilbo.bio.purdue.edu


Bob Clements, K1BC, clements@bbn.com