The new version of LimeWire has a problem ... whether or not LimeWire believes it. Things were pretty fine until I upgraded and now I consistently get the dreaded Awaiting Sources message. Something is broken. I tried this for several days, on audio and video, and everyu once in a while get a d/l, but mainly that remarkably unhelpful message.

penguin40, maybe the message should be changed to something like "search again", "more sources needed", or "awaiting new search". btw, older versions are still available.

sykogurl, any luck?

Ok - what happened? Aren't upgrades supposed to make things better? Now on 2.98, and like many, am now expecting the "Could not Download" message, vs. downloading. It's almost become a game, hmm, let's find a file that lists as being active, click and see what happens. Seems to be more an issue w/larger files, but not exclusively. I'm on Win2k on a decent DSL connection - so reciept shouldn't be the issue. People seem to be able to upload from me.....

Lime Guys? Whassup?

i recieved the "bug in limewire" message yesterday. the problem has slowed down my ENTIRE PC!!!!!!! need help asap

It seems obvious to me that when one searches for a file to download, the list of possible download sites that appears be only ones THAT CAN ACTUALLY BE DOWNLOADED FROM! I have been trying for weeks to download from Limewire (2.9.7) only to get, in almost every single instance, the dreaded "could not download, awaiting more sources" message, or, if a download does actually start, the bandwith is set so low as to be virtually impossible to complete. Having read in this forum the brilliant remedy of initiating a new search for the file and trying to download from someone else ( I have tried this but to no avail) I have to wonder why it isn't set up to do this automatically? INown both a PC and a Mac and found Limewire (previous versions) to be an excellent way of finding files for both platforms. Now I am going to uninstall Limewire forever and switch to KaZaa. They don't have a much for Macs yet but I can get a successfull download at least 95% of the time as opposed to 1% with Limewire. I have to wonder why anyone in their right mind would actually pay for limewire pro

You saying I'm not in my right mind? It's gotta be good enough for me!

I DONATED to Pro, and to Acquisition, to do my little bit to HELP p2p for OSX on Gnutella--LW and Acq are doing the most work for my platform, so they deserve some credit and support. I mean to get around to Phex, but they're all Java. Yeah, it's frustrating, but don't dis the progress made! You've read how greedy servents were flooding the network with automatic queries--why do you think responsible clients reluctantly agreed to give up such an obvious advantage?

Sheesh--short fuse tonight: sorry. Back to the u/l problem (I don't care about d/l's--open sharing is what interests me, and there are way too many leechers):

btw--did you know that OS 10.2.4 has a buried setting in the firewall for allowing gnutella[System Preferences->Sharing->Firewall->Other->Gnutella/Limewire (6346)]? I just found that out an hour ago. So much for all the reading I've been doing! If that's all it takes to get around the firewall problem, I need a better reading list. Don't know what difference it makes yet. [Darn--just checked: something quit in Monitors (a lone Gnucleus 1.8.4.0 at 52 KB/s has outperformed the other 9 LW's in completing uploads) and all the 40 + alternates on 3 of the 4 test mpg's have been lost again. Process Viewer looks normal. Hmm. new entry in console: Apr 4 23:29:30 Stief xinetd[1731]: 1731 {hard_reconfig} No available services. Exiting. Mean anything to anyone? Guess I'll start back at square one with a clean install, etc. Sigh]

Something's wrong with the way LW uploads and downloads connect at such consistently slow speeds, but trying to isolate that variable amongst all the many factors that affect internet connections is really tough. Any new information would be appreciated.

Who is doing that work, and for what reward? Most seems to be done by the LimeWire opensource PROJECT, and I notice the contributions there seem to come from a lot of UNPAID volunteers. Maybe there is a LimeWire CORPORATION that will capitalize on the volunteer work somewhere in the future, but in the meantime an open technology is being advanced.

Right mind? Left somewhere. Get in and help! No mind necessary, and don't mind me.

LimeWire can't do much about the actual upload/download speed. The one with the fastest connection (with the lowest latency) get's the biggest share of the upstream.

First thing you do, if you want to investigate a problem, is checking the "Show Advanced Statistics" box in the statistics window.

If you want to know what's wrong with your uploads, disable ultrapeer capabilities and then wait for a little while until you have had some upload requests. Then go to the statistics and look at the number of push messages you received via TCP. If you receive any pushes (or at least more than 1 or 2 per hour) it means people have trouble establishing TCP connections to you.

__________________
Morgens ess ich Cornflakes und abends ess ich Brot
Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot

--Fischmob

Thanks trap_jaw. Yes I'm seeing an ave of 0.005 pushes , max 3 total 74 in Gnutella-Received-Number-TCP. I'll have to study the stats more to see if i can understand the data. Thanks for starting me on the "push" stuff.

Flow control-Routing Errors showed zeroes for Push and Reply Errors, but 38,094 total Pong errors. I'll have to do some reading on pongs--I recall something about a different port needed for pongs.

0.005 push messages per second (= 18 per hour) is not necessarily a large value unless you only receive about the same number of upload requests per hour. In that case the rest of the network cannot connect to you properly.

How many HTTP HEAD Requests do you receive per second?

__________________
Morgens ess ich Cornflakes und abends ess ich Brot
Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot

--Fischmob

HTTP Requests showed zeroes in ALL, GET, and HEAD columns.

[thanks for adding the "per second" re the push. That makes so much more sense now]