Cable Forum - View Single Post

KyleMac · 23-08-2004, 07:05

I fixed it, bit of an odd solution.

1. Tried shad0w's experimental client, same problem.
2. Uninstalled Azureus and shad0w's (making sure to delete any left over files in the install dir and Documents and Settings).
3. Reinstalled shad0w's, same problem.
4. Reinstalled Azureus, same problem.
5. Uninstalled both clients the same way as before.
6. Reinstalled Azureus. Didn't look like it would work, it was stuck at 1.1kb/s for a while, then 2.1kb/s, then 3.2kb/s, 4.2kb/s, 5.2kb/s... 20kb/s... 160kb/s. Anyone recognise that pattern?
7. Torrents that had an ETA of 1 day were finished in 10 minutes.

The reason? Well I can only guess it's because Azureus was running and downloading during the downtime. When my cable came back up, even though I had the same IP I had to reboot to get back on the net. My only assumption is that some setting changed and the BT clients didn't realise / Windows didn't tell the BT clients. Perhaps something was set to read only when Azureus was running.

23-08-2004, 07:05	#110
KyleMac Inactive Join Date: Aug 2004 Posts: 6	Re: [merged] NTL & BitTorrent I fixed it, bit of an odd solution. 1. Tried shad0w's experimental client, same problem. 2. Uninstalled Azureus and shad0w's (making sure to delete any left over files in the install dir and Documents and Settings). 3. Reinstalled shad0w's, same problem. 4. Reinstalled Azureus, same problem. 5. Uninstalled both clients the same way as before. 6. Reinstalled Azureus. Didn't look like it would work, it was stuck at 1.1kb/s for a while, then 2.1kb/s, then 3.2kb/s, 4.2kb/s, 5.2kb/s... 20kb/s... 160kb/s. Anyone recognise that pattern? 7. Torrents that had an ETA of 1 day were finished in 10 minutes. The reason? Well I can only guess it's because Azureus was running and downloading during the downtime. When my cable came back up, even though I had the same IP I had to reboot to get back on the net. My only assumption is that some setting changed and the BT clients didn't realise / Windows didn't tell the BT clients. Perhaps something was set to read only when Azureus was running.