Well, hi all.

First of all Xolox is the best, grrreat work, wow!

Have been following these threads for some time now and must say maybe your being a little unfair here Moak. If I search for "dropping partial" the only match is, guess what: this thread...

The actual problem as I see it (consider this a preliminary bug report) is that when a part from a 'erronously serving' host is dropped, which happens at 99% (in my case 50% of a 500 MB file, ack!), Xolox dutyfully reconnects to that host and re-downloads exactly that piece of junked-up data again and again and... (10 times is it, before that host is ignored ?)

You get to see the point: You simply don't want to download 250 MB of 'junk' 10 times in a row in order to permanently ignore that host, so aborting (thereby sacrificing the other half of the download that checked out OK) is the only viable "solution". Ouch.

Also such a critical error message such as "dropping erronously served part" should remain in the message bar, so users like DanninEmX and all the others know what actually happened.

Hope THAT helps :-)

Love, boo.