From: clemc at ccc.com (Clem Cole)
Subject: [COFF] PiDP Obsolesces Guaranteed
Date: Mon, 9 Jul 2018 09:06:10 -0400 [thread overview]
Message-ID: <CAC20D2OqRcrFJ3rAvdKLNU4cMmgMArWS47mhG4Og3Ac5=5voAQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2M+SA+nNkvxdxzugSvzVx+wbEtvwGWy=uJDKLd6n9TLsg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
BTW. Just last night before I went to bed, I booted for the first time my
PiDP-11/70. I have one of the first alpha units since I’ve been coaching
Oscar with the project a small amount. I left it running a some tests last
night and am off to USENIX ATC today, so I have not even tried to boot Unix
on it yet. One of the cool things about this project, I was able to
arrange for the designer of the original 11/70 front panel to be consulted
(Jim Bleck) on the molds to Oscar who was able to have the molds and the
switches made in Europe. Anyway, the PiDP-8 is cool and looks the same as
the original 8/I, but the panel is framed/finished in wood. For the 11,
the panel is the real thing - DEC white (hopefully will not fade using
modern plastics). FYI Oscar is considering doing the -10 next but given
the amount of work from the 8 and the 11 it’s more than a hobby.
--
Sent from a handheld expect more typos than usual
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20180709/31fdd6ed/attachment.html>
next prev parent reply other threads:[~2018-07-09 13:06 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 5:56 [COFF] Other OSes? wkt
2018-07-05 6:29 ` spedraja
2018-07-05 6:40 ` bakul
2018-07-05 15:23 ` clemc
2018-07-05 20:49 ` scj
2018-07-05 21:25 ` david
2018-07-06 15:42 ` gtaylor
2018-07-05 22:38 ` ralph
2018-07-05 23:11 ` bakul
2018-07-06 0:06 ` lm
2018-07-06 15:49 ` gtaylor
2018-07-06 0:52 ` tytso
2018-07-06 5:59 ` ralph
2018-07-06 15:59 ` gtaylor
2018-07-06 16:10 ` ralph
2018-07-06 16:47 ` gtaylor
2018-07-06 15:57 ` gtaylor
2018-07-06 15:38 ` gtaylor
2018-07-09 1:56 ` tytso
2018-07-09 3:25 ` gtaylor
2018-07-09 3:35 ` crossd
2018-07-09 3:43 ` gtaylor
2018-07-09 3:52 ` imp
2018-07-09 11:32 ` perry
2018-07-09 11:50 ` perry
2018-07-09 11:34 ` crossd
2018-07-09 5:23 ` tytso
2018-07-09 12:52 ` clemc
2018-07-09 13:06 ` clemc [this message]
2018-07-09 14:39 ` tytso
2018-07-09 14:46 ` clemc
2018-07-09 11:24 ` perry
2018-07-05 22:51 ` ewayte
2018-07-08 20:31 ` perry
2018-07-08 20:53 ` perry
2018-07-09 2:44 ` crossd
2018-07-10 5:30 ` bakul
2018-07-16 14:49 ` crossd
2018-07-16 16:59 ` [COFF] Capabilities (was " bakul
2018-07-06 0:55 ` [COFF] " crossd
2018-07-06 5:42 ` bakul
2018-07-09 2:51 ` crossd
2018-07-10 5:41 ` bakul
2018-07-06 4:04 ` grog
2018-07-06 16:10 ` gtaylor
2018-07-06 18:27 ` [COFF] Editor Scripts scj
2018-07-06 19:04 ` gtaylor
2018-07-08 20:50 ` [COFF] Other OSes? perry
2018-07-08 23:27 ` bakul
2018-07-09 0:00 ` grog
2018-07-09 0:13 ` perry
2018-07-09 0:05 ` crossd
2018-07-09 0:56 ` lm
2018-07-09 2:23 ` crossd
2018-07-09 0:11 ` perry
2018-07-09 0:19 ` crossd
2018-07-09 2:00 ` bakul
2018-07-09 3:02 ` [COFF] Origination of awful security design [COFF, COFF] bill
2018-07-09 13:10 ` [COFF] Other OSes? david
2018-07-09 13:17 ` perry
2018-07-09 13:13 ` perry
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='CAC20D2OqRcrFJ3rAvdKLNU4cMmgMArWS47mhG4Og3Ac5=5voAQ@mail.gmail.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).