when going in ultrapeer mode it opens up about 50 leaf connections .

I understand why this is normal , so don't start explaining me how LimeWire works .

What I need to know :

Is there anyway to change the default of 50 to for example 30 .

I have a big enough connection so bandwidht is not my problem .

The problem is that my CPU has to manage too many searches and it's making LimeWire unresponsive .

And it's not that 99% CPU time bug either that's seems to be going around and assaulting people .

I now that i'll probely need to edit the limewire.props file .

So , any ideas on how to change the maximum conection limit in Ultrapeer mode ?

Well ?

Are you sure you're not running out of free memory? My system gets unresponsive from uploads causing my Win2000 setup to dedicate all available memory to file caching. If I disable my anti-virus software (Norton 2001), the problem goes away.

I have 256MB of memory and only 117MB of files ...
How can I run out of memory ?

256 MB isn't much if you also run a lot of apps. I've got one system with 256 MB of RAM, and 36 is available. If I were to fire up LimeWire, it would take more than half of this available RAM away too (Java = memory hog).

Using WinNT/2000/XP, when LW becomes unresponsive, right click on your taskbar and open up your task manager from the menu (if "task manager" doesn't show up, make sure you're clicking on a blank area of your taskbar).

Click the "Processes" tab and search for Limewire in the "Image Name" column. Might help to sort that column by clicking on the column-header.

Once found, right click on the Limewire entry, select "Set Priority" and then "Low".

Hopefully, this gives some time back to your CPU and LW will become responsive again.

P.S.: Sometimes you may seem not to run that many apps. Only explorer shows up in your taskbar. But with the above method, you can also see how many apps are actually running in the background (services, etc.) and how much memory they take - you'd be amazed.

I already know the CPU priority trick , been running it in low priority since version 1.9

And I still have a good 10MB of memory open .
It's running on a dedicated PC together with an FTP server and I already tried to fish out and disable all unecsery programs .

Besides after I posted this I took a good look at limewire.props and figured it out myself .

I changed the parameter MAX_SHIELDED_CONNECTIONS
And now I can control the maximum leaf connections easily .
Made it 20 instead of the default of 50 and LW is now runing fine .