Your clock is set in the future
in [Solaris]
|
From: Barry OGrady on 11 Jan 2010 23:56 I have a Sunblade 150 running Solaris 10 and which has a SunPCI3 card. I tried to run Windows XP on the card for the first time this year and got an error message to the effect that the date is set in the future. I discovered that it will run with the year set to 2009 but not with the year set to 2010. Is there any way to fix it so it will run with the proper date? I haven't checked the Sun website yet. Perhaps there is updated SunPCI software. =-=-= Barry http://members.iinet.net.au/~barry.og
From: Richard B. Gilbert on 12 Jan 2010 10:10 Barry OGrady wrote: > I have a Sunblade 150 running Solaris 10 and which has a SunPCI3 card. > I tried to run Windows XP on the card for the first time this year and > got an error message to the effect that the date is set in the future. > I discovered that it will run with the year set to 2009 but not with > the year set to 2010. Is there any way to fix it so it will run with > the proper date? I haven't checked the Sun website yet. Perhaps there > is updated SunPCI software. > > =-=-= > Barry > http://members.iinet.net.au/~barry.og Why are people having Y2K+10 problems? I thought that 2037 was supposed to be the next big stumbling block! Did somebody just put a band-aid on Y2K instead of fixing it?
From: Gordon Sande on 12 Jan 2010 10:34 On 2010-01-12 11:10:41 -0400, "Richard B. Gilbert" <rgilbert88(a)comcast.net> said: > Barry OGrady wrote: >> I have a Sunblade 150 running Solaris 10 and which has a SunPCI3 card. >> I tried to run Windows XP on the card for the first time this year and >> got an error message to the effect that the date is set in the future. >> I discovered that it will run with the year set to 2009 but not with >> the year set to 2010. Is there any way to fix it so it will run with >> the proper date? I haven't checked the Sun website yet. Perhaps there >> is updated SunPCI software. >> >> =-=-= >> Barry >> http://members.iinet.net.au/~barry.og > > Why are people having Y2K+10 problems? I thought that 2037 was > supposed to be the next big stumbling block! > > Did somebody just put a band-aid on Y2K instead of fixing it? Four differnt problems: 1. expected 200A but got 2010! 2. 2010 outside the possible future of 2000-2009 hardwired back in 2000 3. buggy code checking for a leapyear after 2000 problems 4. 30 bit version of Unix 2032 bug (hits on Jan 6, 2020) according to a couple minutes with Google
From: Richard B. Gilbert on 12 Jan 2010 10:49 Gordon Sande wrote: > On 2010-01-12 11:10:41 -0400, "Richard B. Gilbert" > <rgilbert88(a)comcast.net> said: > >> Barry OGrady wrote: >>> I have a Sunblade 150 running Solaris 10 and which has a SunPCI3 card. >>> I tried to run Windows XP on the card for the first time this year and >>> got an error message to the effect that the date is set in the future. >>> I discovered that it will run with the year set to 2009 but not with >>> the year set to 2010. Is there any way to fix it so it will run with >>> the proper date? I haven't checked the Sun website yet. Perhaps there >>> is updated SunPCI software. >>> >>> =-=-= >>> Barry >>> http://members.iinet.net.au/~barry.og >> >> Why are people having Y2K+10 problems? I thought that 2037 was >> supposed to be the next big stumbling block! >> >> Did somebody just put a band-aid on Y2K instead of fixing it? > > Four differnt problems: > > 1. expected 200A but got 2010! > 2. 2010 outside the possible future of 2000-2009 hardwired back in 2000 > 3. buggy code checking for a leapyear after 2000 problems > 4. 30 bit version of Unix 2032 bug (hits on Jan 6, 2020) > > according to a couple minutes with Google > Those who created such problems deserve them! Never underestimate the power of human stupidity!
From: Chris Ridd on 12 Jan 2010 10:59
On 2010-01-12 15:34:11 +0000, Gordon Sande said: > 4. 30 bit version of Unix 2032 bug (hits on Jan 6, 2020) I've not heard of that - you don't mean the 32-bit time_t rollover in 2038 do you? -- Chris |