The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: John Floren <john@jfloren.net>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] A stack of PDP-11 field maintenance print sets
Date: Fri, 5 Mar 2021 19:25:25 -0500	[thread overview]
Message-ID: <CAMQbRb0jZ8F_0-rmJ2+Jun_XmXV24VN1s=NQT0gQrhA6b8W2hg@mail.gmail.com> (raw)
In-Reply-To: <CAL4LZyhDTH9yXgwXES6XxZf2Hv=KAmOeqrEc8f0GYz+GVFy=aA@mail.gmail.com>

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

There are several computer museums that might be interested in them
So don't toss them at this point.

On Fri, Mar 5, 2021, 5:52 PM John Floren <john@jfloren.net> wrote:

> I've been hauling around a pile of DEC Field Maintenance Print Sets
> for PDP-11 components for over a decade now, intending to see if
> they're worth having scanned or if there are digital versions out
> there already. Can anyone on the list point me to either an existing
> archive where these exist, or an archivist who would be interested in
> scanning them? They're full of exploded diagrams, schematics, and
> assembly listings.
>
> Here's the list of what I have:
>
> Field Maintenance Print Set (17" wide, 11" high):
> RLV11 disk controller
> RL01-AK disk drive
> ADV-11A (??)
>
> Field Maintenance Print Set (14" wide, 8.5" high):
> RL01 disk drive
> DLV11-J serial line controller
> RLV11 disk controller
> KFD11-A cpu
> KEF11-A floating point processor
> PDP11/23
> PDP11/03-L
>
> Thanks,
>
> John Floren
>

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

  reply	other threads:[~2021-03-06  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 22:51 John Floren
2021-03-06  0:25 ` Kenneth Goodwin [this message]
2021-03-06  0:29   ` John Floren
2021-03-06 14:15 Noel Chiappa

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='CAMQbRb0jZ8F_0-rmJ2+Jun_XmXV24VN1s=NQT0gQrhA6b8W2hg@mail.gmail.com' \
    --to=kennethgoodwin56@gmail.com \
    --cc=john@jfloren.net \
    --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).