[Info-vax] Changed Boot behavior on XP1000 since 2013

[Hans Vlems]

On 26 jan, 15:17, VAXman-  @SendSpamHere.ORG wrote:
> In article <65d1ac8f-5248-4231-8651-fd2be3089... at 4g2000yqv.googlegroups.com>, Hans Vlems <hvl... at freenet.de> writes:
>
> >On 26 jan, 11:38, Volker Halle <volker_ha... at hotmail.com> wrote:
> >> Cross-reference:
>
> >> This issue is also being discussed in the HP Support Forums:
>
> >>http://h30499.www3.hp.com/t5/Hardware/Changes-Boot-behavior-on-XP1000...
>
> >> Volker.
>
> >It sure is, but no direction for a solution, right?
> >Or should we put a $ SET TIME command in SYSHUTDWN.COM?
>
> Just use SYS$SYSTEM:SHUTDOWN.COM to shutdown your system(s).  There's a
> $ SET TIME in there already.
>
> --
> VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG
>
> Well I speak to machines with the voice of humanity.

Well actually Brian my remark was somewhat cynical actually.
This is the first time something happened to my VMS systems which I
fear has a soluation way out of my scope.
Over the years I got to feel comfortable with several DEC built
systems. The PDP 11/44, the VAX 8650, the VAX 8550,
VAXstation 4000/90A and the AlphaServer 1200 (including its niece the
Digital Server 5305).
There are two systems I run frequently, ARGON (VAXstation 4000/90A)
and even more often OSMIUM ( Digital Server 5305).
Reliable, have them for 12 years or so and all I had to do is just
turn them on.
Now suddenly the AS1200 class machines developed a sudden urge to have
somebody else to look at the clock.

OK, for me it's just a hobby, right?
Hans