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

[Robert Jarratt]

"Steven Schweda" <sms.antinode at gmail.com> wrote in message 
news:eee5282f-e158-4921-aef4-1294ac082e9e at f25g2000vbf.googlegroups.com...
> 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?

When I typed BOOT XQA0 on the MicroVAX II the message above appeared on the 
boot server (which is running VMS 5.4). Here is the full message:

%%%%%%%%%%%  OPCOM  11-APR-2009 22:56:30.14  %%%%%%%%%%%
Message from user DECNET on VX3900
DECnet event 0.7, aborted service request
>From node 1.9 (VX3900), 11-APR-2009 22:56:30.13
Circuit QNA-0, Line open error, File open error, Load file
%LAA-F-RMTNOTCLS, remote node is not a VAXcluster member
Node = 1.10 (MICRO1), Ethernet address = 08-00-2B-04-AE-54



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

The question here is referring to the boot server. The boot server is 
running VMS 5.4 and I have created a standalone backup kit on this machine 
(actually a SIMH 3900) which I want to make available for network booting to 
the MicroVAX II.


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

I will try again with MDM. My last attempt with it ended thus:

uVDOS V4.0 built on 21-apr-1992  12:01
**** Fatal Bugcheck, VAXELN V4.0 INVEXCEPTN, unhandled exception at elevated 
ipl
    Current Job = 00020121