J
Jan Plett
I uninstalled the file-sharing program Kazaa which I had
tried for a month or so, but then, needing it again, when
I installed it a second time it worked (albeit very
slowly) but totally hogged the processor, so that
nothing else could get a look in and it could take a
minute to even get a response from a mouse click.
Although the problem seemed much to radical for such
tinkering, I adjusted the WinXP settings that
give priority to background tasks, but of course it made no difference at all.
I seem to remember I've had such problems before with other programs running on NT;
could there be a registry setting somewhere that's
allowing this to happen? Or is there likely to be
something wrong with my install of Kazaa? - it's kazaa.exe
that's hogging the processor, not the associated P2P and
spyware that goes with it.
tried for a month or so, but then, needing it again, when
I installed it a second time it worked (albeit very
slowly) but totally hogged the processor, so that
nothing else could get a look in and it could take a
minute to even get a response from a mouse click.
Although the problem seemed much to radical for such
tinkering, I adjusted the WinXP settings that
give priority to background tasks, but of course it made no difference at all.
I seem to remember I've had such problems before with other programs running on NT;
could there be a registry setting somewhere that's
allowing this to happen? Or is there likely to be
something wrong with my install of Kazaa? - it's kazaa.exe
that's hogging the processor, not the associated P2P and
spyware that goes with it.