No such problem here.
Hi All,
Strangely, my two tivos had not made a daily call since last Wednesday.
So, I forced a daily call via tivoweb on both. They both now have data, though I'm being nagged as there is less than 7 days of data remaining.
Anyone else having problems?
No such problem here.
I'll take another look tonight. Perhaps it was still indexing.
Cheers.
No problem here either...
US Philips HDR212 Series 1 Tivo, Cachecard with 512MB RAM, 320GB hard disk, OzTivo Image 1.6.2-20061109. Tivo rocks!
New Zealand
Okies.. problem my end. I probably didn't leave it long enough for indexing. Will confirm tonight.
Thanks.
Funny you should say that. I had all the same daylight savings traumas as everyone else.
I deleted everything, set the flag for GS via tivoweb and rebooted, however this didn't fix my problem. It was only when I ran the dellsources scripts that the GS would now work.
But, my tivo will no longer index. I have tried /var/hack/bin/force_index30.tcl but the last time it indexed was as part of GS.
Bit stumped really.
Spike
My seasons passes were all working when I got home. I wasn't patient enough for indexing.
Sounds like maybe you have a warped clock? Have you checked for that?
Are you seeing any guide data at all?
Something you could look at, is this URL
http://minnie.tuhs.org/twiki/bin/vie...aveNoGuideData
Zolly,
fixtivotime isn't where this FAQ says it should be, any where else it hides? My clock is warped... Seems to be catching.
Any other ways to fix this?
__________________
US Series 1 Philips TiVo
nzTiVo-Philips-Installer.img, Tivo from eBay
250Gb WD HDD, CacheCard + 512MB SDRAM
Slices: Sky Digital, Auckland, XTRA Broadband
I don't think it was included in the latest version of the oztivo image...
I've attached it... you'll need to unzip it on your PC and then ftp it to the /var/hack/bin directory on your tivo . Then type chmod 755 fixtivotime (from memory) it's been a while
David,
which version of the image are you running ?
If it's one of the r1.4's from this year it won't have fixtivotime as it should not be needed.
But there was an error with some of the early r1.4 releases where the wrong ntpdate file was used and can cause warped clocks.
check which version you have by looking in the file /etc/oztivo_version, It should have a date code. if the code is earlier than 20050419, you have the faulty file.
Download a replacement from ntpdate
Peter
Bookmarks