Path: utzoo!attcan!uunet!pyrdc!pyrnj!hhb!bvk
From: bvk@hhb.UUCP (Brett Kuehner)
Newsgroups: comp.sys.amiga
Subject: Re: forwarded message concerning DNet 2.0
Message-ID: <233@hhb.UUCP>
Date: 26 May 89 17:44:02 GMT
References: <8905241959.AA20054@postgres.Berkeley.EDU> <7184@etana.tut.fi>
Organization: HHB Systems, Mawah, NJ
Lines: 48

In article <7184@etana.tut.fi>, pl@etana.tut.fi (Lehtinen Pertti) writes:
> 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

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. 

--
Brett Kuehner, HHB Systems, Mawah, NJ
...!princeton!hhb!bvk
bvk%hhb@princeton.EDU