From: Rik Farrow <rik@rikfarrow.com>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: Al Kossow <aek@bitsavers.org>, tuhs@tuhs.org
Subject: [TUHS] Re: Fwd: Anyone have Plexus docs/software squirreled away?
Date: Wed, 19 Jun 2024 16:03:46 -0700 [thread overview]
Message-ID: <CACY3YMG+qMD31Hvo8HYtH3qg27KTfgEwTVUHeACqYMRktjgZtw@mail.gmail.com> (raw)
In-Reply-To: <CAK7dMtDrq+koZG-2+SKrvJ=VuESDY95dW6x6Ldy0aNTNAA0OXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Wed, Jun 19, 2024 at 3:58 PM Kevin Bowling <kevin.bowling@kev009.com>
wrote:
>
>
> I’m weak in my DEC history and collection but I’ve heard some in person
> stories that VMS source was not impossible to find on microfiche at certain
> institutions. They might have had at least board level schematics too.
> That situation would be roughly equivalent to IBM mainframes through the
> 1980s but you’d still be missing a lot of microcode and logic equations to
> zoom in at any level for these two examples.
>
> Someone who had previously worked at Lawrence Livermore Labs offered me
the VMS source on microfiche, sometime around 1990. I turned him down...
Rik
[-- Attachment #2: Type: text/html, Size: 1147 bytes --]
next prev parent reply other threads:[~2024-06-19 23:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d949c87a-01ae-08d3-eee0-871f5975d935@bitsavers.org>
2024-06-19 16:07 ` [TUHS] " Al Kossow
2024-06-19 16:20 ` [TUHS] " Steve Nickolas
2024-06-19 17:22 ` Al Kossow
2024-06-19 22:13 ` Grant Taylor via TUHS
2024-06-19 22:25 ` Kevin Bowling
2024-06-19 22:46 ` Al Kossow
2024-06-19 22:58 ` Kevin Bowling
2024-06-19 23:03 ` Rik Farrow [this message]
2024-06-19 23:10 ` Al Kossow
2024-06-19 23:21 ` [TUHS] " Peter Yardley
2024-06-20 0:20 ` Warner Losh
2024-06-20 1:18 ` Peter Yardley
2024-06-20 2:30 ` Henry Bent
2024-06-20 2:48 ` Warner Losh
2024-06-20 4:12 ` segaloco via TUHS
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=CACY3YMG+qMD31Hvo8HYtH3qg27KTfgEwTVUHeACqYMRktjgZtw@mail.gmail.com \
--to=rik@rikfarrow.com \
--cc=aek@bitsavers.org \
--cc=kevin.bowling@kev009.com \
--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).