The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] First CRT terminal on Unix?
Date: Wed, 22 Nov 2017 16:54:21 -0500	[thread overview]
Message-ID: <CAC20D2Pxv6cSsnpsX5BpGVzciU=PPSnk+MakmRmTxP8Zg-7Jcg@mail.gmail.com> (raw)
In-Reply-To: <20171122213349.GA9067@indra.papnet.eu>

ASR-37 were used at the labs

On Wed, Nov 22, 2017 at 4:33 PM, Angelo Papenhoff <aap at papnet.eu> wrote:

> On 23/11/17, Nigel Williams wrote:
> > On Thu, Nov 23, 2017 at 6:40 AM, Nigel Williams
> > <nw at retrocomputingtasmania.com> wrote:
> > > I suspect the VT05 was not popular as it was slow, uppercase only, 72
> > > characters x 20 lines, and not cursor addressable (much like Teletypes
> > > of that time).
> >
> > I am wrong, DEC VT05 was cursor addressable, it could even erase to end
> of line.
> >
> > 3.8 Direct Cursor Addressing (CAD)
> >
> > https://vt100.net/docs/vt05-rm/chapter3.html#S3.8
> >
> > Through the use of CAD (0168), the cursor can be directed to any one
> > of the 1440 character locations on the CRT screen using three
> > instructions. The CAD function is used to allow updating of displayed
> > data without retransmitting the complete page.
>
> I wrote a VT05 emulator some while ago: https://github.com/aap/vt05
> It's certainly not perfect and probably has some bugs, but I somehow had
> the urge to write it for no particular reason.
> I would actually be interested in the newline delay the machine needs
> because I didn't implement it.
>
> I hope this doesn't derail the discussion too much, but I would actually
> like to know which teletypes were used at bell labs. What strikes me as
> odd is that in UNIX lower case is the norm yet the ASR-33, which I would
> assume was ubiquitous, does only to upper case and also doesn't do some
> characters used by C, like {}. In this famous photo you see ASR-33s...so
> were they really the main interface to early UNIX?
> https://www.bell-labs.com/usr/dmr/www/kd14.jpg
>
> aap
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171122/2da39b5e/attachment.html>


  reply	other threads:[~2017-11-22 21:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 10:43 Nigel Williams
2017-11-22 12:22 ` Robert Diamond
2017-11-22 13:26   ` Clem Cole
2017-11-22 13:28     ` Clem Cole
2017-11-22 14:18       ` Ron Natalie
2017-11-22 16:33 ` Random832
2017-11-22 16:42   ` Ben Greenfield
2017-11-22 17:15     ` Random832
2017-11-22 17:55     ` Henry Bent
2017-11-22 19:39       ` Random832
2017-11-22 19:40       ` Nigel Williams
2017-11-22 19:48         ` Nigel Williams
2017-11-22 21:33           ` Angelo Papenhoff
2017-11-22 21:54             ` Clem Cole [this message]
2017-11-23 19:33               ` Ron Natalie
2017-11-23 19:49                 ` Jon Steinhart
2017-11-24  1:42                   ` Ron Natalie
2017-11-22 22:14             ` Random832
2017-11-22 20:07         ` Clem Cole
2017-11-22 21:50   ` Dave Horsfall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC20D2Pxv6cSsnpsX5BpGVzciU=PPSnk+MakmRmTxP8Zg-7Jcg@mail.gmail.com' \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).