The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Seth J. Morabito" <web@loomcom.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] ATT Hardware
Date: Fri, 29 Jun 2018 15:26:15 +0000	[thread overview]
Message-ID: <87muvdlilk.fsf@loomcom.com> (raw)
In-Reply-To: <00f101d40fab$5af29aa0$10d7cfe0$@ronnatalie.com>


ron@ronnatalie.com writes:

> The recent reference to the Dennis's comments on ATT chip production had me
> feeling nostalgic to the 3B line of computers.
> [...]

Oh I love hearing anecdotes about AT&T hardware. It should go without
saying that the 3B2, even with all its horrible flaws, is pretty special
to my heart, given all the effort I put into emulating it! I've learned
to really like the WE32000 architecture. It's just so well suited for
UNIX and C. It's a pity the clock speed was so slow, and that the
3B2/310 and 3B2/400 were so limited in memory. A 4MB maximum was not a
lot for a serious multi-user machine, even for 1985.

But, I have absolutely no experience with the 3B5 and 3B20. I would love
to hear more about them from those of you with experience. Were they
ever a marketing success? (And here, by marketing success, I mean as a
general purpose UNIX computer, not as a telephone switch)

Emulating a 3B5 or 3B20 would be fun, but I've seen even less internals
documentation about them than I have about the 3B2, so I fear it's a
hopeless task.

-Seth
--
Seth Morabito
https://loomcom.com/
web@loomcom.com

  parent reply	other threads:[~2018-06-29 15:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29 13:16 ron
2018-06-29 14:55 ` John P. Linderman
2018-06-29 15:07   ` Clem Cole
2018-06-29 16:31   ` ron
2018-06-29 17:51     ` Seth J. Morabito
2018-06-29 15:26 ` Seth J. Morabito [this message]
2018-06-29 16:29   ` ron
2018-06-29 18:48 ` Perry E. Metzger
2018-06-30 11:15 Norman Wilson
2018-07-01  2:17 ` Greg 'groggy' Lehey
2018-07-01 20:14   ` John P. Linderman
2018-07-02  0:20     ` William Corcoran
2018-07-02  0:55       ` John P. Linderman
2018-07-02  3:59         ` William Corcoran
2018-07-02 10:13       ` Kevin Bowling
2018-07-03  1:02     ` Dave Horsfall

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=87muvdlilk.fsf@loomcom.com \
    --to=web@loomcom.com \
    --cc=tuhs@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).