Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About TraderJones

  • Rank
    Advanced Member
  1. change log for build 29835? Asking too much?
  2. look up, the RC was changed to stable for a few hours yesterday and now is back to RC
  3. the version was rolled back to RC again?
  4. You think? Maybe we are not fully aware hiw 'many" there really are? Maybe those users here represent only 0.1% of the overall total? They do have better stats then we have' date=' don't they? I guess that's the price you pay for "progress" ... ;p No one is forcing you to upgrade... But how is it "progress" when if I "move" a 20Mb torrent within uTorrent 3x it takes 5 minutes. If I simply copy the folder using explorer it takes 5 seconds (+time to re-point uTorrent). It's very apparent they have something incorrectly implemented in the "new" disk i/o. I've used and written a lot of software that included the copying/moving of files and nothing I've ever done is as slow as the current disk i/o in utorrent....
  5. Clean up your "act"... having more then 10-20 active torrent is really not advised... But, resume file should be written to also per all user/state related events This is an annoying behavior that started with version 3.3. It's been mentioned a couple times but I don't remember anyone determining that it's likely tied to the Save_Resume_Rate. It shouldn't freeze the client for 30 seconds to save the resume.dat file when it's not that large (~5Mb). Ever since the dev team "updated" the disk i/o subsystem there have been problems when writing to disk, both torrent data and now it appears resume.dat. The devs need to wrap their heads around the fact that many of the users frequently have > 20 torrents in the client.
  6. I never had good luck with Comodo and torrenting. I don't know if the newer versions are better, but I found they couldn't handle the load. Try disabling the firewall for a few hours.
  7. If you connect to just about any site running TBdev derivative code you'll find that 6881 (and most of the ports below 10000) are blocked by default. Most of the coders on those sites aren't even aware that the default config blocks these ports. I can't speak to other codebases but for TBdev the "standard" port blacklist includes 411, 413, 1214, 4662, 6881-6889, 6346, 6347 and 6699. Most sites recommend using ports over 10000.
  8. Hey we actually agree on something.... It takes a bit more work, but the sites that do this are much easier to deal with.
  9. yeah, right..... another example of "customer service"
  10. Unfortunately the QA process for uTorrent sucks. From an external viewpoint it simply doesn't exist, forcing private trackers to whitelist or blacklist by build number. The sites would prefer not to have to do this, but until they can depend on releases being adequately tested before release I don't see much change. I agree with Rafi that a better use of version numbers would be far preferable to the current practice. Calling the private trackers "stupid", "backward" and so forth is completely non-productive. Fixing the QA process and addressing the concerns will go a lot further.
  11. As a professional developer and a holder of certifications in software development I wholeheartedly agree with Rafi on this. It may seem like a minor issue, but not supplying complete and timely changelogs is part of projecting a professional appearance [and one that I'm sadly just as guilty of at times]. This point has been raised multiple times. Sites that restrict based on the versions and builds need this to be done, how else are they to keep their configurations up to date?
  12. will build 22450 be put in the auto update anytime soon?
  13. And before I forget, a big thank you for backporting the patch....
  14. It could be that one has the firewall/router configured correctly and the other doesn't, or that one's router can't handle uTP well. There's a number of reasons other than bad ISPs that need to be addressed by the end user. I'm not saying the uTP implementation is perfect, just that there's more possible issues out there.
  15. about half of the 2.0.x clients that I've seen over the last 48 hours now exhibit the behavior of this bug now.... so much for a "small number" of users affected. (and I've restarted my system and the router to make sure it's not something on my side).