[Info-vax] Trying to boot a MicroVAX II with VMS 7.3

[Robert Jarratt]

"JF Mezei" <jfmezei.spamnot at vaxination.ca> wrote in message 
news:00186c3f$0$23337$c3e8da3 at news.astraweb.com...
> Wilm Boerhout wrote:
>
>>
>> SYSBOOT> USE DEFAULT
>>
>> This will *almost* allow you to boot /any/ VMS version on /any/
>> hardware,
>
>
> The question becomes whether the defaults will work on an 8mb All Mighty
> microvax II.  Not sure what the SPD says about MVII support for 7.3. It
> could be that 8mb is just not enough.
>
> BTW, to the original poster:
>
> There is a way to gnerate a disk based standalone backup. You could then
> change the LANCP or NCP database to point that node to the standalone
> backup hiearchy. (say you point the boot to SYS21 isntead of SYS1 and
> SYS21 contains the standalone backup).
>
> This is a much faster method than booting from a TK50 which is measured
> in hours intead of seconds.


I am trying to MOP boot standalone backup. As I am not entirely sure how to 
repoint the satellite to SYSE where the standalone backup is situated I 
renamed some directories so that the SYS10 directory which the node points 
to held the contents of SYSE. When I did this I got the following error:

%LAA-F-RMTNOTCLS, remote node is not a VAXcluster member

So presumably I have done something wrong and perhaps you can't just rename 
directories in the way I did. So the question is, how do I reconfigure the 
node in NCP? This is what NCP is telling me now:

NCP>sh node micro1 char


Node Volatile Characteristics as of 11-APR-2009 23:16:26

Remote node =   1.10 (MICRO1)

Hardware address         = 08-00-2B-04-AE-54
Tertiary loader          = SYS$SYSTEM:TERTIARY_VMB.EXE
Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE
Load Assist Parameter    = DISK$VAXVMSRL054:<SYS10.>

Do I need to just change that last parameter to point to SYSE? Or do I need 
to do something else too? Note that this is now VMS 5.4.

Thanks

Rob

PS I am beginning to strongly suspect a hardware problem with the memory.