Upgraded to 2.9.6 and now can't download
 

I was running 2.3.3 Basic with dial up and just upgraded to 2.9.6 Basic with DSL thinking if DSL is the way to go I would buy Pro. Now I can not download anything. I was probably having 90% success with 2.3.3 and now I have 0%. Why can I not download. I can search and select files and my files are shared but after a few seconds of trying to connect it gives me "Could not Download" on everything I try. I am running Windows 98 SE.

LimeWire doesn't go into "Requery" mode any more. It doesn't search for more alternate locations - you have to submit a new search for the filename manually and the download will restart automatically if it finds an alternate source.

Thank you, that seemed to work. Is this problem (at least I see it as a problem) alleviated in Pro?

The Pro version is almost exactly the same as the Free version (except for missing bundled software like LimeShop and whatever LimeWire is distributing with its Windows installer at the moment).

The problem was that automatic requeries by other clients were reducing the network performance. Over the last few months only a fraction of the network could be searched due to all the requeries. The communication with other gnutella developers to much more careful about sending requeries proved not very fruitful, so the LimeWire developers decided to ban requeries altogether (unfortunately including LimeWire's requeries).

Manually entered searches should return a lot more results once more users upgrade - the first effects of this new policy should already be visible.

Is getting rid of re-queries a gnutella-wide policy or just limewire?

It seems a bit cumbersome for files that are rare. You basically have to check LimeWire every 10 minutes or so and re-search. Why not just use longer intervals between re-queries?

LimeWire filters all requeries by any vendor. Queries (in the gnutella protocol) don't have a vendor tag so you cannot really identify who sent the query.

LimeWire is the first vendor to introduce this policy, but the impact will be on the whole network (not just on LimeWire's).

If LimeWire would just stop sending requeries and leave requeries by other clients untouched, the effect would be too small to measure.