In article <[log in to unmask]>, Craig Vespe <[log in to unmask]>
says:
>
>Hi all -
>
>   I mentioned a while back we were using SETCLOCK for year 2000 testing
>   on one of our 'crash and burn' machines.  There were quite a few
>   people using it, both developers and support people, but somehow our
>   925 got into a curious state:
>   ..............................................

I believe that particular '925 has been in a "curious state" since
1989 (or was it 1899?).  My advice: NEVER allow "developers" or
"support" people to access a '3000 (except for you and me of course).

Getting back to business, I've also been doing a lot of clock shifting
lately for the same reason--even setting the year to 2027, but so far,
nothing like this has happened.  What is the hardware clock setting
(ISL> CLKUTIL) ?  Maybe this will yield a clue as to where the problem
originates.  Maybe resetting it and also the software clock when
STARTing the system will accidently fix it.  Let us all know what
you find--since it's only a matter of time before another one of us
gets into the same fix.  Good luck ................

Winston K.
Proprietor
Cactus Technology
APR 25, 2027