Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!sol.ctr.columbia.edu!lll-winken!snll-arpagw!hilary
From: hilary@snll-arpagw.UUCP (Hilary Jones)
Newsgroups: comp.sys.mips
Subject: Help!  My clock is wandering!
Summary: I upgraded to 4.51 and can't set the date now.
Message-ID: <172@snll-arpagw.UUCP>
Date: 29 Mar 91 17:05:33 GMT
Reply-To: hilary@snll-arpagw.UUCP (Hilary Jones)
Organization: Sandia National Labs, Livermore, CA
Lines: 18

I just upgraded by RS 2030 workstation to system 4.51.  That's a
long story in itself, but I have an even more serious problem.
During the upgraded, inst complained that the date was wrong, so
I reset it.  Later when I rebooted the system, the date was wrong
again (by a couple of days).  If I use the date command to reset
the time, it doesn't "stick."  While the machine is up, it loses
time steadily, presumably trying to get back to the original date.
If I reboot, the date gets reset by a couple of days to the wrong
value again.

I have tried using the prom monitor "inittod" command, then using
the RISC/os "date" command to set the time, but it still doesn't
stick.  I think I am supposed to use the prom monitor "date"
command to reset the time, but I have no idea how to find the
value to use with this command.

Does anyone have suggestions on how to make the date stick?