From: pechter@gmail.com (Bill Pechter)
Subject: [TUHS] Can't load split I&D files (in one PDP-11/23 PLUS)
Date: Thu, 25 Jun 2009 17:19:47 -0400 [thread overview]
Message-ID: <ee5521f80906251419u35800e08wafdb68e3b11403e3@mail.gmail.com> (raw)
In-Reply-To: <20090625204930.GC10610@freebie.xs4all.nl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Thu, Jun 25, 2009 at 4:49 PM, Wilko Bulte<wb at freebie.xs4all.nl> wrote:
> Quoting SPC, who wrote on Thu, Jun 25, 2009 at 08:57:47PM +0200 ..
>> Well, the matter is simple: I'm trying to install 2.11 BSD in one PDP-11/23
>> PLUS with 4MB of ram, and the 'restor' and 'icheck' utilities don't load in
>> he PDP, returning this message:
>>
>> "Can't load split I&D files"
>>
>> I tried with the diverse distributions of Vtserver and diverse versions of
>> 'restor'. In the case of the 2.9BSD this don't happen but the utility can't
>> understand what is the 'vt' device.
>>
>> Someone has encountered and solved this problem ?
>
> I could be wrong, but I think the 11/23 is not a split ID CPU?
>
> Wilko
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
IIRC -- Split I&D 11/45,11/50/11/55,11/70,11/44 and the 11/73 J11 and
11/83, 11/84, 11/94.
I think the 11/40 and the 11/34 didn't have it. I don't think the
11/60 did either.
The 11/03, 11/23 and 11/23 plus and 11/24 didn't.
Bill
--
d|i|g|i|t|a|l had it THEN. Don't you wish you could still buy it now!
pechter-at-gmail.com
next prev parent reply other threads:[~2009-06-25 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 18:57 SPC
2009-06-25 20:49 ` Wilko Bulte
2009-06-25 21:12 ` Lyle Bickley
2009-06-25 21:19 ` Bill Pechter [this message]
2009-06-25 21:31 ` Wilko Bulte
2009-06-25 21:26 ` Pete Turnbull
2009-06-25 22:17 ` Lyle Bickley
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=ee5521f80906251419u35800e08wafdb68e3b11403e3@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).