The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: carl.lowenstein@gmail.com (Carl Lowenstein)
Subject: [TUHS] ATT 3b2
Date: Mon, 20 Feb 2006 22:28:07 -0800	[thread overview]
Message-ID: <5904d5730602202228o26dc9d68m6b302386b468d8ec@mail.gmail.com> (raw)
In-Reply-To: <dc50b0abdcf6b048b5529f34287f8bf8@plan9.bell-labs.com>

On 2/20/06, dmr at plan9.bell-labs.com <dmr at plan9.bell-labs.com> wrote:
>  > I'm interested in acquring an AT&T 3b2 computer.  One of these systems
>  > used to run a famous public UNIX system "killer".  They also run #5ess
>  > telephone switches, however the OS is different in that case
>  > (DMERT/UNIX-RTR instead of whatever the consumer-level 3b2 runs).
>
>  > If anyone has information on where to acquire these (I saw the recent
>  > discussion on 3b1s and I know they are more prolific than 3b2s-- infact
>  > a friend of mine used to have a UNIX PC which we set up a BBS on).
>
> The 3B2 was not the same machine as the one in 5ESS, which
> was/is the 3B20D, a fairly large duplexed machine (two processors
> that mutually checked each other).  The 3B2 was a desktop.
> The 3B20D wasn't sold commercially, as far as I know.  There
> was a 3B20S (multi-cabinet) that at least nominally
> was commercially available.
>
> Their ISAs were not quite the same, but some assembler language
> tricks made the assembler-level languages look quite similar.

Here at U.C. San Diego, the Electrical Engineering and Computer
Science department  received an AT&T donation of a whole lab full of
3B2 computers for instructional purposes.

I had the unenviable task of trying to teach a course based around
Assembly language and interfacing to higher-level languages (like C)
and OS functionality.  Using the 3B2, for which the official AT&T
position was that these computers were not intended to be programmed
in assembly language, and the appropriate documentation was sort of
non-existent to us outsiders.

I remember when I discovered that the assembler would generate
instructions different from those that were present in the source
code, as demonstrated by running the object-code disassembler.

    carl
--
    carl lowenstein         marine physical lab     u.c. san diego
                                                 clowenst at ucsd.edu



  parent reply	other threads:[~2006-02-21  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21  4:16 [TUHS] " dmr
2006-02-21  5:05 ` [TUHS] " Corey Lindsly
2006-02-21  6:28 ` Carl Lowenstein [this message]
2006-02-21  6:58 ` Michael Davidson
  -- strict thread matches above, loose matches on Subject: below --
2006-02-20 17:43 Stuart, Jon
2006-03-02 16:03 ` Kees Stravers

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=5904d5730602202228o26dc9d68m6b302386b468d8ec@mail.gmail.com \
    --to=carl.lowenstein@gmail.com \
    /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).