On 3/22/06, Bryan Phinney <[EMAIL PROTECTED]> wrote: > On Wednesday 22 March 2006 09:53, paul wrote: > > Received a phone call from a perplexed colleague, who is using XP home > > on his desktop. > > > > His PC bios clock jumped to December, 2048 yesterday afternoon, and has > > done it 3 times since. As he is obsessional (no exaggeration) about time > > this is screwing him up. > > > > I can't explain why this would be, especially as it is happening when > > his PC is running. > > > > Any ideas? > > He might be pointing at a bad ntp server for his time updates. >
I accidentally mixed up the year 2048 with 2038 (kinda tired). 2038 is the Unix "Y2K". But in my mix up I serched for 2048 and found this page. http://www.iee.org/Policy/Areas/it/practice/problemdates/index.cfm In addition to the 2038 issue it cites two potential problems that occur in 2048. They are both "Unix" problems, but hey, M$ stole or bought out everything they make and I would be surprised if they ignored Unix. At first it just seemed wierd that it was a perfect 10 years from the Unix y2k, but the number is also a nice even binary number. Yeah, it could be a virus or bad ntp server, but could it also be M$ sneaking in through a back door to do some real world testing of their OS? :-) They could easily have that kind of control and Trusted Computing (M$) is pushing for more. I appologize if I've made everyone paranoid now. :-P ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
