Force resume won't work. A simple "Repeat search" won't return new results. You might have to wait an hour or so before repeating the search. You might try killing the download and download the search result again.

Your settings are not the problem. And LimeWire 2.8.6 probably won't work any better, it will simply go into "Requery Sent" mode and stay there for ages.

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

--Fischmob

Have Windows XP Professional. Yes, I am sure of clean install. I came here to post problem and have seen that I am not the only one having this specific problem. Thanks

trap jaw, you are not paying attention sir. 2.8.6 worked FINE. It has only been since installing 2.9.8 that I have encountered this problem. I have deleted file... new search, etc, etc etc. Have been using Limewire for quite sometime now - was using Gnutella when Napster was still around, I want to say was using it before Napster was around... but memory isnt like it used to be Am working on installing 2.8.6 now.. if I can recover file. Was cleaning house this morning and deleted 2.8.6 bacause was certain of LimeWire's update working correctly. Way it goes man. If anyone has help or suggestions that would be great!! But please dont tell me that going back to previous isnt going to help when I know better. thanks, astec40

I have uninstalled 2.9.8 - recovered my deleted 2.8.6 file, installed it and have downloaded several files that I have trying to download for two days using 2.9.8 - sounds like a bug to me. Not all are are effected by it apparently, by reading posts. I am not a "techie" all I know is that it didnt freakin work right and now it does. peace out.

Does LimeWire ever go into the "Connecting..." state? Activate the advanced statistics. Does LimeWire send Push messages via TCP?

All older versions of LimeWire can be found here:
http://www3.limewire.com/download/

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

--Fischmob

Yes, 2.9.8 did go into connecting.... state every time. But would be for just a second or two then go into the Cannot download mode. Dont get me wrong, I was able to download a few files utilizing 2.9.8 but was a pain in butt to work with. I had to keep freakin messing with it. And with other files it did not seem to matter how much I 'messed with it' I have activated the Advanced Statistics option, but am not familiar with this "Push messages via TCP" Please keep in mind I have reinstalled 2.8.6
And thank you for taking the time to help me resolve problem with 2.9.8 - if we can tentatively work out a solution I would reinstall 2.9.8

The problem I have, is that the basic connection and download code was not really changed. I could imagine that somehow the timeouts are a little more strict in the latest version but that would not explain your problems, unless of course you became an ultrapeer with 2.9.8 and never became an ultrapeer with 2.8.6 since download attempts tend to timeout more often when you are an ultrapeer.

If LimeWire goes into "Connecting..." state the Push statistics is not important anymore. I was afraid it could even be a strange problem causing LimeWire not to request files properly.

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

--Fischmob

Yeah yeah, I'm seeing this too. I never had any problems before, but the instant I updated to 2.9.8, everything basically fell apart. I can barely maintain three connections, when I was always able to maintain 6 before. And about 95% of attempted downloads fail with the "Could not Download' message. I'm running OSX 10.2.4.

Yup--lots of changes from 2.8.6 to 2.9.8! Did you notice the fixes? I haven't seen that damned "could not move to library" message (and others) for a long time now, so I sure wouldn't want to go back. Found out a lot of the problems I'd been having were OSX firewall related.

3 connections is normal now and is part of the plan to make three connections work better than 6, I think. As LW gets closer to the 3.0 release and 2.9 is more widespread, we should see that happen. Seems better for me, but there are too many variables like the firewall to say for sure.

Found any new ways to help reduce the "could not download . . ." ?

down loading problem.

Every time I try to download a song a message comes up that says "could not move to library" and will not download. when I try to delete a song in my file it says "It may be in use by another application" and will not let me delete it. please tell me what I'm doind wrong.I am unable to download or delete.