[speedy]

Nooooo!!! My download speed was extra slow so I paused Limewire and shut it down correctly. Disconnected fromt he internet and reconnected after a few seconds. Then I reopened LIMEWIRE, to continue my download. After a few seconds, the download speed went to 0, and by the time I realized, I had lost 75 percent of what I downloaded to corruption! This is definitely a glitch in Limewire 12 because the public version doesnt do this. I can shut down limewire and always continue my download at a later date. I cant do this however, with this new beta version. Please fix this, it's driving me crazy. This is my 3rd time trying to download the same file which I keep loosing to corruption because limewire went haywire..... I think there should be backup on the product so corruption in theis case never happens As a file is downoading, there is a backup stored elsewhere on the computer so incase of corruption, you could still download from where you were.

[Aaron.Walkhouse]

Given the speed at which it "corrupted", do you think maybe the download data
or tiger hash was corrupted instead of the actual file?

Also, next time try that line recycle without shutting down LimeWire. It should work.

[Sam]

Is anyone else experiencing this frequest download corruption problem?

[stief]

I've learned not to use the pause button: it seems to lock the download so that nothing more can be done with it.

Other than that, over six sessions 755 .jpg's were attempted to download with 4.12.0. 625 successfully completed. The other 130 were deleted from the Library/incomplete after one attempt to resume them.

IIRC, only one of those .jpg's popped up the '. . .corrupt: continue?' dialog

[speedy]

i tried to post this in the morning but I couldnt get on here:
the bandwith went all the way down to zero again. However, instead of pausing it and restarting the download and consequently loosing some of it to corruption, I searched for the file name's keywords and minimized the window. Next time I opened, it was downloading in the 30kb range.