Woke up this morning with message that hard drive was full and limewire could not complete download. Closed it, cleared drive and when I restarted limewire, it went through set up. Now I show no history of downloads that were in progress.

CAn I reconnect the files to limewire to complete?

Thanks

You can, but the files will begin from zero percent despite whatever size & past % downlded they might have been before this issue. Go to LW's Library window, Select the incomplete folder, Select the files within & press the Resume button. This will force them back into the Downld window.

Why do they restart from 0%? Is there any way to get them back to the % they were at before the crash?

No. That's an issue mostly only suffered on the windows platform. So only advice is try ensure there's plenty of disk space & you defrag the HDD reasonably often.

This is on a Mac. Everytime I have to force quit Limewire when the app hangs, I lose whatever I was in the middle of downloading. The file is still there. Why can't LW reread it? And why do other downloads that weren't interrupted by the Force Quit resume fine from their previous dl quantity?

I didn't think Mac had this tipe of problem

__________________










A little common sense goes a long way

Later Grandpa

Unless I'm tripping, it's happening on mine. Is there anything I can do about it? Why is it happening?

If you're finding your LW is getting sluggish, close it down. Then re-open it. Java on the mac is not that efficient. And unfortunately virtual memory which all osx apps use grows due to Java's inefficiency. If you are using Tiger, then update your Java to 1.5 & use the Java preferences to force LW to use 1.5; Setting up Java 1.5 Unfortunately, Java 1.5 is only available for Tiger OS 10.4

OK, that explains why LW is sluggish. Why is it unable to resume download from the last position saved? If the file was entirely in VM, that I could understand. But the file is on disk, as much of it as was downloaded before the crash. Yet LW isn't able to identify where it was in writing the file before the crash, and resets to zero. The buffer obviously wrote to disk before the app crashed. Why can't LW recognize it?
Even weirder, sometimes when I quit out of LW, I lose huge quantities of the file. Sometimes I'd be half-way through a dl, quit out of the app, and only be at 25% when I relaunch LW. What gives?

If you're frequently suffering this issue then you should frequently backup your downld preference files. These are called downloads.dat & downloads.bak & are found in the incomplete folder. Normally these files should not be touched or tampered with. But make copies of them perhaps once every few hours. Then if LW crashes, replace the ones in the incomplete folder with the ones you backed up. Then restart LW. But you MUST ONLY do this whilst LW is closed!

It seems as though I lost an edit to my previous post. I tried to emphasise not having too many shared files & definitely not too many incomplete files. See Tip: Purge the Downloads Queue! which will help to spriten up LW & greatly reduce the amount of VM that builds up. I'd suggest you do it with files that are zero KB or zero % downlded. Perhaps you could also apply it to those that are 100 KB or less. You'll notice the difference immediately as LW will start up faster.