From: Jonathan Gray <jsg@jsg.id.au>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: project athena (was Re: Setting up an X Development Environment for Mac OS)
Date: Sat, 11 Feb 2023 14:51:55 +1100 [thread overview]
Message-ID: <Y+cQ2/yG9+UWUSsg@largo.jsg.id.au> (raw)
In-Reply-To: <20230211005322.GF28037@mcvoy.com>
On Fri, Feb 10, 2023 at 04:53:22PM -0800, Larry McVoy wrote:
> On Fri, Feb 10, 2023 at 07:13:41PM -0500, Henry Mensch wrote:
> > that would have happened before I arrived in April of 1986. my first job at Athena was to. get folks off those XTs and (mostly) ATs.
> >
> > This was wildly unsuccessful and unpopular because the replacement hardware wouldn't be similarly capable... and also because, even then, there were more things that could be plugged into XTs and ATs. The old platform was perceived as more versatile.
> >
> > - Henry
>
> So the "old platform" was the National 32016 addon cards that somehow
> ran a Unix?
It seems that configuration wasn't used.
"Phase I: The off-the-shelf system
...
The closest approximation to the intended workstation environment
economically feasible on available Digital hardware at the time the
project began was minicomputer time-sharing systems. Approximately 50
VAX 11/750 minicomputers have been installed, each with six to eight
graphics-capable terminals.
...
The closest approximation to the eventual workstation configuration
available in the IBM catalog for Phase I was the PC/AT personal
computer, with a Professional Graphics Display and 3COM Ethernet
interface. Approximately 160 PC/AT's have been installed. The software
environment consists of PC/DOS, plus a set of higher level languages and
application packages chosen to simplify moving to an eventual UNIX
environment. In addition, 105 PC/XT personal computers, mostly with
Color Graphics Display, have been installed, primarily for use as
laboratory experiment controllers and also as cluster print servers for
the PC/AT's."
Evolution to the Athena Workstation Model: An Overview of the
Development Plan
http://web.mit.edu/saltzer/www/publications/athenaplan/d.pdf
>
> I'd love to learn more about that, I really liked the 320xx architecture,
> seemed like a winner but my memory is they were buggy. Still would like
> to get some idea of what it was like to run on an XT/AT with that card
> plugged in. Did you boot DOS and that somehow booted Unix or what?
>
> --lm
Multiple companies made these kinds of cards.
Some are mentioned in an ad:
https://archive.org/details/bitsavers_MiniMicroS_110087111/page/20/mode/2up
http://www.cpu-ns32k.net/Defhard.html
http://www.cpu-ns32k.net/Opus.html
http://bitsavers.org/pdf/opusSystems/32k/800-00237-000_Opus_100pm_User_Manual_1987.pdf
The DSI-32 Coprocessor Board, Part 1: The Hardware
https://archive.org/details/BYTE_Vol_10-08_1985-08_The_Amiga/page/n127/mode/2up
The DSI-32 Coprocessor Board, Part 2: The Software
https://archive.org/details/byte-magazine-1985-09/page/n103/mode/2up
next prev parent reply other threads:[~2023-02-11 3:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 1:46 [TUHS] Setting up an X Development Environment for Mac OS Will Senn
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
2023-02-08 22:12 ` [TUHS] project athena (was Re: Setting up an X Development Environment for Mac OS) Jonathan Gray
2023-02-09 2:51 ` [TUHS] " Theodore Ts'o
2023-02-11 0:13 ` Henry Mensch
2023-02-11 0:53 ` Larry McVoy
2023-02-11 3:51 ` Jonathan Gray [this message]
2023-02-11 14:48 ` Larry McVoy
2023-02-12 2:26 ` Jonathan Gray
2023-02-12 21:35 ` Henry Mensch
2023-02-11 0:23 ` Henry Mensch
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=Y+cQ2/yG9+UWUSsg@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=lm@mcvoy.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).