WinMX transfers slow down when computer idle

[cosmo9000]

Hi guys,

I'm quite new in file sharing so this puzzles me a lot.
I use WinMX on Windows XP Professional. My computer's spec is P4 2.0 GH, 256 DDRam Memory with 80GB hard drive.

Whenever I left my computer on idle while I went to sleep or out, the transfers would drop to very low like 0.3 kb per sec!
After I move the mouse 15-30 secs, the transfer would go back to as high as 50k once (normally 20-30k).

As first I thought the screensaver does this, but even after I removed it and also any power management on my computer (bios and windows), it still happens.

Any suggestion will be greatly appreciated.

:bk

[DigitalJunkie]

Are you using other programs at same time? Such as cache web pages while computer is idle, etc.

[cosmo9000]

No i don't use any other program (that I know of) that require internet connection. I made sure of that after I first notice this happened.

[DigitalJunkie]

Are you on primary or secondary connection?

[cosmo9000]

I'm on secondary connection, cause my adsl only allow 128kbps upload.

[jabba|xtra]

Have you run a virus scan lately? Do you have a firewall? If you dont have a firewall, there may be something acessing the net when the computers idle that you dont know about. Also check for viruses.

[cosmo9000]

I found this page while researching on the net:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q317751

Symptoms
Under certain circumstances, the Explorer.exe process uses an excessive number of CPU cycles when Windows is idle, and as a result, Windows performance is degraded.


Resolution
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem. This fix may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this fix.

So I guess I'll just have to wait for the service pack to be released then.

Thanks to all who have responded.