HP3000-L Archives

November 2004, Week 4

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:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Wed, 24 Nov 2004 16:29:46 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
John writes:

> This doesn't work in Telnet, as telnet doesn't send DC1s (do a telnet
>  connection, turn on display functions, should not be any DC1).
>  I have block mode working un UX/reflections by telling reflections not to
>  wait for trigger char from computer, as the connection is telnet.
>  Looks like this FDEVICECONTROL is setting up for non-DC1 reads.....as if in
>  telnet?
>  Make any sense?

No.

Telnet transmits DC1's just as any other piece of wire would. The only
difference between the communications cable you ran between the HP3000 and your
terminal, back in the days when your terminals were within viewing distance of the
host, is the wire tht telnet implies can often be a heck of a lot longer.
Otherwise, there is absolutely no difference.

It's UNIX that doesn't transmit the DC1, not telnet. They simply aren't part
of UNIX's heritage. The presence of the go-ahead signals that DC1's represent
are an MPE-ism not shared by another operating system that I know of.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2