Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!mentor.cc.purdue.edu!mace.cc.purdue.edu!ajt
From: ajt@mace.cc.purdue.edu (Andy Thomas)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: 3Com 503
Message-ID: <3560@mace.cc.purdue.edu>
Date: 15 Nov 89 19:22:55 GMT
References: <8911091338.aa14138@louie.udel.edu>
Reply-To: ajt@mace.cc.purdue.edu (Andy Thomas)
Organization: Purdue University
Lines: 26

In article <8911091338.aa14138@louie.udel.edu> NETWORK@FRSAC11.BITNET writes:
>
>I use NCSA Telnet 2.2D & 2.2tn, and the most recent version of KA9Q NOS.
>With the 3Com 501 Enet card NCSA runs with the packet as well as the internal
>driver.
>NOS runs with the packet driver.
>
>I cant have any of those run with a 3Com 503 packet driver.
>
>Any help ? Something special with 3C503, or is it the packet driver ?
>(The loading of the driver goes OK, but NCSA or NOS get stuck, no message.)

I don't know if this will help or not.  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.  By changing ECNTRL_THIN from
002h to 000 in the 3C503.ASM file, it will work with thick ethernet. 
If you don't have the source you can patch the .COM file with debug.
Address		Old value	New value
 935		3		1
 938		2		0
 93b		6		4
 958		2		0

Andy Thomas
ajt@bilbo.bio.purdue.edu