I attached to Rosetta while it was still in beta phase. I stayed with it during all the software glitches through Christmas. I became disillusioned with all the bugs and ghost WUs I routinely encountered. I tried again in spring and immediately encountered the ghost WU problem on my first attempt to download. I decided it wasn't worth my bandwidth and resource costs to ask for work that I never receive. Ghost WUs are a pet peeve of mine and I will not return to Rosetta unless this problem is corrected.

Does anyone know definitively whether the MTU business researched over at Seti (I'm not a member) was resolved? I only get this ghost WU problem at Rosetta, not any other project I attached to. So I'm assuming the problem is somewhere with Cogent or on the U.S. west coast.

Try the latest 5.6.3 Boinc (Alpha version). It has supposedly taken care of the 500 errors, where you can't connect. I don't recall hearing anything about Ghosts caused by boinc or any efforts to fix those. So far I haven't seen much bad about 5.6.3, though you should know it's in testing and can behave strangely.

I don't know why you're getting ghosts.

tony

Here' are my things that go bump in the night:
https://boinc.bakerlab.org/rosetta/result.php?resultid=12282807 from March 2
https://boinc.bakerlab.org/rosetta/result.php?resultid=13268634 from March 10
https://boinc.bakerlab.org/rosetta/result.php?resultid=14368878 from March 20

These three are still in my results page.

---

dag
--Finding aliens is cool, but understanding the structure of proteins is useful.

Dag, your WUs are lingering on your results page. That is a different issue then "ghost WUs". Ghosts are when you see a WU in your results page which was JUST reported as downloaded to you, but you don't have it on your machine. and never did.

Idle time, if you would, could you explain what a black hole router is? And, it might be helpful if you would explain how the Rosetta server thinking that you have a WU that you do not is impacting your bandwidth and resource costs.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Dag, your WUs are lingering on your results page. That is a different issue then "ghost WUs". ...

Yup, and this will be the third time I'm asking for someone to remove six month old results and/or failures.

---

dag
--Finding aliens is cool, but understanding the structure of proteins is useful.

Black hole routers as presented by Microsoft.

...explain how the Rosetta server thinking that you have a WU that you do not is impacting your bandwidth and resource costs.

Well, time is credit. I wish to imply that time my computer spends asking for and waiting for work (which it doesn't get) is wasted because that same time/resources could have been used doing actual work for another project that doesn't have the ghost problem.

I suspended Rosetta around Christmas and tried again in March (iirc) and all I got for my effort was approximately 25 ghosts and 1 real WU. Rosetta doesn't use the re-send option like EaH does, so the number of ghosts continue to rise. This wastes a lot of time asking for work while not getting it. So I suspend Rosetta again and run EaH full time. I still keep up with the msg boards though.

Do know what your problem is. I started at the end of July and I've had no problems.

---

Do know what your problem is. I started at the end of July and I've had no problems.

I've had the ghost WU problem since I joined last Oct 2005. I believe that my location in NE Ohio relative to the University of Washington causes my communications to pass through a black hole router periodically. That is all I can postulate. I'm not PC literate enough to risk playing with the windows registry and messing up MTU sizes even if that will correct the problem. And it's not cost effective (I presume) for Rosetta to turn on the re-send function of BOINC.

You might try some of the tools at DSLREPORTS.com (they are mostly free).

If you look at this link there is information on the tool to use and some free software that will let you update your MTU setting (without editing the registry directly) to hopefully alleviate your "balck hole router" issue.

Best of luck if you so desire to venture onward. Worth a look, maybe?

---

!!Stupidity should be PAINFUL!!

I used to have to set my MTU to 1460 to get a connection to the internet. Wierd :S

I've fixed a number of problems by changing my MTU, I would reccomend trying to change it.

---

Thanks to you all; I will consider your proposals. Please consider this topic closed.