Your "Incomplete" or your "Shared" directory may be write protected.

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

--Fischmob

Interesting. In the last few hours, I've seen more "could not move to library" errors than I've seen for weeks. This error also blanks out the display of items in the library pane. Usually one click on refresh will bring the display list back, but sometimes two or three clicks are necessary.

I just gave the inc and shared folder full r/w permissions (never had to that before) so we'll see. Might be related to the latest update from OS 10.2.4 to OSX .2.5.

I also tripled the size and number of the shared items. (Can you see if access/content looks OK trap_jaw? I'll try the magnet to provide a link--uploads are frequent but rates are usually <1k) .

Could not library errors can still occur when downloading from clients without HUGE support.

By full r/w permissions on OSX you mean changing the mod to 777 (read, write, execute permission for user, group and everybody else)? Only the user running LimeWire needs full read and write access to the folders.

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

--Fischmob

Not sure about 777.There's probably a terminal line I can use to get info on folder permissions--but I've very limited experience with the Terminal. In Get Info on a folder, I gave the same full read/write perms to the Group and Others categories: same as Owner.

HUGE?--Did note that d/l's from older clients LW 2.7.3, 2.6.5, were more likely to trigger the library error. I tried to trim connections to avoid older Ultrapeers, but that no guarantee of alternate listings.

Yes, that should be more or less the same as chmod 777 <file>. As I said, if the owner of the shared / incomplete dir is the one running LimeWire, he should not encounter any problems unless the owner does not have full permissions to access the dirs.

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

--Fischmob

I'm the only user, but run as an admin. Root user is disabled by default.
don't know what I did here, but
Last login: Sat Apr 12 07:32:01 on ttyp1
Welcome to Darwin!
[Steve:~] steve% chmod 777/Users/steve/Incomplete
usage: chmod [-R [-H | -L | -P]] mode file ...
[Steve:~] steve%

you have to put a space between the mode and the target directory.

chmod 777 <directory> allows everybody to access <directory> but for LimeWire a chmod 700 <directory> (allowing just the owner read, write or execution) will work as well as the other one.

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

--Fischmob

Ah--thanks. man chmod gave me more than I have time for, but looks interesting. btw--Didn't have time for a fresh install, but did a delete incompletes (incl .dat), full restart, fsck -y (safe boot), repaired perms, restart, ran LW, entered same search criteria, and had the same results. Watched for older vendors, but only 1 older (LW 2.1.3) vendor of 12 (mostly 2.9.8; 1 BSh 4.2.5) was involved in the "could not move to lib".

Thought maybe I could trigger it by refreshing the Library/Incomplete display (sometimes took three clicks to refresh from a blank), but couldn't reproduce this consistently. Java draw involved? The spinning lime often disappears.

The "could not download error" quickly went away after "repeat search" found new sources of course. I only have 3 UP's since LW usually crashes if "disable Ultrapeer" is left unchecked. Alternates found ranged up to 20 or so for each of the four .mpg's involved. Each is 100-190MB, and not worth having.

I'm outta here--real work awaits. Thanks for the terminal advice and enjoy your break. Cheers.

First, I can't find a Post Button just a reply.. (Sorry to the user this reply goes to. Its supposed to be for the Limewire crew) Thanks. NOW....What happened to the Limerwire that I can't DL? I get this 'Cant Download' message even before a token has been sent out of my system. I paid for Limewire because I KNOW it to be a GREAT product of some wizards. I have always loved Limewire so I thought.. Since Limewire was so insistant that I upgrade to the 2.9.8 I did only to find that I can't DL. What Happened guys? There is DEFINATELY soemthing coded incorrectly. People can Download from me but not vice versa.
I am on a Mac OS 10.1.5/DSL/512MB. Everthing used to work now I can't do what I need to do. HELP PLease FIX THIS!!!
Thanks in advance,
germ240

I thought it only fair to tell the guys at Limewire that when I wrote my post, Limewire was uploading but not downloading. I began to read the other comments of users with the same prob. I began the process of DL again from different sites and Low and behold, the DL-ing process began; but first, let me tell you what happened.
1. I clicked on the file I wanted to dl and
2. Limewire's DL screen did NOT go immediately to COULD NOT DOWNLOAD (It actually sent a request for the file.. it didn't do this before)
3. I am able to download and upload

So far, The program is functioning. If hosts are turning off their machines or disconnecting from the net, there is nothing we can do about that.
It seemed every host I went to (T1-T3), Limewire would immediately respond with "COULD NOT DOWNLOAD"
Modem and Cable hosts seems to work fine. I'm sure I will update this post in the coming days. Thought I'd share this info.