The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Bakul Shah <bakul@bitblocks.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Doug McIlroy <doug@cs.dartmouth.edu>
Subject: Re: [TUHS] Failing Memory of an Algol Based System from years ago
Date: Sat, 9 Mar 2019 15:06:34 -0500	[thread overview]
Message-ID: <CAC20D2Oa72_-oaxfyDTqTgQUkNFs3Mr=Q_XPUDqQToyxV-koHw@mail.gmail.com> (raw)
In-Reply-To: <20190309200250.BE1F0156E40C@mail.bitblocks.com>

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

Right, I had found it there right after Doug's refresh of my memory. Many
thanks to you both.

I grab a copy and put it in my own historic archives.
Clem

http://bitsavers.org/pdf/regnecentralen/RC_4000_Reference_Manual_Jun69.pdf

ᐧ

On Sat, Mar 9, 2019 at 3:03 PM Bakul Shah <bakul@bitblocks.com> wrote:

> On Sat, 09 Mar 2019 14:19:43 -0500 Doug McIlroy <doug@cs.dartmouth.edu>
> wrote:
> > Clem,
> >
> > I think the "Algol machine" you have in mind is the RC-2000 (not quite
> sure
> > of the designation--could look it up in the attic if it matters)
> designed by
> > Per Brinch Hansen for Regencentralen (again, the name may not be quite
> right).
>
> I believe he architected and wrote the OS for RC-4000.
>
> > The manual used Algol as a hardware description language.  The
> instruction
> > set was not unusual. It has come up before in TUHS. I have the manual
> > if you need more info.
>
> This manual is at bitsavers.
>

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

  reply	other threads:[~2019-03-09 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 19:19 Doug McIlroy
2019-03-09 20:02 ` Bakul Shah
2019-03-09 20:06   ` Clem Cole [this message]
2019-03-09 22:29 Nelson H. F. Beebe
2019-03-10  5:16 ` Bakul Shah
2019-03-10  4:39 Rudi Blom
2019-03-11  5:45 Rudi Blom

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='CAC20D2Oa72_-oaxfyDTqTgQUkNFs3Mr=Q_XPUDqQToyxV-koHw@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=bakul@bitblocks.com \
    --cc=doug@cs.dartmouth.edu \
    --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).