cannot move to library
 

I have the same issue, downloading programs, MP3s, and videos. This anomaly happens on my Mac Dual GHz machine, running Mac OS 9.2.2, with many items, both with and without "/". Any assistance would be appreciated.

If you encounter a file whose host computer owner thinks he can write a short novel as a title, then LW for Mac can't download it and you get the "cannot move to library" error. Find the equivalent file with a shorter name.

Is that the same explanation for "cannot move to library" errors on PCs? :confused:

Talking to my finger (Dutch expression)
 

No, Ria, you get the same error message with short titled files, but they DO contain slashes '/'. So is that the real problem?

Yes, that is an "illegal" character and won't download for any version of LW.

library issue
 

I have WinXP with all released patches. I also have installed Java 2 runtime environment. I have had no problems with Limewire until upgrading to 2.54. I have tried to install this release various ways (diiferent drives, different share locations, ETC).

This release has problems and I hope that the developers admit it and fix what ever the bug is!

I aslo found that they delivered some sort of patch into the shared directory. When you go to install it, it provides a very basic description as to what it is - all. What is all? Am I supposed to install software that says all?

Any insight would be appreciated.

i seem to have the same prob with not being able to move songs to the library where you able to figure it out and if so could you help me . Thanks

More cases of cannot move to library error
 

Freiluft, I have the same problem with other files: the title is not too long and doesn't contain a slash. I can't see a common denominator. Are you sure the problem is with the file name?

This thread goes into greater detail about could not move to library:
<http://www.gnutellaforums.com/showth...&threadid=7455>

It might mention a case not given here.

Can't Move to Library Fix
 

Fixed the problem of getting the can't move to library message. I was running Limewire 5.4.4 on Windows XP. Uninstalled 2.5.4 and installed 2.4.3. I have had no problems since. This is an obvious coding problem in 2.5.

All of the speculation as to how users are sharing is BULL. Why does 2.4.3 work fine????

I suggest a LImewire developer exam the code difference between 2.4.3 abd 2.5.4 and see what changed that may be causing this problem!

Can't Move To Library Issue
 

I see this as a really big product performance issue: Limewire 2.5.4 is basically useless to me if I can't download the majority of mp3 files due to long file names. I see two possible fixes:
a. Check the source code to find the cause of this bug between 2.4.3 and 2.5.4 or
b. Add a Save As feature to 2.5.5 so we can shorten the damn names!

Also, another issue: I am running Mac OSX 10.1.5, IE 5.1, and Limewire 2.5.4 and I can't see the topics or click on them in the Forums. I am writing this message from a Windows machine at work (where the firewall prevents me from actually using Limewire).

Please address these issues,
John

Your OS X issue is a -- guess what -- Java issue. You also can't enter Java chatrooms, such as Yahoo, unless you go back to 9 -- the REAL Mac OS. ;)

i get that error regardless to what the filename is. it can be less than 12 characters, and it's still there.

because of that LW bug, the majority of what's available will not download.

that is a pain. wasted time downloading ties up network.

Why not scan/replace 'illegal' characters from file name so it
can be successfully stored onto target system?

Java knows where it is running from system properties.

Re: Cannot move to library
 

There does appear to be an additional problem that causes this error - it may have been introduced in one of the recent releases (since I haven't previously seen this particular problem).

I have no idea what triggers the problem. But effectively, any new search added to the download queue cannot be moved to the library. Shutting down LimeWire and restarting it appears to cure the problem.

I shall be reporting this as a new bug - could those who have seen this problem try to take as much note of the circumstances as possible and comment here.

Mark