Prev: enterprise 220s, 420s for parts
Next: System ACPI Power State?
From: Gordon Sande on 12 Jan 2010 12:39
On 2010-01-12 11:59:35 -0400, Chris Ridd <chrisridd(a)mac.com> said:

> 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?

Two typos! Jan 6, 2010 is 30 bit version of Unix 2038 bug. Evidently
some folks have a
30 bit clock from some (not immediately spcified or obvious) origin.

From: Richard B. Gilbert on 12 Jan 2010 14:41
Gordon Sande wrote:
> On 2010-01-12 11:59:35 -0400, Chris Ridd <chrisridd(a)mac.com> said:
>
>> 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?
>
> Two typos! Jan 6, 2010 is 30 bit version of Unix 2038 bug. Evidently
> some folks have a
> 30 bit clock from some (not immediately spcified or obvious) origin.
>

<sigh!!!!!!!>

At least one better designed system has a 64 bit clock that will not
fail till the year 30,000 or thereabouts. I don't think they allowed
for five digit years however.

As may be! Our descendants can struggle with that one a few centuries
from now.
From: Barry OGrady on 12 Jan 2010 15:30
On Tue, 12 Jan 2010 10:10:41 -0500, "Richard B. Gilbert"
<rgilbert88(a)comcast.net> wrote:

>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?

In this case it turns out that the SunPCI program does a date check.
Someone offered a fix by replacing the call to date check with a noop.

=-=-=
Barry
http://members.iinet.net.au/~barry.og
From: Martin Møller Skarbiniks Pedersen on 13 Jan 2010 19:16
Richard B. Gilbert wrote:
> 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!

It is a BCD problem.
http://en.wikipedia.org/wiki/Binary-coded_decimal

/Martin
From: David Kirkby on 14 Jan 2010 00:29
On Jan 12, 8:30 pm, Barry OGrady <god_free_jo...(a)hotmail.com> wrote:
> On Tue, 12 Jan 2010 10:10:41 -0500, "Richard B. Gilbert"
>
>
>
> <rgilber...(a)comcast.net> wrote:
> >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?
>
> In this case it turns out that the SunPCI program does a date check.
> Someone offered a fix by replacing the call to date check with a noop.
>
> =-=-=
> Barryhttp://members.iinet.net.au/~barry.og

Since you have the fix, can you share it? I happen to have one of
those cards in a Blade 2000, though since I bought an Ultra 27, I've
not used the SunPCi card and to be honest doubt I will. But I'd like
to know of a fix if there is one.

dave
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: enterprise 220s, 420s for parts
Next: System ACPI Power State?