From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Date madness
Date: Wed, 13 Dec 2017 15:22:26 -0500 (EST) [thread overview]
Message-ID: <20171213202226.5214E18C094@mercury.lcs.mit.edu> (raw)
> From: Tom Ivar Helbekkmo
> My /83s have them, but I'm not so sure it's a feature of the CPU board:
> there's this thought nagging in the back of my head that the ToY thing
> actually sits in the front panel module with the various buttons on it.
/83 documentation seems to be very thin on the ground, alas.
It's definitely not the CPU; the KDJ11-B CPU (of the /83) manual
(EK-KDJ1B-UG-001) makes no mention of it; and in the PDP-11/94E System User
and Maintenance Guide (EK-KDJ1E-UG-001), section D.2 "PDP-11/94 and 11/84
Hardware Differences" (the /?3 and /?4 models use the same CPU board, but a
different backplane, with QBUS/UNIBUS converter, so this could equally well be
titled "PDP-11/93 and 11/83 Hardware Differences") says "Time of Year Clock",
indicating the 83/84 don't have one.
Several companies made after-market ToD clocks to plug into the QBUS, e.g.
here:
https://www.ebay.com/itm/371284594072
Is something like that what your /83 has?
Noel
next reply other threads:[~2017-12-13 20:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 20:22 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-16 10:50 Doug McIlroy
2017-12-16 16:11 ` Random832
2017-12-16 17:11 ` Ralph Corderoy
2017-12-13 22:16 Norman Wilson
2017-12-14 0:24 ` Chris Torek
2017-12-17 16:20 ` Ron Natalie
2017-12-17 18:53 ` Tom Ivar Helbekkmo
2017-12-17 20:07 ` Ron Natalie
2017-12-13 19:12 Doug McIlroy
2017-12-14 3:07 ` Random832
2017-12-15 3:04 ` Random832
2017-12-13 17:16 Noel Chiappa
2017-12-13 18:53 ` Tom Ivar Helbekkmo
2017-12-13 20:46 ` arnold
2017-12-15 16:41 ` Paul Winalski
2017-12-15 17:19 ` Dave Horsfall
2017-12-16 15:45 ` Clem Cole
2017-12-16 3:39 ` Dave Horsfall
2017-12-16 3:45 ` Lyndon Nerenberg
2017-12-17 1:43 ` Dave Horsfall
2017-12-14 3:08 ` Dave Horsfall
2017-12-14 3:13 ` Warner Losh
2017-12-13 16:31 Noel Chiappa
2017-12-13 16:50 ` arnold
2017-12-13 16:08 Noel Chiappa
2017-12-13 16:23 ` arnold
2017-12-13 15:56 Noel Chiappa
2017-12-12 18:31 Noel Chiappa
2017-12-12 18:01 Noel Chiappa
2017-12-12 18:21 ` Warner Losh
2017-12-13 15:07 ` Random832
2017-12-13 17:00 ` Jason Stevens
2017-12-13 17:18 ` Ron Natalie
2017-12-13 18:02 ` Arthur Krewat
2017-12-13 15:39 ` Wolfgang Helbig
2017-12-14 0:57 ` Dave Horsfall
2017-12-14 14:09 ` William Cheswick
2017-12-17 16:19 ` Ron Natalie
2017-12-17 16:33 ` William Cheswick
2017-12-17 17:54 ` Random832
2017-12-17 22:15 ` Dave Horsfall
2017-12-17 22:54 ` Ian Zimmerman
2017-12-16 18:12 ` Wolfgang Helbig
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=20171213202226.5214E18C094@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).