LimeWire 3.6.15 is a dog...
 

I backed up to LimeWire 3.5.8 because 3.6.15 is so VERY sloooooooooooooooooooooow.

It takes 24 hours or so to verify a 400 MB mpg, searches are super slow, just clicking on anything in general is too slow to believe. No way I can tolerate.

what do you mean "backed up to"? if it means that you are using version 3.5.8, how did you get that version? i cannot make 3.6.15 work, no matter what. i downloaded the new beta version, 3.7.1 or something, i can't remember numbers, and i still get stuck at "loading core componenets." i have a G4, 256 mg ram, aol.

Re: 3.6.15 is a dog...
 

I'm using a G3 on 9.2.2 with half a gigabyte of built-in RAM. I keep all my old versions of software on a second unmounted disk, and then if I have a problem I "back up" to a previous version. In this case I backed up to LimeWire 3.5.8, and am very impressed with it's performance over LimeWire 3.6.15...

Search speed did not change with the new version, - simply because the client has almost no influence on the search speed.

The file-verification algorithm (the algorithm to calculate the SHA-1 hash) has not been changed for more than a year.

It is slow
 

So you think I'm imagining file verification taking 24+ hours instead of 15 minutes or so, and I'm also imagining all the other sluggish responses I'm getting, such as net searches and the like. These problems don't exist with the predecessor version.

That's sure being open to problems with the software. No sense coming back for later versions, I guess.

Im using LimeWIre3.6.15 as its so slow....when i search the file then scroll window but scroll bar was stoped while Ive looking search result,but few second later,scrollbar was moving....so I couldnt adjust the mouse cursor more faster ...

Yikes, is there any way in the world I could get a copy of that version? Is it posted anywhere? The latest version doesn't work on my machine at all. Evrything is "queued" for ever...

ajskully@talk21.com

I've finally got it working great again! It was down to memory, pure and simple. I'm now allocating Minimum size at 70,000K and Preferred size at 100,000k with MRJ 2.2.5 and it's rocking.