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

[Steven Schweda]

Robert Jarratt wrote:

> I am trying to MOP boot standalone backup. [...]

   On what?  From what?  I'm lost.

> 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.

   As I recall, STABACKIT.COM lets you specify where to put
the kit.  [SYSE} is the default, not a mandate.  One could
also use SET FILE /ENTER to alias one directory with another.
For example, I have a Tru64-VMS dual-boot Alpha system.
Tru64 wants "a" for the boot flags, but that makes VMS try to
boot from [SYSA].  One solution:
      SET DEFAULT SYS$SYSDEVICE:[000000]
      SET FILE /ENTER = SYSA.DIR SYS0.DIR
Now it thinks it's booting from [SYSA], but anyone who looks
at [SYS0] will be happy, too.

>  When I did this I got the following error:
>
> %LAA-F-RMTNOTCLS, remote node is not a VAXcluster member

   When you did _what_, exactly?

> [...]
> 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.

   _What_ is VMS V5.4?  (Yup.  I'm lost.)

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

   If I thought that, then I'd still be trying to boot MDM off
a TK50.