On the completely frustrating 99.9% donwload-that-won't-complete, it is I believe the price you have to pay for the programming decision to allow uploads from partially downloaded files. If the original of a large file goes off line before anyone has a complete copy of it, several thousand people may then be downloading from several thousand incomplete - and never to be completed - copies of the file.

which is another technique of the paid henchmen of the MAFIAA

Abso-defina-lutely... and obviously so! You would think that Shareaza programmers might have foreseen that - or at least rectified it - wouldn't you? :wasntme:

(Later) K, I'm off to the PhoenixLabs forum, see what can be found out. Back in a while.

LOL
This is funny :) I guess none of you ever had a lesson in networking?
Anyway, I'll make it short ;)
With HTTP (the transfer protocol used to watch a webpage, but also for most filesharing networks) you don't have so-called Endgame. Endgame means that if you have 0.01% 'missing', you can ask that 0.01% from another source.
But HTTP cannot do it.
HTTP assigned that 0.01% to a specific source, but maybe it got offline, or it's using it upload for something else, anyway, it can't ask another source for that 0.01%, unless you delete/forget/disconnect from that specific source, so another source can give the remaining part to you.
Shareaza doesn't do this auto, because it's a very aggressive way to do, and will give faithful uploaders a lot of pressure on their pc.

I guess you haven't read the articles which point to the fact that this is a known technique of anti-p2p groups....doesn't matter if its BT, DC, or gnutella....I'm not saying this is always the case, but it is sometimes....

Yeah, I know, but that doesn't mean nobody ELSE has got that 0.01% ;)
Then my Endgame thingy hops in :p

The endgame tie-in to a particular source only lasts for that session, until you close Shareaza. When you restart, I understand that Shareaza searches for new sources. Anyone who has experienced this problem knows well that we are referring to the 99.9% file that you finally have to delete after waiting for days or weeks to complete. And that behavior can hardly be explained by the single-session endgame limitation. So why the mockery, Neglacio?

(Later) OK, we're sorted! The server invasion came from somewhere else... it had nothing at all to do with PeerGuardian2. PeerGuardian2 is clean. Thanks for everybody's help and everything. :)

POSTSCRIPT
Looking at the documentation for PeerGuardian2, though, one has to wonder how such a bucket-with-holes as a continually out-of-date list of 700 million IP's can possibly be an effective remedy for the systematic attacks against P2P, which some contributors on this forum are even anxious to deny. (I wonder why???)

Maybe its time to be looking for another P2P client. Phex! Come here Phex! Where are you boy? Lets see if you can bring us something when you're told to to "Go fetch".