From: stewart at serissa.com (Lawrence Stewart)
Subject: [COFF] ARPAnet now 4 nodes
Date: Sun, 8 Dec 2019 20:09:02 -0500 [thread overview]
Message-ID: <C4141374-114F-4DBB-A2F3-48271AA51804@serissa.com> (raw)
In-Reply-To: <20191206173338.2BB0218C07E@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
> On 2019, Dec 6, at 12:33 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu <mailto:jnc at mercury.lcs.mit.edu>> wrote:
>
>> From: Lars Brinkhoff
>
>>> PARC's MAXC appears in the mid-1970s.
>
>> Maybe this is a good time to ask if anyone knows whether any of those
>> diverse systems has software preserved? Specifically, the
>> implementation of the NCP and 1822 Host-to-IMP protocols?
>
> Both MAXC's were PDP-10 re-implementations, and ran TENEX. So the basic
> system is still around, not sure if they had any interesting local hacks
> (well, probably PUP support; MIT tried to put it in MIT-XX, so it may
> still exist on thats backup tapes).
>
I am pretty sure that the NCP implementation for the MAXCs was the TENEX version, with local mods by Ed Taft.
I designed the Alto BBN-1822 interface, which was used for connecting to the Bay Area Packet Radio network and also used for PARC-MAXC2. MAXC1 had a Nova as the front end, about which I know nothing, but MAXC2 used an Alto. Both machines were 40 bit word microcoded machines programmed to be PDP-10s. Corporate wanted PARC to use SDS but the CSL folks wanted a 10, so they had to build one.
The software specifically for the Alto 1822 survives, oddly enough, because Marc Verdiell (CuriousMarc)’s
Alto Restoration project showed my old 1822 development disk pack in https://www.youtube.com/watch?v=LxFv2JNNW-A <https://www.youtube.com/watch?v=LxFv2JNNW-A> I found the bits at
http://xeroxalto.computerhistory.org/Indigo/Alto-1822/.index.html <http://xeroxalto.computerhistory.org/Indigo/Alto-1822/.index.html>
I only tested my own code up to successful loopback to the local IMP, then Ed took over. I did the low level code for the PRNet interface, which was not NCP, and hooked it up to Hal Murray’s Mesa implmentation of the Pup stack.
-Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191208/744dcfb5/attachment.html>
next prev parent reply other threads:[~2019-12-09 1:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 17:33 jnc
2019-12-06 18:02 ` lm
2019-12-06 19:38 ` lars
2019-12-09 1:09 ` stewart [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-04 20:29 Dave Horsfall
2020-12-10 8:12 rudi.j.blom
2020-12-05 23:14 jnc
2020-12-09 2:41 ` dave
2020-12-04 21:05 dave
2019-12-05 0:08 dave
2019-12-05 4:19 ` lm
2019-12-05 8:01 ` lars
2019-12-05 12:37 ` clemc
2019-12-05 18:20 ` gingell
2019-12-05 18:33 ` lars
2019-12-05 19:05 ` lm
2019-12-05 20:41 ` gingell
2019-12-06 1:19 ` amp1ron
2019-12-06 3:25 ` gingell
2019-12-06 4:19 ` amp1ron
2019-12-06 4:43 ` amp1ron
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=C4141374-114F-4DBB-A2F3-48271AA51804@serissa.com \
--to=coff@minnie.tuhs.org \
/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).