First, note that there is no *this* group here. The thread is crossposted to
five different newsgroups.
More important, realize two things:
1. If you're reading about problems here, this where people come with their
problems, not with their successes. You get a very distorted view of what's
going on in the real world here; as someone once said, "hang around a
transmission shop and you will think that all cars have transmission
problems."
Clown said:
That pretty clearly seems to say that one person on the planet has the
problem. (To be fair I realize clown has his head far up his A&& and
doesn't know what he is talking about)
How does what you said in any way refute what he and I originally said?
2. Most problems, by far, that people report here--whether or not they are
SP2-related--have nothing to do with defects in the software. They result
from people's ignorance, from bad or inadequate hardware, from old drivers,
from viruses, from spyware, and so on. And except for very rare situations,
they always get a fix for their problems, and in most cases, that fix is a
very simple one to implement.
I reported the same problem in detail to these newsgroups and to Microsoft
telephone technical support for most of a year. It was precisely
reproducible. Back when I was doing software professionally I would have
given my paycheck for a reproducible bug. In the end there was never a
fix for this. (Check any of the long list of postings I made to the
xp general newsgroup with all the supposed causes, all the testing of
these and that none of these ever worked if you want to see details.)
LOTS of people have reported problems with Windows Explorer, if we limit
the discussion to just the problems that SP2 caused with that. Only a
handful of causes have ever been tracked down. I suspect that a fair
proportion of the Windows Explorer causes were ever resolved.
But it is easy to blame it on the user, or the ever popular spyware
and viruses. Who can ever convince someone that isn't the case.
I reported another SP2 bug having to do with Windows Explorer corrupting
the file sort order. This was reproduced by layer after layer in India
and bumped again and again up the levels of techs. Finally it was
actually reported to Microsoft, and was never heard of again.