The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Riley <paul@rileyriot.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Fwd: Choice of Unix for 11/03 and 11/23+ Systems
Date: Tue, 29 Sep 2020 21:20:25 +0800	[thread overview]
Message-ID: <CAD05_j1jcV-gQBsuv8hih6f9hY9-NHW6HGCJ1i_5cObHBqCGGQ@mail.gmail.com> (raw)
In-Reply-To: <20200927205022.2D91918C0C8@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 2877 bytes --]

Noel,

Regarding the boards, the non-DEC one is the 16kW board I bought installed
in the '03, so I guess that works fine.

I managed to follow instructions for SimH and install and configure a V6
system. Was quite satisfying, and was quite an education. So many lessons
in one session, a really good exercise.

I'm checking with Peter Schranz about whether or not his RLV12/RL02 boards
can run on the '03. May be a similar issue with knobbling some of the pins,
if I'm lucky.

*Paul Riley*

Mo: +86 186 8227 8332
Email: paul@rileyriot.com



On Mon, 28 Sep 2020 at 04:51, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > From: Paul Riley
>
>     > I also have a DEC 256KB board, but I doubt I could use it on the
>     > '03.
>
> Yes, DEC 256KB boards are what's called Q22, and those don't seem to work
> with
> LSI-11's; not even CPU ODT works. I just tried a 256KB MSV11-L with an
> LSI-11,
> and it definitely doesn't work; the MSV11-P is definitely a Q22 board, and
> so
> probably also won't work.
>
> What the Q22 means is that early in the lifetime of the QBUS, it only had
> 18
> address line - so-called Q18. (Technially the LII-11 used only 16 address
> lines,
> so it's actually Q16.) DEC latter snarfed some of the 'unused' pins, and
> made them QDAL18-21. So boards that use those pins for QDAL18-21 are 'Q22'
> boards.
>
> My theory on what the problem is is that the LSI-11 uses some of those pins
> for other things - I think the 'run' light, IIRC. So that confuses Q22
> memory.
> If one tries to use one with an LSI-11, the machine is totally dead - not
> even
> ODT. It doesn't do any harm, though; unplug the Q22 memory, and plug in a
> Q18
> card like an MSV11-D, and it'll be fine.
>
> If you need memory for the LSI-11, MSV11-D boards are pretty common on
> eBait,
> for not much. They tend to be flaky, though; sometimes they come back to
> life
> if you leave them sit for a bit after you plug them in.
>
>   > I believe the [memory] board is non-DEC.
>
> Well, if it's Q22 it won't work either. Both that and the DEC board should
> work in the /23, though. (If you have the part number on the memory chips,
> a
> little arithmetic should give you the board size. 256K and up are
> generallly
> Q22; if you have a manual for that card it might say.)
>
>
> I'm still working with Mini-Unix; it's very fragile. When I got it running,
> the first thing I tried to do was changle the line editing characters
> (since
> my normal ones are burned into ROM). Alas, in stock V6, DEL is hard-wired
> to
> be 'interrupt process', so I can't just 'stty [mumble]', I have to rebuild
> the
> kernel to change that. Not a problem, necessarily - but I edited tty.h and
> said 'cc -c tty.c', and it crashed and re-started - and roached the disk.
> So
> I'm still trying to make progress. I might have mis-configured the
> simulator,
> I'll see.
>
>      Noel
>

[-- Attachment #2: Type: text/html, Size: 3898 bytes --]

  reply	other threads:[~2020-09-29 13:22 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 20:50 Noel Chiappa
2020-09-29 13:20 ` Paul Riley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-03  1:25 Noel Chiappa
2020-10-18 21:36 Norman Wilson
2020-10-12 22:43 Noel Chiappa
2020-10-12 19:27 Noel Chiappa
2020-10-10 23:29 Noel Chiappa
2020-10-11  2:30 ` Jay Logue
2020-10-11 23:24 ` Paul Riley
2020-10-12  0:53   ` Dave Horsfall
2020-10-12  1:56     ` Warner Losh
2020-10-12  2:09       ` Andrew Warkentin
2020-10-12 16:57       ` Arthur Krewat
2020-10-18 20:42     ` Michael Huff
2020-10-08 23:49 Noel Chiappa
2020-10-08 16:06 Noel Chiappa
2020-10-06 23:08 Noel Chiappa
2020-10-07  5:24 ` Jay Logue
2020-10-06 20:34 Noel Chiappa
2020-10-06 19:34 Noel Chiappa
2020-10-06 19:04 Noel Chiappa
2020-10-06 14:46 Noel Chiappa
2020-10-06 16:22 ` jay-tuhs9915
2020-10-02  0:39 Noel Chiappa
2020-10-01 12:51 Noel Chiappa
2020-10-02  0:23 ` Paul Riley
2020-09-30 23:16 Noel Chiappa
2020-09-30 18:51 Noel Chiappa
2020-09-30 17:58 Noel Chiappa
2020-09-28 23:21 Noel Chiappa
2020-09-30  1:50 ` Paul Riley
2020-09-27 21:07 Noel Chiappa
2020-09-27 21:12 ` Warner Losh
2020-09-28  0:22   ` Pete Turnbull
2020-09-25 22:08 Noel Chiappa
2020-09-26 14:52 ` John Foust
2020-09-28  0:03 ` Paul Riley
2020-09-28  0:06   ` Paul Riley
2020-09-24 18:56 Noel Chiappa
2020-09-24 13:04 Noel Chiappa
2020-09-24 18:24 ` John Cowan
2020-09-24 11:02 Paul Ruizendaal
2021-02-03  0:12 ` Greg A. Woods
2020-09-24  1:28 Noel Chiappa
2020-09-23 23:14 Noel Chiappa
2020-09-24  1:09 ` John Foust
2020-09-22 21:51 John Foust
2020-09-22 21:36 Noel Chiappa
2020-09-22 21:46 ` Warner Losh
2020-09-22 21:49 ` John Foust
2020-09-22 15:59 Noel Chiappa
2021-02-03  0:07 ` Greg A. Woods
2020-09-22  0:47 Noel Chiappa
2020-09-21 19:37 Noel Chiappa
2020-09-21 23:16 ` devin davison
2020-09-21 18:13 Noel Chiappa
2020-09-21 17:59 Noel Chiappa
2020-09-21 18:18 ` Arthur Krewat
2020-09-20 13:12 Noel Chiappa
2020-09-19 15:28 Noel Chiappa
2020-09-21 10:26 ` Paul Riley
2021-01-24 16:07 ` Tom Ivar Helbekkmo via TUHS
2021-01-25  4:58   ` Gregg Levine
2021-01-25  8:21     ` Tom Ivar Helbekkmo via TUHS
     [not found] <CAD05_j1bc6DDRtfPkd4QVeWXjwSp73bty46D=2ATozUbHThBWw@mail.gmail.com>
2020-09-19  3:22 ` Paul Riley
2020-09-19 14:20   ` Heinz Lycklama
2020-09-21 13:54     ` Paul Riley
2020-09-21 15:30       ` Heinz Lycklama
2020-09-21 23:27   ` Henry Bent
     [not found]     ` <4C35E6D2-8ABD-4DC2-BB2F-F15FA5BF30DD@icloud.com>
2020-09-22  0:22       ` Henry Bent

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=CAD05_j1jcV-gQBsuv8hih6f9hY9-NHW6HGCJ1i_5cObHBqCGGQ@mail.gmail.com \
    --to=paul@rileyriot.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).