Trap_Jaw,
Thanks for your response. If I was still using 2.9.8, I would definitely put to work your suggestions. I might, in fact, re-install and see what happens. I did like some of the other improvements, I must admit. Over all, though, it still seems like a significant downgrade when I compare 2.9.8's download frequency and general ease-of-use with what I am currently back to using (2.8.5).
I do appreciate your suggestions, though, and I hope I didn't come off as a chump in previous responses.

Best,
Lareux

I wonder if there's more to it than that. My daughter has been pulling her hair out for the past 2-3 months because she couldn't download on her iMac upstairs, while I had the same problem on the PC in the office. We've been behind a router for longer than that with no problems, so I don't see that the router settings alone has anything to do with it.
Anyway, I've been working on a project out of town recently and staying in a corporate apartment. The setup there uses static IP addresses and I tried Limewire 2.9.8 again last week. Great results by comparison. The success rate was around 50%. Today I'm back at home and have had one success after 20 attempts. So I'm wondering if Static IPs vs DHCP may have anything to do with it.

You're right that the router alone can't explain the variety of results with all the gnutella changes and the dynamic nature of the network.

FWIW, I've always been on a static IP.
I did try a direct connection for a while, and didn't see much difference between it and when I was behind my NAT. I've seen the most improvement by fiddling with the firewall and NAT software.

Looks like LW 3 is getting closer, and will probably bring in the most changes for Macs, and probably other platforms too. There are still lots of GUI bugs, but the project seems to be emphasizing search changes right now.

>There are still lots of GUI bugs

hi stief,

which bugs are you referring to?

thanks.

hi sam--hope you get an easter break too. I've been trying to follow your work on the compression stuff, and it looks pretty interesting for Ultrapeers. Thanks again for the tip on reading the dev mailing lists to get a sense of what is happening. Much less frustrating (but less entertaining) than reading a bunch of "doesn't work" posts looking for troubleshooting tips.

I haven't bothered with a list of the gui glitches, since it looked like the team was busy with the cross-platform search and connection issues. Too, I figured most of the GUI stuff would be java 1.3 related on OSX, so thought that when LW switched to using 1.4.1, I'd start paying more attention. Acq looks to have done a very nice job working those out.

Just off the top of my head, the bugs that seem to be GUI related are

--LW crashing as Ultrapeer. I sent in quite a few crashlogs on this one, and hope it can be fixed soon so I can run reliably as an Ultrapeer rather than as a leaf.

--columns not refreshing a sort quickly. I usually have to scroll up and down one screen to get reliable views.

--"Could not move to Library" triggers a blank display in the Library Pane

--the close button on search tabs above the first row doesn't work (the command-click does)

--would like to see tooltip data for completed uploads, and a better way to follow chunked uploads than just "complete" for each chunk in the Monitor Pane. Too, reporting of KB/s in the 0-1 range would be appreciated. This would help me optimize for sharing. (adding the vendor info has been very useful here)

Is that enough for starters, or are there others you like us to watch for? Would a new thread in the Beta forum be a better place for this? I could delete this post and start a new thread there if you think that would be useful.

Cheers--hope your internship with LW is rewarding.

I updated today to the latest version. Before updating I could download files, now I cannot. I get the awaiting sources msg EVERY TIME I attempt a download.

I also noticed that often the D/L will start, only to stop and spit out that error msg a few seconds later. If I restart the D/L then it goes again for a few seconds and then stops again, with the same error msg. Now after about 30 or 40 times starting and waiting, starting and waiting, I have my file.

I did not have this problem with the previous version which suggests to me that something has been overlooked here by the developers...

Hi sector--what platform and versions are you using?

Thanks alot. this page solves this mystery that has plagued me for a few weeks.!