WINMX SLOWING VISTA DOWN TO SNAILS PACE

[e160877]

When I run Winmx, Vista slows down to a snails pace and once you click on something, it can take 20 seconds for that program to come up.  Winmx connects but it will be extremely slow to show anything, to the point where it's unbearable.  For example, you will see it's been connected for 1min and then the timer will stop, then the next time you see the timer go it will be 1min 25 secs then it will go for a few more seconds and freeze again.

Details:

Vista Home Premium (clean install)
Counterspy
Zonealarm
NOD32

I have tried stopping counterspy and zonealarm, have tried different versions and patches for Winmx to no avail.  This is driving me crazy!!

[reef]

Are you running WinMX as a Primary? If so,have you tried Secondary?   

Also you mention you've tried different versions and patches.If you are
on Primary you should make sure your running the latest patch from

https://www.winmxworld.com/tutorials/connection.html

[e160877]

I should have mentioned that I have it running as a secondary as I only have dial-up.  It used to work perfectly on WinXP, but not now......

[Bearded Blunder]

ZoneAlarm is known to cause issues with winmx on some systems.. try with it uninstalled (vista's native firewall is perfectly adequate in any case)

[ñòóKýçrÕôK]

Another thing you may wish to try is changing the compatibility of winmx.exe in your WinMX folder to Windows XP compatibility byright clicking the winmx.exe and clicking properties. If it isn't changed to that already, the slowing could be Vista trying to deal with the exe and the dll file in a way that WinMX doens't know it's supposed to dealt with. If it's available do a properties on OLEDLG.dll also and check compatibility on that. I only got to run Vista for a day or so on a dual boot setup to see how well Vista would do before unfortunately it had screwed with my XP install making it troublesome, but when I installed WinMX on the Vista system I also set the compatibility of the installer to Windows XP and it installed fine and connected fine. Only issue I seemed to have would be just dropping connection.

[e160877]

I've tried running it under different compatibilities with no luck, but I didn't try it on the .DLL file.  Will try this, along with uninstalling Zonealarm, and let you know how I go.  Stay tuned for updates.........

[]-[êll.Ôñ.ËÀR'][']-[.]

no need to uninstall it to see just turn it off then try winmx

[e160877]

Already tried just turning off, so I uninstalled it, then tried different compatibility modes and still no luck.  Beginning to think it's a lost cause.  Goes normal speed when installing but when it gets to the connection stage, and even after connection, the whole system just trawls along.  I checked in task manager and it appears to use anywhere between 15 - 20 Mb or resources.  Is that correct?  Doesn't seem right for such a small program.

[SamSeeSam]

If you are on primary, then I think that is normal, Try a secondary connection and see if it helps....

Cheers

[Bearded Blunder]

if your whole system is slowing try looking in task manager if some app is using tonns of cpu & which one

[e160877]

Obviously people aren't reading my previous posts.

1.  I'm using Secondary, not primary

2.  Yes there is an app using lots of CPU, it's called Winmx.  It's using between 15 - 20 mb

[Bearded Blunder]

obviously you aren't reading the replies carefully  either CPU usage would be expressed in % of CPU time MB is memory usage & the amount quoted wouldn't be unusual, or a problem on any modern system...

sometimes security software will go nuts with p2p software running, hence me asking you to look for processes with high CPU usage (not memory)..

also being dialup it may be worth you visiting the bandwidth script page, things going too fast can saturate the limited connection & slow ie in particular way down... dialup users are some of the few where throttling incoming as well as outgoing bandwidth can help, in both cases around 80% of available should do

[e160877]

Thanks, I've found the culprit.  I disabled the active protection part of Counterspy which seems to have done the trick.  Winmx was making the Scan Service part of this program go nuts.  Thanks for the help, it was the CPU monitor that gave it away.