Originally Posted by ETGorm
For about two weeks, my time in DC was accurate. Just yesterday, I noticed that it was slow by about 5 minutes. I did a soft reboot around 10 pm that night and the new time was accurate. Today, the time was slow again by about 3 minutes.
THE AUSTIN SHUFFLE
You have duplicated the Austin experiment. In Austin, they used TSReader software to examine the broadcast time-stamps. Most times-tamps were skewed, but a few were dead-on. When they rebooted the Pal to coincide with a perfect time-stamp, the PAL clock corrected. A few hours later, the clock skewed again.
Here's a possible scenario:
You rebooted at 10pm. This forced the PAL to seek the TV Guide clock broadcast which was accurate, so the PAL clock corrected. The Pal checked the broadcast time again at 11pm, 12am, 1am, and 2am. At about 1am the TV Guide program listings started broadcasting which delayed the time-stamps. (In Austin, they assume the stamps were buffered because of a shortage of bandwidth). After the 5 time samples were collected, your PAL made its final clock adjustment (which resulted in a skew of -3 minutes).
GUYS! Let's stop with the 6pm-7pm magic time reset. That worked for a while in Austin and it seems to be ok in DC--for now. No one on this thread reported success restoring their clock at that hour during the original DC time skew crisis. In fact, J-D-H and I reported the opposite: a 6:30pm reset only lessened the skew. My successful clock resets occurred after 7pm and continue to maintain the correct time.
Based on my experiences: Reset your PAL at 7:10pm (maybe 7pm-8pm) by doing one
of the following:
1. A zip code toggle,
2. Deleting, then adding the TV Guide broadcast station.
3. A reboot (hard or soft),
4. A full channel scan,
Leave the update disabled. The Pal seems to repeat the time scan during the same period each day (according to the time of your reset) so, if nothing else goes wrong, you'll be ok. (And avoid anything that triggers a clock reset at the wrong time of day).