The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ronald Natalie <ron@ronnatalie.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Model 37's
Date: Mon, 16 Sep 2019 21:11:59 -0400	[thread overview]
Message-ID: <77060A04-696A-4789-A63A-D7A725B5AA63@ronnatalie.com> (raw)
In-Reply-To: <a29bfbe24692c1908f8a880041b816f6e9262baa@webmail.yaccman.com>

Hopkins had a KSR37 in a small office (or perhaps closet) on the second floor.   It was also fitted with a modem I built (a Pennywhistle, an absolutely abhorrant design).
It had the greek box and we used it for many a nroff term paper or the like.    It was also our way of getting on the Arpanet.    The university had a “tie line” that let us call the DC metro area so we could get into the Pentagon TIP.    However, Mike Muuss also convinced the operator once to place a collect call.    “It’s a computer we are calling,” he told her.   “If it beeps, it accepts the charges.”   (This was perhaps one of the boldest operator hacks until Brian Redman and Peter Langston were screwing around with a phone switch and programmed it to answer the phone:   “Bell Communications Research” (long pause) “Yes, Operator!   I’ll accept the charges.”


After I graduated from JHU, I found an ASR 37 in a surplus sale.    I had it for years in my apartment kitchen.   Not only did it handle all the nroff ESC-8/ESC-9 stuff and the like without need for an output filter, it had a giant NEWLINE key on the right side and was perhaps the only terminal I ever used that didn’t need the unix NL->CRLF mapping turned on.     Amusingly, the thing sat there idle until DSR came up on the modem and then its motors would start.    When CD came on a bright green PROCEED light illuminated on the front of it.    I used it for years until modems got up to the 9600 baud range and decided a CRT would be nicer than the printing terminal.

I gave mine to RS who I think used it to block in someone’s car at one of the nacent long distance data carriers (was either Sprint or MCI).
   
	

  parent reply	other threads:[~2019-09-17  1:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 22:07 [TUHS] earliest Unix roff Doug McIlroy
2019-09-17  0:20 ` Steve Johnson
2019-09-17  1:11   ` Arthur Krewat
2019-09-17  1:17     ` Larry McVoy
2019-09-17  1:26       ` Clem cole
2019-09-17  1:33         ` Larry McVoy
2019-09-17 22:39           ` Dave Horsfall
2019-09-17  1:36         ` Richard Salz
2019-09-17  1:36       ` [TUHS] wizards test [was roff] Clem cole
2019-09-17  1:38         ` Clem cole
2019-09-17  2:34         ` Larry McVoy
2019-09-17  1:57       ` [TUHS] earliest Unix roff Bakul Shah
2019-09-17  1:11   ` Ronald Natalie [this message]
2019-09-17  1:19   ` Bakul Shah

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=77060A04-696A-4789-A63A-D7A725B5AA63@ronnatalie.com \
    --to=ron@ronnatalie.com \
    --cc=tuhs@tuhs.org \
    /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).