JessZahn:Yeah, so, "invalid time" is a strange message, but you get the point, right: for content that you're only allowed to have a copy of for a particular amount of time - whether it be CGMS-A protected content or a movie you downloaded from Movielink or whatever - if you reset your clock while you have that content, our software is going to think you're trying to subvert the CP rules.
Syncing your clock, though, seems like it shouldn't result in a significant enough change to cause the error message to show up. How far off was the clock anyway when it went to sync?
Mine syncs every 2 hours, as follows:
12/06/2007 12:37:46 AM: Time Synchronized to Host 'bonehed.lcs.mit.edu' : -0.161 (0062).
12/06/2007 02:37:46 AM: Time Synchronized to Host 'bonehed.lcs.mit.edu' : -0.199 (0062).
12/06/2007 04:37:46 AM: Time Synchronized to Host 'bonehed.lcs.mit.edu' : -0.193 (0062).
12/06/2007 06:37:45 AM: Time Synchronized to Host 'bonehed.lcs.mit.edu' : -0.336 (0062).
12/06/2007 08:37:45 AM: Time Synchronized to Host 'bonehed.lcs.mit.edu' : -0.195 (0062).
12/06/2007 10:37:45 AM: Time Synchronized to Host 'bonehed.lcs.mit.edu' : -0.195 (0062).
It seems to me it had something to do with the buffer, if you weren't behind a bit then maybe it wouldn't fire. IF you are were watching the buffer (like you pressed pause for a minute to go pee), every time it would sync, it would fire the blue screen.
Just a note on this, I use a 3rd party time sync app, as appears the other poster. I don't use any of the windows ones, and it is entirely possible this doesn't affect systems with do not use 3rd party time sync applications.
Now - the dumb thing. This seems to only be applied to "copy never" content. At least here, since the only two flags we get is "copy never" or no restriction at all.
Since you can't record the stupid show anyway, this appears to be "leftover" code from pre-RU2 when you still could record it. It's kinda crazy to apply the "don't subvert CP rules" to the timeshift buffer.