Jump to content

uthappyuser

Established Members
 View Profile  See their activity

  • Posts

    26

  • Joined

  • Last visited

 Content Type 

Posts posted by uthappyuser

  1. Do you use a 2.x or older version of uT?

    in Announcements

    Posted

    I'm using 2.2.1, though I'd be happy with 2.0.4 which was also great for me. Another member summed it up nicely:

    Stable; has never crashed

    No disk I/O and caching issues

    No ads

    No social features

    No streaming features

    No multimedia features

    No anti-virus integration

    Clean and fast UI

    Seriously, µtorrent became the king because it was tiny, fast, any computer could run it, and it had no stupid bulk. Everything since 2.2.1 has forked in an entirely different and highly annoying direction. It used to be that clients would get banned from different trackers when they got old. Fortunately, everyone seems to realize how dreadful the 3.x versions are so client-banning has virtually disappeared with the realization that a lot of people have no intentions of upgrading. As long as that remains the case, I'll be using 2.2.1 for years to come.

    Who wants ads, streaming, multimedia, and social features in a content downloading program??

    • Like 1

  3. µTorrent 2.0.4 released

    in Announcements

    Posted

    I've stepped back to 2.0.3.21177 and it's solved all the problems of 2.0.4.21586. The afore-mentioned tracker problems, internet shutdowns... it's kind of a mess. One thing I noticed was if the torrent has the following tracker list (for example):

    http://tracker.openbittorrent.com:80/announce

    udp://tracker.openbittorrent.com:80/announce

    udp://tracker.publicbt.com:80/announce

    http://tracker.publicbt.com:80/announce

    http://genesis.1337x.org:1337/announce

    Then the only trackers that'll show up in uTorrent's tracker tab are:

    http://tracker.openbittorrent.com:80/announce

    udp://tracker.publicbt.com:80/announce

    http://genesis.1337x.org:1337/announce

    That is, the spaceless (same machine) trackers only show up as the first line in the group. They all show up (properly) in 2.0.3.

  4. µTorrent 2.0.4 released

    in Announcements

    Posted

    Ya, there's still a problem. When I've got more than 2 torrents off a private tracker, the third one won't come to life for an hour or two. The third torrent shows that the tracker is offline or refusing the connection. I switch back a few builds and it works fine.

  12. µTorrent 1.8.4 released

    in Announcements

    Posted

    Using the latest 1.8.4 build, but tested with 16442 as well:

    => 9 torrents running with a 60kb/s global upload limit. All's fine.

    => add a torrent with a 4kb/s individual upload.

    All is not fine anymore. The new torrent's individual cap becomes the global limit in practice (even though it's still set at 60).

    Anyone else having this happen?

  13. µTorrent 1.8.4 released

    in Announcements

    Posted · Edited by uthappyuser

    While they're looking at the availability regression, I'd suggest looking at the overall functioning. I loaded a torrent with 54 seeds and 16667 wouldn't download a drop of it. I backtracked to 16442 and immediately the torrent took off with 300kb/s. Tested with 2 other torrents - same result. No firewall.

  15. 1.8.1 Release Candidate 1 (build 12549)

    in Announcements

    Posted

    DreadWingKnight blurted:

    The problem will come back again and again as long as this setting is set THIS FUCKING STUPIDLY HIGH.

    You know, people really don't benefit from a jackass like you swearing at them like a moron.

    150 really isn't high. 65535 is high, but still fully allowed by Windows (and was in fact the default value not that long back). 10 is chokingly low - that is well established. The patches for TCPIP.SYS all originally appeared when XPSP2 came out and imposed that limit. Under normal computing circumstances with multiple applications doing multiple things and only 10 half-open spots, Windows started generating huge amounts of 4226 events (not 4662). The patches came along to halt those errors by giving back the half-open breathing room to the applications. A perfectly valid and useful way to increase the productivity of one's system and eliminate a huge number of logged errors.

    Higher half-open limits do not get better transfer speeds; however, they do allow µtorrent to acquire sources faster. If someone's running a lot of torrents and wants to connect to their sources 150 at a time instead of 8, there's nothing wrong with that reasoning. In the end it may not make much of a difference, but some people like every little bit that they can get and faster connection and commencement is just like people who tweak their computer boot-up times: It doesn't make a difference in the end with how fast they can get their work done, but it's nice to be able to start up quicker.

    And so what if Microsoft updates TCPIP.SYS from time to time? There are a host of tools that can reset the limit in 10 seconds. By my count, TCPIP.SYS has only received 3 updates in more than the last 2 years. No reason to not change the limit for me I'm afraid.

×
×
  • Create New...