Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!unmvax!indri!xanth!cs.odu.edu!tadguy
From: tadguy@cs.odu.edu (Tad Guy)
Newsgroups: comp.sys.amiga
Subject: Re: forwarded message concerning DNet 2.0
Summary: there's something wrong somewhere (Dnet-2)
Message-ID: <9006@xanth.cs.odu.edu>
Date: 31 May 89 17:16:07 GMT
References: <8905241959.AA20054@postgres.Berkeley.EDU> <7184@etana.tut.fi> <233@hhb.UUCP>
Sender: news@cs.odu.edu
Reply-To: tadguy@cs.odu.edu (Tad Guy)
Organization: Old Dominion University, Norfolk, VA
Lines: 22
In-reply-to: bvk@hhb.UUCP (Brett Kuehner)

In article <233@hhb.UUCP>, bvk@hhb (Brett Kuehner) writes:
>Something very similar happens to me. I'm running DNet 2.0 connected through a
>dialup (no terminal concentrator) to a Vax running Ultrix 2.2. I can connect
>ok, Fterm starts, and the shell prompt appears. If I try doing an ls or
>anything else that produces more than a few lines of output, the fterm locks
>up and the SD and RD lights just flicker occasionally. If I quit DNet and then
>run it again, the rest of the output, mixed with some garble, shows up in the
>initial DNet window. 

Same here, except it's on a direct dialup between a VAX-11/785
(4.3BSD) and my A1000.  No problem with Dnet-1, but Dnet-2 will freeze
occasionally (typically when I am in emacs, furiously typing).  

The VAX is clearly sending packets to the Amiga, but the Amiga never
acks them.  It looks to me like Dnet-2 gets to a state where it
forgets to wait on the serial.device (since it doesn't appear to see
any more packets).  I have flow control turned off...

I've mentioned it to Matt on occasion, but he doesn't see what could
be going wrong.  It's good to know I'm not alone in this...

	...tad