The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pechter@gmail.com (Bill Pechter)
Subject: [TUHS] pdp11 question
Date: Thu, 18 Nov 2010 14:26:39 -0500	[thread overview]
Message-ID: <AANLkTinBWzZxxH9c0NEk=n2UN9737YSBa-Y+XZcyapKZ@mail.gmail.com> (raw)
In-Reply-To: <1290106759.945.for-standards-violators@oclsc.org>

Actually the 11/780 and 11/785 used an 11V03.(I believe they had either 12
or 16k of memory to start and when upgrading to the 11/785 the console was
upgraded to either 16 or 28k.

  The OS was a very stripped down one.  It used an RT11 filesystem, but I
don't know if it was RT11 based.  I was told it wasn't.

The 11/750 was 8085 (IIRC) based.  The 11/730, I think, used an 8088 or 8086

The 8600/8650 used a T11 chip on a special board and ran  a version of RT11
IIRC.

The later (85xx) Vaxes often used left-over Pro350's and later Pro380's as
VAX consoles.

The biggest problem with RT11 on the Pro is they had to make the bitmap
display emulate a DEC standard terminal. (Not sure if it was VT100 or just
VT52 compatible...)

I gave away my Pro350.  They'll get my Vaxstation when they pry it from my
cold dead hands.  (Or my wife wins the argument).


Bill Pechter
been a long time since Field Circus...


On Thu, Nov 18, 2010 at 1:57 PM, Norman Wilson <norman at oclsc.org> wrote:

> Just to loop things around a bit:
>
> Some of the larger VAXes used small PDP-11s (and their
> bastard offspring) as console processors.
>
> This started with the very first VAX, the 11/780, which
> used an 11/23 as a console.  The console ran a stripped-down
> system, possibly based on RT-11 or RSX-11, I forget (and
> am typing this on a train in the Outer Mongolia part of
> Texas where it's hard to look up references).
>
> I don't know the whole list of what was used as a console
> for different VAXes, but I do remember that the Nautilus
> series (8500-8550-8700-8800) used either a Pro/350 or a
> Pro/380, running P/OS, which was slightly more satisfactory
> than the rude English non-computer expansion of PoS might
> imply, but only slightly.  Especially for those of us who
> wrote code to fit into UNIX on the VAX and talk to the
> console processor.
>
> I also vaguely remember that although Digital were
> reluctant (at least early on) to make an RT-11 that would
> run on the Pro-series systems, someone made a UNIX for
> those systems.
>
> I never knew a lot about this stuff and have forgotten much
> of what I did know, but perhaps my words will trigger others'
> memories.
>
> Norman Wilson
> Toronto ON
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20101118/61cf1199/attachment.html>


  reply	other threads:[~2010-11-18 19:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 18:57 Norman Wilson
2010-11-18 19:26 ` Bill Pechter [this message]
2010-11-18 19:27 ` Carl Lowenstein
2010-11-18 21:03   ` Wilko Bulte
2010-11-29 23:05   ` Ian King
  -- strict thread matches above, loose matches on Subject: below --
2010-11-14  0:38 Tim Newsham
2010-11-14  1:03 ` Larry McVoy
2010-11-14  1:59   ` Warner Losh
2010-11-14  2:43     ` Pasquale Villani
2010-11-14  7:08     ` Greg 'groggy' Lehey
2010-11-14  9:56       ` Wilko Bulte
2010-11-17 23:36         ` Pete Turnbull
2010-11-14 22:22       ` Nick Downing
2010-11-15  0:17         ` Larry McVoy
2010-11-14  9:51     ` Wilko Bulte
2010-11-18  6:34       ` Lars Brinkhoff
2010-11-14 12:32     ` Pete Turnbull
2010-11-14  8:14 ` Jochen Kunz
2010-11-14 14:01 ` Pat Villani

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='AANLkTinBWzZxxH9c0NEk=n2UN9737YSBa-Y+XZcyapKZ@mail.gmail.com' \
    --to=pechter@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).