brutlern Posted August 13, 2008 Report Share Posted August 13, 2008 utorrent 1.7.7 doesn't report any new versions available, which usually happens if the latest release is still beta. So is 1.8 final? And if it is, why won't the update notification pop-up? Link to comment Share on other sites More sharing options...
thelittlefire Posted August 13, 2008 Report Share Posted August 13, 2008 It is not an "automatic" system. Given some of the reports post-release with all the coverage, it's not auto-update material apparently They'll make it auto-updateable when they want to. If you want to get the latest release you can use http://utorrent.com/download.php Link to comment Share on other sites More sharing options...
brutlern Posted August 13, 2008 Author Report Share Posted August 13, 2008 I'll stick to 1.7.7 until it will be auto-updateable. Many trackers have strict rules against using any beta versions even RC versions. I just enabled the "auto-update to beta versions" and the version that pops up is RC6 and not final. Link to comment Share on other sites More sharing options...
thelittlefire Posted August 13, 2008 Report Share Posted August 13, 2008 indeed. There's continuing talk in the 1.8 release thread as well as the in-development thread.Even if you don't get the EXE, I'd recommend checking out the Manual which has been updated Link to comment Share on other sites More sharing options...
Guest Posted August 13, 2008 Report Share Posted August 13, 2008 Oh. I was just about to post the same thread Same here, sticking with .7.7 until I am sure there will be no (or when there are ) post-release bugfix version good work devs anyway Link to comment Share on other sites More sharing options...
okeee Posted August 13, 2008 Report Share Posted August 13, 2008 about version 1.8, will it soon be updated again? Link to comment Share on other sites More sharing options...
brutlern Posted August 13, 2008 Author Report Share Posted August 13, 2008 The only problem so far with 1.8 is that you have download it separately (can't update from 1.7.7) and the HTTP Error 400 is a real drag. I know it's a nod32 related issue but I shouldn't be forced to switch to nod32 3.0 just because the development team missed this little problem. I hope 1.8.1 will be out soon to address this issue. Link to comment Share on other sites More sharing options...
scruff Posted August 13, 2008 Report Share Posted August 13, 2008 I got the problem with the HTTP Error 400 with 1.8 on 2 sites but it works on another 10 or so so far so I was going to down grade back to 1.7.7 again but it is nolonger available for download. and as i only get the HTTP Error 400 on 2 torrent sites how could it be a nod32 problem? more likely that the trackers have an allowed clients list and have not yet included the latest release. but I have got some seeding to do as I just uploaded some large files and have not yet seeded them fully and there are a lot of peoples downloads stuck at 62%If I could down grade again I would be happy. I will have to search for 1.7.7 on e-mule, as far as I can tell thats the only way I can get everything to work again and finish what I started. If the 1.7.7 release could be shown on the µTorrent download page it would help people in my position immensely Link to comment Share on other sites More sharing options...
brutlern Posted August 13, 2008 Author Report Share Posted August 13, 2008 Here's a link for 1.7.7 http://download.utorrent.com/1.7.7/utorrent.exeHowever i managed to fix the http error 400 by adding utorrent to nod32 IMON Exclusion List, so I'm staying with 1.8 if no other issues come up.I've been running 1.8 for a few hours now and download is fine, upload is fine and no more errors. Link to comment Share on other sites More sharing options...
scruff Posted August 13, 2008 Report Share Posted August 13, 2008 Cheers Brutlern, I did as you did and its working now, Its still strange that it only affected 2 sites Link to comment Share on other sites More sharing options...
Firon Posted August 13, 2008 Report Share Posted August 13, 2008 HTTP 400 is a BUG WITH NOD32 2.7. NOD32'S OWN DEVELOPMENT TEAM ADMITTED THE ISSUE.But you don't have to switch, you just have to disable IMON or add utorrent to IMON's exceptions. Link to comment Share on other sites More sharing options...
brutlern Posted August 13, 2008 Author Report Share Posted August 13, 2008 True, Firon. I googled a bit and it is a nod32 issue. But there's no need to point fingers, everything works fine now. And yes, scruff, it is strange that only a few trackers present this problem. But I'm sure a new update on nod32 and/or utorrent and/or the trackers themselves will resolve this minor inconvenience. Somebody is bound to fix it eventually. 'Till then, IMON Exception List everyone! Link to comment Share on other sites More sharing options...
Firon Posted August 13, 2008 Report Share Posted August 13, 2008 2.7 is dead. It will never get fixed. They're on v3 now, which doesn't have IMON anymore.Not something we can fix on our part either. Link to comment Share on other sites More sharing options...
brutlern Posted August 14, 2008 Author Report Share Posted August 14, 2008 utorrent 1.8 is now available as auto-update. Thanks. (Which should convince everyone that 1.8 IS final, stable and not beta, for real :cool: ) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.