The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Peter Yardley <peter.martin.yardley@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Al Kossow <aek@bitsavers.org>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Anyone have Plexus docs/software squirreled away?
Date: Thu, 20 Jun 2024 11:18:24 +1000	[thread overview]
Message-ID: <04086DAD-2267-45D8-80AA-8A9A4D38D125@gmail.com> (raw)
In-Reply-To: <CANCZdfra5tPw=0iBtzj7R9SQBEmYw1erXtesumm9o+Meo_C9LA@mail.gmail.com>

There is still OpenVMS.

> On 20 Jun 2024, at 10:20 AM, Warner Losh <imp@bsdimp.com> wrote:
> 
> At one point, a google search could find most of the VMS source, at least through VMS 5 or maybe 6. I didn't download it at the time and haven't searched since... Given the ubiquity of vms on microfiche I wasn't surprised at the time. A quick search today, though, comes up dry.
> 
> Warner
> 
> On Wed, Jun 19, 2024, 5:21 PM Peter Yardley <peter.martin.yardley@gmail.com> wrote:
> We had VMS source on microfiche as part of he support contract. If you payed more you could have got it as machine readable.
> 
> > On 20 Jun 2024, at 8:58 AM, Kevin Bowling <kevin.bowling@kev009.com> wrote:
> > 
> > On Thu, Jun 20, 2024 at 6:46 AM Al Kossow <aek@bitsavers.org> wrote:
> > On 6/19/24 3:25 PM, Kevin Bowling wrote:
> > 
> > > Seems like yet another mediocre UNIX port at first, but then they happen to find the system schematic netlists and PAL equations in addition 
> > > to partial source code on the hard disk.  If those are published that will make a quite wholesome thing to study.
> > 
> > I tried to stress on their discord that finding things like that 40 years out is a very unusual occurence.
> > I've spent decades digging through people's garages trying to find stuff like that for bitsavers.
> > 
> > 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.
> > 
> > Are you aware of anything else where the whole kit and caboodle is available?  Particularly keen on microcode and logic equations since that stuff is indeed hard to come by.
> 
> Peter Yardley
> peter.martin.yardley@gmail.com
> 

Peter Yardley
peter.martin.yardley@gmail.com


  reply	other threads:[~2024-06-20  1:18 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] Fwd: " 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
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 [this message]
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=04086DAD-2267-45D8-80AA-8A9A4D38D125@gmail.com \
    --to=peter.martin.yardley@gmail.com \
    --cc=aek@bitsavers.org \
    --cc=imp@bsdimp.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).