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 15:07:32 -0500	[thread overview]
Message-ID: <CAC20D2Pjh7x_nxNUfwe9kBwM-VY4yFvPXF5aFg6mdAit=o9ebw@mail.gmail.com> (raw)
In-Reply-To: <CACCFpdwiCXgA_5gKxL9Z+xDec50QAbLufrQ_qRqRc5Re5as3pA@mail.gmail.com>

Some thoughts...   In the late 60s, early 70s the number glass tty's being
made were actually fairly small at first.  They tended to be custom build
for specific uses, such as the airlines or wall street traders.   The idea
of the glass tty was not quite ready to be birthed.   Mostly because the
cost was high and the need was not quite yet there.  IIRC VT05 and the like
cost multiple thousands of dollars in late 1960/early 1970s money [FYI -
the dollartimes.com website says that's between $13K-$15K in todays money].

Remember that at the time the of the VT05, its follow on the VT52 and its
contemporary, the logic was built primarily with using MSI TTL; including
all the video logic to drive the display itself.   A dominate cost of the
terminal was the static ram chips.   A single 24x80 lines of 2000 chars was
$50-100 in OEM quantities.  The keyboard cost about the same.   The video
sub systems were black and white TV monitors.   You still need a case,
keyboard and the rest of the logic.     The $999 cost of the Lear Siegler
Kit that you assembled yourself was a steal.    DEC used an Intel 8080 in
the VT-100 a few years later, they paid approx a huge amount of money for
it, but they were able to make the logic board so much smaller.   IIRC the
original price for the VT-100 was $3500 in 1976 (they did sell a ton of the
them).      Shortly thereafter, most terminals had 8080's, 6502s, or Z80s
in them.    Motorola built the first video chips and it's interesting, how
many of the terminals all used same video chips but the processors were
more varied.   With the prices settling around $700-$1.5K mark by the early
1980s.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171122/b33eb781/attachment-0001.html>


  parent reply	other threads:[~2017-11-22 20:07 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
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 [this message]
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='CAC20D2Pjh7x_nxNUfwe9kBwM-VY4yFvPXF5aFg6mdAit=o9ebw@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).