----------------------------------------------------------------------------------
@MSGID:
<f1f1d06d-1bc3-4983-a910-a58359c165d1n@googlegroups.com> e9d541e4
@REPLY: <mdd4jjck4rr.fsf@panix5.panix.com>
3b7757ba
@REPLYADDR gah4 <gah4@u.washington.edu>
@REPLYTO 2:5075/128 gah4
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<76a1f909-6624-4c35-bcc1-7f542d18f80en@googlegroups.com> <a264f576-2cef-430c-bc79-fe499f70353an@googlegroups.com>
<mdd4jjck4rr.fsf@panix5.panix.com>
@RFC-Message-ID:
<f1f1d06d-1bc3-4983-a910-a58359c165d1n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Friday, September 29, 2023 at 3:12:43 PM UTC-7, Rich Alderson wrote:
> gah4 <
ga...@u.washington.edu> writes:
> > Until a few years ago, the best place to find a running VAX was the Living
> > Computer Museum in Seattle. (That is, a non-micro VAX.)
> > The museum is still there, but has been closed since early 2000.
> You meant "2020", of course.
Yes, but it makes a better excuse for forgetting which machines are
connected to what.
And it was a while before 2020 when I was last there.
> > I believe the VAX runs on emulated disk, though.=20
> Your belief is irrelevant.
> The VAX 11/780-5 ran against an HSJ with a full load of 2GB drives.
I remember the corner with drives, and remember it being closer
to the PDP-10 than the 11/780-5. The web site doesn`t have much
of a map of what is where, and even less, what is connected to what.
> > They do have VAX disk drives, but I don`t remember RM05 being one of them.
> We had a couple of RM05s, but they were part of a
DECSYSTEM-2020 that was kept
> unrestored (the late Mark Crispin`s Lingling.Panda.com).
> > Keeping old disk drives running is much harder than old CPUs.
> Preach.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441