correcting the time

[Alistair]

Can somebody point me to an idiot's guide to setting the time. I can telnet into the TiVo using hyperterminal but then any instructions I try come back with bad command or unknown command.

I am completely new to TiVo and had it working fine until the daylight savings change. I have not managed to get it to the right time since. Even after its daily telephone call it remains wrong - so I presume there is no time update in this process.

[Wanted]

Did you try Wibbles' comment here?

http://forums.oztivo.net/showthread.php?t=1638

The Auckland file needs replacing and needs a reboot after that. What Wibble said is basically what worked for me.

[Alistair]

I tried that and got the following:

TiVo [p0] ~]# cp -p /var/hack/zoneinfo/Pacific/Auckland timezone-backup/
cp: /var/hack/zoneinfo/Pacific/Auckland: No such file or directory
[TiVo [p0] ~]# wget ftp://210.48.107.133/install/Auckland.zip
--11:09:27-- ftp://210.48.107.133/install/Auckland.zip
=> `Auckland.zip'
Connecting to 210.48.107.133:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /install ... done.
==> PORT ... done. ==> RETR Auckland.zip ... done.
Length: 800 (unauthoritative)

100%[====================================>] 800 390.62K/s

11:09:28 (390.62 KB/s) - `Auckland.zip' saved [800]

[TiVo [p0] ~]# cp Auckland /var/hack/zoneinfo/Pacific/
cp: Auckland: No such file or directory
[TiVo [p0] ~]# cp Auckland /var/hack/zoneinfo/Pacific/
cp: Auckland: No such file or directory
[TiVo [p0] ~]# ls -la /var/hack/zoneinfo/Pacific/Auckland
ls: /var/hack/zoneinfo/Pacific/Auckland: No such file or directory
[TiVo [p0] ~]#
[TiVo [p0] ~]#

Obviously something more basic is amiss - any idea anyone?

[catdog]

you missed a line in the instructions (in bold below)

#Get the update
wget ftp://210.48.107.133/install/Auckland.zip

unzip Auckland.zip
cp Auckland /var/hack/zoneinfo/Pacific/

[Alistair]

OK. So I missed a line. I have the right responses now - shouldn,t be so quick to shout for help. The time is right now, but the date is wrong and the program that it thinks is playing does not move on.

[Alistair]

Now the TiVo won't play live TV at all after rebooting again. So its back to square one - rip it out and reconnect it when I haven't got a house full of kids wanting to watch TV. Anybody got ant ideas?

[Wanted]

If nobody has any more informed ideas you can do a clear episode guide data and to do list. Just back up your season passes etc or write them down to put back afterwards. I had some problems with a few channels being wrong after the change and that fixed it.

Just run it from the menu, force a daily call, I left it overnight after that and then I ran a force index the next day when it seemed slow to get some of the data. If I remember rightly you don't loose any recorded shows but obviously do it when theres not much to record.

[Alistair]

I've done that, although the TiVo won't let me drive a phone call from the on screen menus and I have to do it from the computer. I also notice that if I change from PAL to NTSC I can't watch live TV at all. All very strange as it still thinks it is last Saturday althouhg the time is right. Here is something intersting as well. If I go to "Info" this is what appears:

INTERNAL SERVER ERROR
--cut here--
action_info '/' ''
Invalid /Schedule format: ''
while executing
"error "Invalid /Schedule format: '[lindex $schedlist 1]'""
("uplevel" body line 30)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 5)
invoked from within
"RetryTransaction {
set state [db $db open "/State/MyWorld"]
set channel [dbobj $state get LastChannel]
set chnum [dbobj $c..."
(procedure "::action_info" line 15)
invoked from within
"::action_$action $chan $part $env"
("eval" body line 1)
invoked from within
"eval {::action_$action $chan $part $env}"
--cut here--

H'mm doesn't sound too promising.

[Alistair]

OK, so I set the time manually by using 'settime YYYYMMDDHHMMSS' and then rebooting. Currently all seems to be working - but does anyone know if this will bring issues next time I try to do a daylight savings time?