Didn't work for Me...I had to do a System Restore.
Win XP Pro Box.

I did it to my XP Pro 64bit install with no problems using Richard's command line.

How did you attempt the change?

I tried it with the Optimizer...No Joy.
I may try Richard's command line later.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Can I add a "me too" here? My finger will get a rest now, as both my machines seem to be getting data continuously now, no flatlining anymore.

YAY!!!

I did it just as suggested in the first post here...

Thanks!

Unfortunately, all the GPU WUs I'm getting are shorties, so the fact that I'm (seemingly) back on the air will suck up some of YOUR bandwidth.

---

Since adding the value to my win7 registry, I have since rebooted, and I was able to download 2 APs today without a proxy and they went to completion.

As for slowing other things down.. I have not observed this. In fact, I downloaded an Ubuntu ISO just a few minutes ago and it took about 5 seconds to ramp up to 4.2 MiB/s and stayed there until completion.

Downloaded a 720p youtube video and it, too, took a few seconds to ramp up, but ran at 4.2 MiB/s until completion. However, I was able to download like that before, except now AP downloads don't time-out and stall.

Seems like a win-win.

In practice the 8 bytes of overhead per packet will not have any noticeable slow down.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

1) Does cdemers' "netsh" command line, setting Tcp1323Opts to 2, work well enough by itself?

Yes.
I manually changed mine to 3, and the only difference was when downloading larger files it got up to speed faster.
Just having it set to 2 sorted out the stalling problem. I still get the odd download stalling, but it usually only lasts for 10 seconds or so (the longest i've noticed is 30 sec) & then it restarts. They don't just sit there for up to 50 min as before.

---

Grant
Darwin NT

After I made this change to TCP1323 my downloads from all other website seem to be affected. My downloads begin at a normal pace compared to what I am use to with my ISP but after 2 or three minutes my download drops from 1.2MB per second to 23k/per second. Has anyone seen this as a side affect in making the change to fix the SETI downlaod problem?

Nope.
For me other downloads started off slightly slower than they used to, but quickly built up to their usual speed. Setting the value to 3 resulted in them getting up to speed much faster.

---

Grant
Darwin NT

Sorry about the delay... My ISP just decided to have a 2 hour outage both mobile and broadband which was nice of them.

Yes Mark, I did a reboot, actually, I did several to see if it changed anything on the 5th go :)

Tried both the manual and Richards suggestions :/

Also, it may have worked, I didnt get nearly as many timeouts as previous but download speed was still only as shown in the screenshot

---

Sorry about the delay... My ISP just decided to have a 2 hour outage both mobile and broadband which was nice of them.

Yes Mark, I did a reboot, actually, I did several to see if it changed anything on the 5th go :)

Tried both the manual and Richards suggestions :/

Also, it may have worked, I didnt get nearly as many timeouts as previous but download speed was still only as shown in the screenshot

For me there was only a slight increase in speed, but it did sort out all the stalled downloads- i haven't been getting many timing out, just sitting there, download timer running but nothing actually downloading.

I'd suggest you open up Regedit & check to see that the entries have been made as they should, where they should.
If they have, and you've still got issues it may relate to your ISPs issues.

---

Grant
Darwin NT

And to repeat, yet again - this thread is not about speed, it's simply about reliability.

The idea is to get your downloads with no http errors, no backoffs.

The fix has nothing to do with download speeds. It's for timeouts
and the resulting retries. No time outs, no retries.

Apologies... must have missed that bit! :)

---

and to not have to use a Proxy which may be here today and gone tomorrow.

Although I had been recommending SETI put a Linux proxy at the bottom of the hill.

This would also concentrate and make better use of the bandwidth thru our
narrow pipe.

but if this fix did speed transfers up we would quickly run into the old
saying by Mr Spock. "The needs of the many outweigh the needs of the few or the one."
and action would be taken:-)

I thought that was Marx. Arrgghhh, topic drift (headslaps self).
Bad poster! Bad poster!

And to repeat, yet again - this thread is not about speed, it's simply about reliability.

The idea is to get your downloads with no http errors, no backoffs.

Sorry. I read that earlier on, and I was just simply commenting/replying to a few mentions about how this fix slowed speed down for some people. I was just pointing out that it didn't slow mine down, so other factors may be involved for those cases.

The fix does, however, fix reliability, which I also mentioned in my post that mentioned speed. I observed no change in speed, but now I have the reliability to go along with it.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I just wanted to point out that the download site does not mention Win8.....I tried it on my Win8 computer and it does not work there.

According to Speedguide.net Forums (TCP Optimizer): It doesn't yet work for Win8 :(

That was the one.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I just wanted to point out that the download site does not mention Win8.....I tried it on my Win8 computer and it does not work there.

According to Speedguide.net Forums (TCP Optimizer): It doesn't yet work for Win8 :(

Does anyone have Win8, and a spirit of adventure enough to try one of the other deployment mechanisms? Does Win8 have regedit? Or a command prompt?

It has both......

I will give it a try tomorrow..too involved right now with me down computer.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Just an observation:
My Pending Validation has risen from circa 2500 to circa 5200 since implementing the change (via TCP Optimiser). The two events may be related though.
cheers

---

Just an observation:
My Pending Validation has risen from circa 2500 to circa 5200 since implementing the change (via TCP Optimiser). The two events may be related though.
cheers

I've noticed my pending climbing as well, but it started before i made the networking changes.
I suspect it's related to the number of AP WUs out there (for those doing both AP & MB i suspect it's first in first out untill a MB WU gets close to it's deadline), combined which a whole bunch of shorties that have been going through.

---

Grant
Darwin NT

so...i have also that stalling download problem on 1 pc, another runs seti just fine..since there has not been any changes on client end pc hardware, is the problem on BOINC, Seti servers or Seti client mishandling nerwork traffic ?

---

Marko First apply the fix, then try if you still have any problem post again.

---

Just an observation:
My Pending Validation has risen from circa 2500 to circa 5200 since implementing the change (via TCP Optimiser). The two events may be related though.
cheers

I've noticed my pending climbing as well, but it started before i made the networking changes.
I suspect it's related to the number of AP WUs out there (for those doing both AP & MB i suspect it's first in first out untill a MB WU gets close to it's deadline), combined which a whole bunch of shorties that have been going through.

My pending was inching up prior to the change as well and took a hike following that. I suspect that the two are not related though. Shorties coming through like intermittent short showers but like a thundering storm. I am seeing the occasional stalled wu though (not box specific). Largest I have seen was 6 stalled wus out of 102 new tasks.

cheers

---