Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!POSTGRES.BERKELEY.EDU!dillon
From: dillon@POSTGRES.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: forwarded message concerning DNet 2.0
Message-ID: <8905241959.AA20054@postgres.Berkeley.EDU>
Date: 24 May 89 19:59:09 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 51


	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.

				Thanks

				-Matt


>From @mist.math.uoregon.edu:dmose@drizzle.cs.uoregon.edu

I've been mucking around with DNet 2.0 for awhile and I still can't get it
to work. 

I've been starting DNet with 
run dnet -X -8

after which I use the DNet window to dialup (via a 1200 baud modem) some
sort of port switcher known as the Gandalf switch.  I use this to connect
to UONet which is a Bridge CS/200 terminal server.  I connect to the VAX
I'm on now (BSD Unix 4.3).  After loggin in, I hit the ecmchar ^[, and 
after setting fcf=none, fct=none, ecmchar=disabled, and (sometimes)
xmitbinary = on, I attempt to start dnet on the unix side.  So far so good.
The DNet window closes, FTerm opens up, says opening...please wait, after
a few seconds the window dimensions appear on the titlebar, and I guess
dnet then runs either .login or .cshrc since the computer asks the normal
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.
 
An earlier article suggested using stty -parity and some other option
....the stty on our machine doesn't support those particular keywords,
although it supprots the setting in other forms.  I tried messing around
with a bunch of those, as well as starting DNet with -h0, and none of
it makes a difference.

.Another things to note...above I said that I only set xmitbinary=on
sometimes...this is because 95% of the time when I turn xmitbinary on, 
and then resume my session with the unix box, I start having typing
problems:  every time I type 1 character, a return is automatically supplied,
and then csh prints a list of all files in the current dir which start
with that letter.  the few times when xmitbinary doesn't mess things up 
like this, I still have the same locked condition with dnet.
 
Any help would be appreciated!
dmose@drizzle.UUCP