Big Muscle

Member
  • Content count

    702
  • Joined

  • Last visited

Everything posted by Big Muscle

  1. Disable partial sharing

    live with slow transfer ? and then lives with 10 slow transfers and eat all slots in the network so nobody can download anything? You just don't realize that DC is about sharing and not about downloading!!!
  2. apexdc has not been released yet

    of course, you can ;-)
  3. Development begins

    hi, I'll open my CVS in a few days as a holiday present, so you will be able to make your client quickly :)
  4. block user

    ok, so when it is implemented, I'll block only you :thumbsup:
  5. two more requests

    I've removed global emulation due to segmented downloading. In DC++ emulation mode not all "segmented" features are available.
  6. Kademlia support ?

    I think you don't understand matter of Kademlia. It has nothing to with hubs, so you can't disable it for certain hubs.
  7. Welcome to ApexDC++

    interesting, but STLPort 4 doesn't work under VS2005. Actually I use my modded STLPort where's fixed bug which is there since version 4.
  8. Different shares for different hubs

    and what would it write in tag/description ? Something like "Hub A: XXX GB, Hub B: YYY GB, Hub C: ZZZ..." I think it's weird :-P People are lazy so they would share only minimum what they can.
  9. Different shares for different hubs

    I guess that the client with this feature will be banned everywhere ... or hubs will increase their minimum share size
  10. Intel 9 Compiled Version!

    MSVS 2005 also supports these optimizations =] but most of them can't be set manually but it's done automatically (e.g. vectorization). But just remember that no optimization can really improve your program, it can be done only using by optimized algorithm.
  11. When will ApexDC++ be released?

    Ok.. I try to guess too.... hmmmm. 5th December 2007 :D
  12. win98 compatibility & other reqs

    Maybe I understand what you're talking about - losing slot when chunk is finished. I don't know exactly how it's done in PWDC, but if it's like in StrongDC++ then there's possibility to lose slot only when you have enabled DC++ emulation for hub you're downloading from... When emulation is disabled, then you can't lose slot In next version of StrongDC++ there will be feature that if user speed is known then chunk position will be assigned according to the speed :)
  13. Search by file type

    it's already in every DC client
  14. Different appearance

    yes
  15. Different appearance

    check RevConnect's search window :)
  16. When will ApexDC++ be released?

    yeah, it's better to fix all bugs and then released it, than try to fix only some bugs to some date and release it.