The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Anyone have Plexus docs/software squirreled away?
Date: Thu, 20 Jun 2024 04:12:27 +0000	[thread overview]
Message-ID: <X95_OnVfdBIGud1StAWfSZxB_d8HOkfcYh5rkRX759BrqlLxiLvRd0imqa6gPa7beVwh2D9NPM8u9OTVamQcEXQU4Oa7vdCdxu4ZBCkuXfk=@protonmail.com> (raw)
In-Reply-To: <CANCZdfos13fYN4amfkSzkOLAasie5U21CvhdoNe9XNgJGN4KFQ@mail.gmail.com>

On Wednesday, June 19th, 2024 at 7:48 PM, Warner Losh <imp@bsdimp.com> wrote:

> 
> 
> On Wed, Jun 19, 2024, 8:31 PM Henry Bent <henry.r.bent@gmail.com> wrote:
> 
> > On Wed, 19 Jun 2024 at 20:20, 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.
> > 
> > 
> > Someone uploaded what looks to be a full set of VMS V4.0 microfiche to archive.org, but they did it in such a way that it is hundreds of separate documents instead of one cohesive collection. I guess it's in keeping with the "here it is, but not in a particularly easy to use format" idea of the microfiche distribution...
> 
> 
> Pictures of printouts of listing of compiler output with various source directives that control the ouput. It's hard to beat retyping by hand for recovering the original source....
> 
> And these are what i found... and was part of an effort to recover the original sources.... can't recall what hapoened to that...
> 
> Warner
> 
> 
> > I'm not a VMS person but I do look through a lot of DEC archives in more and less above-board places and I've only ever seen VMS source up to V4.0.
> > 
> > -Henry

It's a shame, a VMS source microfiche set popped up on eBay some time in the past year, I can't recall why I didn't hop on it.  I do keep an eye out though.  If I ever find another I may be fiching around for some help :)

- Matt G.

      reply	other threads:[~2024-06-20  4:12 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
2024-06-20  2:30             ` Henry Bent
2024-06-20  2:48               ` Warner Losh
2024-06-20  4:12                 ` segaloco via TUHS [this message]

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='X95_OnVfdBIGud1StAWfSZxB_d8HOkfcYh5rkRX759BrqlLxiLvRd0imqa6gPa7beVwh2D9NPM8u9OTVamQcEXQU4Oa7vdCdxu4ZBCkuXfk=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).