From: litt at ieee.org (Timothe Litt)
Subject: [COFF] [Simh] Of DEC and cards
Date: Thu, 13 Feb 2020 15:09:44 -0500 [thread overview]
Message-ID: <fd52cdab-66ff-9837-3643-577c023f590d@ieee.org> (raw)
In-Reply-To: <20200213195715.8D05F18C0AA@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On 13-Feb-20 14:57, Noel Chiappa wrote:
> > From: Clem Cole
>
> > I just don't remember seeing actual card readers or punches on the
> > PDP-11s
>
> I'm not sure DEC _had_ a card punch for the PDP11's. Readers, yes, the CR11:
>
> https://gunkies.org/wiki/CR11_Card_Readers
>
> but I don't think they had a punch (although there was one for the PDP-10
> family, the CP10).
>
> I think the CR11 must have been _relatively_ common, based on how many
> readers and CR11 controller cards survive. Maybe not in computer science
> installations, though... :-)
>
> Noel
Not common, but yes:
CP11-UP Punch interface for Univac 1710 Card RDR/PUNCH
Before anyone asks, there were also:
CP08-(N,P) (CSS) Data Products Speedpuch 120 100 CPM Punch and controller
CP10-(A,B) MD6011 300 CPM CARD PUNCH & Controller (60,50 Hz)
CP15-(A,B) Ditto for the -15
and
CP20-E (The CP10 for orange boxes)
There were a few other part numbers, especially for the 10/20, which
included various mechanical options - e.g. racks for the controllers vs.
just the controller, colors, etc. What's listed are the main models for
each family.
The CP01-(A,B) "Documation LC15 Model 2 Card Puhcn, 80 Col, 100CPM,
RS322 interfaces, ASCII or Imaged mode 100-9600 BAUD
Not sure what platforms used the CP01...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200213/11687d52/attachment-0001.html>
next prev parent reply other threads:[~2020-02-13 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 19:57 jnc
2020-02-13 20:09 ` litt [this message]
2020-02-14 0:08 ` brad
[not found] <mailman.115.1581575952.971.simh@trailing-edge.com>
[not found] ` <b68b4129-b87c-7323-7ff0-13272e0aeee0@supnik.org>
[not found] ` <6167693c-1608-47c2-b7cf-790dd0f6da49@snobol4.com>
[not found] ` <20200213102754.0000119d@sky-visions.com>
[not found] ` <a2530004-10aa-93ed-8437-f7461a31df10@ieee.org>
[not found] ` <CAC20D2NbiF2AYKDkWoMn-uSN=iOnVncV3-db6WBiUJAUBPejgA@mail.gmail.com>
[not found] ` <b84c8230-4b99-da0c-aa08-3455ece15e58@ieee.org>
2020-02-13 18:37 ` clemc
2020-02-13 20:33 ` litt
2020-02-15 5:10 ` dave
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=fd52cdab-66ff-9837-3643-577c023f590d@ieee.org \
--to=coff@minnie.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).