LinuxManMikeC wrote: >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 > > Yes, I'd already looked at a similar page; unfortunately it cites January 2048 - this pc gets it's date reset to December.
I've given him the two alternatives - although ntp isn't accurate enough for him, he uses a radio clock (yes, he really is that obsessive); so it's time for Norton to earn the money they've got out of him. Many Thanks, P. ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
