Re: xp sp2 download, computer won't boot up now
From: Ron Reaugh (rondashreaugh_at_att.net)
Date: 09/05/04
- Next message: Ron Reaugh: "Re: sp2 is a certified killer"
- Previous message: George: "Windows Update Access Problem"
- In reply to: cquirke (MVP Win9x): "Re: xp sp2 download, computer won't boot up now"
- Next in thread: cquirke (MVP Win9x): "Re: xp sp2 download, computer won't boot up now"
- Reply: cquirke (MVP Win9x): "Re: xp sp2 download, computer won't boot up now"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 05 Sep 2004 00:23:02 GMT
"cquirke (MVP Win9x)" <cquirkenews@nospam.mvps.org> wrote in message
news:koejj09e34ji9apnsric8tbcd85r2f5c48@4ax.com...
> On Tue, 31 Aug 2004 21:53:00 GMT, "Ron Reaugh" <rondashreaugh@att.net>
>
> >Why is the temp fix to rename update.sys?
>
> Update.sys is the driver file that locks up when XP SP2 boots on a
> system that has Prescott processor running < revision 8 or 7.
>
> Just why that happens - i.e. what SP2's larger Update.sys is doing
> that older SP1a's Update.sys doesn't do - remains a mystery to me.
What does either/both update.sys's job?? I was under the impression that
update.sys loads microcode into processors. Is that true?
> >When can we expect a hotfix from MS for SP2's update.sys?
>
> Not sure if that is the path the resolution will take. Update.sys may
> just be the tip of the iceberg here; the real problem is within
> Intel's Prescott itself - i.e. that unless it has been updated by BIOS
> on Intel's behalf, it doesn't work properly.
I thought update.sys DID update microcode on CPUs. Nicht wahr?
> >A buggy SP2 update.sys with respect to the Prescott seems to
> >be what's really behind this whole issue, right?
>
> Not really - it certainly brings to light the difference between
> Prescott as-shipped and Prescott as patched by BIOS to revision 7
> microcode (steppings 2, 3 aka C0) or 8 (stepping 4 aka D0).
That assumes facts NOT in evidence and in fact assumes facts that you
already said you didn't know. It does bring what you simply say above but
what you simply say above was in response to my question: "A buggy SP2
update.sys with respect to the Prescott seems to be what's really behind
this whole issue, right?"
> One of the things SP2 includes is DirectX 9c, and one of the things
> DirectX 9C offers is the third revision of pixel shaders. This new
> revision uses floating point, which may benefit from Prescott's new
> SIMD3 instructions, if these are available.
>
> Now we get to pure guesswork on my part!
>
> It may be that SIMD3 is buggy at microcode revisions below 7
> (steppings 2, 3 aka C0) and 8 (stepping 4 aka D0), and this may be
> what crashes Update.sys if the latter is trying to ascertain whether
> SIMD3 support exists (so it can path DirectX to use it).
And your guesswork clearly describes a buggy update.sys. The issue of
SP2+Prescott was known/reported in June in RC2 if not BEFORE.
> End of guesswork part. The definitive fix is to get a BIOS that
> updates Prescott's microcode revision.
Shouldn't update.sys load the correct microcode version.
> If your mobo vendor didn't
> have a suitable BIOS revision last week, look again - you may see
> changes RSN. In my case, Jetway hatched BIOS 05 1 Sep 2004.
What's update.sys's job???
- Next message: Ron Reaugh: "Re: sp2 is a certified killer"
- Previous message: George: "Windows Update Access Problem"
- In reply to: cquirke (MVP Win9x): "Re: xp sp2 download, computer won't boot up now"
- Next in thread: cquirke (MVP Win9x): "Re: xp sp2 download, computer won't boot up now"
- Reply: cquirke (MVP Win9x): "Re: xp sp2 download, computer won't boot up now"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
