From: David Kirkby on
On Jan 15, 1:26 am, Barry OGrady <god_free_jo...(a)yahoo.com> wrote:
> On Wed, 13 Jan 2010 21:29:55 -0800 (PST), David Kirkby <drkir...(a)gmail.com> wrote:
> >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.
>
> This is a quote from a forum.
> "In a hex editor (ghex2) I changed the longword at offset 4CF8 in sunpcbinary
> from 7FFFFE2E to 01000000. This replaces the call to validate_system_time
> with a nop. With this modified sunpcbinary managed to get SunPCI3 to boot
> without having to change the date."
>
> That worked for me.
>
> >dave
>
> Barry
> =====
> Home pagehttp://members.iinet.net.au/~barry.og

Thank you,