=doublèdgè=

***SERVICE PACK 3 USERS - READ - READ - READ***

When you open the "TCP/IP Limit" tab, you'll see the following:

"Current OS is not supported to be modified."and you won't be able to set anything here.

WHAT TO DO?

Just use the "Max simultanious half-open TCP connections:" setting found in the "Advanced" settings, under the "Connections" tab.

This should do it for you, and you can verify your half-open connections while looking at "Statistics".

If that doesn't seem to work for some reason, try this:

Run "RegEdit"

Navagate to:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Winsock

and increase the value of "TcpNumConnections" to 50 or 100.

HOPE THIS HELPS SOME OF YOU OUT - WORKS 4 ME

=doublèdgè=

Read the post:

"lilhansli (hansli) Fri Jul 18, 08 07:10 PM "

and my reply.

It's on this page ^^^^ (look up a few posts).

;)

=doublèdgè=

Read the post:

"lilhansli (hansli) Fri Jul 18, 08 07:10 PM "

and my reply.

It's on this page ^^^^ (look up a few posts).

;)

=doublèdgè=

If you can't find "TcpNumConnections" at the Registry location mentioned above, try adding "\Winsock" (no quotation marks).

ie:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Winsock

That's one of the locations where I find it running Service Pack 3

;)

=doublèdgè=

Yeah, but if you're running Service Pack 3 and you do that, Windows will pop up a warning that one of your system files has been changed. You'll then have to ignore the warning, and then shut down auto-updates, 'cause it'll try to download and install the Service Pack 3 version of tcpip.sys.

I think BitComet somehow gets around any limits imposed by the newer SP-3 tcpip, because I don't seem to notice any problems setting half-open limits.

Once in awhile, my event log will show errors that my tcpip limits have been exceeded, but I don't seem to notice any impact on my downloading capabilities.

(Oh, yeah...I am running an older version of BitComet:

"BitComet 0.85 Stable Release for Windows 2000/XP" and the reason for that is I like the "Summary" information lay-out a lot more, and I seem to get better speeds with this version.)

You got to modulate the ovulator!

When your download is complete, stop it [it will probably be uploading at this point].

Right click the download task, and select "Manual Hash Check"

When the hash check is done, it will now show you that it is indeed incomplete [usually lacking only a couple of megabytes].

Start it back up again and finish the download.

You can have this happen automatically if you turn on the option: "Hash-check again when the task download finished" (don't ya just love that grammar!- LOL).

It's listed under "BT Task" in "Preferences"

GOOD LUCK!

=doublèdgè=

@standamon:

This will fix your problem with the "dissapearing" download list (It's happened to me several times...also, this will get you back in shape if you upgrade your BitComet version then decide to go back to an older version, which requires a complete uninstall/reinstall).

1. Start BitComet. [Download(ing) list is blank].

2. Click the "Open" button.

3. Browse to where BitComet saved all your torrents [default location= ___C:\Program Files\BitComet\Torrents\]

4. Open all the torrents for your incomplete "BC files" [one at a time]

5. When the download starts, it will look like it's starting over from ___Zero Percent...DON'T PANIC, just stop the download.

6. Right Click the download task, and select "Manual Hash Check"

That's it! After the hash check is complete, your incomplete files will now show the size/status that they were before they dissapeared. Now you can resume your download task(s).

- OH, YEAH - Make sure that your "Default Destination Directory" is still at the same place that it was before [usually C:\Downloads]

HOPE THIS HELPS YOU OUT!

=doublèdgè=