All of the clients I have tried so far (Gnotella, Limewire, Bearshare, Fury, to mention only the ones I actually used for more than half an hour!) locked all of my system memory at a certain point (didn't USE it, they only LOCKED it!)

While Gnotella was still the most usable client (I could even manage to d/l some 600Meg+ files with it), it still wasn't possible to actually run it in the background.
The only chance to finish big d/l's was to run the client and don't touch the system anymore.

Is this something that cannot be avoided? No other application ever used that much system resources!

I might mention I have an Athlon 1000@1040, 384MB RAM and I am a power-user, I finish a Seti@home workunit in 7 hours and get 5875 points in 3DMark 2000 - and not to forget: I'm on a 10Mbit LAN connection...

the only thing i can think of is the way you have your system setup. I have an Athlon 700, 256mb ram, 40GB HD @ 26,400kb/s modem connection. The only thing that screws me over is my bandwidth. I can do anything that doesnt envolve using it and I'm fine. My system worked fine with limewire 1.3, 1.4, and 1.4b.

[This message has been edited by mpaasucks (edited 05-19-2001).]

Running under Linux and OpenBSD, I've had many gnutella clients such as Furi running for weeks at a time with no problems... Use a decent OS (anything but Windows) and your life will be easier.

Has to be the OS. I'm runiing Win98SE on a AMD K-7 with 128 megs of ram and there's no slowdowns or hangs with Bearshare... though my upload bandwidth is usually rotten-to-abysmal (but that's just my ISP being their usual jolly selves).

hm ... gnotella was actually the slowest servent i tried out so far. but even gnotella just lagged itself - it didn't lag the system though. currently i get high cpu usage only when all host connections are established from scratch. because there is so much traffic then i guess. however, what os are you running? on my 500 athlon everything is fine and i watch movies in the background and burn cd's simultanously, so something seems misconfigured.

btw, i had a broken network card once, that worked but made the whole system stand still whenever it was sending tcp/ip packets. maybe its a hardware problem?!?