The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: TUHS main list <TUHS@minnie.tuhs.org>
Subject: Re: [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ]
Date: Wed, 15 Jan 2020 13:35:48 -0500	[thread overview]
Message-ID: <CAC20D2NCCHvo_wjtguVrfd4om3ZeV1kA-eekVhBYrFLp9fuViw@mail.gmail.com> (raw)
In-Reply-To: <20200115164647.AA0D218C0A2@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

On Wed, Jan 15, 2020 at 11:47 AM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:

> Wow! WD created the QBUS? Fascinating. I wonder if DEC made any changes to
> the
> QBUS between the original demo WD boards and the first DEC ones?

I can not say I know and I would suspect they peed on it in some manner,
that *was the DEC culture*.  I've just sent a note to Mr. BI to see if he
knows and I'll pass back anything I learn if I do.  Sounds like the sort of
thing they might have gotten changed before it was release.




> Are there any documents about the WD original still extant, do you know?
>
I'm pretty sure we had some stuff from WD at CMU, because CM* was made out
of a lot of them, and CMU did custom microcode so they could talk to the
capabilities and K.map HW.  I remember seeing some prints with WD markings
on it, but I was not heavily involved other than working the new
distributed front-end which we did with LSI-11s.

Somebody from the CMU HW lab like Jim Teter might know, although he did the
11/40e for C.mmp, I'm not sure who was the microcode guru on CM*  as that
was all happening as I was leaving.  I sent a couple of emails to folks
like Danny Klein, Mike Liebensberger, and Tron McConnell. Danny and Mike
are SW folks, Tron was a EE/HW type but mostly worked on other stuff at
Mellon Institute in those days.    But, IIRC, Tron was worked on a 3Mbit
Xerox board for the LSIs, so he might have had something.   We all did some
stuff with CM* (Mike more than any of us). FWIW: Tron was (is) a bit of
packrat and if he ever had anything like that, he might still have it.

[-- Attachment #2: Type: text/html, Size: 2598 bytes --]

  reply	other threads:[~2020-01-15 18:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 16:46 Noel Chiappa
2020-01-15 18:35 ` Clem Cole [this message]
2020-01-29 20:25 ` Dave Horsfall
     [not found]   ` <CABH=_VSPTV-rwu202hYuiXViiBG2ReMnshxUAvD9Lb6HqG4tQQ@mail.gmail.com>
     [not found]     ` <CAC20D2Mr1vqpoAELU3a+4cV7W99uh_76ogGQq28wktJM+onDQA@mail.gmail.com>
2020-02-04 20:26       ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2020-01-15  6:17 [TUHS] Spacewar at Bell Labs Lars Brinkhoff
2020-01-15  6:34 ` Earl Baugh
2020-01-15  7:10   ` [TUHS] Spacewar at Bell Labs [ really paper tape readers and tangentially related things ] Jon Steinhart
2020-01-15  8:05     ` Earl Baugh
2020-01-15 14:50     ` Clem Cole
2020-01-15 23:40       ` Al Kossow

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=CAC20D2NCCHvo_wjtguVrfd4om3ZeV1kA-eekVhBYrFLp9fuViw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=TUHS@minnie.tuhs.org \
    --cc=jnc@mercury.lcs.mit.edu \
    /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).