I used to use Limewire and share tons of files. I found that there were issues with it so I switched to Gnucleus. Gnucleus finds tons of files. I thought I'd give Lime wire a go again as I liked the interface and the new s/w 3.3.5 looks promising. Well to say I'm dissappointed is an understatement. Few files. Small files. As if there is a "cap" on file size or quantity. When I run the same search on Gnucleus, I get thousands of AVAILABLE files.

There is nowhere to add addiotional servers to allow searching alternate geographies.

I have a very fast computer and a rockin' t1 connection. Speed is not an issue and the machine is on all day. and evening.

LimeWire limits the number of search results it returns. If you search for "divx avi" your LimeWire ultrapeers will stop the search when they have returned a few hundred results. It doesn't mean there aren't more files available but you will have to do a much more specific search to locate them.

There is no limit on the file size, but usually the spam is what you get first because it's much more distributed.

Instead of searching for "divx" or "avi" try searching for "dvdrip avi" or "screener avi" that should take you to the big files.

I appreciate what you're saying re- being specific. I'm aware that Limewire is crippled in that it will only report 150 hits - however in doing a specifi search for

<1st specifier> <2nd Specifier> <3rd Specifier> and even <4th Specifier> Lime wire might select the 3rd Specifier to "key off of and get all these results that aren't really relevant, and of course that eats into the 150 hit limit. I am quite specific & and am surprised that even while staring at the file in the download window I can't find it with a search.

1) It's not possible to search the whole network, - gnutella wasn't designed to do that. (Searching 50%-80% of the gnutella network depending on the time of the day and the quality of your ultrapeer connection is about the best you can achieve with LimeWire)
2) Gnutella clients are supposed to do AND-searches. Searches for "key1 key2" should only return queryhits containing key1 AND key2. But LimeWire doesn't check this, it expects all other clients to comply with the protocol specs.
3) Busy clients cannot always be searched. Some just drop queries if they are busy (I think newer LimeWire's do the same under certain circumstances). So even if the host you are downloading from were in your search horizon you might not see any results from it.
4) The LimeWire versions 2.9.9 - 3.1.0 have a bug that keeps you from searching their leaves.

IC.

well thats a bit helpful, thanks. Doesn't really complete my searches, but it's good information. I'm running the latest 3.3.5 or whatever version of Limewire.