Home

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

known_client_issues_and_incompatibilities
 

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
known_client_issues_and_incompatibilities [2010/05/07 03:54]
lucy
known_client_issues_and_incompatibilities [2010/05/10 02:12]
lucy
Line 23: Line 23:
 This issue is not inflicted by BitComet, it is Nvidia's firewall that is causing the problem. This issue is not inflicted by BitComet, it is Nvidia's firewall that is causing the problem.
  
-Sources from http://forums.nvidia.com/lofiversion/index.php?t2682.html +//Sources from// http://forums.nvidia.com/lofiversion/index.php?t2682.html
  
 ---- ----
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.\\
-<html><span style=color:Red>Tip:</span></html> Recent versions of BitComet include a patch which can alter your system's tcpip.sys file, to change this rate limit. We strongly recommend this only be attempted by computer professionals, and only if there is a specific reason for wanting to change said limit, as it could cause problems, or make the system become unstable. Use this at your own risk. Don't ask for help recovering from it, they'll only laugh at you. +<html><span style=color:Red>Warning:</span></html> Recent versions of BitComet include a patch which can alter your system's tcpip.sys file, to change this rate limit. We strongly recommend this only be attempted by computer professionals, and only if there is a specific reason for wanting to change said limit, as it could cause problems, or make the system become unstable. Use this at your own risk. Don't ask for help recovering from it, they'll only laugh at you. 
  
 ---- ----
Line 109: 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]]
 
known_client_issues_and_incompatibilities.txt · Last modified: 2015/11/17 04:48 by the_unusual_suspect
[unknown button type]
 
Recent changes RSS feed Driven by DokuWiki