SP2 with Intel 865 and 875 Chipsets

[Roger_Over]

I've seen a few posts by the gurus in here that refer to a known problem with those
Intel motherboard chipsets, but there were no references given. Since I'm running
the 875 with SP2, and encountering some problems (not the Blue Screen), I'd like
more info
on the nature of the problem. Will SP2 require a patch for this? Or can Intel
correct it? Could this problem be the source of my ACPI difficulties, i.e., the PC
will not powerdown after SP2 is installed (SP2 does not correctly recognize the
capabilities of
my mobo)?

 

[Carey Frisch [MVP]]

There is no problem with SP2 and Intel 865/875 chipsets. If you
experiencing a problem, it's likely your BIOS settings are not set
correctly. For example, you should turn-off the motherboard's
power-saving features and let Windows XP handle it. Also, disable
USB legacy support and use "native" support. Additionally,
plug-n-play should be disabled since XP is a plug-n-play O/S.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

---------------------------------------------------------------------------------------------

:

| I've seen a few posts by the gurus in here that refer to a known problem with those
| Intel motherboard chipsets, but there were no references given. Since I'm running
| the 875 with SP2, and encountering some problems (not the Blue Screen), I'd like
| more info
| on the nature of the problem. Will SP2 require a patch for this? Or can Intel
| correct it? Could this problem be the source of my ACPI difficulties, i.e., the PC
| will not powerdown after SP2 is installed (SP2 does not correctly recognize the
| capabilities of
| my mobo)?
|
|

 

[root]

Additionally,
plug-n-play should be disabled since XP is a plug-n-play O/S.

Do you really mean the above?

 

[Carey Frisch [MVP]]

Yes, I have a MSI 865PE Neo2 motherboard and have found
that the BIOS settings I suggested allow Windows XP to run best.
It took some time, but these new motherboards have so many
different BIOS settings, the default ones are not necessarily the best.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

 

[root]

Yes, I have a MSI 865PE Neo2 motherboard and have found
that the BIOS settings I suggested allow Windows XP to run best.
It took some time, but these new motherboards have so many
different BIOS settings, the default ones are not necessarily the best.

I see you snipped what you said. You said to disable plug and play in mobo
BIOS setup. That can't be right for XP.

 

[Cari \(MS MVP\)]

There is a potential problem if you have a Prescott CPU. However it
manifests itself by a Screen freeze after the initial install. Since you are
already running SP2 you are not among the afflicted.

 

[Cari \(MS MVP\)]

INCORRECT. See numerous postings regarding Prescott CPUs and Intel i865/i875
chipsets.

 

[Cari \(MS MVP\)]

It's correct for both XP AND 2000. It would be incorrect for 9x.

 

[root]

INCORRECT. See numerous postings regarding Prescott CPUs and Intel i865/i875
chipsets.

Exactly where? Google doesn't confirm your assertion.

 

[V Green]

Exactly where? Google doesn't confirm your assertion.

And Google is ALWAYS up to date, right?

No, of course not...

This stuff just manifested itself in the last few days.
Of course Google has no knowledge of it!

Now, if ya wanna PAY them to put it there, feel free ;-)

 

[root]

And Google is ALWAYS up to date, right?

No, of course not...

This stuff just manifested itself in the last few days.
Of course Google has no knowledge of it!

Clueless. Stuff propagates to Google in HOURS these days. Where you been?

 

[V Green]

Clueless. Stuff propagates to Google in HOURS these days. Where you been?

Only if you pay (indirectly) for it, or it's on some big commercial site.
It took almost a YEAR for a direct link
to my little piss-ant business' website to show in search results on its
name.
All that time, I was bombarded by spam that guaranteed me
that it could shorten that time...for a fee.

We're NOT talking about web site content here, just
NG postings. Google probably doesn't crawl NG
postings until they've been archived...they change too much.

Obviously, it's screwed up somewhere, cuz' the 865/875 issue
has been discussed HERE for the last four days or so, and you
just stated yourself that big G doesn't know about it...

 

[root]

We're NOT talking about web site content here, just
NG postings. Google probably doesn't crawl NG
postings until they've been archived...they change too much.

Nope, this post will be in Google Groups within hours.

Obviously, it's screwed up somewhere, cuz' the 865/875 issue
has been discussed HERE for the last four days or so, and you
just stated yourself that big G doesn't know about it...

Supply some thread titles and dates from THIS NG.

 

[V Green]

Nope, this post will be in Google Groups within hours.


Supply some thread titles and dates from THIS NG.

Look for them yourself.

You're the expert!

 

[Cari \(MS MVP\)]

I think I've done about 100+ in the last couple of days. Would you perhaps
like a list of affected motherboards? Or perhaps you'd like to come to my
house where my desktop will repro the problem every single time.

 

[root]

Look for them yourself.

I did and they aren't there and I suspect that's because they don't exist.
I've now challenged two posters on "where's the beef" on this issue and both
have abondoned the thread with NO citation.

Therefore the only logical conclusion is that somebody overheard something
in the bathroom and started a story about SP2 and 875 chipsets and then
modified the story to the even more obscure case of 875+Prescott+SP2.

Claire wants to know WHERE'S THE BEEF?

 

[root]

I think I've done about 100+ in the last couple of days. Would you perhaps
like a list of affected motherboards?
YES!

Or perhaps you'd like to come to my
house where my desktop will repro the problem every single time.

A precise description would be nice along with a citation to where it was
first reported.

A "100+" what have you done?

 

[V Green]

I did and they aren't there and I suspect that's because they don't exist.
I've now challenged two posters on "where's the beef" on this issue and both
have abondoned the thread with NO citation.

Therefore the only logical conclusion is that somebody overheard something
in the bathroom and started a story about SP2 and 875 chipsets and then
modified the story to the even more obscure case of 875+Prescott+SP2.

Claire wants to know WHERE'S THE BEEF?

You have a strange definition of "abondoned" (sic) - it seems to be that
since you have made the most recent post, all other participants
in it have "abandoned" it...

Here ya go, Google finally came through for ya...but NOT
on the recent posts here-

http://forum.msi.com.tw/thread.php?threadid=53431

although I don't know why I'm wasting my time posting
this for you, you'll just bash it anyway...likely cuz' some
of the users were still running the RC2 beta...

thes folks been reporting probs. all the way back to
06/30/2004 up till release version.

But I'm curious...why are you so rabid in your position
that SP2 should be installed, no matter what? Were you
part of the team that wrote it? If so, I can forgive your rather
one-sided approach to any criticism of it...it's partly your baby,
and you're rightly proud of it.

 

[root]

Here ya go, Google finally came through for ya...but NOT
on the recent posts here-

http://forum.msi.com.tw/thread.php?threadid=53431

But your claim was HERE. Thanks for the obscure URL.

Ok so there's a claim about a certain MSI mobo going all the way back to RC2
in June.

Is there ANY confirmation that this behavior affects any OTHER 865/875
chipset mobos??

The FACT remains that 99+% of SP2 users find it works just great.

 

[V Green]

But your claim was HERE. Thanks for the obscure URL.

Told ya you were gonna bash it ;-)

You said NOTHING, had NO criteria re: any links I
could provide, now that I've found one, you do.

I will waste NO more of my time discussing this with you.