LimeWire 3.1.0 Beta
 

We've released the LimeWire 3.1.0 Beta. This version dramatically improves the success rates for firewalled search results -- those search results will work a much higher percentage of the time.

This change relies on the firewalled hosts on the network returning results in the new format, though, so the more people who start using 3.1.0, the more reliable search results will become.

The free beta is available at:

http://www.limewire.com/index.jsp/download_beta

and the pro beta is available from your pro download page.

Many thanks.

-The LimeWire Team

thanks! that's great news.

i am wondering:

do these search result improvements apply for both firewalls with port forwarding on and off?

also: if i understand correctly, that means that firewalled hosts will get more search results and consequently more downloads. however, they still can't upload to other firewalled hosts. isn't this amplifying the (forced) leeching status of firewalled hosts (w/port forwarding off)?

Sweet. Sounds great. I dled Jum's build of it, seems to be running fine, to soon to tell tho.

adam, or anyone: I'm having big problems connecting after a clean install (a few uploads are going through), even after letting it run all night with a direct connection to the internet. I tried reverting to older versions and the usual troubleshooting.
I'm trying on a different computer next.

Is the gnutella.net file the only one that supplies and stores the IP's , or are those retrieved from some other system file too?

Did anything change in the code that would make connections so difficult?

The gnutella.net file is the only one that stores IPs of gnutella servents. - However, there are some hardcoded GWebCache addresses that should get you connected even after deleting the gnutella.net file.

Don't you get any connections at all with the new version? But uploads work?

What OS are you running on again Stief? We've heard rumors of other users having trouble with this as well. I did not update the list of GWebCache addresses to use in 3.1.0 over 3.0.2, but the GWebCache list is still pretty up to date.

Did older versions have an easier time connecting? Are you behind a firewall and are you on a broadband connection?

Thanks.

OS 10.2.6; iBook 700; connected directly all last night static ip via com 21 cable modem capped at 1 Mbit/sec up and down, with the firewall off.
Currently back behind the LinkSys BEFSR 41 v2 router updated with the latest firmware, and trying Limewire 3.1.0/jum168.
Connections are pretty sparse (popular content only returns one result from a 192.*.* red host), probably because of the few connections and running as an UP.
A few uploads are completing and hits are coming through. I haven't been trying very hard to download anything.

I did do a completely clean install for the 3.1.0 version (trashed all the prefs so I could note any set-up/config oddities). Previous versions connected easily as a leaf.

I installed on the G4 iMac and saw similar behaviour, so stopped trying to check out user pref issues. My ISP says all should be good, so I'm trying to get in touch with a neighbour who hasn't updated.

Thanks Adam, and good to hear from you again trap_jaw
btw--I did try replacing the gnutella.net file from one I'd backed up from about LW 2.9.8.

3.1 Beta a Bust
 

Installed & ran 3.1 Beta & all seemed fine but the big setback was others downloading from me were not able to do so. Ran everything as I normally had done in the past but still no go. Re-installed version 3.0.1 & all is working fine again. PowerPC G3 iMac 233Mhz-OS 9.2.1 / DSL router.

Previous Incomplete Download Unable To Continue
 

Hi All,

I am currently using 3.1.0 Pro (Beta) versionof Limewire using Mac OS X Platform. I found out that my recent days of incomplete downloads will not continue anymore after the next day I try to resume the file download.

If I remember early version of LimeWire don't have this problem.

Looking forward for your attention or advise.

It could be coincidence and the people who had the file weren't on.

LimeWire does not send automated requeries anymore, so if you try to resume a file it goes into "Awaiting Sources"-mode. - You will have to search for the file manually and the download will eventually resume if LimeWire encounters another download location for this file.

Thanks trap_jaw4
 

Hi trap_jaw4,

Your reply is quite usable for me. But since we are in the forum, can we have some improvement to have auto-search for those incomplete download files to auto-start the downloading upon file availability???

If I use the Incomplete folder and click the Resume, still the same, it will start back to 0% even i have been gone through until 76% from my previous connection status.

Cheers and thanks!

Dondon (Singapore MAC User)

Hello,

LimeWire is a great program (staring with 3.0) and its getting better and better

Searches are fast, downloads are fast, and everything works great. You are really the best gnutella client out there!

Anyways, I would REALLY appreciate if you added auto-resume capabilities to LimeWire. Without this feature LimeWire looks primitive as every other program has it. Auto-resume is really important because I cannot finish a file in LimeWire if I leave LW with a file transfer...everything goes back to 0% when I try to resume..

Now please tell me, would any noobs know that they have to manually search for a file? It's really a hassal and I really think you should add Auto-Resume, its one of the great features of a program where it automatically searches for sources and downloads the file without your help

I would also like One more thing, can you show the Transfer Rates with decimals like 45.65KB/s instead of the rounded 46KB/s?
I'm used to that decimal one and so are many I know so If you can add these 2 requests to LW that would truly be great.

Thank you,

I hope the LW team is as good as the program!

>If I use the Incomplete folder and click the Resume, still the same, it will start back to 0% even i have been gone through until 76% from my previous connection status.

Which version are you using? This shouldn't happen.

sam--I've seen this happen occasionally, but once the dl starts, the % jumps to the correct level.

Reply for sberlin
 

Hi sberlin,

I am currently using 3.1.0 Pro (beta). Initially, I am using 3.0.2Pro. Due to the problem anticipation, i thought that the problem will be resolved so I intend to use the beta release, but the problem still the same.

Hope to have this feature.

Hi stief,

This never happens in early versions like what you have said.

Cheers!

MAC user in Singapore

hi dondon
This happened like I said. Some (not all) large incompletes resumed from the library pane showed no progress until a repeat search started them connecting. Then either the % or the colour on the progress bar jumped to the correct level.
Cheers.

NEED REPLY FROM LIMEWIRE DEVELOPER
 

It really gives me an impression that there is something missing if there is no continuous downloading.

It is also quite demoralizing if you start back to 0 % after 96% completion from the previous day.

My point is not all the LimeWire user will understand the explanation given. There must be an improvement when it comes to the application design.

As long as the file is available and the file belongs to the same groun no matter who is the owner in the network, the dopwnloading should proceed back to previous ended percentage.

Any reaction from the developer??

Here comes the ol' GUI v. Core (or whatever you call the actual program, w/o GUI) debate.

[Edit] I hate to start this up again. I certainly have issues with the Limewire GUI, and I have been and still am an advocate of many GUI things, such as an in-program help menu, and a bunch of other little things, however, at this point of LW's development, the developers (without passing judgement on them, for I know nothing of such things) are more concerned with developing and strengthening the methods of file transfer, reducing the bandwith load on ultrapeers and other issues.

FYI--my connection problems turned out to be a flaky modem I'd been using for years (LanCity), a horrible replacement (Com21) and now one that works SMC8002CM--aka DOCSIS.

So the advice now for people with persistent broadband connection problems: Rule out the modem!

In reply to the earlier question about how the firewalled host downloading works, this change really benefits everyone on the network. It does not improve downloads for people who are already firewalled. If you're behind a firewall, you already cannot download from other hosts behind a firewall simply because there's no way to make a direct connection between the two.

Rather, this change improves downloads for people who are not behind firewalls, as it makes it more likely that they'll be able to successfully download from firewalled sources. This is because the firewalled host returns "proxies" in the query hit that tell the downloader multiple paths it can take to download the file (to have the downloaded source open the TCP connection after a push request, and then transfer the file).

Hope that makes some sense.

Limited automated requerying
 

Maybe you could reintroduce automated requerying, but limit it to one single requery every 15min or so.

For 4 files it would take an hour to requery them all, but I think that this is better, than flooding the network, and still makes it possible to leave LW on for a night/week/month and to know, that the files will eventually arrive, even though one is away.

That would also increase the number of sharers, and increase the uptime of hosts.

I hate micromanaging my progs.