30 Oct
2009
30 Oct
'09
10:32 a.m.
Rich Alderson <RichA at vulcan.com> wrote:
Afraid you might be right on that one, Rich. :-(
Correct.
From: Johnny
Billquist
Sent: Wednesday, October 28, 2009 12:00 PM
Pontus Pihlgren <pontus at Update.UU.SE>
wrote:
> Ps.
> Checking the archives, both you and Peter
posted the link :D
>
http://www.classiccmp.org/mailman/htdig/cctalk/2003-July/025598.html
> http://www.classiccmp.org/mailman/htdig/cctalk/2009-January/267600.html
Ah. That first link was really good. There people
can see what Peter
have in storage. Most of it very much possible to get running. So he
have actually four KI10 systems, as well as two KA10, and a bunch of KL
and KS. It was more than I thought.
Looks like a pretty good collection of all 36-bit
machines with PDP-10
like architecture. Missing is a PDP-6, as well as a few clones.
No one has a PDP-6. No one. :-((( The SC30 is
actually online on HECnet. :-)
.ncp tell sol sho exec
Node summary as of 28-OCT-09 19:53:09
Executor node = 59.10 (SOL)
Identification = Systems Concepts SF CA USA -
SC30M - DN-20 4.0
State = On, Active links = 0
I think his TOAD-1 is also running, but it
don't seem to be online on
HECnet right now.
If I understand it correctly, HECNET is a DECnet network, right? In that case, unless Peter or someone else has done
the work to make the
Toad-1 speak DECnet, no one's Toad-1, Peter's or any other, will ever be
on HECNET. The management at XKL absolutely forbade the software people
to work on DECnet, for reasons obvious to anyone knowing the company history.
Hmm. What would prevent it? After all DECnet already exists for TOPS-20.
Did XKL make such big, incompatible changes to T20 after they got it
from DEC?
I would definitely not hold it above Peter to fix it if it didn't work
for some reason. He has done things like that in the past.
The Toad-1 do have a node number allocated on HECnet anyway.
.ncp sho nod toad1
Node summary as of 30-OCT-09 18:29:13
Remote Active Next
Node State Links Delay Circuit Node
59.30 (TOAD1) 0 30 60.664 (PDXVAX)
Johnny
2 Nov
2 Nov
1:08 p.m.
From: Johnny Billquist
Sent: Friday, October 30, 2009 10:33 AM
Rich Alderson <RichA at vulcan.com> wrote:
>> From: Johnny Billquist
>> Sent: Wednesday, October 28, 2009 12:00 PM
> No one has a PDP-6. No one. :-(((
Afraid you might be right on that one, Rich. :-(
I'm pretty sure that I am. At the time of the 1984 DECUS Fall Symposium,
the only known PDP-6 in the world was the one at the Stanford Artificial
Intelligence laboratory. This was taken to Anaheim to be displayed for the
20th Anniversary of 36-Bit Computing. From there it was destined for the
Computer Museum in Boston, but it disappeared into the mists of time.
>> I think his TOAD-1 is also running, but it
don't seem to be online on
>> HECnet right now.
> If I understand it correctly, HECNET is a DECnet
network, right?
Correct.
> In that case, unless Peter or someone else has
done the work to make the
> Toad-1 speak DECnet, no one's Toad-1, Peter's or any other, will ever be
> on HECNET. The management at XKL absolutely forbade the software people
> to work on DECnet, for reasons obvious to anyone knowing the company
> history.
Hmm. What would prevent it? After all DECnet already
exists for TOPS-20.
Did XKL make such big, incompatible changes to T20 after they got it
from DEC?
There were a number of incompatible changes to TOPS-20, of course. The
Toad-1 uses SCSI peripherals instead of Massbus, Stanford/Cisco MEIS-style
Ethernet instead of NIA-20, and provides the full 30 bits of address that
Digital defined for the extended addressing scheme of the PDP-10 rather
than the 22 physical/23 virtual of the KL-10. The Ethernet differences are
what would require work in the monitor's DECnet code.
I would definitely not hold it above Peter to fix it
if it didn't work
for some reason. He has done things like that in the past.
Oh, I know. I've seen his implementation of TCP/IP for Tops-10 v7.02, which
used an ANF-10 style connection as I recall. I just don't know that Peter
has the time for that.
The Toad-1 do have a node number allocated on HECnet
anyway.
.ncp sho nod toad1
Node summary as of 30-OCT-09 18:29:13
Remote Active
Next
Node State Links Delay Circuit Node
59.30 (TOAD1) 0 30
60.664 (PDXVAX)
Interesting, but it's possible that that's just a place holder in case
someone ever does the required work.
Rich
5529
days inactive
5532
days old
1 comments
2 participants
participants (2)
-
bqt＠softjar.se -
RichA＠vulcan.com