Frozen Screen

[calvin and hobbes]

:shoot :tol

I've notice that when I used my mouse's center scroll wheel to navigate up/down screens in WinMx 3.1 and now in WinMx 3.2 the screen will occationally freeze up and completely lock up my computer. Nothing works, not even ctl-alt-delete. I have to physically shut down the computer. If I do nothing and wait, after about 10-15 minutes my computer will restart itself and I will lose all the information that was currently being downloaded during that sesion, unless I saved it. Now I save my files I download about once an hour to prevent losing everything.

Has anyone else had this problem? It is just a result of System Resorses drain? Perhaps scrolling puts an added drain on the System Resorse, although I find that hard to believe. Perhaps it is just a bug in the program, or unique to my machine. Obviously I don't use the scroll wheel any more, but old habits are hard to break and sometimes I forget and the problem re occurs.

I use Win 98 SE, 900 Mz, ASDL 760/128, 384 MB Ram with Ram idle running, and run WinMx w/o a firewall or antivirus.

I have unistalled and re-installed the WinMx, espescially after crashes, along with checking my System files to make sure they havne't been currupted during crashes. The problem persists.

CALVIN LIVES!!!!!

[Wolfie]

If you are low on resources try using a seconadry connection to winmx instead of a primary connection. It'll won't be as much of drain on your resources.
Other thing I would suggest look for things that might running in background which you might not be aware of (ctrl+alt+del).
Look in start up group (run msconfig) for such programs activating everytime you boot up.

[calvin and hobbes]

I do make sure (msconfig) that no other programs are running and it happens even as a secondary connection. I don't think it's a System Resorce's problem ( I monitor system resorces in my bottom toolbar). It gets down to about 50-55% for System and User, and about 75-80% for GDI). I think it might be a bug in the program.

[eclectica]

I've noticed that WPNP has been down for a week, since the release of 3.22, so I've been connecting to tons of "opennap" servers as an alternative. I attribute all these opennap connections to causing my computer to freeze up. Is this the case with you?

[Pikey]

I'm glad I found this forum ... coz I'm getting almost exactly the same problem!. WinMX 2.6 works fine .. but If I fire up 3.22 my PC is brought to a standstill almost immediately! Every second or so everything freezes, then un-freezes, then freezes and so on ad-infinitum!
I'm able to do ctrl-alt-del to bring up 'task manager' (this is WinXP pro by the way) and this reveals that cpu usage is spiking at 100%, which corresponds with the freezing.
Sometimes shutting down WinMX stops the problem, on other occasions only a re-boot will do the trick!
I'll keep experimenting with the settings and post back here if anything improves ... meantime has anyone here got any suggestions or thoughts??

[lion7718]

Try this program MaxMem, it has done wonders for me with WinMX and now the New Blubster 2.0.
It will free up needed RAM to help run & keep the program running.:upside

[calvin and hobbes]

Electra,

I do connect to as many open nap servers as i can, Sometimes as many as 20. I use NapMx and Napigator. When I log on I highlight all the servers and hit connect. I usually get 3-5 right away, and after a while that increases to between 10 and 20, although every couple of minutes the unconnected ones are tried again. Maybe I should remove some of the obvious servers and keep my number of servers I connect to limited.

Anybody out there know if connecting to( or trying to connect to) a high number of servers would cause a computer to freeze?

If so, what would be a realistic limit on servers.

By the way, Are all servers the same? I would think some are better then others as far as connection and speed, but I don't know. I would think that different servers have different CPU speed and different connections types and bandwith as well as different resources available. Maybe I'm connecting to a lousy server.

To Lion 7718: I use Ram Idle, which I'm sure does the same thing as MaxMem. I keep my available Ram at above 200 Meg.

[Pikey]

Thanks for the link lion ... but I've tried most of these 'ram improver' type proggies and don't notice any difference ... I tend to have very little running in the background (StyleXP only at the moment).
I seem to have sorted the problem by using the 'secondary connection' option as wolfie mentioned above ... seems to be working quite nicely now!

[lion7718]

I mainly use MaxMem when I download overnite, it will get back RAM in certain time frames,. I think it's 3,20 and 45 min, it will free up RAM to keep the program running all night without crashing.
As for WinMX and Blubster, sometimes I use it just to get the programs to start right. If you need RAM right away all you have to do is click the Icon in the tray.

[eclectica]

calvin and hobbes

By the way, Are all servers the same? I would think some are better then others as far as connection and speed, but I don't know. I would think that different servers have different CPU speed and different connections types and bandwith as well as different resources available. Maybe I'm connecting to a lousy server.
Most servers are either running OpenNap or SlavaNap. What I've noticed is that the OpenNap servers allow more filetypes to be shared, and have fewer restrictions. A lot of people overload their servers for the prestige of having a large database. But then what happens is that the server becomes too slow, so bigger is not better. My own estimate of the resources you need for running an OpenNap server is 1.5 KB a second uploading bandwidth reserved per 100 users, and 40 MB of memory available per 100 users.

You'll see in your attempted uploads section, that some people time out uploading (0 of xxxxxxx bytes). I usually think when I see this that it's either the server is slow, or the person has a bad firewall configuration. But if the same person succeeds on one server but fails on another, that indicates that it's the server's fault.