The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Tom Lyon <pugs78@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Compatibility question
Date: Tue, 19 Dec 2023 15:23:57 -0500	[thread overview]
Message-ID: <CAC20D2P+TS09eUprSpOtZfwwhXdFnCCew2fAdsEcUPyeEON82w@mail.gmail.com> (raw)
In-Reply-To: <CANxB0bQrrfk+AyrmUE0LS67jn1boE7vzpjYUfSCVn5p6yYdjKw@mail.gmail.com>

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

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,
much less what it looked like (or how heavy they were when you
changed them).  Also, with the loss of the use of real lineprinters, you
have to wonder if those same folks understand why the asa(1) program that
POSIX.2 requires is there (although IIRC later *.2 revisions moved it to
the "FORTRAN Runtime Utilities" as an option POSX2_FORT_RUN - but we had it
there in the original draft).

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

I equate four sounds to my early computing days: the ASR33 printing, a 1403
printing, a 1402 reading card, and finally, the constant fan noise in the
machine room, plus the smell of light machine oil [definitely in a terminal
room of ASR33s].
ᐧ
ᐧ

On Tue, Dec 19, 2023 at 1:07 PM Tom Lyon <pugs78@gmail.com> wrote:

> Yes, Amdahl UTS supported the 1403 from earliest days.
> There even seem to be some mods to 'tbl' to support it.
>
> On Tue, Dec 19, 2023 at 9:40 AM Paul Winalski <paul.winalski@gmail.com>
> wrote:
>
>> On 12/18/23, Dave Horsfall <dave@horsfall.org> wrote:
>> > On Mon, 18 Dec 2023, Paul Winalski wrote:
>> >
>> >> The 132-character screen width was for displaying files originally
>> >> formatted to be printed on a line printer.  Compiler listings and
>> linker
>> >> maps, for example.
>> >
>> > Such as the mighty 1403 :-)
>> >
>> > Hint: never leave your cup of coffee on top of it, as the lid will open
>> > automatically when it runs out of paper...
>>
>> The 1403 was the best line printer ever made.  It was originally the
>> printer for the IBM 1400 second-generation (discrete transistor-based)
>> computer.  It continued to be the line printer for S/360.  The deluxe
>> model, the IBM 1403 N1, had a power cover that could be operated under
>> computer control.  The OS/360 operating system would raise the
>> printer's cover if an error condition occurred, such as out of paper
>> or a paper jam.  This was a very useful feature in large data centers
>> where there were several line printers, to indicate which printer had
>> a problem.
>>
>> The cover of a 1403 N1 also provided a convenient and attractive flat
>> surface on which to place things.  But a dangerous one.  Many a card
>> deck magtape reel, coffee cup, or pizza box has been unceremoniously
>> dumped on the floor.
>>
>> When our shop upgraded from a S/360 model 25 to a S/370 model 125, our
>> 1403 was replaced by a 3203 line printer.  It was not as good as the
>> 1401 had been.
>>
>> There was a business in Massachusetts in the 1980s that bought and
>> sold old IBM computer gear.  A company asked them for a quote on their
>> IBM 1400 system (1401 processor, 1402 card read/punch, 1403 printer).
>> They were offered $18,000 for the whole system, or $15,000 for the
>> 1403 printer alone.  That's how valued those printers were.
>>
>> To bring this closer on-topic, was there Unix support for the IBM 1403?
>>
>> -Paul W.
>>
>

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

  reply	other threads:[~2023-12-19 20:24 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 [this message]
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
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=CAC20D2P+TS09eUprSpOtZfwwhXdFnCCew2fAdsEcUPyeEON82w@mail.gmail.com \
    --to=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).