Path: utzoo!attcan!uunet!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!jarthur!spectre.ccsf.caltech.edu!tybalt.caltech.edu!jjfeiler
From: jjfeiler@tybalt.caltech.edu (John J. Feiler)
Newsgroups: comp.sys.amiga
Subject: dnet
Keywords: even parity
Message-ID: <1990Mar28.220642.18646@spectre.ccsf.caltech.edu>
Date: 28 Mar 90 22:06:42 GMT
Sender: news@spectre.ccsf.caltech.edu
Distribution: comp
Organization: California Institute of Technology
Lines: 42

Well, I finally got dnet up and running on our Sun3 and the CCO vax11/750.
Through much playing around, I finally hit upon the -Z2 switch.  This
allows me to eventually connect, but acts rather strange as I start up.
Here's the only way I've been able to get it to work:

Amiga>  dnet -X -8 -b2400 -Z2

dnet> atdt(whatever)
	CONNECT 2400

at this point, nothing I do has any effect in the dnet window.  no
net prompt, no nothing.  breaks and Ctrl-C do nothing

So, in despair, I try:
start dnet
(fterm window opens  does nothing))

break 2 (from cli)
(fterm closes, small dnet window opens)

now, I finally get a response to typing in dnet window.  However, it does
not echo all characters(presumably due to some kind of parity/bitnumber prob)

I type : connect tybalt
it says:cnncttat   (or something like that)

Finally, I get the login prompt, CORRECTLY
ie, : tybalt login:

from then on, everything goes smoothly.  I can set up multiple
fterms, put/getfiles, etc.

So, the question is, can I straighten out all the startup nonsense, get the
parity's set right, etc. or should I be happy that I finally found a 
way to get it to work, and leave it at that?

John Feiler


--
John Feiler	 709 Locust #7	 Pasadena, CA 91101
jjfeiler@tybalt.caltech.edu