The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Tom Lyon <pugs78@gmail.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Compatibility question
Date: Tue, 19 Dec 2023 16:31:43 -0500	[thread overview]
Message-ID: <CABH=_VSV4KiX4r2du6EG6z0tyTjad__YCrE8LkF-ZU_mdZDxPA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P+TS09eUprSpOtZfwwhXdFnCCew2fAdsEcUPyeEON82w@mail.gmail.com>

On 12/19/23, Clem Cole <clemc@ccc.com> wrote:
> Tom smiled while reading that man page: "It is assumed that the TN print
> train is being used."
> I have to wonder how many younger programmers know what a print train is,

For the edification of those who don't know, the 1403 line printer and
its brothers worked like this.  There was a (removable and switchable)
horizontal cartridge that sat midway in the printer, laid out
horizontally across the paper, behind an ink-soaked cloth band located
between the print train and the paper.  Behind the paper was a series
of 132 hammers (one per column of print).  The cartridge contained a
single chain of type that was spun at high speed.  Whenever the
position of a desired character passed in front of its desired colu,
that column's hammer struck the back of the paper and thus printed the
character.

There were several print trains available, just as there were several
typeballs for the IBM Selectric typewriter.  One of these used a space
character '  ' both for the space and for the underscore '_'.  This
was the origin of using underscores to represent spaces in program
identifiers.

The other way to do line printing is to have a rotating drum with the
full character set for each column.  This is the way the DEC line
printers worked.  Of course there were minor inaccuracies in the
timing of the hammers, and with the drum-based printers this resulted
in wavy lines.  There were inaccuracies in the print train-style
printers, too, but waviness in the columns is not as noticeable to the
eye as waviness in the lines.  Coming from the IBM world, I considered
the DEC printers total junk.

> Paul -- you left out the other "feature" -- the noise, which was still
> deafening even with a model N1 and its cover.

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.

-Paul W.

  reply	other threads:[~2023-12-19 21:31 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 [this message]
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
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='CABH=_VSV4KiX4r2du6EG6z0tyTjad__YCrE8LkF-ZU_mdZDxPA@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=clemc@ccc.com \
    --cc=pugs78@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).