Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!kth!draken!tut!pl
From: pl@etana.tut.fi (Lehtinen Pertti)
Newsgroups: comp.sys.amiga
Subject: Re: forwarded message concerning DNet 2.0
Message-ID: <7184@etana.tut.fi>
Date: 25 May 89 08:24:17 GMT
References: <8905241959.AA20054@postgres.Berkeley.EDU>
Sender: News@tut.fi
Lines: 35

From article <8905241959.AA20054@postgres.Berkeley.EDU>, by dillon@POSTGRES.BERKELEY.EDU (Matt Dillon):
> 
> 	This is a forwarded message from Daniel Albert Mosedale
> concerning problems he is having w/ DNet 2.0.  I have been unable
> to help him.  Anybody w/ ideas should mailhim directly.
> 
> TERM = (vt100)? and I'll hit return, 
> as always when I login, at which point things start
> to screw up.  I can no longer type anything, and nothing appears in the DNet
> window.....however, wathching the lights on my modem, then SEND light flickers
> about once every half second, and the receive is constantly on.  This locked
> state will go on indefinitely, or until I shut off the modem.
>  

	I don't know any solution but I have similar problem.

	I have dnet 2.0 on SUN and i works ok when I connect thru
	CS-100 terminal server.

	But when I connect from home with dialup line I get also
	fterm-window and first line of output from .cshrc,
	but rest of output is hung and it seems some sort
	of handshake problem between amy and unix-end of dnet,
	because if I drop fterm window, unix end still sends rest
	of lines several times.

	Is there any possibility that certain modems screw handshake chars?

					Pertti Lehtinen
					pl@tut.fi

pl@tut.fi				! -------------------------------- !
Pertti Lehtinen				!  Alone at the edge of the world  !
Tampere University of Technology	! -------------------------------- !
Software Systems Laboratory