home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!henson!news.u.washington.edu!milton.u.washington.edu!seymour
- From: seymour@milton.u.washington.edu (Richard Seymour)
- Newsgroups: comp.os.vms
- Subject: Re: RE-summary of VMS 5.5 upgrade
- Message-ID: <1992Jul23.185725.27699@u.washington.edu>
- Date: 23 Jul 92 18:57:25 GMT
- Article-I.D.: u.1992Jul23.185725.27699
- References: <9207221105.AA04617@genrad.com>
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington, Seattle
- Lines: 21
-
- In article <9207221105.AA04617@genrad.com> dongray@cdclu1.genrad.com (Derek Dongray) writes:
- >> 1.) TOD clock was set ahead? (I think it was ahead) by about 1 day.
- >> Don't create any files or change anything until you check this
- >> out.
- >I had this happen to my system too ... which was a *real* PITA because the node
- ...
- >What I'd like to know is why the upgrade (V5.4-2 -> A5.5) changed the clock at
- >all?
-
- ?because it's historical? MANY major (but few minor) upgrades have kiboshed
- the TOY... i think it was v2.x-->v3.0 which did a 1-YEAR set-ahead...
- (so you look at the output, and it reads right-day_right-month_ and you don't
- notice that the last digit of the year is off... until things go weird...)
-
- Some of the mis-settings were due to the way VMS and the VAX keep their clocks.
- On the 780 it looked like the hardware was supplying the lower 32 bits, but
- the software was supplying the upper... hence if the hardware zeroed, you'd
- end up up to 4 billion 100-nanosecond units off...
- On microVAX II and III's, the HALT button freezes the hardware clock, too...
- so prolonged life in the >>> lane would drift the clock....
- --dick
-