cosell@bbn.com (Bernie Cosell) (01/01/90)
Well, I'm continuing to push on DNET and not getting very far. Several
questions crop up:
a) DNET seems to be doing a _very_ strange thing: it appears to *require*
some sort of correct parity on its incoming characters and just throws
away characters that it doesn't like. Is this true? If so, is there
some way to tell dnet to **IGNORE** the parity on incoming chars?
[this in the initial dial-up window.. I haven't gotten anywhere near close
enough to actually try to get an fterm to connect-up].
[e.g., my concentrator tried to type out
ATTENTION CORPORATE DIAL-IN USERS
and all that appeared in the dnet dial-up window was
ANNPADA-NUSS]
b) what is the real scoop on baud rate selection? The dnet.config file
claims that the AUTA lines are only scanned in '-a' mode, whereas the
dnet.doc file claims that they are basically always scanned. Is there
some way just to *tell* dnet what baud rate to use and have it just
ignore the CONNECT stuff?
c) what is the actual char/parity used by dnet. The top of dnet.doc
assert "New this release: 7 bit support. In fact, it is the default.."
but when I look at "-8" it is "NOTE! This only effects the initial
login window. The Protocol, when running, always uses 8 bits no parity".
Is that true? I run in a strictly 7-bit world and trying to set 8-bits
no parity ain't gonna work. Am I screwed? [and how does '-8' relate to
'-m0'/'-m1', not to mention the -P and -Z settings.
Sorry to be such a nuisance about this, but it is all very frustrating...
on the one hand dnet looks like it is so easy to install and use, but on
the other it is proving to be VERY hard to get it to come to life...
Thanks!
/Bernie\