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

[Hans Vlems]

On 26 jan, 04:51, David Froble <da... at tsoft-inc.com> wrote:
> Hans Vlems wrote:
> > On 25 jan, 12:12, Jan-Erik Soderholm <jan-erik.soderh... at telia.com>
> > wrote:
> >> Hans Vlems wrote 2013-01-25 11:57:
>
> >>> On 22 jan, 16:21, DaveG <davel... at gmail.com> wrote:
> >>>> On Friday, January 18, 2013 7:47:21 AM UTC-6, MichaelM wrote:
> >>>>> XP1000, VMS V7.2-1 or V7.3-2, latest Firmware V5.9-1, SYSGEN- TIMEPROMPTWAIT=65535 (default), battery ok. Since 2013 all machines booting up from "Power off" or after doing ">>> INIT" on the boot prompt stop booting and ask for the system time DD-MMM-YYYY MM:HH. IF you set the time back to 2012 they boot until login normally. All XP1000 boot normally too if power wasn't off or if no >>> INIT was given on the boot prompt. Only XP1000 are infected, our DS10 and some other alphas boot as expected. You can force the machines to boot through with another TIMEPROMPTWAIT value, but than the system time will be inaccurate (time of last boot or of last $SET TIME). It seems that any time from 2013 on is an invalid time for the processors time-of-year clock and this clock becomes important after "power off" or >>>INIT.
> >>>> I was asked for the system time (same as the others here) this morning on an Alpha 4000 after a power down restart.  I did set the date as 22-JAN-2013 and the boot continuded normally.  I thought battery too then stumbled on this thread.
> >>>> Don't recall this being a problem before 2013 rung in.
> >>> I saw this happen on a Digital Server 5305 5/533. Now this is not a
> >>> supported VMS system so I didn't do anything about it.
> >>> A reboot without a powering off the system will still get you to the
> >>> date and time prompt.
> >>> Something else that I noticed on this system: in ARC the date is set
> >>> to 24 January 2073.
> >>> The 5305 runs the last issued firmware for the 5305 and is the same
> >>> for the Alpha Server 1200.
> >>> I'll check my other systems this evening. All I can say is that my
> >>> DS20E does not show this behaviour.
> >>> Hans
> >> Same with my customers D20e's. I havn't checked but I do not
> >> expect my DS25 to ask for a date either.
>
> >> Everything right now points to some "feature" in older firmware
> >> versions where it can't handle dates that are too "new", right ?
>
> >> Jan-Erik.- Tekst uit oorspronkelijk bericht niet weergeven -
>
> >> - Tekst uit oorspronkelijk bericht weergeven -
>
> > No the date found in the ARC console today was January 25 2073
> > And the year will go as high as 2080 before it returns to 1908 again.
> > I've tried setting the value to 2013 but that isn't kept correctly.
> > 'So I'll try and set the year to 1985 and see what happens.
> > Hans
>
> Been reading this thread, and curiosity finally got to me.  So I did
> some testing.
>
> DS20, EV6, single processor, firmware V6.9 or something like that, I
> didn't write it down.  Not running for several months.  Powered it up,
> booted VMS, no date and time prompt.
>
> So, to be complete, at least for me ...
>
> AlphaServer 800, 500 MHz, don't know if that's EV5 or EV56.  Shut it
> down, powered it down, powered it up, booted VMS, and again no date and
> time prompt.
>
> That's my survey, all the AlphaStation 200s are busted  :-(
>
> Oh, VMS 8.3, if it matters ...
>
> Oh, oh, didn't try the DS10L ...
>
> Dave- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -

I didn't check my AlphaServer 800's and AlphaServer 300 yet.
The AS800 is an EV5. Does that mean that the EV56 systems are
affected?

The next question : Is there a fix / will there be a fix for these
elderly systems?

Hans