Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <>
To: segaloco <>
Cc: COFF <>
Subject: [COFF] Re: VAX/VMS 4.4 Source Listing?
Date: Mon, 6 Feb 2023 15:23:54 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

    I sent a former co-worker the VMS developer lead an email this AM.  I
was pretty sure I knew the answer to my question when I asked if this had
any value.   His reply was:

*Not sure about this particular version, but there certainly are other
copies floating around.*

*One thing to be aware of is that to my knowledge**, DEC never released a
complete source kit outside of the company at any price *(...  we certainly
had that behavior in Ultrix/Tru64-land I know for sure...)*.  The kits
redacted "sensitive" information, including some of the authentication
methods and the license enforcement (er, compliance assistance) code.  What
was sold as a "source kit" (media, under license) was, nonetheless
considered a trade secret with all the markings. *

*I had a complete copy of the master source pack in Marlborough during the
Aquarius development/debug time; I know I put backup tape of that into the
CHM.  That has the CMS library which would go back to at least V1.  (That
would be c.a. 1987-9.)  But the master pack contains only the VMS OS & some
tightly coupled products (e.g. rms).  The languages were elsewhere, as was
the workstation software.*


On Mon, Feb 6, 2023 at 12:38 PM segaloco via COFF <> wrote:

> Good morning all, I was wondering if anyone in this group was aware of any
> known preservation of VAX/VMS 4.4 source code?
> Just saw this on eBay:
> I certainly don't have the equipment for this in my arsenal, but at the
> same time, if this represents long-lost source code, I'd happy try and nab
> it and then get it to someone who can do the restoration work from this.
> Thoughts?
> - Matt G.

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

  reply	other threads:[~2023-02-06 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 17:37 [COFF] " segaloco via COFF
2023-02-06 20:23 ` Clem Cole [this message]
2023-02-06 20:36   ` [COFF] " Warner Losh
2023-02-07 16:40     ` Paul Winalski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).