Gnutella Forums - LimeWire 4.9.3 Beta

Gnutella Forums (https://www.gnutellaforums.com/)

- LimeWire Beta Archives (https://www.gnutellaforums.com/limewire-beta-archives/)

- - LimeWire 4.9.3 Beta (https://www.gnutellaforums.com/limewire-beta-archives/41029-limewire-4-9-3-beta.html)

Quote:

Originally posted by ultracross
1. I have noticed that if the file completes 100% before a user has a chance to click NO on the corruption dialog, the file is already saved into saving directory and the NO is ignored by limewire. This poses a problem if the download directory is being shared. Then other users will download this corrupt file.

This is actually not a problem because LimeWire remembers to share only the verified parts of the file.

Quote:

4. Downloading multiple files (around 8 files, and 3-4MB in size each) still rasies the cpu usage signifigantly and disk access is heavy.

Does this happen always, no matter how fast or slow the downloads are going?

Quote:

5. And tons of bugs that i posted in other threads are still lingering around.

We've been trying to address the most serious bugs first.. if you could be kind enough to put together a short list of the most annoying issue (or just links to the posts where you originally posted them) it would be easier for us to look them up and start ticking them off ;-)

Thanks for the input!

Quote:

Originally posted by zab
This is actually not a problem because LimeWire remembers to share only the verified parts of the file.

but it still shouldnt be saved to my shared folder. If i click no on the box, then i expect limewire to remove it from my shared dir. if limewire is going to share out verified parts of the file, thats fine, but put them in the incompletes directory or something.. just _not_ in my shared folder. i dont like listening to corrupt [CC] music ;)

Quote:

Originally posted by zab
Does this happen always, no matter how fast or slow the downloads are going?

well my best speed with limewire sofar has beenr around 320KB/s, but normal transfers when downloading around 8-10 files are around 20KB/s each. and i normal pick the files that have the best bitrate and mosts hosts.

Quote:

Originally posted by zab
We've been trying to address the most serious bugs first.. if you could be kind enough to put together a short list of the most annoying issue (or just links to the posts where you originally posted them) it would be easier for us to look them up and start ticking them off ;-)

well my list wasnt short.. lmao. im not rushing you guys, i just want those things fixed before you put out 5.0.. cause the beta process is slow, but the versions are closing in on 5.0 which i think limewire should start taking there time with releases.. or extend the version numbers to have letters at the end: 4.9.5a, 4.9.5b etc..

Quote:

Originally posted by zab
Thanks for the input!

thats why im here.. not somewhere else. i appreciate the thanks though, but its not needed. just doing my job as an end-user.. ;)

Quote:

but it still shouldnt be saved to my shared folder. If i click no on the box, then i expect limewire to remove it from my shared dir.

actually... did you verify that the file was corrupt? What happens is that LimeWire decides a file is corrupt after certain % of it fails verification. But if before you have the chance to click "No" LimeWire manages to successfully download the rest of the file from other source(s), it will get saved and will be just fine.

Quote:

but the versions are closing in on 5.0

There's always 4.9.10, 4.9.11... ;-)

Quote:

so then what happens if limewire doesnt manage to successfully download the full file? will it still save it to my shared directory?

No, they stay in the Incomplete folder, prefixed with CORRUPT-....