The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Burroughs funded $30,000 for a port to E-mode stack machine in 1983!
Date: Sun, 15 Jan 2023 16:51:47 -0800	[thread overview]
Message-ID: <CAP6exY+-pH9zUSfKvq5JjfjvM6Z4w9Ob=nm4-LQ_-jcXQ1gzUw@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYKNw-_x_XYa4Z3iPi8urhyJ+0YuLMLYm4DjgomjjnL2yA@mail.gmail.com>

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

https://web.archive.org/web/20130521183231/http://jack.hoa.org/hoajaa/BurrMain.html

has the burroughs info.

On Sun, Jan 15, 2023 at 11:09 AM ron minnich <rminnich@gmail.com> wrote:

> I just stumbled across an old letter, from a VP of Burroughs to me and
> Steve Bartels, authorizing $30,000 for a port of Unix to the E-mode stack
> machine. I had forgotten getting it.
>
> Burroughs was famed for its stack machines. E-mode was a kind of last gasp
> attempt to save the stack architecture, which failed as far as I know, see
> this table:
> http://jack.hoa.org/hoajaa/Burr126b.html
>
> I worked as a hardware engineer on the A15. I also had been a Unix user
> for 7 years at that point and kept pointing out how awful the Burroughs
> CANDE time-sharing system was, and how much better Unix was. At some point
> I guess they asked me to put up or shut up. I got that money, and left
> Burroughs a week later for grad school.
>
> Funny note: A15 was Motorola ECL (MECL), and ran at 16 Mhz., considered
> fast at that time.  We used a technique called "stored logic" which was,
> believe it or not, using MECL RAM to map logic inputs to outputs, i.e.
> implement combinational logic with SRAM. Kind of nuts, but it worked at the
> time. We also used a precursor of JTAG to scan it in. Those of you who know
> JTAG have some idea of how fun this had to be.
>
> One side effect of working with MECL is you realized just how well
> designed the TI 7400 SSI/MSI parts were ... MECL always just felt like an
> awkward family to design with.
>
> Another funny story, pointing to what was about to happen to Burroughs. We
> had an app that ran for hours on the stack machine. We quick ported it to a
> VAX, started it up, and headed out to lunch -- "this will take a while,
> let's go eat." We got to the front door and: "Oh, wait, let me hop back
> into the office,I  forgot my jacket". And, noticed, the program was done in
> ... about 3 minutes. Not 8 hours.
>
> That's when we knew it was game over for Burroughs.
>
> If a picture of this letter would be useful in some archive somewhere, let
> me know, I can send it.
>
>
>

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

  parent reply	other threads:[~2023-01-16  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 19:09 [TUHS] " ron minnich
2023-01-15 19:19 ` [TUHS] " Luther Johnson
2023-01-16  0:51 ` ron minnich [this message]
2023-01-16  1:59   ` Lawrence Stewart

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='CAP6exY+-pH9zUSfKvq5JjfjvM6Z4w9Ob=nm4-LQ_-jcXQ1gzUw@mail.gmail.com' \
    --to=rminnich@gmail.com \
    --cc=tuhs@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).