Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!sdd.hp.com!wuarchive!psuvax1!ukma!dftsrv!nssdcb.gsfc.nasa.gov!brotzman
From: brotzman@nssdcb.gsfc.nasa.gov (Lee E. Brotzman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Clarkson 3c503 Driver Problem
Summary: Me too, except with the 3c505 driver
Message-ID: <4476@dftsrv.gsfc.nasa.gov>
Date: 1 Mar 91 16:47:09 GMT
References: <MOCK.91Feb28220846@watt.support.Corp.Sun.COM>
Sender: news@dftsrv.gsfc.nasa.gov
Reply-To: brotzman@nssdcb.gsfc.nasa.gov
Distribution: comp
Organization: ST Systems Corp.
Lines: 23
News-Software: VAX/VMS VNEWS 1.3-4

In article <MOCK.91Feb28220846@watt.support.Corp.Sun.COM>, mock@watt.support.Corp.Sun.COM (Joseph Mocker) writes...
> 
>I have encountered a rather strange problem with the Clarkson Packet driver
>for the 3c503 card...here it is...
> 
 [description of problem program deleted]
> 
>What is happening is that after a while of chugging along, I stop receiving
>packets. If I quit the program and start it up (without rebooting) it will
>work for a while and stop again.

   I just put a 3c505 in my 386SX clone and I am experiencing similar problems.
NCSA telnet seems to crash at random intervals (the clock in the lower right 
corner stops running, so it isn't just network lag time).  FTP, Inc. telnet 
crashes also (in fact FTP's telnet goes down even earlier than NCSA).
   Anyone considering sending an answer to the original posting, please either 
post to the net, or cc: a copy of your E-mail to me, too.  Thanks a bunch.

-- Lee E. Brotzman                    Internet:  brotzman@nssdca.gsfc.nasa.gov
-- ST Systems Corp.                   SPAN:      NSSDCA::BROTZMAN
-- National Space Science Data Center BITNET:    ZMLEB@SCFVM
-- "My thoughts are my own"           "Prayer: the last refuge of a scoundrel"
--                                                          Lisa Simpson, 1990