home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!wupost!sdd.hp.com!swrinde!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: RE-summary of VMS 5.5 upgrade
- Message-ID: <1992Jul23.231421.26876@cco.caltech.edu>
- Date: 23 Jul 92 23:14:21 GMT
- References: <9207221105.AA04617@genrad.com>,<1992Jul23.185725.27699@u.washington.edu>
- Sender: news@cco.caltech.edu
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- Organization: HST Wide Field/Planetary Camera
- Lines: 26
- Nntp-Posting-Host: sol1.gps.caltech.edu
-
- In article <1992Jul23.185725.27699@u.washington.edu>, seymour@milton.u.washington.edu (Richard Seymour) writes:
- >>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...)
-
- Well, remember, TOY stands for Time Of Year. What caused the off by one year
- problems is that the system writes the time occasionally (when it boots? When
- it shuts down? periodically?) to SYS.EXE (I think that's the right file).
- Next time you boot, the system combines the value stored in SYS.EXE and the
- information from the TOY clock to figure out what the current time, including
- the year, is. So if there's a long enough delay from the time the saveset of
- the system disk you're restoring was written and the time you restore it, you
- get the wrong year next time you boot. As far as I know, there's nothing
- analogous that could cause you to be off by one day.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-