2 Jan
2018
2 Jan
'18
7:11 a.m.
I am not sure how RSX boots. Does the message give any indication where in the boot
process things go wrong?
I imagine that the boot process loads one part at a time with each part being something I
would think of as a driver. So I was wondering if there would be a way to look at the
boot blocks and say this starts with XXXXXXXX so it is for device YYYY, then the next
thing to load is AAAAAAAA and that is a ZZZZ and so on until it finally turns execution
over to $startup (or whatever the equivalent of autoexec.bat from DOS is). That sort of
thing is what I meant by mounting and examining the disk.
On the other hand might it be possible boot from another installation, attach and mount
this pack, replace the boot blocks and then boot this system? I do have a six volume set
of SYSGEN. I suppose I could make a new one.
Sent from my iPhone
On Jan 2, 2018, at 8:38 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu> wrote:
From: John
Welch
>> SAV -- SOFTWARE CONFIGURED FOR ENABLE
HARDWARE WHICH DOES NOT RESPOND.
I can boot RSX from a different device (or RT-11,
or unix maybe) and
then mount this RL02 pack and go exploring through its contents. Is
there a possibility that I may find what is missing that way?
Sorry, I'm confused by this? The message (above) seems to indicate there's
_hardware_ missing. How is looking through the disk contents going to help
with that?
Or is your point that you might be able to find a version of the system which
does not use that hardware? Perhaps; there's no way to know without looking.
Noel