"Standard" clock (timekeeping) software code has to have been adjusting for leap year correctly for a long time now. If this software was incorrect, it must have been because MS wrote it from scratch for this device. Now just why would MS write original software for timekeeping on this device???
And why did it happen at 2 PM? If it was local time everywhere, that makes no sense. If it was local time here, that's not even midnight GMT (UCT). Or maybe this was a bomb written by a disgruntled employee?? Fred Holmes At 04:05 PM 1/1/2009, Chris Dunford wrote: >> >> When Apple had a similar problem with the iPhone we >> >> called it "bricking" (turning our expensive toy into >> >> the equivalent of a brick) and it was not acceptable >> >> at all. We gave Apple hell. >> > >> >And you accused them of intentionally creating the glitch to sell more >> >stuff. Right? >> >> Actually, that was exactly the case. Jail broken iPhones got bricked. >> J'accuse! > >So, in that case, you're comparing an intentional and presumably permanent >bricking of hacked iPhones to an obviously unintentional and very temporary >Zune software bug? Apples, oranges. > >No matter how you slice it, your accusation that this bug was intentional is >nothing short of ludicrous. ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
