I don't know why, but that is an old version of LW. At least the files LW couldn't move to Library are complete. So you can use them.

My guess is LW's been running for a long time & used up a massive amount of virtual memory. And as a result, you've run out of HDD space whilst LW was open or LW simply stopped functioning properly due to the VM build up.

It might be an idea to clean out some of your incompletes anyway as that will put much less pressure & stress & demand less VM on LW; Tip: Purge the Downloads Queue!

i can say confidently that is not the case. the files marked "could not move to library" were definetely not complete -- they were all well under the size that they should have been

nope, i was using the computer at the time it happened once and there's no way that happened -- unless it was very quickly filled up and then very quickly emptied again but i really doubt that. i had at least 15GB spear anyway. i would have noticed that being filled up.

seems very odd. i searched for "could not move to library" and it seemed to be a serious problem some time ago for windows users. i didn't notice it saying that the downloads.dat and downloads.bak files were gone/missing/deleted which is actually the really serious part.

the second time lw had already well and truly purged the downloads que for me -- all gone. and i threw away the prefs. hardly any things were in the incompletes folder and hardly any things were in lw's downloads list -- maybe 20 max the second time it happened. i don't think there was that many the first time either.

nope, i appreciate your answer but i don't think it's right at all. maybe i'm paranoid, no i'm being silly.. is there anyway something like that could be induced by someone -- another lw user? i'm probably way off there myself. it just seems a odd. months and months of use, nothing like it. then twice in space of a few days it happens -- all partially dl'ed files useless (i haven't used it since.) i might try and update and try using lw again.

i'm thinking of making a little app myself that every 30 seconds or so copies / backs up the downloads.dat file, because the loss of that has been my main problem with lw throughout my use of it over the years. some previous versions to what i'm using now were terrible because that happened regularly and now it's happening again, although in a very different and odd way. it's very annoying because it wastes so much dl time (and when you're on a modem/dial up that's more valuable i think).

a utility that could remake a downloads.dat file from the partially downloaded files would be truly fantastic app from my point of view.

Hmm I'm not sure if an apple script could do this. If you know how to use apple script it might be handy. In any case, it might be an idea to backup the downloads.dat & .bak files every day or few hours. I do keep backups for when I run different versions of LW. Since changing backward in versions can corrupt the downld prefs. Keep that in mind!

I know what you mean with the much earlier versions of LW the downld prefs did seem to corrupt very easily. A total PIA b/c I was also on dial up.

Yes it's possble the issue is with LW 4.2.x I also recall there was such an issue with an earlier version. I also recall LW 4.2 had problems. Whether it was the same I can't remember. I think the earliest 4.9 version had this issue in the extreme. LW 4.8.1 was much better than LW 4.2 so if you update & have problems, let us know & I can send you a copy of an earlier version. But it'd also be good to try to solve the issues of any new version 1st. BTW which OS version are you running?

i should think a.s. could do it but i don't know it at all. i know cocoa/objective-c to a certain extent and backing up the downloads.dat/bak files at regular intervals would be very easy, at least in a rudimentary way. it would need a bit of extra cleverness though i think to try and make sure having made a good backup, then the downloads.dat file gets mangled not to backup the mangled version (over the good backup) -- check it hasn't reduced in size significantly since the last back up for example, although it reduces in size in correct use i think as it finishes downloads but if it goes from say 600k to 4k in one jump that's probably a good sign there's a problem with it. so to do it completely correctly/thoroughly might be a little bit more tricky but even a most basic a version would have saved me in the last two dissaster situations i think.

i used to do that but also used to also forget to do that, and haven't had the necessity with the current version i'm using until this new problem that is.

it was terrible.

ok thanks. i haven't made up my mind weather to make the bu utility thing (i probably will because i don't think it'll take long) and/or upgrade (not sure, as lw is so temperomental and this version has been not too bad so apart from this new recent problem i'm loathed to fix something that isn't broken, because that can easily break it (!) if you see what i mean, although this version is now broken for me it would seem.)

maybe i'll try a complete reinstall of this version after having deleted everything related to lw first (as well as making my bu utility thing) and see how that goes. if it happens again, upgrade.

10.2.8 with whatever the latest version of java is possible with that (i think -- at least apple isn't making a newer version available through software update to me).