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: Mon, 28 Sep 2020 08:06:33 +0800	[thread overview]
Message-ID: <CAD05_j0K05B48KZE7sOmyrREKH1Ns6JsQ_+gBYu-GJa1myUM7w@mail.gmail.com> (raw)
In-Reply-To: <CAD05_j1ZBxVSvn0ByD8xi=T23NPJR1xkMFeKveooB2TZsaNR4g@mail.gmail.com>

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

Sorry, That should be 8kB (4kW) of high memory...


On Mon, 28 Sep 2020 at 08:03, Paul Riley <paul@rileyriot.com> wrote:

>
>> don't know how that board uses the SD card, in terms of where it keeps the
>> RL02 image, but if you can find that out, SD<->USB3 adaptors are cheap and
>> plentiful, and it shouldn't be too hard to load the disk image into it
>> using
>> one of them. (For the QSIC, I found a 'dd' for Winsdoze and used that to
>> write
>> the disk image onto the SD card.)
>>
>> Here's how the formatting of the SD card is done. First you partition the
> disk into n 'FAT 12" partitions, one for each drive you wish to connect.
> Then you pop the card in the emulator board, and run a utility which
> formats the partitions as "Linux" and you then have n 10.5MB Linux
> partitions. Putting the card back into your host machine, you then copy
> your RL02 disk images to the newly formatted Linux partitions.
>
> Here's the full explanation:
>
> https://www.5volts.ch/pages/rlv12/rlv12-createdisk/
>
>
>>     > I don't have any PROMs other than what would be on the '03 or '23+
>>     > boards now.
>>
>> Not a problem: if you hook up the -11's console to another computer, you
>> can download a bootstrap into it over the serial line, using the -11's
>> ODT.
>>
>
> Thanks for the tip.
>
>
>> Speaking of booting, I have Mini-Uix booting under an -11/05 simulator
>> (Ersatz-11); I used the RK image from here:
>>
>> Thanks again.
>
>
>> Oh, I recently realized how to make a  bit more room on an -11/03: most
>> DEC small QBUS memory cards allow you to use half the 'I/O page' for
>> memory,
>>
>
> Sounds beyond me, and not necessary at this stage.
>
>
>> What kind of memory card(s) do you have for the -11/03?
>>
>>
> The 256kB card is:
> M8067-KA MSV11-PK 256-kbyte MOS memory with parity CSR
>  I'll keep that for the '23+.
>
> Can you clarify something for me regarding memory? I understand the bottom
> area of memory in a Unix system is for the Kernel and it's stuff, and that
> the top 8kB is set aside for device I/O (with the exceptions you mentioned
> in a previous email about using some of that space). The LSI-11 board has
> 4kW of RAM on it, and I have already a 16KW board. If I want to further
> expand the RAM, and say I buy another 16kW board, that makes an arithmetic
> sum of 32kW for the boards, making 36kW total. Can the 4kW of on-board RAM
> be disabled, and only the 32kW on the boards be used? Is it ok for the
> installed RA mto overlap the 8kW at the high memory area? Do the devices
> spoof these addresses or do they read/write in the high installed RAM area?
>
> Paul
>

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

  reply	other threads:[~2020-09-28  0:07 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [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-27 20:50 Noel Chiappa
2020-09-29 13:20 ` 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_j0K05B48KZE7sOmyrREKH1Ns6JsQ_+gBYu-GJa1myUM7w@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).