fowl

oblig: What does in the new build mean? Specifically, what is the "upload-only extension"? Google returns this thread... Ta. I'd also note that this build is being pushed out by auto update, for those following along at home.

Yes, I understand what to do, but what I was pointing out that the confusion that would occur to non-beta (less technically adept) participant's

I meant the second uninstall entry. It is quite confusing to have two.

Perhaps it could clean up after itself? (I hope that it still supports per-user installation)

Ah, it's because 1.9 was in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\uTorrent and 2.0 was in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\uTorrent Not sure why. They both point to the main uTorrent.exe in program files so uninstalling either of them would break both.

I've noticed that I have two uTorrent entries in Add or Remove Programs, one for 1.9 and another for 2.0

It seems that bt.transp_disposition keeps getting set to 5 with no action on my part. I swear I've pressed the reset (sets it to 15) 3 or 4 times now. edit: It's the "Enable Bandwidth Management" box.

I've noticed that all of the text has gone gray for some reason.

Statistics box is still different to the one in options. Options one is at least internally consistant now, but is way lower than it should be (statistics looks OK). edit: talking about Transfer cap feature.

I haven't used µTorrent for 3 or 4 days (was shaped... ), and now the number of DHT nodes is hovering around 100, whereas normally it's at ~300. Is this normal/expected? PS. bt.tcp_rate_control kills my download speeds. My connection is so down biased that it really pains me to discover uTorrent thinks it's a good idea to limit downloads.

Transfer Cap figures are clearly incorrect. They are also different to the figures in the the statistics box. µTorrent 2.0 beta 16850, Windows 7 x86 RTM

Whole system crashes are indicative of a fault somewhere other than µTorrent, in fact even if it was directly µTorrent's fault it would still be a bug in the operating system. Could be hardware failure of some kind (for example overheating), or just a badly written driver. Try updating your network card drivers, and uninstalling (not disabling!) any 3rd party firewall or 'security' software you might have.

I would like to know if there is any response to my questions from back here: http://forum.utorrent.com/viewtopic.php?pid=410484#p410484 Specifically around the meaning of net.utp_target_delay

Is this an expected error? (Windows 7 RTM, Windows Firewall)

I really like the current (well I'm using the last 1.9 alpha as I find it more stable, shockingly enough) behaviour desirable. If I were in different circumstances (eg. counted uploads) however, it would be disastrous if it were not configurable. I have no idea about how to describe the feature as it stands however. (but I do like it)

What does this mean? (Still getting constant "Out of memory" + hang)

@superdupont Disable net.calc_overhead if you don't like it. (all this stuff was discussed back in the 1.9 thread)

Oh of course, I was just pointing out that µTorrent auto-update is not the only place where the signature is checked. (I use Firefox btw)

I think you'll find that my browser correctly uses the attachment api and tells the shell to verify the signature... which it does!

Still hangs for me on w7 (RTM x86) Got a taskmanager dump if it is any help, mention if it is because it took /ages/ to upload. http://www.mediafire.com/file/othtm2n0mqa/uTorrent.rar This time it was without a visible error dialog and was while minimised with a forgotten speedguide: I have another that I can upload (also about 30MB) that displayed this: (reverting to 1.9alpha because I can't stand hangs like this every few minutes)

I found this dump from when I was using the beta: http://www.mediafire.com/file/mzgumgmylyy/uTorrent.exe.1476.rar

Got debugging tools installed and got a dump. http://www.mediafire.com/file/mwzy3xnnbdq/WER4E10.tmp.rar -- Ok, I'm reverting to the 1.9 alpha; this "beta" is just too unstable, even on my XP box.

Does uTorrent periodically retry when it fails to bind to the configured port? If it does, it doesn't look like it's working, otherwise, would be great if it did. (OT: if it said what process was holding the port, that would be really useful. Oh and a "try again" button...) The crashes seem more frequent when I'm actively interacting with my computer (not uTorrent), seems to crash every few hours when I'm using my computer, but can go overnight most of the time. -- On my newly installed copy of w7: I don't have dumps because I haven't installed Debugging Tools for Windows yet, and they were hangs, not crashes.

I got a crash too. http://www.mediafire.com/file/4tnaztzzuyv/16081-utorrent.7962.dmp and again http://www.mediafire.com/?itwowm5jclc When it restarts it fails to bind... and again http://www.mediafire.com/file/xx4dmdddkzz/16081-utorrent.3fcf.dmp

Just thought I'd add a data point to where it was going a little awry, so that it can be tweaked if need be. My connection definitely maxes out at 256kbs tho.