![]() ![]() So I control-alt-deleted to bring up the Task Manager and clicked on the processes tab to see what is eating up my CPU. I attempted to shut down some background programs to speed up my computer but that didn't help. ![]() When I am downloading something big on Azureus lasting a couple of days, I noticed that my computer is running slower than usual. For this reason, I actually preferred using Azureus rather than ABC, only because my computer is powerful enough! I have used ABC, Azureus, and Bit-Comet.įor user-friendliness, Azureus is better than ABC but not Bit-Comet. Having used three different Bit-torrent clients, I have concluded that Azureus is the worst of the bit-torrent clients. No wonder the leech bug hasn't been fixed. ![]() So not only does he have the hardware with the problem, but he can now reproduce the problem himself, see what's causing it and fix it. "woo! my K6 266 only have 32M memory(still in use ^_^), yours has such a large memory." Only a small thing, but the Client is running just fine on it" This is shown, when I run BitComet on my old PC which has an AMD K6 266mhz MMX His last post was: Thu 8:22 pm, the last version of BitComet 0.57 was released on and there isn't even any new beta versions to try and fix the problems: In the BitComet forums at the developer hasn't posted a fix or some kind update status as to when the tracker bugs will be fixed. can send in a fix because anyone can download the source code. Azureus once got banned from trackers too but the developer fixed it ages ago, probably because it's open-source and things get fixed alot quicker if there is a decent number of devs or someone who isn't even a dev. This isn't Azureus's problem, it's Sun's problem because they make Java, so complain to them for the memory problems, here's their forums: īitComet is great if you are a leech or like getting banned from as many trackers as possible. I run Azureus on an AMD K6-2 550 cpu with 512mb RAM running WinXP and the main resource problems I have with Azureus is javaw.exe 's RAM usage.Īzureus.exe and Javaw.exe should use hardly any CPU at all if your system is configured properly. If you are having high cpu troubles then make sure you are using the latest Java Run Time Environment from It should be version 1.5 update 2. It's the javaw.exe which Azureus needs to run which uses the most system resources. Azureus itself uses very little cpu and ram. The only bad thing about Azureus is Java. Transmission is another, as is Deluge.Azureus has the best multi-torrent GUI, the most features, the best speeds and the best performance behind a NAT Firewall (BitComet is nothing but a leech client and it's so called NAT Traversal blows, I've done speed tests with Azureus, BitComet and Bit Tornado and Azureus blew the other two away). There are many free and open source solutions out there. And your antivirus has picked it up and instead of dealing with the threat individually has dealt with the program sending and receiving the data. Or, it could be the traffic going through the torrent client. Moreover it's annoying stuff like bunded software you didn't want and/or stuff that does shady things in the background like collecting information etc. They might throw in suspicious stuff that gets picked up by antivirus. It's happens a lot with lots of originally really good software. ![]() It's not uncommon for developers to sell out and have their software bundled with crap. The applications themselves are usually clean and well packaged. And this is where lots of people get confused. Antivirus won't flag P2P clients just because they are known to download illegal stuff and therefore more likely to also be linked to malware. If your P2P application is being flagged by antivirus then you've got issues. I can't remember exactly but they began pushing additional software in installation and I believe there was a substantial drop in users after these changes. I stopped using Azereus a while ago after they got taken over. Therefore you can revert the changes by adding exceptions and restoring the files that have been removed. The changes made after Windows Defender takes action should not be permanent. ![]()
0 Comments
Leave a Reply. |