Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| known_client_issues_and_incompatibilities [2010/05/06 10:07] – lucy | known_client_issues_and_incompatibilities [2015/11/17 04:48] (current) – [My file download stops at 9x.x%. What can I do about that?] the_unusual_suspect | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| This issue is not inflicted by BitComet, it is Nvidia' | This issue is not inflicted by BitComet, it is Nvidia' | ||
| - | Sources from http:// | + | //Sources from// http:// |
| ---- | ---- | ||
| Line 66: | Line 66: | ||
| The Pedantic Part: A connection attempt (half-open connection) is an attempt to connect to another computer. If the TCP connection is accepted and confirmed (it's a three-part process) (don't ask), it is no longer "half open", as it becomes a completed TCP connection. If there is no response or no response to the response (we said, don't ask), the connection will remain in the "half open" state, until a time-out occurs (usually a few seconds) and the connection attempt is dropped (disconnected). The slot on the receiver becomes ready to accept another request for connection.\\ | The Pedantic Part: A connection attempt (half-open connection) is an attempt to connect to another computer. If the TCP connection is accepted and confirmed (it's a three-part process) (don't ask), it is no longer "half open", as it becomes a completed TCP connection. If there is no response or no response to the response (we said, don't ask), the connection will remain in the "half open" state, until a time-out occurs (usually a few seconds) and the connection attempt is dropped (disconnected). The slot on the receiver becomes ready to accept another request for connection.\\ | ||
| Event 4226 Report, when generated by normal use of BitComet, is NOT a problem and is an expected, normal occurrance.\\ | Event 4226 Report, when generated by normal use of BitComet, is NOT a problem and is an expected, normal occurrance.\\ | ||
| - | **Warning:** Recent versions of BitComet include a patch which can alter your system' | + | < |
| ---- | ---- | ||
| Line 72: | Line 72: | ||
| ==== What are these “_padding_file…” things in the filelist? ==== | ==== What are these “_padding_file…” things in the filelist? ==== | ||
| - | When downloading a BT task where not all of the files are selected, BitComet must create a file containing boundary data. This data will be saved at present time, in a special file: // | + | When downloading a BT task where not all of the files are selected, BitComet must create a file containing boundary data. This data will be saved at present time, in a special file: // |
| BitTorrent clients exchange data which has been broken down into small pieces, not entire original files. Often, one or more of these pieces may span over two or more files, making it necessary to download parts of a file that was not selected to be downloaded. In order for the selected files to be fully downloaded and pass a hash check, this excess data must be present, and will be stored in this additional file. | BitTorrent clients exchange data which has been broken down into small pieces, not entire original files. Often, one or more of these pieces may span over two or more files, making it necessary to download parts of a file that was not selected to be downloaded. In order for the selected files to be fully downloaded and pass a hash check, this excess data must be present, and will be stored in this additional file. | ||
| - | BitComet versions prior to v. 1.02 do not use this type of boundary data file (taskname.piece_part.bc!) and could, in some cases, cause valid files to fail a hash-check, if the task properties have been altered, or the files are manually hash-checked. | + | BitComet versions prior to v. 1.02 do not use this type of boundary data file (taskname.piece_part.bc!) and could, in some cases, cause valid files to fail a hash-check, if the task properties have been altered, or the files are manually hash-checked.\\ |
| This file (// | This file (// | ||
| Line 91: | Line 89: | ||
| * The torrent is out of date without complete BT seeds. Only if someone makes up for the lacking seed or provides a long-time seed, can you complete the download, in this situation. But for video files, 0.y% will not affect much the rest of the file, so you may still be able to play it. | * The torrent is out of date without complete BT seeds. Only if someone makes up for the lacking seed or provides a long-time seed, can you complete the download, in this situation. But for video files, 0.y% will not affect much the rest of the file, so you may still be able to play it. | ||
| - | * Along with the large files (e.g. video files), there are sometimes other small image or text files contained in the BT task. As there might be no seed or there could be less seeds for these small files (since others may have chosen not to download them), this may prevent your finishing the task. In this case, it's recommended that you do not download (deselect) these extra files. | + | * Along with the large files (e.g. video files), there are sometimes other small image or text files contained in the BT task. As there might be no seed or there could be less seeds for these small files (since others may have chosen not to download them), this may prevent your finishing the task. Under normal circumstances you should always download all the files so you can fully seed the torrent for others, but In this case, it's recommended that you do not download (deselect) these extra files if they are not available in the swarm. |
| * The torrent maker included by mistake a system file in the torrent (such as // | * The torrent maker included by mistake a system file in the torrent (such as // | ||
| * You are getting rubbish (corrupted) data (pieces which fail the hash-check and are discarded). This can occur due to bad peers but sometimes this is also caused by some faulty implementations of NAT on some SOHO routers. Make sure you're not in the DMZ. A firmware update might help. | * You are getting rubbish (corrupted) data (pieces which fail the hash-check and are discarded). This can occur due to bad peers but sometimes this is also caused by some faulty implementations of NAT on some SOHO routers. Make sure you're not in the DMZ. A firmware update might help. | ||
| Line 111: | Line 109: | ||
| ---- | ---- | ||
| - | -[[configuration_and_user_settings|Previous Page]] -[[torrent_related|Next Page]] | + | -[[configuration_and_user_settings|Previous Page]] -[[torrent_related|Next Page]]\\ |
| -[[start|Main Index]] | -[[start|Main Index]] | ||
