Incorrect time

[Wibble]

Unfortunately my TiVo still doesn't have the right time.
Tony

Could you try the command from this thread and post the result.
http://forums.oztivo.net/showthread....t-time-on-tivo

[jumbophut]

Could you try the command from this thread and post the result.
http://forums.oztivo.net/showthread....t-time-on-tivo

[TiVo [p1] ~]# /bin/ntpdate -b -v 210.48.107.133
[TiVo [p1] ~]# Time set to: Mon Mar 29 21:40:42 2010
Have a nice day.

It is actually the right time. However, when I plug the TiVo back into the TV (and with no further connection to the Internet) it tells me in system information that the time is 10.40pm.

It doesn't mention postcodes at all (possibly because I'm running 2.5.5 Thomson image?).

However:

[TiVo [p1] /hack/bin]# ./get_postalcode
02124

And

[TiVo [p1] /hack/bin]# cat /etc/postcodezones
...
02124 Pacific/Auckland

So that should all be fine.

While poking around, I did notice /hack/bin/set_NZ_Timezone_DaylightSayingsPolicy (yes, with a 'y'), which contains:

dbsetx /Setup TimeZone 0
dbsetx /Setup DaylightSavingsPolicy 0

If that's being run somewhere, would it make a difference?

[Skolink]

While poking around, I did notice /hack/bin/set_NZ_Timezone_DaylightSayingsPolicy (yes, with a 'y'), which contains:

Heh, must have been the same person that spelt 'RecieverNumDigits'. I don't seem to have that script, but then I'm running a US TiVo with the ozTiVo 1.6.2 image and updated from oztivo.net.
Also, the time on mine is correct.
If you haven't fixed it by Sunday it will probably come right,and you will have to wait another year to fix it.

If it is any help, http://IPaddress/mfs/State/LocationConfig contains
LocationConfig 2278/10 {
Version = 122
PostalCode = 02112
TimeZoneOld = 7
DaylightSavingsPolicy = 0
IndexPath = /State/LocationConfig
}

[catdog]

[TiVo [p1] ~]# /bin/ntpdate -b -v 210.48.107.133
[TiVo [p1] ~]# Time set to: Mon Mar 29 21:40:42 2010
Have a nice day.

...

It doesn't mention postcodes at all (possibly because I'm running 2.5.5 Thomson image?).

From memory, ntpdate is just a symbolic link to fixtivotime on the UK2.5.5 image. The easiest solution is to replace it with the newer version used on the US image. Pete posted a version here a while back:

http://forums.oztivo.net/showthread....0702#post10702

However:

[TiVo [p1] /hack/bin]# ./get_postalcode
02124

And

[TiVo [p1] /hack/bin]# cat /etc/postcodezones
...
02124 Pacific/Auckland

So that should all be fine.

Yep, that looks good. The blank space between 02124 and Pacific *must* be a tab (i.e. not a bunch of spaces), and there *must* be a new line character at the end of the line.

While poking around, I did notice /hack/bin/set_NZ_Timezone_DaylightSayingsPolicy (yes, with a 'y'), which contains:

dbsetx /Setup TimeZone 0
dbsetx /Setup DaylightSavingsPolicy 0

If that's being run somewhere, would it make a difference?

Can you please check "http://IPaddress/mfs/Setup" to make sure the TimeZone and DaylightSavingsPolicy are actually in there. This is what Skolink was trying to show you, but the settings are in a different location on the UK tivo! If those two variables don't exist then you'll need to manually run "set_NZ_Timezone..." to set them. (This only needs to be done once).

Heh, must have been the same person that spelt 'RecieverNumDigits'. I don't seem to have that script, but then I'm running a US TiVo with the ozTiVo 1.6.2 image and updated from oztivo.net.

I don't have that script either and I'm running a UK2.5.5 image! That spelling mistake must have been from a local addition on the latest release of the image!

[jumbophut]

Can you please check "http://IPaddress/mfs/Setup" to make sure the TimeZone and DaylightSavingsPolicy are actually in there. This is what Skolink was trying to show you, but the settings are in a different location on the UK tivo! If those two variables don't exist then you'll need to manually run "set_NZ_Timezone..." to set them. (This only needs to be done once).

I checked and they weren't there. Running "set_NZ_Timezone..." as you suggested has put them in and the time now seems correct on the TiVo. The next test will be a daily call, but hopefully all is fixed now.

Thanks for all your help.