Differences

This shows you the differences between two versions of the page.

--- bitcomet_client_issues_and_possible_solutions [2010/08/16 04:44] – greywizard
+++ bitcomet_client_issues_and_possible_solutions [2015/08/15 04:21] (current) – external edit 127.0.0.1
@@ Line 35: / Line 35: @@
   This is not an exhaustive list of all the causes which might raise this error but of the
   most frequent. As a thumb rule, this error is related to disk writes mostly, so anything
-  that prevented BitComet from writing to disk would bring up this error
+  that prevented BitComet from writing to disk would bring up this error.
 ----
@@ Line 59: / Line 59: @@
     * //if the IP Address and the Default Gateway// are identical then **you do not use a router** and you can go to the [[create_firewall_rules|Create Firewall Rules guide]];
-    * //if the IP Address and Default Gateway// are not identical then **you may have a router** standing between you and your ISP and therefore besides the guide for creating firewall rules you'll also have to follow the instructions of the [[add_port_mapping_in_nat_router|Add Port Mapping in NAT Router guide]].
+    * //if the IP Address and Default Gateway// are not identical then **you may have a router** standing between you and your ISP and therefore **besides** the guide for creating firewall rules you'll **also** have to follow the instructions of the [[add_port_mapping_in_nat_router|Add Port Mapping in NAT Router guide]].
 The goal of these guides is to help you open the listening port of BitComet for incoming connections. When you succeed in doing that you will get rid of the yellow status light and your client will be able to run at maximum speed. That is, assuming your client is properly configured as described in the [[http://www.cometforums.com/topic/410-up-to-date-bitcomet-speed-guide/|BitComet settings guide]].
@@ Line 135: / Line 135: @@
 Starting with version **1.20**, BitComet is able to automatically import unfinished downloads of the **BitComet**, **uTorrent** and **Xunlei/Thunder** clients, which have their client's specific extensions appended to the unfinished files. If you intend to import any downloads from these clients, which use their specific file extension, then use //Method 2// from below.
-However, if your files have appended a different extension which is belonging to another unsupported client, then you will have to remove the appended extensions first, before importing the downloads into BitComet. If your torrent contains only 2-3 files you can easily do that manually.\\
+However, if your files have appended a different extension which is belonging to another unsupported client, then you will have to remove the appended extensions first, before importing the downloads into BitComet.\\ <html><span style=color:teal;font-weight:bold>Note:</span></html>
+  This operation is not necessary anymore for v.1.23 and above as BitComet can now import unfinished downloads from
+  any client. So, if you use v.1.23 or above, skip directly to "Method 2" below. If you're using a version prior to
+  v.1.23 read further on.
+If your torrent contains only 2-3 files you can easily do that manually.
 But if your torrent contains dozens or hundreds of files, then doing this manually would quickly become a REALLY tedious task and it would drive anyone insane.
 In order to avoid that you can download one of the many free utilities which allow you to change extensions for multiple files (such as [[http://download.cnet.com/Extension-Renamer/3000-2248_4-10438759.html|Extension Renamer]], [[http://www.analogx.com/contents/download/system/extchg/Freeware.htm|Extension Changer]], [[http://www.filetransit.com/view.php?id=6885|RenameIt]], [[http://www.softpedia.com/get/System/File-Management/Denis-Kozlov-ReNamer.shtml|Renamer]] or use an Internet search to find a lot others) or use a batch script such as the one you can find [[http://www.bittorrent.com/btusers/guides/bittorrent-user-manual/chapter-03-advanced-guides/switching-another-client#Removing_Extra_Extensions|here]].
@@ Line 152: / Line 156: @@
 Starting with **v.1.20** you are able to do this automatically through the //File -> Import Unfinished Download...// menu for unfinished downloads of **BitComet**, **µTorrent** and **Xunlei** clients, so far. You can read detailed instructions on how to do that, here: [[bitcomet_main_menus#import|Import Unfinished Download]].
-<html><span style=color:teal;font-weight:bold>Note:</span></html> If your unfinished downloads didn't have any extensions appended (i.e. the previous client wasn't set to append a specific extension to unfinished files) then you won't be able to always successfully import the downloads into BitComet by using //Method 2// (i.e. for single-file torrents you won't be able to select the file and for both single and multi file torrents BitComet won't be able to automatically detect the location of the .torrent file). In this case it's recommended that you use //Method 1// to import your downloads.
+<html><span style=color:teal;font-weight:bold>Note:</span></html> If your unfinished downloads didn't have any extensions appended (i.e. the previous client wasn't set to append a specific extension to unfinished files) then you won't be able to always successfully import the downloads into BitComet by using //Method 2// (i.e. for single-file torrents you won't be able to select the file and for both single and multi file torrents BitComet won't be able to automatically detect the location of the .torrent file). In this case it's recommended that you use //Method 1// to import your downloads.\\
+<html><span style=color:teal;font-weight:bold>UPDATE:</span></html> Starting with v.1.23 BitComet is capable of importing downloads from other clients as well (with specific extensions appended or with no extension appended). You'll have to choose //All files// in the drop-down box where you can choose the extension type, in the //Import Unfinished Download// dialog. The only difference will be that BitComet will not try to automatically locate the .torrent file, since it doesn't know the previous downloading application and therefore it has no way of knowing where the .torrent files for that application reside. Therefore you'll have to manually point it to the location of the .torrent file, by choosing //Use specified .torrent// in the importing dialog.
 ----
@@ Line 174: / Line 179: @@
 You can and must impose an upper limit on the global upload bandwidth that BitComet is allowed to use. The limit must be large enough to permit good upload speed for each task you are running, yet small enough that other applications have enough bandwidth to get their jobs done.
-Practically, this means you must find out what your actual upstream bandwidth is, and then set your Global Maximum Upload Bandwidth in BC to about 80% of that maximum. (Don't rely on what your internet service provider told you your speed was: test it, with nothing else using any part of it, at [[http://www.speedtest.net/|speedtest.net]] or a service fairly nearby, and do it at different times of day and night on different days, to get a reliable average value.)
+Practically, this means you must find out what your actual upstream bandwidth is, and then set your Global Maximum Upload Bandwidth in BC to about 80% of that maximum. (Don't rely on what your internet service provider told you your speed was: test it, with nothing else using any part of it, at [[http://www.speedtest.net/|speedtest.net]] or a service fairly nearby, and do it at different times of day and night on different days, to get a reliable average value.) You will need to make sure you transform K**b** in K**B** (a division by 8 will pretty much cover it), then multiply it with 0.8 and input the result on the [[bitcomet_options#connection|BitComet Options --> Connection]] page, in the "//Global Max Upload Rate//" box.
 When you aren't using any other applications, you still **can't** leave your GMUB unlimited, because BitComet will even interfere with itself, dropping packets in the same way. You can increase the rate, but remember to decrease it again when you want to do other things.\\ <html><br /></html>
@@ Line 187: / Line 192: @@
 Setting your global maximum upload bandwidth very low means you effectively won't be downloading anything before next Kwanza. Set your GMUB back to the 80% that we recommend, then shut down and restart BitComet, and your speed will come back to normal. //("Now calmly think about supposed leechers for a few moments, and you will be enlightened, Chinchbug".)//
+----
+==== When BitComet is running my router/modem reboots itself or freezes. Why is this happening and what can I do to fix this? ====
+**A little theory first.**
+All BitTorrent clients, by the design of the BitTorrent protocol, work by opening simultaneous connections to a very high number of peers. BitComet is no exception from this axiom.
+This very high number of simultaneous connections to different IP addresses, will have to be handled by your system and your networking equipment (modem, router). That is to say, BitTorrent clients place a higher stress on certain components (software and hardware) both in your system and in the devices connecting you to the Internet.\\
+While this is no bad thing in itself, if often may bring to surface hardware or software limitations, flaws or conflicts which otherwise don't manifest themselves and rest unbeknown to the user.
+This is one such example.\\
+The main issue here, is related to a technology employed by your router/modem, called NAT (Network Address Translation).
+In short, what this does for you is allowing you to use multiple devices in your personal home LAN (Local Area Network), while having/paying only for one single public IP address to connect to the global network known as the Internet.\\
+NAT does this by translating the private IP addresses used by the devices in your LAN (PCs, servers, etc.) to the public IP address (which your ISP assigns to you), for all the outgoing traffic of your network, and vice-verse, translating the public IP to the private IP addresses each device on your LAN uses, for all incoming traffic going to any of your local devices.
+It doesn't matter if you have only one PC connected to the router, it doesn't care about that. As long as NAT is enabled it will do it's job and translate addresses.
+The NAT process does that by using a //NAT session table// which keeps tabs of which port is mapped to which local IP address, so that it may forward incoming reply traffic to the proper local device on the LAN.
+As you may have guessed, this NAT table is hosted into the router's memory and as we all know, memory is a limited and expensive resource. Depending on the brand and the model of your router/modem, your equipment will be able to hold various maximum numbers of simultaneous entries depending on the amount of memory allotted to it.
+While better equipments have no problem in handling the great number of connections initiated by a BitTorrent client, others do. This isn't to say that the respective device is a bad one per se (it will probably work OK in most other situations), it's just not fit for handling BitTorrent traffic.
+To make a long story short, when this issue occurs the NAT table becomes filled up with entries, while your BitComet client is running, and can't handle any more new connections.
+While some better routers (of the lot of those who can't support too many connections) handle this situation gracefully by dropping outgoing packets for new connections, until such time an entry times out in the NAT table, other worse equipments stutter and crash or entirely freeze into a state where they may need a manual reboot, to get back on feet.
+On top of that running BitTorrent client may keep initiating many new connections for a long time (especially when downloading) therefore even if your device doesn't crash, you may experience a total inability to access the Internet with any other application, or from other computers in your LAN (however this effect may have also a different cause; see the [[bitcomet_client_issues_and_possible_solutions#all_my_other_internet_applications_either_slow_down_or_say_they_can_t_connect_when_i_use_bitcomet_what_s_going_on_and_how_can_i_fix_this|previous topic]] for details on that).
+**What can you do to fix this?**
+The first and best option would be to find an equipment which doesn't have this limitation (buy, trade or swap your actual one for it).
+If that's is not an option for you at present time, then there are some measures you could try to contain this.
+  - If you have LT-Seeding enabled in your client, make sure that you go to [[bitcomet_options#advanced|Options-->Advanced]] and change the value of the //bittorrent.connection_ltseed_protocol_selection// option to **0** instead of the default 2. This will force BitComet to use only TCP as a transport protocol for LT-Seeding connections.\\
+   - Next, set the //network.max_connections// option to a conservative value such as 200, for starters. This will limit the number of simultaneous TCP connections maintained by BitComet, to whatever value you set for this option, and in turn reduce the number of entries which BitComet may place in the NAT table, by the use of TCP connections.
+  - (Optional) If you're using Windows XP, you may also want to set the number of maximum embryonic connections allowed by Windows to something a little higher than the default 10 (by using the [[bitcomet_options#tcp_ip_limit|TCP/IP Limit]] option in BitComet to set it at something like 20) and then make sure that the //network.max_connecting_connections// option is set to something lower than that (the default 10 should be OK).
+  - Another thing you might want to watch out for is the number of simultaneous running tasks BitComet has, since incoming TCP connections and UDP traffic for each additional task cannot be stopped before reaching the router so each different IP source will create a new entry in the NAT table. Starting out with 1-2 running tasks in total (both downloading and seeding) might be a good place to begin, along with all the above measures if you encounter this type of issue.
+  - If after doing all the above your problem still isn't solved, then it means that the culprit here is probably the UDP transport protocol. BitComet may communicate with very large number of different IPs using UDP, on account of DHT and Torrent Exchange messages which use UDP as a transport protocol. Each UDP datagram outgoing towards a different IP address will create a new entry in the NAT table of your router as well as each new IP address sending a datagram towards you, so your router's NAT table can easily become cluttered simply on account of UDP traffic even though the traffic volume in itself may not be very high, necessarily.\\
+An option in BitComet, that you can use to contain this effect, is //network.max_udp_pkt_per_sec// which will limit the maximum number of UDP datagrams which BitComet may send per second. Setting this value to a conservative value, such as 5 will limit the max number of new entries which BitComet can create through UDP, in the NAT table of your router, to 300 new entries per minute.
+Summed with the 200 you set for TCP, this will give a max number of 500 entries BitComet can place any minute in the NAT table, on behalf of outgoing traffic.
+If the above settings work for you, then you should start to gradually increase the values until you find some values which make the issue re-appear and then stay below that threshold. For instance, you may try to first increase the number of TCP connections, by a increment of 50 or even lower and then test your router for a while and see how it works. Do this until you get to a value of 500-800 and if nothing goes wrong stop there.\\
+Then, once you found a number of TCP connections where your router is stable you can start increasing the number of UDP packets per second, by small increments of 5 or lower and again test your router. Once you've found a value which makes your router crash/freeze, go back a couple of increments and let the option set at that value, to keep yourself in the safe zone.
+If on the contrary, the above said settings don't work for you, you may try even more conservative settings or you may consider even disabling DHT altogether, to alleviate this problem.
 ----
@@ Line 212: / Line 266: @@
 ==== Tasks have disappeared/deleted tasks reappeared in my tasklist after a BitComet restart. How can I fix this? ====
+__**A little introduction:**__\\
 BitComet <html><span style="color:navy; font-weight:bold">writes</span></html> its [[bitcomet_task_list|Task List]] (whenever there is a change in the task list or when it exits) into a file named //**downloads.xml**// located in one of several places. (Which place, depends on the version of BitComet and your operating system.)
@@ Line 218: / Line 273: @@
 //**C:\Program Files\BitComet**//
-directory for **Windows XP** and earlier Windows versions, or
+directory, under **Windows XP** and earlier Windows versions, or
 //**C:\Users\%userprofile%\AppData\Local\VirtualStore\Program Files\BitComet**//
@@ Line 242: / Line 297: @@
 under **Windows Vista** or later.
-Therefore, starting with version 1.18 you may also find this file along with all the other configuration files in the //**Application Data\BitComet**// (Windows XP) or in the //**AppData\Roaming\BitComet**// (Windows Vista or later) folder.
+Therefore, starting with version 1.18 you may also find this file along with all the other configuration files in the //**Application Data\BitComet**// (Windows XP) or in the //**AppData\Roaming\BitComet**// (Windows Vista or later) folder alternatively to the //Program Files// folder.
 But this should happen only for clean installations of BitComet; for upgrades over an existing version the default behavior of the client is to seek the configuration files and use the previous location for further storing them. For more detailed info on the conditions when this happens see [[files_used_by_bitcomet#configuration_files_location_changes_since_v118|this topic]].\\
-Also, starting with v.1.18 BitComet saves up to 7 successive copies of the //downloads.xml.bak// file (in the form //downloads.xml.yyyymmdd.bak//, where //yyyymmdd = year, month, day// when the file was saved) thus making it much easier to recover a lost tasklist.\\
+Also, starting with v.1.18 BitComet saves up to 7 successive copies of the //downloads.xml.bak// file (in the form //downloads.xml.yyyymmdd.bak//, where //yyyymmdd = year, month, day// when the file was saved) thus making the recovery of a lost tasklist as easy as removing the //.yyyymmdd.bak// part from any of the backup files present in the same folder.\\
 (Now, be sensible about this. If this is a new installation, yes, of course the files will be in those locations. But if this is an UPGRADE -- you've been running BitComet for a long time and your previous operating system was (or still is) XP, then all the configuration files could still be in the OLD location*. When you install a new version of BC over the old version, it keeps all of the old settings including this one. )
 When BC starts up again it tries to <html><span style="color:navy; font-weight:bold">read</span></html> this file and loads the tasklist from //downloads.xml//, using the torrent copies that it keeps in the **\Torrents** folder, also off of the program directory.\\
-Anything that interferes with any part of the whole write/read sequence, will generate these kinds of problems.\\
+Anything that interferes with any part of the whole write-read sequence, will generate these kinds of problems.\\
-If the file can't be written, then old, deleted tasks will still be in it. If it's missing or empty then BC can't read what isn't there. If the file is set to "read-only", then BC can't update it, so when it reads the file at restart it gets an old version of the list -- tasks started since won't be there and old tasks still will be -- none of the changes either way got saved. If your system or BitComet crashes before writing into the file, any changes made to it will be lost or the entire file may become corrupted.
+If the file can't be written, then old, deleted tasks will still be in it and also the newly added ones won't be added in it. If it's missing or empty then BC can't read what isn't there. If the file is set to "read-only", then BC can't update it, so when it reads the file at restart it gets an old version of the list -- tasks added since won't be there and old tasks still will be -- none of the changes either way, got saved. If your system or BitComet crashes before writing into the file, any changes made to it will be lost or the entire file may become corrupted.
 Sometimes, even a version update may result in a missing tasks file. Also, a Windows upgrade may often result in problems with the tasks file, due to the data virtualization feature of the newer operating systems.
   This is why it's always a good idea to back up your tasklist before performing any upgrades to your client or your
-  Windows version, especially when using BitComet versions prior to v.1.18.
+  Windows installation, especially when using BitComet versions prior to v.1.18.
   See how to do that, at the end of this topic.
@@ Line 262: / Line 317: @@
     * Make sure the //downloads.xml// is not read-only;
-**Ways to recover the tasklist:**
+__**Ways to recover the tasklist:**__
-Do not add or delete any tasks. Doing that WILL make method #1 below, useless (for reasons we trust are obvious), and it will interfere with the others;\\
+Do not add or delete any tasks. Doing that WILL make method #2 below, useless (for reasons we trust are obvious), and it will interfere with the others;\\
-  - If your version is v.1.18 or above (or in case you upgraded, if your previous version was v.1.18 or above), then recovering your tasklist is just a matter of renaming one of the .bak files (you can start with the most recent one) to //downloads.xml// (they should be present in the same folder as //downloads.xml//).
+  - If your version is v.1.18 or above (or in case you upgraded, if your previous version was v.1.18 or above), then recovering your tasklist is just a matter of deleting the current //downloads.xml// file and renaming one of the .bak files (you can start with the most recent one) to //downloads.xml// (they should be present in the same folder as //downloads.xml//).
   - If your version is v.1.07 or above but below v.1.18 (or in case you upgraded, if your previous version was v.1.07 or above), try the backup file: see if there is a //downloads.xml.bak// file in the program directory described in the above sections. Delete the //downloads.xml// file and rename //downloads.xml.bak// to //downloads.xml//. Now start Bitcomet and see if the task list is correct or more nearly correct.
-  - Check the [[torrent_history|Torrent History]] (or [[torrent_share_and_torrent_archive#torrent_archive|Torrent Archive]] in BitComet v.1.16 or the older). The Torrent History may have all of your previously downloaded torrents, unless you disabled this feature or deleted that torrent from the history list... Select the torrents that existed as tasks before your BitComet shutdown, one by one. Double-click the selected torrent and a popup dialog will warn: "The task you want to view is removed, do you want to download again? " Click "Yes" and choose the same destination for the downloaded file and click "Download now" to continue. BitComet will do a hash-check automatically then and after the hash-check is finished, BitComet will start downloading those unfinished tasks.
+  - Check the [[torrent_history|Torrent History]] (or [[torrent_share_and_torrent_archive#torrent_archive|Torrent Archive]] in BitComet v.1.16 or the older). The Torrent History may have all of your previously downloaded torrents, unless you disabled this feature or deleted that torrent from the history list... Select the torrents that existed as tasks before your BitComet shutdown, one by one (starting with v.1.23 you can select multiple torrents and add them with one single command from the right-click context menu: //Add to TaskList...//). Double-click the selected torrent and a popup dialog will warn: "The task you want to view is removed, do you want to download again? " Click "Yes" and choose the same destination for the download as the one where the files for that torrent reside, and click "Download now" to continue. BitComet will do a hash-check automatically then and after the hash-check is finished, it will start downloading those unfinished tasks or seeding if they were finished.
   - Try recreating the task list from the **\Torrents** subfolder. BitComet keeps copies of the torrents for current tasks, in this folder. Copy the entire folder somewhere else for backup. Try to re-add each torrent as a new task, making sure to hash-check it after you add it but before you start it. You *should* be able to recover your entire task list this way.
   - If none of the above applies to you and all you have is the unfinished downloaded files, then you'll have to go about it the hard way. Head to the index sites where you downloaded the torrents the first time, and download the exact same .torrent files (they need to be the ones with the same [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#infohash|info-hash]]) and add them to your Task List again. Upon adding make sure that you point each task's download path to the folder where its unfinished files reside. It should automatically hash-check and pick up where it left. If that doesn't happen, then stop the task, perform a manual hash-check and restart it again.
@@ Line 292: / Line 347: @@
 ==== Why is the speed displayed in the Task List for my task(s), different from the ones BitComet shows in other areas? ====
+Also
+===Why can I see BitComet uploading when there are no active tasks?===
 This might be easier observed when you have no tasks running or you have a single task running in BitComet.
 The usual places where one can observe this different speeds, are: BitComet's [[bitcomet_main_window|title bar]], [[bitcomet_floating_window|Floating Window]] and the [[bitcomet_detailed_info_pane#statistics|Statistics]] tab.
-If you have no tasks running and still, you can see some small traffic reported in these areas, then it means that you are seeing numbers which account for the overhead protocol traffic which BitComet uses for operating (i.e. TCP, BitTorrent, HTTP, FTP, DHT).
+If you have no tasks running and still, you can see some //small// traffic reported in these areas, then it means that you are seeing numbers which account for the overhead protocol traffic which BitComet uses for operating (i.e. TCP, BitTorrent, HTTP, FTP, DHT).
-If you see higher upload speeds and still have no tasks running or you do have something running but the speeds you see for your task(s) in the Task List pane are different from the ones you can see in the other areas, then you should know that the upload speeds reported in the Task List pane are just those used for BitTorrent uploading.
+If you see //higher// upload speeds and still have no tasks running or you do have something running but the speeds you see for your task(s) in the [[bitcomet_task_list|Task List]] pane are different from the ones you can see in the other areas, then you should know that the upload speeds reported in the Task List pane are just those used for [[bittorrent|BitTorrent]] uploading.
-In the rest of the areas, BitComet adds to those speeds the LT-Seeding speeds as well (and the overhead traffic). Therefore the total speeds you will see might differ more or less from the sum of the speeds of all tasks in the Task List pane.
+In the rest of the areas, BitComet adds to those speeds the [[long-term_seeding|LT-Seeding]] speeds as well (and the overhead traffic). Therefore the total speeds you will see might differ more or less from the sum of the speeds of all tasks in the Task List pane.
 ==== What shall I do when BitComet failed to save task list and unfinished torrents? ====
@@ Line 310: / Line 367: @@
 If it's not then recheck the %appdata% permissions -- often you need to check all the permissions for the entire tree and every node in it. The account you usually run BitComet under - normally your own - should own the directory and files, and have full control of both.
+==== How can I transfer all my tasks to another computer? ====
+If you wish to move all your tasks (active and/or stopped) to a new computer and hence to a new installation of BitComet you will have to follow a few easy steps:
+    - Copy the current BitComet download folder (the folder which holds the files for each task) onto the new computer and make sure that it resides in a partition which has the same letter as the previous one (i.e. if your current download folder is //D:\BitComet Downloads// then make sure you move BitComet Downloads on the D:\ partition of the new computer.\\ If you don't have a partition with the same letter on the new computer then you'll have to move all the tasks from within BitComet (select the tasks, right-click and choose //File Move To//) into a folder on the current computer whose path **can** be replicated on the new one and you'll have to do this **prior** to moving the files to the new computer or exporting the tasklist. (E.g. if your download folder on the current computer is //D:\BC_Downloads// but you'll only have a //C:\// partition on the new computer (bad idea by the way) then you'll have to move all your tasks into //C:\BC_Downloads// on the **current** computer **prior** to moving the folder on the new computer. This ensures that each task points toward the right path, not towards an inexistent one, on the new PC.
+  - Go to the //File// menu and choose //Import and Export Download List...//. In the lower section named "Export" click on the ellipsis button and choose a filename and location for the backup file. Make sure that the "Export all tasks" radio button is selected before hitting the //Export// button. This will create a backup copy of the tasklist and BitComet settings into a backup file.
+  - Select all the tasks in the Task List of BitComet and then right click and choose //Save Torrent As// and save all the .torrent files into a location of your choice.
+  - Make sure that in your new installation of BitComet the variable //system.use_app_data// is set to TRUE into //Options-->Advanced//.
+  - Open a new Explorer window and type in the address bar //%appdata%\BitComet\torrents// then hit Enter. You should find yourself into the //\torrents// folder of the new BitComet installation. Copy in here all the .torrent files that you saved in Step 3.
+  - Go into the //File-->Import and Export Download List...// and into the upper section called Import choose the backup file which you saved in Step 2. After BitComet finishes importing the list, you should be done and have an identical completely functional list of tasks as on the old computer.
 ----
 -[[understanding_bitcomet|Previous Page]] -[[configuration_and_user_settings|Next Page]]\\
 -[[start|Main Index]]

A free C++ BitTorrent/HTTP/FTP Download Client

Differences