Ernie writes:

> P.S. When I set the correct date/time with CLKUTIL and start from
>  ISL, reply "N" to the prompt for the software clock, put in the 
>  correct date/time the system hangs.

A system "hang" was my impression too when I first tried to change a wildly 
incorrect date during an ISL boot entry, but I now believe that all that it is 
doing is using the GRADUAL option to change the clock, which runs at about 
twice normal speed. Thus, if your clock is 30 days off, it's my prediction that 
the boot process will complete in about 15 days from now, if you don't mind 
waiting that long.

I'm not absolutely sure about this. I'm only sure enough about it to mention 
it as my leading hypothesis for why the machine simply goes away when you try 
to correct a significantly-in-error time at bootup. But if it's so, I can't 
imagine why anyone would have thought that it would have been a good idea to 
change the time gradually. It's perfectly obvious that the machine isn't running 
any scheduled jobs during bootup.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *