Melissamusic wrote:
Please forgive my ignorance, were is it getting an illogical time/date stamp?
KarboMusic wrote:
Melissamusic wrote:
KarboMusic wrote:
Melissamusic wrote:
I agree. Why would the Zune Player care what time or what day it is without any way to check the correct time? I would understand that the device could fail if there were a conflict in the times if connected to a computer but for it to fail on its own sounds kind of fishy. I think M$ is just buying themselves some time to come up with a fix.
Believe it or not... There was a time when a device could contain an internal clock all by itself... Thats not fishy...
So it has an internal clock, so if that clock is wrong then it would just show the wrong time. not crash a system.
Not really, if a single line of code attempts an operation (dealing with dates/timestamps) and gets back a time/date that isn't "logical" there is going to be an unexpected result. (IE: Freeze)
I'll try once more...
There could be hundreds if not thousands of functions in the zune code and drivers that reference times and dates. It may be last modified timestamps on files, driver version times/dates, DRM, security, the list goes on and on.
It only takes a single "operation" where a conversion, comparison etc. says "take the current time date and compare it to ____". When the code does this and there is suddenly a date that it doesn't expect to be possible, you have an error. Yes its simple to add code to prevent the freeze (could have been missed) but the scenario is completely plausible, more than plausible, its now a reality.
