From: segaloco via TUHS <tuhs@tuhs.org>
To: jnc@mercury.lcs.mit.edu
Cc: mj@broniarz.net, COFF <coff@tuhs.org>
Subject: [TUHS] Re: [COFF] Re: Help needed with some old VAX Machines (moved from TUHS)
Date: Wed, 22 Feb 2023 19:41:35 +0000 [thread overview]
Message-ID: <GBYhoReLSzhhpYhr48yr23-0tFMMXeDiqN82gE6LBKAc9l_N5i9xtqC3yFrRsR44i90qgafXn9ZXXc1udgKJc2ScDfY2l7PJN_9R2YY_JAo=@protonmail.com> (raw)
COFF transfer, TUHS Bcc'd to know where this thread went.
Between the two if you're not doing UNIX-specific things but just trying to resurrect/restore these, COFF will probably be the better place for further discussion. @OP if you're not a member of COFF already, you should be able to reach out to Warren Toomey regarding subscription.
If you're feeling particularly adventurous, NetBSD still supports VAX in some manner: http://wiki.netbsd.org/ports/vax/
YMMV, but I've had some success with NetBSD on some pretty oddball stuff. As the old saying goes, "Of course it runs NetBSD". You might be able to find some old VMS stuff for them as well, but I wouldn't know where to point you other than bitsavers. There's some other archival site out there with a bunch of old DEC stuff but I can never seem to find it when I search for it, only by accident. Best of luck!
- Matt G.
------- Original Message -------
On Wednesday, February 22nd, 2023 at 10:08 AM, jnc@mercury.lcs.mit.edu <jnc@mercury.lcs.mit.edu> wrote:
> > From: Maciej Jan Broniarz
>
>
> > Our local Hackroom acquired some VAX Station machines.
>
>
> Exactly what sort of VAXstations? There are several different kinds; one:
>
> http://gunkies.org/wiki/VAXstation_100
>
> doesn't even include a VAX; it's just a branding deal from DEC Marketing.
> Start with finding out exactly which kind(s) of VAXstation you have.
>
> Noel
next reply other threads:[~2023-02-22 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:41 segaloco via TUHS [this message]
2023-02-23 7:37 ` Jan-Benedict Glaw
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='GBYhoReLSzhhpYhr48yr23-0tFMMXeDiqN82gE6LBKAc9l_N5i9xtqC3yFrRsR44i90qgafXn9ZXXc1udgKJc2ScDfY2l7PJN_9R2YY_JAo=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=coff@tuhs.org \
--cc=jnc@mercury.lcs.mit.edu \
--cc=mj@broniarz.net \
--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).