Originally Posted by DrJoe
How badly have I mucked up the explanation? Please correct me!
Joe, I agree with your first three paragraphs. But I don't see how the connection to my PC running FREESCO could have clobbered your clock. You would have had to have been connected for about 46 minutes to get to the point where your replaytv got around to resolving ntp-rns.replaytv.net (the clock server), and that flow from a R3k thru FREESCO to ntp-rns' actually works and will set the clock if ntp-rns' responds. Unfortuately, my experience has been that the ntp-rns' server often doesn't respond.
I've never had a replaytv's time fall back to 1999. Sounds like a hardware problem (these devices are getting long in the tooth), and the folks at http://www.avsforum.com/avs-vb/showthread.php?t=1397340
have done a great job analysing the problem.
I think it was a wise move for you to have installed the replaytv_manual_clock_set.
As you mentioned in a previous post, having the correct (or near correct) time is essential for getting the channel guide.
I don't remember if we discussed that even with a DNS failure session, it appears to me that a replaytv can get to a replaytv channel server. My traces and PTV console messages show that it may eventually try a session with the numeric IP address of a channel server of previous success. And, unlike a cached name resolution, this "previously successful channel server address" is preserved across replaytv reboots (note, I'm using the term "channel-server" just to differentiate from replaytv's NTP server). So, you could get to updating the channel guide in a session that couldn't set the clock, but if your clock is at 1999 I believe you will still end up with an empty channel guide.
My Mom's showstopper has a full channel guide, but the time was off of what I got from us.pool.ntp.org by almost minute. I'm guessing that at least some of her sessions are the long ones that start with failed DNS and eventually get a "raw IP session".
I suggest people compare their exact time from 243 zones option 2 with a time server like D4time. If you're seeing drift, you might want to install the clock panel.
More importantly, there might now be a reasonably reliable way for people to resurrect a "lost replaytv".
1) Ensure your clock is reasonably accurate with 243-zones toggle clock on. If the time is far off, install the manual set_time panel as did Joe.
2) Connect to a FREESCO to get name resolution of the replaytv channel servers,
3) Do a "real dial" to get to the Replaytv channel servers.
I saw that "reden" offered to point his FREESCO at the Replaytv servers, and make a phone number available. That might be the easiest way to do step 2.