From: Rod Bartlett via TUHS <tuhs@tuhs.org>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Compatibility question
Date: Wed, 20 Dec 2023 22:53:21 -0500 [thread overview]
Message-ID: <E787BAF9-7CCF-4F68-89F9-BC2B87F6883C@mac.com> (raw)
In-Reply-To: <CABH=_VSV4KiX4r2du6EG6z0tyTjad__YCrE8LkF-ZU_mdZDxPA@mail.gmail.com>
> On Dec 19, 2023, at 4:31 PM, Paul Winalski <paul.winalski@gmail.com> wrote:
>
>
> Yes, the 1403 was very loud. The pitch of the noise varied with the
> sequence of characters being printed. Some IBM hacker (yes, they
> existed) came up with a deck of cards that, when printed, played
> "Anchors Aweigh" on the 1403. IBM field service wasn't very keen on
> this hack because it put a lot of wear-and-tear on the print train.
The holidays always seemed to feature people running programs which played festive songs by punching fully laced cards or printing patterns on the line printers. Whenever I noticed something, I'd ask the operators to kill those programs because they could cause equipment failures. A fully laced punch card is much more flexible and likely to jam. Printing all columns on a printer, especially doing so without a line feed, tends to moisten the paper which tended to gum up the print trains.
Those line printers were definitely noisy. I've got tinnitus thanks to working around them.
- Rod
next prev parent reply other threads:[~2023-12-21 3:53 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
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 [this message]
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=E787BAF9-7CCF-4F68-89F9-BC2B87F6883C@mac.com \
--to=tuhs@tuhs.org \
--cc=norwayjose@mac.com \
--cc=paul.winalski@gmail.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).