Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

A very interesting thing has come up regarding SP2 and the motherboard
industry in general. An anomaly was detected in the installation of XP SP2
on Intel 865/875 chipset mobos. After SP2 install most all such mobos from
most all mfgs would HANG on reboot.

See this post in: microsoft.public.windowsxp.general
http://www.google.com/groups?q=+%2 [...] gbl&rnum=1

An MVP there Cari had detected the issue and was pursuing it with MS and
Intel.

Current Intel CPUs have the ability to have their internal microcode updated
on the fly(addenda fixed). Apparently that microcode update is done both by
the mobo's BIOS during POST and during OS init by
%windir%\system32\drivers\update.sys.

What was determined is that MOST all the major mobo mfgs around are NOT
keeping their microcode current, at least for 865/875 chipset mobos, even
with recent BIOS updates! That old CPU microcode(non-existent BIOS
microcode update apparently in many cases[=0]) was causing SP2 to hang after
install.

One can view/report that microcode revision level by running Intel's
Frequency ID utility. The entry to look for is "CPU Revision = n" where n
>= 0 which is the microcode revision level.

Cari's conclusion as apparently gleaned from MS & Intel was that NO major
mobo mfg has been keeping their microcode(addenda) current EXCEPT Intel.
Cari claimed to have tried a broad range of 865 and 875 chipset mobos with
SP2 and most all failed! She then said that she'd never use anything except
an Intel mfged mobo again as if after her eureka moment.

Does anyone know more precise details of the overall technology involved
here and the overall industry competence with respect to CPU microcode
updates. What is the BIOS supposed to be doing here; is there any
standard? What does %windir%\system32\drivers\update.sys do exactly?

The implication is that most all of us 865/875 chipset mobo owners (and I
assume that the issue is MUCH WIDER) have been running with all the CPU
bugs/addenda UNFIXED!

Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

"Ron Reaugh" <rondashreaugh@att.net> wrote in message
newsQ9Yc.266939$OB3.244370@bgtnsc05-news.ops.worldnet.att.net...
> A very interesting thing has come up regarding SP2 and the motherboard
> industry in general. An anomaly was detected in the installation of XP
SP2
> on Intel 865/875 chipset mobos.

I FAILED to mention in my opening post that all this is only when using a
Prescott CPU.

> After SP2 install most all such mobos from
> most all mfgs would HANG on reboot.
>
> See this post in: microsoft.public.windowsxp.general
>
http://www.google.com/groups?q=+%2 [...] gbl&rnum=1
>
> An MVP there Cari had detected the issue and was pursuing it with MS and
> Intel.
>
> Current Intel CPUs have the ability to have their internal microcode
updated
> on the fly(addenda fixed). Apparently that microcode update is done both
by
> the mobo's BIOS during POST and during OS init by
> %windir%\system32\drivers\update.sys.
>
> What was determined is that MOST all the major mobo mfgs around are NOT
> keeping their microcode current, at least for 865/875 chipset mobos,
even
> with recent BIOS updates! That old CPU microcode(non-existent BIOS
> microcode update apparently in many cases[=0]) was causing SP2 to hang
after
> install.
>
> One can view/report that microcode revision level by running Intel's
> Frequency ID utility. The entry to look for is "CPU Revision = n" where n
> >= 0 which is the microcode revision level.
>
> Cari's conclusion as apparently gleaned from MS & Intel was that NO major
> mobo mfg has been keeping their microcode(addenda) current EXCEPT Intel.
> Cari claimed to have tried a broad range of 865 and 875 chipset mobos with
> SP2 and most all failed! She then said that she'd never use anything
except
> an Intel mfged mobo again as if after her eureka moment.
>
> Does anyone know more precise details of the overall technology involved
> here and the overall industry competence with respect to CPU microcode
> updates. What is the BIOS supposed to be doing here; is there any
> standard? What does %windir%\system32\drivers\update.sys do exactly?
>
> The implication is that most all of us 865/875 chipset mobo owners (and I
> assume that the issue is MUCH WIDER) have been running with all the CPU
> bugs/addenda UNFIXED!
>
>
>
>
>
>

Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

Well SP2 seems to be working fine for me. GA8KNXP motherboard, P4 3.0E
Prescott CPU, 875 chipset. Intel Processor Frequency ID says CPU revision B.

Adrian

"Ron Reaugh" <rondashreaugh@att.net> wrote in message
news:xsdYc.267959$OB3.78543@bgtnsc05-news.ops.worldnet.att.net...
>
> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> newsQ9Yc.266939$OB3.244370@bgtnsc05-news.ops.worldnet.att.net...
>> A very interesting thing has come up regarding SP2 and the motherboard
>> industry in general. An anomaly was detected in the installation of XP
> SP2
>> on Intel 865/875 chipset mobos.
>
> I FAILED to mention in my opening post that all this is only when using a
> Prescott CPU.
>
>> After SP2 install most all such mobos from
>> most all mfgs would HANG on reboot.
>>
>> See this post in: microsoft.public.windowsxp.general
>>
> http://www.google.com/groups?q=+%2 [...] gbl&rnum=1
>>
>> An MVP there Cari had detected the issue and was pursuing it with MS and
>> Intel.
>>
>> Current Intel CPUs have the ability to have their internal microcode
> updated
>> on the fly(addenda fixed). Apparently that microcode update is done both
> by
>> the mobo's BIOS during POST and during OS init by
>> %windir%\system32\drivers\update.sys.
>>
>> What was determined is that MOST all the major mobo mfgs around are NOT
>> keeping their microcode current, at least for 865/875 chipset mobos,
> even
>> with recent BIOS updates! That old CPU microcode(non-existent BIOS
>> microcode update apparently in many cases[=0]) was causing SP2 to hang
> after
>> install.
>>
>> One can view/report that microcode revision level by running Intel's
>> Frequency ID utility. The entry to look for is "CPU Revision = n" where
>> n
>> >= 0 which is the microcode revision level.
>>
>> Cari's conclusion as apparently gleaned from MS & Intel was that NO major
>> mobo mfg has been keeping their microcode(addenda) current EXCEPT Intel.
>> Cari claimed to have tried a broad range of 865 and 875 chipset mobos
>> with
>> SP2 and most all failed! She then said that she'd never use anything
> except
>> an Intel mfged mobo again as if after her eureka moment.
>>
>> Does anyone know more precise details of the overall technology involved
>> here and the overall industry competence with respect to CPU microcode
>> updates. What is the BIOS supposed to be doing here; is there any
>> standard? What does %windir%\system32\drivers\update.sys do exactly?
>>
>> The implication is that most all of us 865/875 chipset mobo owners (and I
>> assume that the issue is MUCH WIDER) have been running with all the CPU
>> bugs/addenda UNFIXED!
>>
>>
>>
>>
>>
>>
>
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004

Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

"Adrian Stuart" <adrian.stuart@nospamthanks.com> wrote in message
news:4131adc4$0$20249$cc9e4d1f@news-text.dial.pipex.com...
> Well SP2 seems to be working fine for me. GA8KNXP motherboard, P4 3.0E
> Prescott CPU, 875 chipset. Intel Processor Frequency ID says CPU revision
> B.
>
> Adrian

GA-8KNXP rev 2.1, Northwood 3.2....all works fine, though i do have some SP2
issues, one being my Zyxel USB modem, seems not to initialize properly on
occasion.

Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

Not here, I have problems with SP2 that didn't exist with SP1, in the
GA8KNXP Rev 1 mobo with P4 2.4 GB non-Prescott.

"Adrian Stuart" <adrian.stuart@nospamthanks.com> wrote in message
news:4131adc4$0$20249$cc9e4d1f@news-text.dial.pipex.com...
> Well SP2 seems to be working fine for me. GA8KNXP motherboard, P4 3.0E Prescott
> CPU, 875 chipset. Intel Processor Frequency ID says CPU revision B.
>
> Adrian
>
> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> news:xsdYc.267959$OB3.78543@bgtnsc05-news.ops.worldnet.att.net...
>>
>> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
>> newsQ9Yc.266939$OB3.244370@bgtnsc05-news.ops.worldnet.att.net...
>>> A very interesting thing has come up regarding SP2 and the motherboard
>>> industry in general. An anomaly was detected in the installation of XP
>> SP2
>>> on Intel 865/875 chipset mobos.
>>
>> I FAILED to mention in my opening post that all this is only when using a
>> Prescott CPU.
>>
>>> After SP2 install most all such mobos from
>>> most all mfgs would HANG on reboot.
>>>
>>> See this post in: microsoft.public.windowsxp.general
>>>
>> http://www.google.com/groups?q=+%2 [...] gbl&rnum=1
>>>
>>> An MVP there Cari had detected the issue and was pursuing it with MS and
>>> Intel.
>>>
>>> Current Intel CPUs have the ability to have their internal microcode
>> updated
>>> on the fly(addenda fixed). Apparently that microcode update is done both
>> by
>>> the mobo's BIOS during POST and during OS init by
>>> %windir%\system32\drivers\update.sys.
>>>
>>> What was determined is that MOST all the major mobo mfgs around are NOT
>>> keeping their microcode current, at least for 865/875 chipset mobos,
>> even
>>> with recent BIOS updates! That old CPU microcode(non-existent BIOS
>>> microcode update apparently in many cases[=0]) was causing SP2 to hang
>> after
>>> install.
>>>
>>> One can view/report that microcode revision level by running Intel's
>>> Frequency ID utility. The entry to look for is "CPU Revision = n" where n
>>> >= 0 which is the microcode revision level.
>>>
>>> Cari's conclusion as apparently gleaned from MS & Intel was that NO major
>>> mobo mfg has been keeping their microcode(addenda) current EXCEPT Intel.
>>> Cari claimed to have tried a broad range of 865 and 875 chipset mobos with
>>> SP2 and most all failed! She then said that she'd never use anything
>> except
>>> an Intel mfged mobo again as if after her eureka moment.
>>>
>>> Does anyone know more precise details of the overall technology involved
>>> here and the overall industry competence with respect to CPU microcode
>>> updates. What is the BIOS supposed to be doing here; is there any
>>> standard? What does %windir%\system32\drivers\update.sys do exactly?
>>>
>>> The implication is that most all of us 865/875 chipset mobo owners (and I
>>> assume that the issue is MUCH WIDER) have been running with all the CPU
>>> bugs/addenda UNFIXED!
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004
>

Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

"Adrian Stuart" <adrian.stuart@nospamthanks.com> wrote in message
news:4131adc4$0$20249$cc9e4d1f@news-text.dial.pipex.com...
> Well SP2 seems to be working fine for me. GA8KNXP motherboard, P4 3.0E
> Prescott CPU, 875 chipset. Intel Processor Frequency ID says CPU revision
B.

'B'...hmmm...I thought that they were 0-9 so far. What mobo BIOS version do
you have?

> Adrian
>
> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> news:xsdYc.267959$OB3.78543@bgtnsc05-news.ops.worldnet.att.net...
> >
> > "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> > newsQ9Yc.266939$OB3.244370@bgtnsc05-news.ops.worldnet.att.net...
> >> A very interesting thing has come up regarding SP2 and the motherboard
> >> industry in general. An anomaly was detected in the installation of XP
> > SP2
> >> on Intel 865/875 chipset mobos.
> >
> > I FAILED to mention in my opening post that all this is only when using
a
> > Prescott CPU.
> >
> >> After SP2 install most all such mobos from
> >> most all mfgs would HANG on reboot.
> >>
> >> See this post in: microsoft.public.windowsxp.general
> >>
> >
http://www.google.com/groups?q=+%2 [...] gbl&rnum=1
> >>
> >> An MVP there Cari had detected the issue and was pursuing it with MS
and
> >> Intel.
> >>
> >> Current Intel CPUs have the ability to have their internal microcode
> > updated
> >> on the fly(addenda fixed). Apparently that microcode update is done
both
> > by
> >> the mobo's BIOS during POST and during OS init by
> >> %windir%\system32\drivers\update.sys.
> >>
> >> What was determined is that MOST all the major mobo mfgs around are NOT
> >> keeping their microcode current, at least for 865/875 chipset mobos,
> > even
> >> with recent BIOS updates! That old CPU microcode(non-existent BIOS
> >> microcode update apparently in many cases[=0]) was causing SP2 to hang
> > after
> >> install.
> >>
> >> One can view/report that microcode revision level by running Intel's
> >> Frequency ID utility. The entry to look for is "CPU Revision = n"
where
> >> n
> >> >= 0 which is the microcode revision level.
> >>
> >> Cari's conclusion as apparently gleaned from MS & Intel was that NO
major
> >> mobo mfg has been keeping their microcode(addenda) current EXCEPT
Intel.
> >> Cari claimed to have tried a broad range of 865 and 875 chipset mobos
> >> with
> >> SP2 and most all failed! She then said that she'd never use anything
> > except
> >> an Intel mfged mobo again as if after her eureka moment.
> >>
> >> Does anyone know more precise details of the overall technology
involved
> >> here and the overall industry competence with respect to CPU microcode
> >> updates. What is the BIOS supposed to be doing here; is there any
> >> standard? What does %windir%\system32\drivers\update.sys do exactly?
> >>
> >> The implication is that most all of us 865/875 chipset mobo owners (and
I
> >> assume that the issue is MUCH WIDER) have been running with all the CPU
> >> bugs/addenda UNFIXED!
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004
>
>

Archived from groups: alt.comp.periphs.mainboard.gigabyte,alt.comp.periphs.mainboard.shuttle (More info?)

"Ron Reaugh" <rondashreaugh@att.net> wrote in message
news:HoqYc.271463$OB3.152512@bgtnsc05-news.ops.worldnet.att.net...
>
> "Adrian Stuart" <adrian.stuart@nospamthanks.com> wrote in message
> news:4131adc4$0$20249$cc9e4d1f@news-text.dial.pipex.com...
>> Well SP2 seems to be working fine for me. GA8KNXP motherboard, P4 3.0E
>> Prescott CPU, 875 chipset. Intel Processor Frequency ID says CPU revision
> B.
>
> 'B'...hmmm...I thought that they were 0-9 so far. What mobo BIOS version
> do
> you have?
>
>> Adrian
>>

BIOS is FH so I guess that makes it a revision 2 board

Adrian


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004