Hi Guys,
Tivo newbie here - so be gentle I've read a lot of the OzTivo and of course anything related to NZ setups to but still have a few questions, either these questions haven't been answered elsewhere or in some cases I just need a little bit of clarification.
Just to let you know what I've done since.. so I've just installed the lastest 1.4r of the oztivo iso (dated 19/4/05) on a SA 1 tivo with a turbo net card and a 40gig HD. I fixed the ip at the imaging drive stage and then altered the rc.sysinit.author file line that calls 'emuProxy' to point to the NZ emulator rather than the Oz one. But I didn't change the tclient file as it looked like it would be unnecessary.
Currently the box is at the find G/Setup stage when if does that major indexing that people say can take up to 24hrs.
I've been looking in the tvlog and have seen some fishy entries - I'd love to hear some thoughts.
Q1) Is the fact I didn't change the tclient file a mistake? I noticed that their is an entry to "dennis's emulator" but it seemed like the 127:: entry was going to use the emuProxy server setting from rc.sysinit.author.
Q2) How long have people found the final index takes? Is it on the order of 24hrs or closer to the 4hrs mentioned?
Q3) I've read in threads that you can tell when this indexing is finished by the entry "DbGcStats[158]: Outcome: eSucceeded" mean it's done? The tivo also switched itself from the main screen with options to the live t.v picture after about 20mins from when it said it was going to do the big index operation - is this an indication it is done?
Q4) I see the entry "Db[170]: RecList:GetFirstScheduledbNotFound" after the eSucceeded entry does this mean the indexing did not really succeed?
Q5) I see the entry "DbGc[158]: DbGc::HandleTriggerWhileIdle -- clock is warped -- re-marking in 300 seconds" also after the successful final indexing. But the time is correct on the box and I thought the ntp program bug had been addressed from what I read. I have seen a number of work arounds and solutions to this. Based upon this image being done with the latest release which is the appropriate solution? or does this go away after a reboot after the big indexing is done?
Q6) I haven't rebooted after the final indexing of the G/Setup as I'm not sure that it has done - the "eSucceeded" entry occured - the eSucceeded happened really quickly so I have doubted the indexing occured successfully. There a number of "time warped" and "dbnotfound" entries in the log.
Q7) I see the message "MwContext[177]: ##### OnHeartbeat(): context 6 said NOT to time out to Live TV. (idle time 15:00) #####" or similar ones refering to the heartbeat with an error type of message. What is this refering to - it is important?
I guess that's it, I'm mainly just wondering how do I tell for sure the tivo is done with the indexing and if the error messages I see in the long are important or will just disappear once I reboot post guided setup.
I also included the log file from the tivo as this might be of some use.
Thanks for your help and time.
- Nic
Bookmarks