G
Guest
Apparently MS is unwilling to deal with this problem. I have been unable to
get a response to my emails and their telephone support will not connect me
with anyone but people who say that they have no authority to resolve this
problem. If MS employees keep turning away reports of bugs in Windows, it is
no wonder that a problem can go on for months or years without a resolution.
The problem is this: a bug fix is need in order for Windows XP Pro to run on
machines with dual core processors without locking up all the time and
slowing down to the point where nothing useful can be done on them. The
average speed of my new, 2.66 Core 2 Duo system with 4 GB of RAM is slower
than the slowest processor on the market at this time with 1/8 the RAM.
This is not the "memory leak" issue, the excessive battery power issue or
the GDI "themes" bug purportedly addressed by previous MS hot fixes.
Basically, what happens is that, Windows allows any service, dll, or
application to erratically and unpredictably hog all CPU cycles so that
nothing else can happen. This results in everything freezing for as much as
10 minutes at a time. Multiply this by every instance when a piece of
software needs CPU time and you can see how this often results in more time
staring at an unmoving screen than actually getting any work done. I did not
pay over $3,000 for a new system to run slower than the slowest computer from
pre-Windows days (and far buggier).
A simple test: Open Task Manager. Then open Windows Help (click "Help and
Support") on the Start menu. When I do this on my 3-year-old Pentium 4 system
(with 1GB of RAM) CPU usage spikes to 100% for no more than a couple of
seconds. Once the Help Window has opened, it CPU usage drops to zero -- or
close to it. If I do the same thing on my dual core system (with 4 GB) of RAM
it will do essentially the same thing. But, as often as not, what will happen
is that both cores will spike at nearly 100% and stay there or keep spiking
to that point for from 5-10 minutes. During this time, both Help and
everything else is unusable. I used Windows Help for this example to
demonstrate that this problem is not limited to third party applications, or
those that use complex features such as streaming audio or video. I also want
to make the point that, if you have only one computer, you can't even get
help while this is happening.
get a response to my emails and their telephone support will not connect me
with anyone but people who say that they have no authority to resolve this
problem. If MS employees keep turning away reports of bugs in Windows, it is
no wonder that a problem can go on for months or years without a resolution.
The problem is this: a bug fix is need in order for Windows XP Pro to run on
machines with dual core processors without locking up all the time and
slowing down to the point where nothing useful can be done on them. The
average speed of my new, 2.66 Core 2 Duo system with 4 GB of RAM is slower
than the slowest processor on the market at this time with 1/8 the RAM.
This is not the "memory leak" issue, the excessive battery power issue or
the GDI "themes" bug purportedly addressed by previous MS hot fixes.
Basically, what happens is that, Windows allows any service, dll, or
application to erratically and unpredictably hog all CPU cycles so that
nothing else can happen. This results in everything freezing for as much as
10 minutes at a time. Multiply this by every instance when a piece of
software needs CPU time and you can see how this often results in more time
staring at an unmoving screen than actually getting any work done. I did not
pay over $3,000 for a new system to run slower than the slowest computer from
pre-Windows days (and far buggier).
A simple test: Open Task Manager. Then open Windows Help (click "Help and
Support") on the Start menu. When I do this on my 3-year-old Pentium 4 system
(with 1GB of RAM) CPU usage spikes to 100% for no more than a couple of
seconds. Once the Help Window has opened, it CPU usage drops to zero -- or
close to it. If I do the same thing on my dual core system (with 4 GB) of RAM
it will do essentially the same thing. But, as often as not, what will happen
is that both cores will spike at nearly 100% and stay there or keep spiking
to that point for from 5-10 minutes. During this time, both Help and
everything else is unusable. I used Windows Help for this example to
demonstrate that this problem is not limited to third party applications, or
those that use complex features such as streaming audio or video. I also want
to make the point that, if you have only one computer, you can't even get
help while this is happening.