Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Fwd: Fwd: IBM 1403 line printer on DEC computers?
Date: Thu, 21 Dec 2023 17:03:50 -0500	[thread overview]
Message-ID: <CAC20D2OBGT=SsXk0QxWFaJ-AOFJkp1v8K7rzpQrUDXUyC2w7Yg@mail.gmail.com> (raw)
In-Reply-To: <f39a3749-d2e2-45c1-bdb7-2976b517a585@ieee.org>

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

FYI: Tim was Mr. 36-bit kernel and I/O system until he moved to the Vax and
later Alpha (and Intel).
The CMU device he refers is was the XGP and was a Xerox long-distance fax
(LDX).  Stanford and MIT would get them too, shortly thereafter.

---------- Forwarded message ---------
From: Timothe Litt
Date: Thu, Dec 21, 2023 at 1:52 PM
Subject: Re: Fwd: [COFF] IBM 1403 line printer on DEC computers?
To: Clem Cole

I don't recall ever seeing a 1403 on a DECsystem-10 or DECSYSTEM-20.  I
suppose someone could have connected one to a systems concepts channel...
or the DX20 Massbus -> IBM MUX/SEL channel used for the STC (TU70/1/2)
tape and disk (RP20=STC 8650) disk drives.  (A KMC11-based device.)  Not
sure why anyone would.

Most of the DEC printers on the -10/20 were Dataproducts buy-outs, and were
quite competent.  1,000 - 1,250 LPM.  Earlier, we also bought from MDS and
Analex; good performance (1,000LPM), but needed more TLC from FS.  The
majority were drum printers; the LP25 was a band printer, and lighter duty
(~300LPM).

Traditionally, we had long-line interfaces to allow all the dust and mess
to be located outside the machine room.  Despite filters, dust doesn't go
well with removable disk packs.  ANF-10 (and eventually DECnet) remote
stations provided distributed printing.

CMU had a custom interface to some XeroX printer - that begat Scribe.

The LN01 brought laser printing - light duty, but was nice for those
endless status reports and presentations.  I think the guts were Canon -
but in any case a Japanese buyout.  Postscript.  Networked.

For high volume printing internally, we used XeroX laser printers when they
became available.  Not what you'd think of today - these are huge,
high-volume devices.  Bigger than the commercial copiers you'd see in print
shops.  I(Perhaps interestingly, internally they used PDP-11s running
11M.)  Networked, not direct attach.  They also were popular in IBM shops.
We eventually released the software to drive them (DQS) as part of GALAXY.

The TU7x were solid drives - enough so that the SDC used them for making
distribution tapes.  The copy software managed to keep 8 drives spinning at
125/200 ips - which was non-trivial on TOPS-20.

The DX20/TX0{2,3}/TU7x *was *eventually made available for VAX - IIRC as
part of the "Migration" strategy to keep customers when the -10/20 were
killed.  I think CSS did the work on that for the LCG PL.  Tapes only - I
don't think anyone wanted the disks by them - we had cheaper dual-porting
via the HSC/CI, and larger disks.

The biggest issue for printers on VAX was the omission of VFU support.
Kinda hard to print paychecks and custom forms without it - especially if
you're porting COBOL from the other 3-letter company.  Technically, the
(Unibuas) LP20 could have been used, but wasn't.  CSS eventually solved
that with some prodding from Aquarius - I pushed that among other high-end
I/O requirements.

On 21-Dec-23 12:29, Clem Cole wrote:

 Tim - care to take a stab at this?

ᐧ

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

      parent reply	other threads:[~2023-12-21 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 17:21 [COFF] " Paul Winalski
     [not found] ` <CAC20D2PXvTGoYyLzgH-QiNn013yyyEy+zFMVgK-3_6nLvL8Ogw@mail.gmail.com>
     [not found]   ` <f39a3749-d2e2-45c1-bdb7-2976b517a585@ieee.org>
2023-12-21 22:03     ` Clem Cole [this message]

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='CAC20D2OBGT=SsXk0QxWFaJ-AOFJkp1v8K7rzpQrUDXUyC2w7Yg@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=coff@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).