As many of you who use the current version µtorrent(2.0.2 build 19648) may notice, this bug is still present. There was something on their update page that said that although they had this bug fixed, the had to revert the fix due to some other bug it was causing.
I did some testing on my own end, installing every older stable µtorrent client down to 1.8.5, and resetting all the settings in my µtorrent program except for keeping the "C:\Users\UserName\AppData\Roaming\µTorrent\settings.dat" file in a backup folder. This is the specific file that you can backup to allow µtorrent to remember all of the files you are seeding and downloading, where and when they were started and finished, the upload/download ratio on those files, and the tracker(s) and key(s) you were using.
Unfortunately I had no success. I still noticed multiple upload slots being used by the same client/peer, judging by the fact that some peers are using the exact same port, and displaying having the exact same % torrent - The problem was still present.
Although this bug may not affect the "performance" of µtorrent per se, it does allow one client to use up to 3 upload slots, and it doesn't help them because the upload bandwidth they get from my client is divided equally between however many upload slots they are using. I tend to limit my upload slots because I have so many torrents uploading to this site alone, not to mention that I use the same torrent client to seed and download from other torrent sites. Limiting the upload slots when I have limited upload bandwidth helps keep things fair.
This is why this bug annoys me, if one person or client can use all or most of my allocated slots of any given torrent, it prevents other users of using those slots. This is quite unfair, as it prevents other users from downloading torrent due to users using multiple slots taking up what would be their slot. I have to limit my upload bandwidth and slots per torrent because, for whatever reason, my ISP not giving me the full upload speed I pay for, even with forced incoming and outgoing protocol encryption.
Trying not to stray too far from the point of this thread, due to the µtorrent developers being unable or unwilling to fix this problem, I was wondering if anyone had gotten the Windows version of KDE's KTorrent client to work in Windows 7 x64.
I usually hate GTK, GTK+ & GTK2 coded apps(the GNOME desktop environment, for example) - due to their lack of flexibility and customization in comparison to KDE & its apps, and because KTorrent is still my favorite torrent client(even over µtorrent), I am looking to make a switch from µtorrent to KTorrent for Windows. The primary reason is because even though µtorrent is a great torrent client for Windows, this bug is really starting to annoy me, mainly becuase it hinders how fair I can seed to this community. My previous attempts to use it had failed due to errors launching any of the KDE for Windows executables.
I'm using the latest version of KTorrent on my Linux drive, and I absolutely love it. I'm not really willing to switch from µtorrent to a torrent client other than KTorrent, because I'm very familiar with the way KTorrent works, its the only torrent client that I have always liked better than µtorrent, and would love to make a permanent switch to it. So, if anyone can help me get KTorrent for Windows to work for Windows 7 x64, I would greatly appreciate your help.
Side Note: I'm also upgrading my motherboard and processor from a P35 chipset with a Core 2 Duo to a P55 chipset & a quad-core i5-750 Lynnfield, so I'm going to re-install Windows 7 to make sure there aren't any stability problems with just swapping out the motherboard and trying to keep the same OS install. This means I'll be away from the site and seeding my torrents for around a day or more, depending on how busy I am.
|
