This shows you the differences between two versions of the page.
understanding_bitcomet [2011/04/27 17:23] greywizard [What is web-seeding and how can I make use of it?] |
understanding_bitcomet [2015/08/15 04:21] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Understanding BitComet ===== | ||
- | ==== What is BitComet? ==== | ||
- | |||
- | BitComet is a powerful, clean, fast, and easy-to-use [[bittorrent|BitTorrent]] client running on Windows. You can download torrents, as well as HTTP/FTP and eDonkey/ | ||
- | |||
- | ---- | ||
- | |||
- | ==== What platform does BitComet support? ==== | ||
- | |||
- | Windows only. (Windows 98/ | ||
- | |||
- | It supports Unicode in Windows2000/ | ||
- | |||
- | ---- | ||
- | |||
- | ==== Which port does BitComet use? ==== | ||
- | |||
- | There are 65,536 ports available to you, and you can choose any one of them for your listen port. No port is better than any other. There is no " | ||
- | |||
- | It is better and less confusing to others if you select a port that isn't already commonly used for something else (Example: port 80 is commonly used for web servers, but if you're not running a web server, there' | ||
- | |||
- | BitComet uses a single TCP port to " | ||
- | |||
- | When you select a listen port, your port number is passed to the tracker and to the DHT network for distribution, | ||
- | |||
- | It is up to you to make certain your listen port is not being blocked by a firewall. | ||
- | Do not connect to the Internet without a working firewall. | ||
- | Your system is likely be infected very quickly, if you connect without a firewall. | ||
- | |||
- | This means that you need to configure your firewall(s) to open your chosen listen port, NOT to hunt for a port that your firewall isn't blocking. | ||
- | |||
- | If you are behind a firewall which you cannot control (as is the case with most types of wireless connections, | ||
- | |||
- | ---- | ||
- | |||
- | ==== I am new to BitComet and to torrents, so how do I use it? ==== | ||
- | |||
- | Please read these two topics for starters: | ||
- | |||
- | * [[using_bitcomet_to_download_torrents|Using BitComet to Download Torrents]] | ||
- | * [[using_bitcomet_to_download_files_http_ftp_protocols|Using BitComet to Download Files (HTTP/FTP protocols)]] | ||
- | |||
- | ---- | ||
- | |||
- | ==== Peers, seeds, torrent, tracker, DHT, Peer Exchange (PEX), Magnet Links; what are all these things? ==== | ||
- | |||
- | Click on the following link to see explanations for all these terms: [[Peers, seeds, torrent, tracker, DHT, Peer Exchange (PEX), Magnet Links]]. | ||
- | |||
- | ---- | ||
- | |||
- | ==== What do the icons next to the task mean? ==== | ||
- | |||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | ==== What's the meaning of the line " | ||
- | |||
- | This tells you how many peers(n) the client has failed to connect. It's for your information, | ||
- | |||
- | ---- | ||
- | |||
- | ==== What is " | ||
- | |||
- | If you're downloading some, but not all of the files in a torrent, BitComet must create a file containing data about where the file ends within a transferred piece. (Don't worry about it). This data will be saved in a special file:// taskname.piece_part.bc!// | ||
- | |||
- | Well, if you simply must know, BitTorrent clients exchange data which has been broken down into evenly-sized pieces. That is, at the creation time of a torrent the torrent-making program, virtually concatenates all the files in the torrent, then it divides the resulting data chunk into evenly sized pieces, which are the trading currency of BT protocol. Piece boundaries do not usually match file boundaries, so a piece can contain the end of one file and the beginning of another file. BitTorrent must download the entire piece, probably including the beginning part of a file that was not selected. Hash-checking for errors is done on the entire piece, so the extra data can't be discarded yet. This extra data is stored in these additional files. These files must be present as long as the task is active in BitComet (as well as if, in the future, you need to reseed the torrent). They are not required in order to use the files after downloading. BitComet versions prior to v.1.02 do not use this type of boundary data file and could, in some circumstances, | ||
- | |||
- | Please note that also, in version 0.85 or above, BitComet introduced an [[Align File to Piece Boundary]] function into its Torrent Maker, as a previous means to deal with pieces overlapping two different files. When enabled, the function makes sure that BT pieces do not span over more files. It does that by inserting empty padding files of the exact size as the remainder of space into every " | ||
- | |||
- | ---- | ||
- | |||
- | ==== How do I change my default download directory? ==== | ||
- | |||
- | Please make sure there is no task running before you change the default download directory. There are two ways to change the download directory for all tasks: | ||
- | |||
- | * Go to **Options -> Directories -> Directories** (or in **Preferences -> Task**, for older versions), click the browse button to change another directory as the default download directory. Or | ||
- | * In the main bar, click **Tools -> Default Directory -> Other Directory**, | ||
- | |||
- | < | ||
- | |||
- | * Stop the task, right-click it and choose: **Files Move to**... (Version 0.71 and later); | ||
- | * Stop the task, right-click it and choose **Properties**. Then on the General tab you change the **Save path** parameter to whatever you want. When you hit the OK button a prompt will appear asking you to choose whether to move the downloaded files to the new location. (Version 1.07 and later). | ||
- | |||
- | ---- | ||
- | |||
- | ==== What is UPnP Auto Port Mapping? ==== | ||
- | |||
- | To get the best speed, P2P applications like BitComet need a public listening port. However, if you use a router with an active firewall, or use Windows Internet Connection Sharing (ICS), you will need to configure port mapping (port forwarding from gateway/ | ||
- | |||
- | < | ||
- | |||
- | If you do not use a router and do not use ICS, then port-forwarding, | ||
- | |||
- | ---- | ||
- | |||
- | ==== What is Disk Cache in BitComet? ==== | ||
- | |||
- | The function of our [[Intelligent Disk Cache]] is an important reason to choose BitComet. The disk-cache is designed to speed up downloads and reduce mechanical wear of the hard-disk. When the transfer rate exceeds a certain value, a carefully-designed disk cache mechanism in BitComet buffers writing to the hard disk. This can greatly improve performance, | ||
- | |||
- | ---- | ||
- | |||
- | ==== What is NAT Traversal in BitComet? ==== | ||
- | |||
- | Network Address Translation means that a packet passes through a gateway that changes its IP address when it passes traffic onwards either way. If you are behind such a gateway then it isn't possible to initiate contact with you directly -- all contact with you must be through the gateway. | ||
- | |||
- | This means that other peers can't initiate contact with you, because while the gateway knows where to route replies to your requests, it doesn' | ||
- | |||
- | Non-firewalled clients and clients on publicly routable IP addresses are able to help clients which ARE behind such a gateway, to communicate in spite of this, when transferring the same torrent. | ||
- | |||
- | A server is needed to assist in setting up this communication (so that it "looks like" a reply to both parties) which server BitComet provides for its clients. BitComet does an even better job for users behind such gateways, by enabling them to contact each other via one-way UDP. If other peers can initiate contact with you despite the gateway, your download rate will increase because you can now connect with more peers. NAT traversal is not as fast as having an open listen port, but is notably faster than no-listen-port mode. | ||
- | |||
- | Bitcomet needs no configuration to auto-detect your Internet connection (to find out if you are behind a translating gateway, and will try to do this automatically. You can control this feature in the Options -> | ||
- | |||
- | < | ||
- | |||
- | //' | ||
- | //Nat Traversal was removed from BitComet v. 1.03// (Core Improved: removed NAT Traversal via UDP, in order to improve TCP transfer efficiency)\\ | ||
- | //Nat Traversal was automatically disabled when not needed in v. 0.90// (Core Improved: disabled NAT Traversal via UDP automatically for WAN IP user, in order to improve TCP transfer efficiency)\\ | ||
- | //Nat Traversal was updated in v. 0.86// (Core Improved: improved NAT Traversal via UDP component, decreased CPU usage)\\ | ||
- | //Nat Traversal reintroduced with Encryption enabled in v. 0.83// (Core Improved: reconstruction of NAT Traversal via UDP using encryption connections)\\ | ||
- | //Nat Traversal was removed, temporarily, | ||
- | //Early implementation of this technology was on an experimental basis in v.0.54// (Core Improved: NAT pass-through by UDP! (still experimental) | ||
- | |||
- | ---- | ||
- | |||
- | ==== What does the peer status " | ||
- | |||
- | D--- downloading data from peer now | ||
- | |||
- | U--- uploading data from peer now | ||
- | |||
- | d--- I request data from peer, want to download from peer ( peer has data that I need ) | ||
- | |||
- | u--- peer request data from me, asking for me to upload ( I have data that the peer needs ) | ||
- | |||
- | In the latter versions, replaced with the symbols: {I, i, C, c, _}. See [[connection_status|here]] a full description of all status meanings for different combinations of these symbols. | ||
- | |||
- | ---- | ||
- | |||
- | ==== What is P2PCache (in Advanced Options)? ==== | ||
- | |||
- | P2PCache can enable your Internet Service Provider to improve content delivery and acceleration of internet traffic by using caching technologies. (If your ISP does not support P2PCache, then it will not work for you.) | ||
- | |||
- | For further information, | ||
- | |||
- | ---- | ||
- | |||
- | ==== What to do when garbled text appears in the CometID pane ==== | ||
- | This problem is usually caused by the corruption of Outlook. You may also find that any .mht file can't be open by IE correctly. Please try Method 1 first, if the problem still exists, please then try method 2. | ||
- | |||
- | **Method 1: | ||
- | Step[1]: Windows Start menu -> run -> regsvr32 inetcomm.dll\\ | ||
- | Step[2]: If last step failed due to missing inetcomm.dll, | ||
- | Step[3]: Repeat step[1], if still faild due to “module missing”, try to find msoert2.dll and inetres.dll, | ||
- | Step[4]: Repeat step[1], and it should work. | ||
- | |||
- | **Method 2: | ||
- | Download the mht file from [[http:// | ||
- | |||
- | ---- | ||
- | |||
- | ==== How to change the default media player to play/ | ||
- | |||
- | Go to **Options** -> **Advanced**, | ||
- | |||
- | More information about preview while downloading can be read [[preview_while_downloading|HERE]]. | ||
- | |||
- | ====What is the encryption option in BitComet and what effects does it have on the operation of the client?==== | ||
- | |||
- | The encryption option in BitComet (just as in other clients) has the purpose of obfuscating BitTorrent traffic in order to render it undetectable (or at least less detectable) to traffic shaping applications which some ISPs use, in order to throttle BitTorrent traffic.\\ | ||
- | BitComet uses the MSE/PE encryption method introduced by Azureus and (when encryption is activated) it encrypts both protocol header and message payload. | ||
- | |||
- | For more detailed information on this subject, as well as for a description of the effect each encryption level chosen in the client has on connections read [[protocol_encryption|this topic]]. | ||
- | |||
- | ====What is web-seeding and how can I make use of it?==== | ||
- | |||
- | Simply put, web-seeding is a technology which allows a BitTorrent swarm to use a web server as a peer of the swarm. In other words if you have content you want to distribute through a web server, you can use web-seeding to create a BitTorrent swarm around that content and offload the burden from the web-server, as it would act a simple seed in that swarm maintaining it alive for as long as you share that content, but as soon as there are more than one downloaders, | ||
- | |||
- | Currently there are two web-seeding specifications available out there: | ||
- | * BitTornado style web-seeding (needs a special web server to be set up, which serves content by info-hash and piece rather than file name); | ||
- | * GetRight style web-seeding (can use a standard HTTP web server, with no additional setup required). | ||
- | |||
- | |||
- | In order to benefit from the presence of a web-seeding server in the torrent swarm, a BitTorrent client must support web-seeding.\\ BitComet supports GetRight style web-seeding since v.1.14. For details on how to create a torrent with a web-seeding server check [[making_torrents_with_bitcomet|this topic]]. | ||
- | |||
- | |||
- | ---- | ||
- | -[[bitcomet_client_issues_and_possible_solutions|Next Page]]\\ | ||
- | -[[start|Main Index]] |