This shows you the differences between two versions of the page.
bitcomet_client_issues_and_possible_solutions [2012/08/09 15:17] greywizard [When BitComet is running my router/modem reboots itself or freezes. Why is this happening and what can I do to fix this?] - Added point nr.4 in list |
bitcomet_client_issues_and_possible_solutions [2015/08/15 04:21] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== BitComet Client Issues and Possible Solutions ===== | ||
- | ==== What's this red cross that appears next to my torrent? ==== | ||
- | |||
- | {{: | ||
- | |||
- | This red cross basically means that BitComet cannot continue downloading this torrent into your download directory because any of the following **reasons**: | ||
- | |||
- | - You are trying to download a file over 4G to a FAT32 disk drive. | ||
- | - There is insufficient space on the drive where your Download Directory resides, to save the file(s) you are trying to download. | ||
- | - The // | ||
- | - The // | ||
- | - BitComet can't find the download path (e.g. the download folder was on an external drive). | ||
- | - The path to the torrent task's file(s) contains illegal characters (i.e the torrent was created under Macintosh or *nix). | ||
- | - You have two or more torrent tasks running, which are trying to write in the same directory a file with the same filename. | ||
- | - BitComet can't write to the download folder (e.g. it's running under an account without writing permissions or permissions have been changed). | ||
- | - The file(s)/ | ||
- | - The file is locked by another application/ | ||
- | - The Download Directory for your BitComet client may be corrupt or your hard disk has suffered a hardware failure resulting in bad sectors which cause write-check to fail. | ||
- | |||
- | **Solution: | ||
- | |||
- | - This is due to FAT32 limitations (the largest single file can only be 4G), you can convert to NTFS disk format and then re-download or change destination to another NTFS disk drive. | ||
- | - Increase the free space available for BitComet' | ||
- | - Read about [[torrent_exchange|Torrent Exchange]]. | ||
- | - Switch to [[torrent_history|Torrent History]] ([[torrent_share_and_torrent_archive# | ||
- | - If you use an external drive for the download folder, make sure it's connected and that it's got assigned the same drive letter. Make sure that Windows recognizes and assigns a drive letter to the hard drive partition where the download folder resides. Make sure the partition was not hidden by some other application. If it was a mounted partition make sure it is still mounted. If it was a mapped network drive make sure the mapping is permanent. | ||
- | - Use an application for invalid filenames renaming, such as MacNames, to rename the file/ | ||
- | - Stop the running tasks and change the download directory for any of the tasks, to another folder. | ||
- | - Make sure BitComet has writing permissions on the download folder. | ||
- | - Make sure the torrent' | ||
- | - Close the application/ | ||
- | - Change download directory to another folder, run a file system check and make sure your hardware works fine. | ||
- | |||
- | 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. | ||
- | |||
- | ---- | ||
- | |||
- | ==== I have a yellow status light, and my download speeds are slow. What should I do? ==== | ||
- | === It says my firewall is blocking BitComet, but I allowed BitComet as an exception. What's up? === | ||
- | |||
- | If the [[bitcomet_status_bar|status light]] on the right hand lower corner of BitComet' | ||
- | |||
- | Adding BitComet to your software firewall permits BitComet to send outgoing traffic (and replies to it) through the firewall to the Internet. That's necessary but it's only half of the job. You must also open your designated listen port on all of your firewalls, to permit new INCOMING traffic through. That's what we're concerned with now. | ||
- | |||
- | Having a firewall is a good thing since it protects you from the whole plethora of dangers lurking in the dark corners of the world-wide network. In fact you should never connect to the Internet without a working firewall; you'll most likely get infected in a matter of minutes. But in order to make BitComet work (or any BitTorrent client for that matter) you'll need to make some adjustments. | ||
- | |||
- | If you're reading this topic, I'm going to assume that you don't know very much about networking so let's get our hands dirty. First of all you have to determine **what** is blocking your incoming connections. In order to do that, first answer yourself this question: "Do I have a router?" | ||
- | |||
- | If you don't know the answer to that question then do this: | ||
- | |||
- | * press the " | ||
- | * type //cmd// in the box and hit Enter; | ||
- | * at the command prompt type // | ||
- | |||
- | {{: | ||
- | |||
- | * //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]]. | ||
- | |||
- | 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:// | ||
- | |||
- | ---- | ||
- | |||
- | ==== What is DHT? Why is BitComet telling me, “DHT not Connected”, | ||
- | |||
- | // | ||
- | |||
- | === How come I have "DHT not connected"? | ||
- | |||
- | **Solution 1** | ||
- | |||
- | * Open BitComet, click Options -> Advanced -> Connection -> UNCHECK Enable DHT Network -> Click OK | ||
- | * Close BitComet to allow saved changes to take place. | ||
- | * Reboot PC if possible. | ||
- | * Open BitComet, click Options -> Advanced -> Connection -> CHECK Enable DHT Network -> Click OK | ||
- | * Look at the status of the DHT network at the bottom right hand corner. | ||
- | |||
- | Refer to solution 2 if solution 1 doesn' | ||
- | |||
- | **Solution 2** | ||
- | |||
- | **A: If you use a router, follow the steps below. If you do not use a router, proceed to B.**\\ | ||
- | * Open your Router Webpage (e.g. 192.168.2.1) | ||
- | * Open the Router Page which controls all the forwarding of Ports. | ||
- | * Next, create a new rule, for a UDP Virtual Server type entry. (In other words, in addition to the TCP Portforwarding done for BitComet, you will need to create an EXACT replica of that rule, except it isn't TCP, but UDP) | ||
- | * Ensure that the UDP Port is exactly the same as your TCP Port. (TCP & UDP Ports should be exactly identical to [[http:// | ||
- | * Continue on to B if you use a Firewall in addition to your Router. | ||
- | |||
- | **B: If you use a software firewall, follow the steps below**\\ | ||
- | * Open your firewall' | ||
- | * Locate BitComet.exe (by default: C: Program Files/ | ||
- | * Add it into your firewall' | ||
- | * Add in exactly the same port used as in your listening port. (Once again, this should also be the same as your TCP Port). | ||
- | * Make sure your firewall rule updates for use with new versions when you update BitComet. Better firewalls such as McAfee do this automatically. | ||
- | |||
- | **For Windows Firewall only users:** | ||
- | |||
- | * People who use Windows XP SP-2 firewall need to make sure exceptions are allowed. | ||
- | * BitComet will add the ports for you when the following setting " | ||
- | * Windows Vista users need too, the above rule turned on as well as the " | ||
- | |||
- | If after all of this, and your issue still remains we suggest you upgrade to the last BitComet version. | ||
- | |||
- | ---- | ||
- | |||
- | ==== My ISP is throttling P2P bandwidth. What can I do about that? ==== | ||
- | |||
- | Obviously, the best solution is to change your ISP as soon as possible! You do not want to waste $70 on some 20Mb connection, if you're now only using 2 gigabytes out of your 50 gigabyte download quota. Because simply, there are a lot of other ISPs in the market who care only about the money. You as a consumer pay them $$ and they will in return provide you their service. | ||
- | |||
- | Alternatively, | ||
- | |||
- | You can enable this encryption protocol within Bitcomet by following these steps: | ||
- | |||
- | * Open BitComet (ensure that its not an old version like 0.60 or below) and go to: //Options -> Task -> BitTorrent// | ||
- | * Locate "// | ||
- | |||
- | Our Recommendation is for the use of "// | ||
- | |||
- | It should look like this: | ||
- | |||
- | {{: | ||
- | |||
- | or like this (in older versions): | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | ==== How do I resume a previous download file from another client? ==== | ||
- | Before getting into the actual methods of importing a download you need to acknowledge a fact first. Many BitTorrent clients have an option (enabled by default in many of them) to add an extension (specific to that particular client) to all **unfinished** files. (E.g. BitComet adds the //.bc!// extension, uTorrent adds the //.!ut// extension and so on.) | ||
- | |||
- | Starting with version **1.20**, BitComet is able to automatically import unfinished downloads of the **BitComet**, | ||
- | |||
- | 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.\\ < | ||
- | 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 " | ||
- | 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:// | ||
- | |||
- | Once you got rid of the appended extensions or if your unfinished downloads didn't have any extensions appended (i.e. the previous client didn't have enabled the option to append an extension to unfinished files) you can use any of the below methods to import the downloads into BitComet. | ||
- | |||
- | **Method 1:** | ||
- | You will need the exact same // | ||
- | If you're one of those tidy persons who save all their torrents to some folder before opening them in their client then you shouldn' | ||
- | If you were a little lazier but still have the previous client installed, you may still be in luck. Look into the folder where your other client stores the .torrent files and you may still find you .torrent file in there. Especially, if your task is still present in your other client, you should definitely be able to find the .torrent file in your clients settings folder, since no BitTorrent client can run a task without having the .torrent file for it. Due to the great variety of OS/client type combinations we cannot provide for every case the exact location where your client stores the .torrent files. But usually this is somewhere either in the program directory (under XP or earlier) or in the //Documents and Settings// (in //Windows XP//) or //User// folders (in Vista or later) buried somewhere in the // | ||
- | |||
- | If you're unlucky enough to have lost the .torrent file from your machine, you'll have to go back to the site where you downloaded it the first time, and download it again. //But make sure you download the exact same torrent (i.e. the .torrent file with the same info-hash) or you won't be able to pick up your download where it was left// | ||
- | | ||
- | |||
- | **Method 2:** | ||
- | Starting with **v.1.20** you are able to do this automatically through the //File -> Import Unfinished Download...// | ||
- | |||
- | < | ||
- | < | ||
- | |||
- | ---- | ||
- | |||
- | ==== 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? ==== | ||
- | |||
- | What's happening is that TCP packets are not being acknowledged. TCP is a two-way protocol, and every packet that is sent out into the chancy world of the Internet, requires an acknowledgment (ACK) from the receiver back to the sender, indicating that the packet was received. | ||
- | |||
- | If that ACK doesn' | ||
- | |||
- | Why would this happen? It's because those ACK's from your applications are upstream traffic, using your upload (not download) bandwidth. BitComet is also using upload bandwidth, not just for its own ACK's, but also to send pieces you've already received, to others. If all of this upstream traffic exceeds your upstream bandwidth, then packets have to wait in a queue for their turn to be sent. | ||
- | |||
- | If the wait is too long, packets begin expiring (all packets have a maximum time-to-live) before they can make it to their destinations. ACK's aren't being received. The servers your applications connect with, are sending the last packet (which you already got), and still not getting the ACK for that packet. To you, this looks like the application slowed down or stalled -- it keeps getting packets that it has already received instead of getting the next one.\\ < | ||
- | |||
- | //But I have a 10Mb connection!! BitComet shows my speed is much less than that! How can this happen?!?// | ||
- | |||
- | Most ISP's only talk about the downstream speed of the connection -- they usually don't even mention the upstream speed, or bury it in the fine print. But that oft-forgotten " | ||
- | |||
- | //Then what can I do about it?// | ||
- | |||
- | 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, | ||
- | |||
- | When you aren't using any other applications, | ||
- | |||
- | // | ||
- | |||
- | No. | ||
- | |||
- | But try it, don't just take our word for it. This is a useful thing to understand clearly. Set yours to zero. (First make sure that " | ||
- | |||
- | Now let the client run for about 15-20 minutes, then check it again. Notice that the your client stopped downloading -- your download speed has dropped to zero? The reason for that is that **you must give to get**, and if you are a slow or unreliable peer, most other peers will chose not to offer you anything since they can't get anything from you. (What you receive, someone must, obviously, have sent to you.) | ||
- | |||
- | 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. // | ||
- | |||
- | ---- | ||
- | |||
- | ==== When BitComet is running my router/ | ||
- | |||
- | **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, | ||
- | |||
- | This is one such example.\\ | ||
- | The main issue here, is related to a technology employed by your router/ | ||
- | In short, what this does for you is allowing you to use multiple devices in your personal home LAN (Local Area Network), while having/ | ||
- | 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-versa, 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' | ||
- | |||
- | 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' | ||
- | |||
- | 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), | ||
- | |||
- | 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, | ||
- | |||
- | 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' | ||
- | |||
- | **What can you do to fix this?** | ||
- | |||
- | The first and best option would be to find an equipment which doesn' | ||
- | |||
- | 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# | ||
- | - Next, set the // | ||
- | - (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# | ||
- | - 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 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 messages which use UDP as a transport protocol as well as Torrent Exchange. Each UDP datagram outgoing towards a different IP address will create a new entry in the NAT table of your router, so it can easily become cluttered simply on account of UDP traffic.\\ | ||
- | An option in BitComet, that you can use to contain this effect, is // | ||
- | 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, | ||
- | 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/ | ||
- | |||
- | 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. | ||
- | |||
- | ---- | ||
- | |||
- | ==== How many tasks can I run simultaneously (at one time)? ==== | ||
- | |||
- | There is no built-in, program-imposed limit. BitComet has been tested and will work for over one hundred simultaneous seeding tasks. | ||
- | |||
- | **However, | ||
- | |||
- | There IS a limit imposed by the bandwidth of your connection, particularly the upstream side of it. (See the answer to the question above). If any task is starving for upstream bandwidth, then you will find few or no peers willing to transfer to or from you. (They may CONNECT to you, but this is simply to see what you're offering and is not the same as actually transferring any pieces to/from you.) Generally, all of your tasks should receive a bare minimum of 8 Kilobytes per second of upload bandwidth. Any less, and running that task is essentially a waste of your time. It should be as much above 8 as you can manage. If you have any tasks that routinely drop below this, you are trying to run too many. | ||
- | |||
- | For most people, most typical home broadband connections, | ||
- | |||
- | You can change the maximum number of concurrent downloading tasks in the **Options -> Task -> Task Schedule.** | ||
- | |||
- | ---- | ||
- | |||
- | ==== How can I download embedded video from webpages, with BitComet? ==== | ||
- | |||
- | Please read the [[video download instructions]] for details. | ||
- | |||
- | ---- | ||
- | |||
- | ==== Tasks have disappeared/ | ||
- | |||
- | __**A little introduction: | ||
- | BitComet < | ||
- | |||
- | Under versions prior to 1.17, BitComet stored its task list (and all of its settings) in the | ||
- | |||
- | // | ||
- | |||
- | directory, under **Windows XP** and earlier Windows versions, or | ||
- | |||
- | // | ||
- | |||
- | folder in **Windows Vista** or later | ||
- | |||
- | // | ||
- | |||
- | Please note that for some older versions of BitComet, if you disable the UAC feature and therefore Windows' | ||
- | data virtualization feature, your client will write/read in the actual Program Files folder, which may lead | ||
- | to issues like an empty or old Task List when turning UAC back on. | ||
- | |||
- | Windows Vista and later versions deprecate storing information in that tree (i.e. relying on data virtualization feature of Windows), and the storage place preferred by BitComet for configuration data is now (starting with v.1.18): | ||
- | |||
- | // | ||
- | |||
- | under **Windows XP** or | ||
- | |||
- | // | ||
- | |||
- | **// | ||
- | |||
- | 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 // | ||
- | 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# | ||
- | Also, starting with v.1.18 BitComet saves up to 7 successive copies of the // | ||
- | |||
- | (Now, be sensible about this. If this is a new installation, | ||
- | |||
- | When BC starts up again it tries to < | ||
- | 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 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 " | ||
- | 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 installation, | ||
- | See how to do that, at the end of this topic. | ||
- | |||
- | Also, if you've deleted a torrent from the **\Torrents** folder, BC hasn't got a task to actually start. If BC is running under an account that lacks permission to do any of these things, there can be problems. If the account that BC runs under has CHANGED since last time, there can be permission problems.\\ | ||
- | Therefore, if you haven' | ||
- | * Make sure you have full permission for this file and BitComet folder (in some cases you might need to also take ownership of the folder); | ||
- | * Make sure the // | ||
- | |||
- | __**Ways to recover the tasklist: | ||
- | |||
- | 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 deleting the current // | ||
- | - 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 // | ||
- | - Check the [[torrent_history|Torrent History]] (or [[torrent_share_and_torrent_archive# | ||
- | - 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# | ||
- | - If all you have is the unfinished downloaded files and your client version is v.1.20 or later you could also try the [[bitcomet_main_menus# | ||
- | |||
- | If you don't fix the file-writing problem, this will happen again next time you restart. | ||
- | |||
- | < | ||
- | |||
- | In order to avoid further nuisances related to recovering the tasklist in BitComet, it is highly recommended that | ||
- | you upgrade your client to a version later than v.1.17. Since, starting with v.1.18 BitComet saves up to 7 | ||
- | chronologically sequential backup files of downloads.xml, | ||
- | for these versions. | ||
- | | ||
- | *If you're upgrading from an older version to a newer one and all your tasks/ | ||
- | | ||
- | (If you don't know what that means, then you should copy all of the contents of one to the other, and then reinstall the version of BitComet that you just installed, again. But you really should learn what it means and do that.) | ||
- | |||
- | **How to manually backup the tasklist** | ||
- | |||
- | Go to //Main Menu Bar-> File-> Import and Export Download List//. Export the tasklist (and optionally, global program settings) into a //.bc_bak// file (these are back-up files). If your tasklist has disappeared when you restarted your BitComet, then do the following: go to //Main Menu Bar-> File-> Import and Export Download List//, then import the //.bc_bak// file you exported previously. | ||
- | |||
- | ---- | ||
- | |||
- | ==== 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' | ||
- | 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 [[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 [[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? ==== | ||
- | |||
- | This problem has been fixed since version 1.22, if you prefer using an older version but experience this problem, please then read the following instructions: | ||
- | |||
- | First of all, go into the options and look at the Advanced tab. Check down near the bottom for a parameter, " | ||
- | |||
- | So if this switch is set to " | ||
- | |||
- | 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 // | ||
- | - Go to the //File// menu and choose //Import and Export Download List...//. In the lower section named " | ||
- | - 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 // | ||
- | - Open a new Explorer window and type in the address bar // | ||
- | - Go into the // | ||
- | |||
- | ---- | ||
- | -[[understanding_bitcomet|Previous Page]] -[[configuration_and_user_settings|Next Page]]\\ | ||
- | -[[start|Main Index]] |