Jump to content

Lord Alderaan

µTorrent Helper
  • Posts

    2,418
  • Joined

  • Last visited

Everything posted by Lord Alderaan

  1. @kurahashi: Well as far as I know (and someone please correct me if I'm wrong) if the people in your LAN all have public IPs utorrent won't recognise them as local using that method. And your router will probably NOT send the Multicast packets over its WAN ethernet port (which is what you use to connect to the rest of your LAN). So effectively µtorrent has no way to determine which IP is local and which is not. You'd need a feature that has been talked about in various topics but afaik never requested in the Feature Request forum that allows you to manually define a certain public IP range as local.
  2. * LordAlderaan does the happy dance. Thanks for all the hard work. No beta-autoupdate?
  3. I actually rofled my ass off at Silverfire statement. I suffer from the same 'problem'.
  4. That is indeed strange behavior and would indicate a problem in the webui/µtorrent.
  5. @globetrotters1: Only thing I can think of is that somehow a cache somewhere is messing with the torrent list. Open up http://yourip:utorrentport/gui/?list=1 in a second tab or window. And try forcing it to refresh (Press F5) and then switch back to the webui tab/window and press F5 there and see if it fixes your list. @greenbull: Because WebUI isn't completed yet detailed errors are unavailable at this time.
  6. @globetrotters1: I think the timeout delay is browser based but not sure. As to your strange bug... that shouldn't happen. Can you reproduce the problem? @incith: Yay! Most people find the webui.zip placing thing out after asking about it here...
  7. Usually it picks up new data the next time. If it happens often it can be a couple of different structural reasons (connections overload of the modem/router, upload speed maxing out causing a long enough delay) but it could be numerous accidental reasons too. It can be both your current computer as the one running µtorrent.
  8. People its both the exact same thing. The server is contacted to see if there is a new version, the user will be asked to update and it downloads the new version and overwrites the old version with it. I don't see why you wouldn't be able to call this an 'auto-update' and/or a 'check for updates automatically' feature. Both terms easily apply to the functions workings and thus are indistinguishable. 'Auto-update' does not imply there will be no user input at all. For instance it is fairly common to (and does in this case) mean only the update process itself (in this case the download of the new exe, the overwriting of the old and the restart of µtorrent). So, please stop the bickering over the politically, morally, physically, psychologically, grammatically and ethically most correct wording of the feature (at least in this thread)
  9. Yep. Blank screen = Misplaced webui.zip in 90% of the cases.
  10. The 'first zip' you talk about is a rar. You should extract the rar and you shouldn't extract the zip. I know it sounds obnoxious but keep in mind that even though this BETA version of the webui is advertised to the masses on the front page of this website it is largely intended for the more experienced users at this time. Hopefully it will become less complicated with the -=>OVERDUE<=- newer versions.
  11. - Change: include all adapters in subnet search for local peers - Change: consider peers in reserved local ranges as local peers As far as I understand that it means that any IP that it can find on any network adapter is considered local as long as its in the local IP ranges regardless of it being in the same subnet, right? Local IP ranges: 10.0.0.0 – 10.255.255.255 172.16.0.0 – 172.31.255.255 192.168.0.0 – 192.168.255.255 @dAbReAkA: No your ISP buddies cannot be considered local peers. Your ISP is providing a very fine service indeed but right now µtorrent isn't able to work with that.
  12. admajic: Indeed sounds like your firewall messing with µtorrents update mechanism.
  13. @LilyMaster: I cannot reproduce that problem here with the newest (2465) build. Can you try renaming settings.dat and settings.dat.old and re-setup your client and see if it still happens?
  14. Normally it doesn't mess up. Sometimes it does (a new beta build combined with certain settings or an outside influence) and deleting it and start afresh in those cases is only a minor nuisance compared to trying to create a fix-all-posible-problems-that-could-occur-to-the-settings-files functionality. We like to say that this Beta is 'stable' and its only a matter of time before there will be a official 1.7 stable but the reality is that using beta's can cause (mostly minor) problems as this thread demonstrates. Prevent/cleaning up the mess is secondary to fixing the actual bugs and tuning the new functionalities. I'm sure the 1.7 final will have a neigh-to-nil chance of messing up the settings
  15. You can disable it in the preferences. Disable Check association on startup in the General preferences.
  16. @DenisCool: Write/Down remember all your settings, rename/delete settings.dat (and .old), restart µtorrent.
  17. quertiy: the Overload thing is just a symptom. The bug has something to do with the cache. If I remember correctly the problem may be that the Cache is filling at high speeds but doesn't write out equal speeds (or doesn't write out at all), then when the cache is full it wants to write so much at the same time it can't manage it and it overloads or something like that. I'm not really technically knowledgeable enough to know exactly what is going on but that is sort of the idea I got.
  18. Afaik there is a bug with the cache that causes a disk overload as soon as the cache is filled. There is a trick to prevent this problem. See this post (make sure you pause the torrent before the cache is full. This guy had set his cache way higher then 200MB) and try it, tell us if it helps. Read that whole topic for more info on this problem.
  19. @quertiy: Thats just plain stupid (I'm not saying you are!!). People who would want to use those IPs have no trouble whatsoever to find those IPs. Heck! they probably don't even use the IPs µtorrent shows, they probably don't even use µtorrent but their own special client. It's like closing your own eyes and then hope someone else doesn't see you. @quertiy & Ultima: From what I've seen in the topics its pretty obvious the high-speed disk overload problem is a bug and not caused by wrong cache settings. Luckily few people download over 1MB/s and there is sort off a workaround but it is annoying to implement.
  20. @saveTheRbtz: Weird that it helped before and doesn't help now. Maybe when deleting settings.dat helped it was a setting you forgot to turn on again. Can you try deleting settings.dat and run µtorrent without changing any setting. The problem could also be related to/caused by your cFosSpeed Driver traffic shaper. Try disabling/uninstalling it.
  21. SaveTheRbtz maybe deleting settings.dat might help. This will reset all your settings though, make a backup in case it doesn't help to quickly restore your current settings.
  22. "The powerful lightweight and efficient BitTorrent Client" Problem solved.
  23. Yeah pretty much. Although its still beta and a couple of options (detailed torrent information, adding trackers to a already loaded torrent) things are missing at this time.
  24. Misplaced webui.zip? Read the readme.txt carefully.
  25. @zazo14: Huh? @bethell & JayZJay: You need the webui.rar from the first post of this topic. In it is a readme.txt with information. Basically the webui allows you to remotely manage µtorrent from any computer with a browser and a internet connection.
×
×
  • Create New...