Big Muscle

But SFV has some disadvantages. a) someone has to make that SFV file and ensure that it's updated SFV file doesn't ensure you that archive is completed, so it's absolutely useless

because it's not problem, but feature

don't visit stupid hubs ;-)

use Opera, it's much faster, secure and eats less memory than FF ;-) I just don't like Opera new skin.

This kind of crash is in all DC++ baesd clients for a very long time and I don't know its source ;)

Sharing, man, sharing... and upload to EVERYONE.

No, you are not right. I think you should leave DC world, because you don't understand its purpose.

I don't think it's about being fan of multisource or ADC. It's because StrongDC++ was first client who used chunked downloads and he dislikes StrongDC++, so it was opportunity to block uploads to StrongDC++.

Yes, this feature comes from fake client called CzDC and it should be banned.

solution is simple. Edit source code and add if(first) return NULL; to ShareManager.cpp before crashed line.

And these zero users share too, because partial file sharing is enabled always ;-)

Iranmaster: go away from DC network, it's not for you.

I don't see any bug in your screenshot. You have disabled multisource downloading and it seems working correctly.

don't worry, it's fixed ;-)

no, there's not fix... if Apex doesn't require admin privileges, then there will be many topics "Why do I see error when creating magnet handler?", "why doesn't it save my settings?", "Why my downloaded files are lost?" etc...

Yes, I know that simple app shouldn't need admin rights. But... then tell me why vista doesn't allow setting for example magnet handler without admin rights?

then call Microsoft to change complete logic of UAC.

please test new StrongDC++ to check whether it's fixed :-)

If you want to block users then just block yourself and go away from DC network. It's not for you!

yes, it is bug. I just suggested simple workaround until fixed version is released ;-)

just don't kick offline users

I think I know where the bug is... the "bad" size comes from TTH tree which was downloaded just before this segment. The size won't be updated then in some cases (especially when there's very little sources at the beginning)

no, it works as designed.

I don't know but have never seen it in StrongDC++.

This has nothing to do with overlapping. It's a bug.