HP3000-L Archives

February 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Mon, 1 Feb 1999 10:18:20 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Wirt writes:
> Ed Milner writes:
>
> > I've recently relocated my office away from the HP3000 and figured I would
> >  still be able to manage it using Reflections (NT v5.20), but when I try to
> >  run NMMGR through reflections, it doesn't work.
>
> "Away" may be the key word in your posting. A lot of LANs nowadays are
> dropping the DC1 character that the HP3000 uses as a host prompt (it actually
> means: "go ahead, it's your turn to talk now"). These damnable LANs are
> interpreting the DC1 as part of the flow control pair DC1/DC3 (XON/XOFF) and
> figure that they can do a better job of flow control than the original host
> computer, so they strip them out (The first rule of any data channel is that
> it should never listen to, interact with, or interfere with dataflow; it
> should pass the data onto the intended recipient, exactly as it received it.

With all due respect to Wirt, I'm aware of no case where anything that
can be referred to as a "LAN" is anything other than a 100% transparent
channel.

"LAN"s do *not* eat DC1/DC3 sequences!

If your DC1s are getting lost when you switch to a VT connection, it
may be the fault of the 3000 VTSERVER or telnet software, or the termtype
you are using, or the VT protocol software / terminal emulator on your
PC, but it is *not* your "LAN" that is eating the characters.

G.

ATOM RSS1 RSS2