The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jss@ou.edu (Jeffrey S. Sharp)
Subject: [pups] Cabinet Questions
Date: Tue, 20 Mar 2001 01:30:38 -0600	[thread overview]
Message-ID: <041601c0b10f$a919a5b0$0a01a8c0@station1> (raw)

Many thanks to those of you who have answered my previous questions.  I have
obtained the 1976 peripherals manual, and have read just enough to bring up
the next set of questions.  This round is about cabineting.

In the peripherals manual, the H960 cabinet comes in two models: the -C and
the -D.  The -D model has a sliding drawer in the lower half of the cabinet
that provides space for 9 "system units".  What are these "system units"?
How big are they?  What goes there?  When do you need the -D model?

Let's say I want to ultimately build a 11/70 system with a TE16/TM03 (in its
own cabinet, I guess), a TU56/TC11, a paper tape reader/punch (PC11?), 3 or
4 RK05s, and 1 or 2 RP04s.  What set of cabinets do I need for this system?
Assume the CPU has the SETASI memory upgrades and not core.

Una vez mas... Let's say I want to ultimately build a 11/40 system with the
same peripherals as above minus the RP04s and with a TU10/TM11 as the
9-track.  What kind of cabineting do I need here?  Assume the CPU has MOS
memory and not core.

I've got guesses, but I'd like to keep them private to save myself the
embarassment. :-)

Finally, how much weight can a H960 support?

--
Jeffrey S. Sharp
jss at ou.edu

"One World, One Web, One Program" -- Microsoft advertisement
"Ein Volk, Ein Reich, Ein Fuhrer" -- Adolf Hitler



Received: (from major at localhost)
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id UAA28053
	for pups-liszt; Tue, 20 Mar 2001 20:02:44 +1100 (EST)
	(envelope-from owner-pups at minnie.cs.adfa.edu.au)
Received: from mail6.mmcable.com (fe6.rdc-kc.rr.com [24.94.163.53])
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id UAA28049
	for <pups at minnie.cs.adfa.edu.au>; Tue, 20 Mar 2001 20:02:41 +1100 (EST)
	(envelope-from jss at ou.edu)
Received: from station1 ([65.26.237.187]) by mail6.mmcable.com  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Tue, 20 Mar 2001 02:54:02 -0600
Message-ID: <003501c0b11c$5ddae0c0$0a01a8c0 at station1>
From: "Jeffrey S. Sharp" <jss@ou.edu>
To: "ClassicCmp Mailing List" <classiccmp at classiccmp.org>,
        "PUPS Mailing List" <pups at minnie.cs.adfa.edu.au>
Subject: [pups] PDP-11/70 Front Panel
Date: Tue, 20 Mar 2001 03:01:35 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk

I will be picking up a PDP-11/70 in a few weeks, but it needs a front panel.
If anybody has an extra, please e-mail me.

--
Jeffrey S. Sharp
jss at ou.edu





             reply	other threads:[~2001-03-20  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20  7:30 Jeffrey S. Sharp [this message]
2001-03-20 20:36 Carl Lowenstein

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='041601c0b10f$a919a5b0$0a01a8c0@station1' \
    --to=jss@ou.edu \
    /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).