The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] Teletype simulator?
Date: Thu, 24 Mar 2016 13:29:05 -0700	[thread overview]
Message-ID: <ea0588615981ed2e70af1ae15622fcb5.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <56F412B5.4010408@mhorton.net>

All this talk about Teletypes brings up memories.  Model 33 TTY's were
single case and each "key" (which was tubular) had to be pressed down over
1/4 inch to register.  It was a significant effort.  The model 37 TTY's
that came along a few years later were upper and lower case (Unix was one
of the few OS's at the time that could handle both cases smoothly).  But
if you opened the case, what was in it was an astonishing assembly of
cams, levers, and other mechanisms.  When glass TTY's came along, they
took over quickly.

One of my most vivid memories of "paper" TTY's happened at my home, early
in my Unix experience.  The TTY had a box of paper feeding it, and the
output was also allowed to pile up behind it.  This "used" paper served a
critical role.  At the time, Unix had two kinds of files -- small and
large -- and if the system crashed (not uncommon in those days) when your
file was in transition from small to large the contents of the file were
lost.  It was also frequently the case that updates were lost in files
being edited.  So when the system crashed, you would haul up the terminal
output and highlight the changes that you made in case you needed to enter
them again.  This typically took a few minutes, by which time the system
was up again and you could start to reenter your changes.

So one day, I was heavily into editing when my wife, in the kitchen,
needed help with the kids so I went to help her out, leaving the terminal
running.  It was several hours before I was able to get back to it, at
which point I discovered that not only had the system crashed, but our cat
had discovered an alternative "litter box" behind the terminal and made
use of it!  Luckily, it was pretty dry by then, but that didn't help the
smell.  And, so help me, holding my breath I marked the lines that needed
to be reentered...

The other TTY story that surfaced happened to Dennis.  He had one of the
last model 37's as his home terminal, and it was getting quirky.  The
vibration of the mechanism occasionally caused a blank space to be
generated that he hadn't typed.  In those days, it was common to delete
the .o files after compiling because disc space was precious.  So Dennis
typed
"rm *.o" and Unix replied ".o not found".





> That sounds like the Teletype model 33, and probably other Teletypes.
>
> If you don't give it the extra .1 second of the LF, the first printed
> character will overstrike in the middle of the line you just typed.  And
> it will be "bold" because the print head is moving very fast to the left.
>




  reply	other threads:[~2016-03-24 20:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 13:19 Noel Chiappa
2016-03-24 14:23 ` Random832
2016-03-24 16:41   ` Jacob Goense
2016-03-24 14:28 ` Lawrence Stewart
2016-03-25 21:27   ` Diomidis Spinellis
2016-03-25 21:56     ` Steffen Nurpmeso
2016-03-28 12:04       ` Steffen Nurpmeso
2016-03-24 14:40 ` George Ross
2016-03-24 15:29   ` Random832
2016-03-24 15:32   ` John Cowan
2016-03-24 16:15   ` Mary Ann Horton
2016-03-24 20:29     ` scj [this message]
2016-03-25 12:54       ` Dave Horsfall
2016-03-26 21:04       ` Ronald Natalie
2016-03-24 19:56 ` scj
  -- strict thread matches above, loose matches on Subject: below --
2016-03-24 20:12 Norman Wilson
2016-03-24 20:24 ` Lyndon Nerenberg
2016-03-24 20:36 ` scj
2016-03-24 13:36 Doug McIlroy
2016-03-23 19:28 [TUHS] PDP-7 Unix: The B compiler works Warren Toomey
2016-03-24  9:01 ` [TUHS] Teletype simulator? Warren Toomey
2016-03-24 10:21   ` Pierre DAVID
2016-03-24 11:00     ` Clem cole
2016-03-24 11:01       ` Clem cole
2016-03-24 21:39       ` Clem Cole
2016-03-25  3:18         ` Mary Ann Horton
2016-03-25  3:57           ` Charles Anthony
2016-03-25 20:13             ` Mary Ann Horton
2016-03-24 16:37   ` Jacob Goense
2016-03-25  2:18   ` Dave Horsfall
2016-03-25  3:43     ` Greg 'groggy' Lehey
2016-03-25  5:59     ` Jacob Goense

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=ea0588615981ed2e70af1ae15622fcb5.squirrel@webmail.yaccman.com \
    --to=scj@yaccman.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).