The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Compatibility question
Date: Wed, 20 Dec 2023 09:07:38 -0700	[thread overview]
Message-ID: <CAP2nic0sixEmHTeeyBUYPoojzp4yY7=-nUrPGHB0y-eqy-3kxQ@mail.gmail.com> (raw)
In-Reply-To: <1a126b3d-412e-4b54-89c7-2d643b47a0cf@mhorton.net>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

On Tue, Dec 19, 2023 at 11:14 PM Mary Ann Horton <mah@mhorton.net> wrote:

> I vaguely recall, as a teen, taking a tour of a DEC-10 shop in about 1970
> in Portland. Their printer played "Anchors Aweigh" and I never knew how.
> But now I wonder - does this mean they had an IBM 1403 connected to a DEC
> 10 somehow?
>

It certainly means they had some kind of chain or train printer, but any
place big enough to have a PDP-10 would probably have had the budget for a
serious printer as well.  I don't know if DEC made a competing printer (I
think they were very early with dot matrix printing?) or not (or who other
than IBM made big lineprinters),  but once you know the trick is possible,
the rest is a relatively simple matter of having someone with a good ear to
tune the printer output so it sounds right.

For a modern and delightful analogue to this, have a look at the
Floppotron.  https://www.youtube.com/@PaweZadrozniak

[-- Attachment #2: Type: text/html, Size: 1365 bytes --]

  reply	other threads:[~2023-12-20 16:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17  2:01 [TUHS] " KenUnix
2023-12-17 18:13 ` [TUHS] " Seth Morabito
2023-12-17 18:23   ` segaloco via TUHS
2023-12-17 22:51     ` Mary Ann Horton
2023-12-17 22:59       ` Ron Natalie
2023-12-17 23:08         ` Warner Losh
2023-12-18  0:35           ` KenUnix
2023-12-18  3:24             ` segaloco via TUHS
2023-12-18 17:05         ` Paul Winalski
2023-12-18 22:29           ` Jon Forrest
2023-12-19  1:46           ` Dave Horsfall
2023-12-19  7:56             ` Harald Arnesen
2023-12-19 17:40             ` Paul Winalski
2023-12-19 18:07               ` Tom Lyon
2023-12-19 20:23                 ` Clem Cole
2023-12-19 21:31                   ` Paul Winalski
2023-12-19 23:52                     ` Bakul Shah
2023-12-20  0:05                       ` Greg 'groggy' Lehey
2023-12-20  1:03                         ` Bakul Shah
2023-12-20  1:32                           ` Greg 'groggy' Lehey
2023-12-20  6:05                             ` Wesley Parish
2023-12-20  0:15                       ` Mary Ann Horton
2023-12-20 16:07                         ` Adam Thornton [this message]
2023-12-20 16:22                           ` Clem Cole
2023-12-20 18:11                           ` Alan D. Salewski
2023-12-20 16:34                         ` Paul Winalski
2023-12-20 18:15                           ` Jon Forrest
2023-12-20  1:11                       ` Steffen Nurpmeso
2023-12-20  1:23                         ` Tom Lyon
2023-12-21  3:53                     ` Rod Bartlett via TUHS
2023-12-19 21:34                   ` Rob Pike
2023-12-17  5:55 David Arnold
2023-12-17  8:08 ` segaloco via TUHS
2023-12-17 18:04   ` James Frew
2023-12-17 18:18     ` Lars Brinkhoff
2023-12-17 19:14       ` Brad Spencer
2023-12-17 18:48     ` Paul Winalski
2023-12-17 18:59       ` Warner Losh
2023-12-17 20:24       ` Dave Horsfall
2023-12-17 19:26     ` Dan Cross
2023-12-17 20:08       ` Warner Losh
2023-12-17 14:07 ` Brad Spencer
2023-12-17 14:47   ` Arrigo Triulzi via TUHS

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='CAP2nic0sixEmHTeeyBUYPoojzp4yY7=-nUrPGHB0y-eqy-3kxQ@mail.gmail.com' \
    --to=athornton@gmail.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).