Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!mixcom!sysop
From: sysop@mixcom.UUCP (System Operator)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: RE: Packet Drivers and Dos 4.01
Message-ID: <168@mixcom.UUCP>
Date: 13 Jul 90 17:39:30 GMT
References: <9007051613.aa10302@louie.udel.edu> <28881.26945cd6@vaxb.acs.unt.edu> <1990Jul9.210810.4055@arsocomvax.socom.mil>
Reply-To: sysop@mixcom.UUCP (System Operator)
Organization: MIX Communications, Milwaukee, WI (Public Access. Modem:414-241-5469)
Lines: 27

In article <1990Jul9.210810.4055@arsocomvax.socom.mil> ted@usasoc.soc.mil (Ted Nolan) writes:
>We're seeing some of this with PCNFS 3.01 and NI5210 cards, both with the
>Micom supplied PCNFS driver and the Clarkson packet driver + pktd.sys.
>Sometimes changing the shared memory address on the card helps, sometimes not.
>If anyone has a definitive fix, I'd be most grateful.  This is happening
>under DOS 3.3, haven't tried 4.x yet.  Since PCs are single tasking, I find
>the fact that this usually occurs only after being idle for a while really odd.
>
>				Ted Nolan
>				ted@usasoc.soc.mil


I've been using NI5210 packet drivers for 1.5 years.  I drive 1GB
through them as part of an acceptance test.  Thus far only
the Clarkson 3.1 NI5210 driver has passed.  All subsequent revisions
have crashed.  I have not tested the 6.x revision yet.  I am using
DOS 3.3 and have not determined whether the crash is caused by the
packet driver or some interaction between DOS's stack(s) and the rate
that interrupts occur.  (DOS's message about stack overflow does not
appear when the system crashes.)  But thus far I have stayed with the
Clarkson 3.1 revision and have been happy.

Dean Roth
sysop@mixcom.uucp
-- 
    Milwaukee Information eXchange (MIX), public access *NIX/Usenet
        MIX Communications, P.O. Box 17166, Milwaukee, WI 53217