The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: emanuel stiebler <emu@e-bbes.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] MicroVAX architecture (was: Linux is on-topic)
Date: Sun, 19 Jul 2020 16:42:49 -0400	[thread overview]
Message-ID: <CABH=_VQLaR+su1psz0CRhPUWXs4sOYwxmZ=MnJ08kCSNN_HAQA@mail.gmail.com> (raw)

On 7/19/20, emanuel stiebler <emu@e-bbes.com> wrote:
>
> That's why DEC made also the MicroVAX. I had once a MVII/BA23 in my
> samsonite. Weird look at customs, but worked ;-)
>
By the early 1980s it was apparent that some of the more complicated
VAX instructions weren't worth the space they took up in firmware.
Especially POLY and EMOD, which turned out to be both slower and less
accurate than coding them up as subroutines.  And the PL/I and COBOL
compilers were implementing packed decimal using decimal shadowing.
Chucking out those instructions and doing them by emulation in the OS
freed up enough chip real estate to allow the remaining VAX
architecture to be implemented on a chip.  All the later VAXen
supported only the MicroVAX subset architecture in hardware/firmware.

I don't recall which was the last VAX to support the whole
architecture in hardware/firmware.  Perhaps the VAX 8200/8300
(Scorpio)?  That was a single-board implementation.  It could be
paired with a high-end Evans & Sutherland 3D graphics monitor.  DEC
tried unsuccessfully to use that combination to compete with Apollo in
the workstation market, but it was too little too late.  One reviewer
said that coupling the E&S graphics to the VAX 8200 was like
turbocharging a lawn mower.  Did Unix support that configuration, or
was it VMS-only?

-Paul W.

             reply	other threads:[~2020-07-19 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 20:42 Paul Winalski [this message]
2020-07-19 22:11 ` John Cowan

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='CABH=_VQLaR+su1psz0CRhPUWXs4sOYwxmZ=MnJ08kCSNN_HAQA@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=emu@e-bbes.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).