Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ucbvax!te.cc.cmu.edu!JM9W From: JM9W@TE.CC.CMU.EDU (Jim Murawski) Newsgroups: mod.computers.vax Subject: Bad date/time on system startup Message-ID: <8511071953.AA09039@ucbvax.berkeley.edu> Date: Thu, 7-Nov-85 13:41:47 EST Article-I.D.: ucbvax.8511071953.AA09039 Posted: Thu Nov 7 13:41:47 1985 Date-Received: Fri, 8-Nov-85 21:52:05 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 16 Approved: info-vax@ucbvax.berkeley.edu Quite a number of times in the past few weeks, when two of our VMS Vaxes have come up, the date/times have been in the future. One Vax, running VMS 3.7, has come up as 18-MAR-1986 each time it came up with a bad date; the other, running VMS 4.2, has come up as 26-MAR-1986 each time it came up with a bad date. Since one is running V3 and the other is running V4, it doesn't seem to be a V4 bug, but a hardware problem. Two other VMS Vaxes, both running V3.7, haven't shown this behavior. Has anyone else out there seen this behavior before, and if so, have you found a solution to it? Thanks for any information. -Jim Murawski -Carnegie-Mellon University -Computation Center Software P.S. Both machines in question are 780s. -------