JackR

Established Members
  • Content Count

    28
  • Joined

  • Last visited

Posts posted by JackR


  1. Hello,

    Some users said they could not download some torrent because they got this error: "Get string too short." (input_length < 60)

    We checked by Wireshark and we found out, the uTorrent cuts the first 10 character from the begin of the passkey. So this is that the uTorrent send:

    b33f5b392241183152d659/announce?info_hash=d%7d.%21%c9%d2%aa%0e%f3%1az%cc%2b%c4%f2g%aa%20%9d%f3&peer_id=-UT2210-%d6b%26d%9c%de7%ea%b8%7d%89%b4&port=25490&uploaded=0&downloaded=0&left=1600453368&corrupt=0&key=11DA2C22&event=started&numwant=200&compact=1&no_peer_id=1

    As you can see, the passkey only 22 character, not 32, BUT in the client it is 32 character, so the problem is in the sending.


  2. But it's not working only with 3.1.x! 3.0 or less it is still working! So I think it is uTorrent's fault. I think uTorrent 3.0 used signed integers too, and I think the nCore torrent site accept the signed and unsigned integers both. So it will be an uTorrent's bug.


  3. A lots of tracker do not accept the signed integers. Why it is necessary in 3.1.x to use signed integers? So many users can not upload because of this stupid thing. If the 3.0 and less already worked only with unsigned integers, why it is necessary to use signed integers?


  4. When will you fix this bug?

    The torrents which made by uTorrent 3.1.x we can not upload to some private torrent site (for example to the nCore, the biggest torrent site in Hungary)! Please do something! (The torrent sites said: "incorrect/invalid torrent file".)

    The upload is working with 3.0 or older uTorrent, but still not working with 3.1.x.

    Please fix the bug!

    The uTorrent 3.1 (beta) published in January and we still can not upload the torrents which made by uTorrent 3.1. Please fix!

    You make unnecessary updates again and again, but we can't download because of the disk load bug and we can't upload because of the bug that I wrote. Please think!


  5. No probleme with my hard drive, because no probleme with uTorrent 1.7.7. So it is the new uTorrent's fault.

    Yes' date=' 2.2.1 also good as I wrote, but it has some unnecessary functions.

    But 3+... the download with 3+ is a bad dream because of the disk bug.[/quote']

    dunno if this is your problem or not..do you know the actual speed of your hard drives?

    check this post, it may help..http://forum.utorrent.com/viewtopic.php?id=109018

    a faster hard drive might be the solution. but your pc has to be able to actually allow the speed too, as in it won't make any diff if you use a PII or PIII, 25-35mb per sec is useless


  6. I reinstalled my operating system x5 for 2010. This bug age ~ 1 years. And not only for me. I'm the member of the largest Hungarian torrent site and hundreds of people said they couldn't download normally with the new uTorrents because of the disk over bug. A lots of people installed 1.7.7 because of this.

    And if you type this to the forum search or Google: Disk Overload 100%

    You can see, tousand of people can't download because of the bug. The latest working version is 1.7.7. (or maybe 2.2.1).