LimeWire dudes should mention this bug in the FAQ, it's the most asked question I've heard, even my mate who has just started using it asked me...

I wonder why these file-sharing apps always have some need to be looked after, they're never fully automatic...

oh well:confused:

This is the best work-around!
But it irritates me that this is not mentioned in the official LW FAQ, it's obviously gonna be a very FA Question, so LW developers should just put in a quick note, and face up to the fact that their program has a "baby-sitting required" bug!

My system is:
Window 2000SP3 running on an
Althlon 1200mhz with 256MB RAM, J2RE 1.41 and connected to the internet through DSL (on an Ni500 box and serving 6 computers in our office) from New Zealand.

I'm having this very same problem with 2.8.6 Pro on my XP Home system all the time now and never in the past but I've been away from it several months. What is going on and where is the fix for it? I see complaints for many months back and no fix. I think this one has the developers stumped.
I wall not pay again for something that is failing and needs so much attention. I wait in line for hours to have it fail and have to start over.

The next version should fix some of those problems. The beta going to be released shortly.

Not Limewire's problem.
 

I sent an email to support. They still think this is a user problem and not a problem with Limewire.

Email follows with my response:

Hi Bill,

This is usually the result of either downloading a file with an
incredibly large name or rogue characters in the name, trying to
download to a full disk, or downloading to a directory to which you
don't have administrator rights. Please try the following:

Press Kill Download
Select the Incomplete folder, in the Library, and select Resume.

Thanks,
Zenzele

My Response:
Dear Zenzele,

Don't get me wrong because I'm a loyal Limewire user and have been over many
years and I know a form response when I see it.
This is not a problem with my PC or the file....it is Limewire.
I switched to BearShare and was able to download the very same files on the
very same PC. I don't like BearShare's interface and prefer Limewire but
BearShare is working.
You can't simply blow this off as a user problem. Please fix it so I can use Limewire.

Bill

Never happened to me on version 2.8.5, then upgraded to 2.8.6 and it started to happen all the time. I'll just stick to 2.8.5

Still waiting
 

I've been using the free version of BearShare since the failure of Limewire. The interface is very different but it works without fail and I need a program that will let me go to bed and not have to watch it for that failure. Limewire worked great for many years and I've been using the pro version ever since it started. I don't understand why they are not working around the clock to fix it. In a few more weeks I'll feel at home with BearShare and will be using the pro version even though it cost more because it works. Limewire is just throwing the business away.

Re: Still waiting
 

Because some people need their sleep.
Couldn't move to libraries where not really such a pressing concern because they happened very rarely (originally). A little bug in 2.8.6 caused them to happen much more often. That bug has been fixed for a while and the latest version does not have that problem anymore.

What and where?
 

What new version are you using and where did you get it? When I go to my personal download page it still has 2.8.6 as the latest version so what do I do to get the version of pro you have?
That library restart fix only works when you are awake to detect it so that is not an acceptable fix. You can't watch the program all the time.

2.9.4 is still an alpha version but it has fixed the "Couldn't move to Library" errors. You can get it from your download page.