can run the ntpdate command again as above, then force a daily call, then post your otclient log here.
Peter.
Thanks for the suggestions. I have rebooted countless times, but the date remains at either 1938 or 2000.
[TiVo [p0] ~]# ntpdate -v 132.163.4.103
oztivo ntpdate $Revision: 1.21 $
Our postcode is 03000. Found matching timezone Australia/Melbourne
Offset 36000 for timezone EST, daylight saving is 0
Connecting to time server 132.163.4.103
Setting the local time to Wed Sep 12 12:49:41 2007
But again, as soon as a call is made, once "setting clock" is displayed, we're back to 1938.
Geoff
Thanks Peter, I'll do that. Last night I ran the guided setup again (out of frustration) but still have the same problem. Should I leave it for a while before I do as you suggest, or is it okay to do it now?
Geoff
It's been going 24 hours now, so I just did it (bad idea?).
TiVo Web doesn't actually show that the process completes, it just stops on "Loading Data... 98%, 1 min". Please find the log file attached. Thanks and regards.
Geoff
Yes. First thing I did.
Are you still using the settings from post 13 since you rebooted. If you are, enter the following commands (in red) at the putty prompt:
[TiVo [p0] ~0]# echo "ntpIP=132.163.4.103" >> /var/hack/etc/emuProxyZA.conf
[TiVo [p0] ~0]# reboot
Once your tivo is rebooting, you can close putty.
Once back up, try the ntpdate command again and then paste the results here.
Peter.
Thanks again for your generosity, Peter. Here is the result from "find . / -name ntpdate*":
[TiVo [p0] ~]# find . / -name ntpdate*
/bin/ntpdate
/bin/ntpdate.orig
Geoff
And here is the result after "echo "ntpIP=132.163.4.103" >> /var/hack/etc/emuProxyZA.conf" then "reboot"
[TiVo [p0] ~]# ntpdate -v 132.163.4.103
oztivo ntpdate $Revision: 1.21 $
Our postcode is 03000. Found matching timezone Australia/Melbourne
Offset 36000 for timezone EST, daylight saving is 0
Connecting to time server 132.163.4.103
Setting the local time to Fri Sep 14 00:53:33 2007
Regards,
Geoff
Bookmarks