Jump to content

Firon

Established Members
  • Posts

    28,757
  • Joined

  • Last visited

Everything posted by Firon

  1. It's not just BitTorrent, it's P2P in general. In fact, it happens with ANYTHING that uses a lot of connections. DWKnight had problems since he ran a tracker on his, and after putting in the start-up script into the firmware, it worked great. Anyway, since there's SO many of these routers about, I thought it warranted making a sticky and mention in the FAQ, considering the severe problems the default firmware causes.
  2. That should be Linksys addressing the issue, but I'm not holding my breath. Apart from that, these routers are awesome (when you change the firmware), so it's kind of funny.
  3. PLEASE read this question in the FAQ... http://utorrent.com/faq.php#Special_note_for_users_with_Linksys_WRT54G_GL_GS_routers You MUST replace the firmware and followed the instructions in this section of the FAQ before complaining about speed or connectivity problems.
  4. We already know what the problem is dudeboyz, seems to be a Unicode-related issue.
  5. What exactly happens when you run build 364? Does it say Listen error, NAT Error, Network OK, or nothing in the status bar? Is DHT on? You behind a router? What does tracker status say? Is it showing a No Entry sign?
  6. http://www.utorrent.com/faq.php#Does_.C2.B5Torrent_have_an_embedded_tracker.3F
  7. You're on an old version mehral, the newest is build 364... numike: no, and it will never be fixed (not possible to). Just turn off diskio.flush_files OR don't use Google Desktop.
  8. apart from the fact that it I don't think it'll reduce memory use, since it's just wrapping UTF-8 internally to ANSI, you can try starting it with /ANSI an ANSI-only build will never happen. why? the bittorrent specification dictates that you must read/write strings as UTF-8 making it ANSI-only would actually violate the spec. since µT wraps UTF-8 to ANSI for non-unicode systems, but is still working internally as UTF-8, it doesn't violate the spec in providing this function.
  9. I crosspost since some people don't read the other thread
  10. hofshi: unicode related, makes µT work with different encoding fields when they're not set to UTF-8, for more compatibility.
  11. µTorrent 1.3 build 364 is out with some last minute fixes, please re-download or use the auto-update feature.
  12. Is the "Associate with .torrent files" button greyed out?
  13. hideto: Opera. dudeboyz: There probably was somewhere, but I think it was just IRC only and no one ever remembered to post it here.
  14. they're just "monitoring the channel" and "seeing what the channel is about" or somesuch
  15. Higher connects to peers faster. Experiment with it at your own risk.
  16. µTorrent 1.2.3-beta build 360 is out. Changelog - http://www.utorrent.com/download/beta/utorrent-beta-unicode-build-360.txt Download link - http://www.utorrent.com/download/beta/utorrent-beta-unicode-build-360.exe
  17. every windows reports a version number, there's probably a system call for it
  18. um, that's exactly what he wants to avoid...
  19. alayn, Redleer, muu, rafi, Markuz Nightwind: can you all test with this new beta build? http://www.utorrent.com/download/beta/utorrent-beta-unicode-build-359.exe
  20. I rather like the ninja cat idea, but I'm not sure if I like the tribal one more. I'll vote for both.
  21. If you went over 100 connections, this might explain it.
  22. Like everything's been used before. So what?
  23. Can you try with the beta again? What OS you on? Which service pack? And next time you should write down what the BSOD says if it happens again.
×
×
  • Create New...