Downloading [awaiting Sources]
 

I HAVE 2.9.8 ALSO I HAVE HAD MANY OF THE OTHER VERSIONS OF LIMEWIRE...NEVER HAD ANY PROBLEMS ..UNTILL NOW ....I'VE TRIED FOR AWEEK NOW TO DOWNLOAD NO MATTER WHAT TIME OF DAY OR NIGHT I KEEP GETTING.....AWAITING SOURCES.....THIS IS WHAT I GET NO MATTER WHAT I DOWNLOAD... .....

"Could not download,..." just replaced "Requery Sent...". I'm sorry you don't have any luck with the latest version but there are plenty of other p2p clients. Try one of them.

Same deal here
 

I also get the same results trying to download w/ the latest LimeWire "Could not download/awaiting other sources" all the frikkin' time. Why is it happening now, and not in previous versions????

b/c "Could not download" replaced the "requery sent" messages. Requeries are now filtered from the gnutella network to save bandwidth.

awaiting sources
 

I am also having the same problem. I've used many versions of Limewire and did OK. When I downloaded the pro version, all of a sudden I keep gettinG the annoying "awaiting Sources" message. I CAN'T DOWNLOD A THING. NOTHING COMES THROUGH. DOES ANYONE HAVE ANY ANSWERS??

I am having the same issue regarding awaiting sources. What is the deal.

AWAITING SOURCES;" WHICH MEANS TOO BAD"
 

IT SEEMS THAT LIMEWIRE HAS NO ANSWER..TRAP MOUTH SAYS IF WE DON'T LIKE IT GO SOMEWHERE ELSE..WHERE DID THIS GUY COME FROM? YOU WOULD THINK HE WOULD ADMIT THERES A PROBLEM AND TRY TO HELP........MIKE

Since I'm not a member of the LimeWire team I have the freedom to choose *not* to help people who come here SHOUTING questions that have already been answered about half a dozen times in similar threads.

When displaying the "Could Not Download, Awaiting Sources" messages LimeWire does exactly what it is supposed to do. It informes the user that all download attempts from all available sources have failed and that LimeWire has run out of alternate locations to try.

Hear! Hear!

empty words, there, mr. trapjaw
 

Your explanation says nothing except the obvious. I don't understand how limewire, or you, for that matter, could think that this 'new and improved' way of dealing with requeries constitutes an actual improvement. Regardless of how it is worded, or from whence the requeries are now filtered, the new version of limewire, for me and, it seems, many, many others, has an almost ZERO percent success rate of downloading ANYTHING WHATSOEVER!!
I have a T-1 connection and I can't even download a frikkin' text file. Three days so far of perpetual retrying with -guess what?- ZERO DOWNLOADS... and you tell me that limewire is "doing exactly what it's supposed to do"?
Hmmm. Hmmmmmmm.

Not angry, just missing your point, here.

Sinc.,
Lareux

3 days and nothing on a T1! Wow--that sounds so bad it sounds like you are being blocked. Some universities have closedown gnutella connections--do other clients work? Post your specs, and somebody might be able to help. I'm no expert, just an OSX user.

(sorry about the interruption--trap_jaw is probably off finding ways to debug LW; I think his record is pretty good at fixing and writing code for a volunteer)

nada.
 

I use OSX as well, and I work out of my home. Several downloads have started, many infact, but every single one of them gets interrupted at some point and becomes inactive with that nagging "awaiting sources" message. In fact I just ended five simultaneous attempts to download five other (hopefully earlier) versions of LW for mac, or any version for that matter: three of them immediately showed 'awaiting sources', cleared those; one of the other two never showed any download rate other than "0.0", then turned inactive; the last one downloaded about 2/3 the way and became inactive.
I'll keep trying to make this one work well enough to avail me of an older version that works like a charm.

thanks for your reply...
Best, Lareux

The new OS 10.2.5 update is out (I just finished installing it) and it looks like it fixes a lot of communications bugs. I hope many of them will help me!

If you want earlier versions of LW, gad. It's been listed on these forums before. trap_jaw first tipped me off to it.

[edit: I can't find the link now onthe usual pages--probably because the old versions caused all kinds of trouble for the network and users. Found it here ]

Cheers. How did you set up your firewall/router? Those are my favourite issues just now.

Thanks for the help
 

I'll try an earlier version of Limewire at the link you provided. Thanks for the help. Hopefully it gets me downloading again.

Thanks a million, Stief.
I'll check it out. Best, r.

Same thing here: I haven't been able to do a single download since I upgraded to 2.9.8.
I can't believe it is just a message thing: I used to see requery messages, but I could download more often than not.

Xavier

btw: I'm kind of angry too because now I have the upgrade popup when I start up lw. I paid for lw (ok, it was some time ago) and now I get a popup on startup no matter what: I don't upgrade -> it says I should, I upgrade -> it says I should pay.

Well, there are no known bugs in the download code that
could be the cause for those failed downloads. LimeWire has
been thoroughly tested and if there was such a problem with
the downloads, somebody would have noticed it.

If a download fails, it is often because of a read-timeout
when reading from a socket: If the connection to a remote
host cannot be established within 4 seconds, the download
fails. If no data is transmitted by the remote host for 8
seconds, the download fails, too.

Those rules are strict but they haven't been changed for
the last couple of months.

Trapjaw,
I still fail to see what your explanation has to do with the fact that this "Awaiting Source" issue seems to be a sudden and widespread problem for tons of people; a problem that did not exist prior to 2.9.8. Your explanation is like answering the question, "Why are we bombing Iraq?" with, "Because bombs are DESIGNED to explode".
Does YOUR 2.9.8 work like a charm? And if so, what is your secret?

The official LW 2.9.8 does indeed work alright, at least it's not worse than previous versions. Maybe it's because of the way I download files. I always try to make my searches as specific as possible (the new search system will return better results for more specific searches) and download three or four versions of the file I want. Then I re-check half an hour or an hour later and search for failed downloads again.

I've found that there are a couple of other tricks to achieve a better success rate when downloading (but it's not such an earth-shaking improvement as you may think): I set the download timeouts higher in the source code and I set up LimeWire to retry sources if the http transfer stopped unexpectedly or if LimeWire could not parse the http header correctly.

I DISLIKE THIS VERSION WITH A PASSION. BUT LIKE TRAP JAW SAID. IF YOU DOWNLOAD THE SAME SONG 6 TIMES ONE OF THE 6 WILL MOST LIKELY COMPLETE. THIS IS A SORRY WAY TO DOWNLOAD. I EXPECTED MORE FROM THIS VERSION.

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.!