Just checked the wu completed by a machine. I was surprised to see that 21 results have been returned with zero credit/cpu time. I checked one:-

https://boinc.bakerlab.org/rosetta/result.php?resultid=15602859

stdoutdae gave
2006-04-02 12:39:19 [rosetta@home] Starting result WEAK_RG_CONSTRAINT_1utg__410_355_0 using rosetta version 483
2006-04-02 14:41:38 [rosetta@home] Computation for result WEAK_RG_CONSTRAINT_1utg__410_355_0 finished
2006-04-02 14:41:38 [rosetta@home] Starting result WEAK_RG_CONSTRAINT_1dhn__410_355_0 using rosetta version 483
2006-04-02 14:41:41 [rosetta@home] Started upload of WEAK_RG_CONSTRAINT_1utg__410_355_0_0
2006-04-02 14:41:51 [rosetta@home] Finished upload of WEAK_RG_CONSTRAINT_1utg__410_355_0_0

Now I watched this one complete after 2 hrs of processing and at the end said cpu time zero

Anybody else getting this problem.

Nairb

---

---

---

I've had the same problem but it has only popped up in the past few days. I had been running 5.2.13 for a while and it was fine. Then a couple of days ago this problem started. This morning I grabbed the latest development version (5.3.31 I believe) and installed that. It's too early to tell if that will help.

So, the question for me is why did this just start happening. Nothing that I'm aware of changed on my old Win98SE box.

Charlie

---

-Charlie

[You shouldn't be running 5.2.13 on win98.

As a Boinc Alpha tester, I have run most every boinc client from 4.07 to the current developmental release (5.3.31) on a win98 and/or win98SE system(PIII 500 an/or Celeron 500). The earlier 4.XX had issues shutting boinc down and the "default.pif" took care of that until the Boinc devs themselves included a fix in the a version a couple dozen or three back from the current one. I even crunch Ralph units on it successfully.

tony

---

Well, the switch to 5.3.31 (latest development verions) did not cause this problem to go away or lessen. To mitigate the problem as best I can, I've switched my two old WIN98 boxes to the SCHOOL venue and lowered the WU run time to 1 hour. At least if a WU fails to report CPU time it won't run for too long like that.

My systems at home consist of my Linux server and my old Win98SE box (which is only used for one lone application). Last week I added a second old Win98 box. My older son moved to his own place and took his laptop with him but left his old Win98 box which I approriated for the cause.

I know these windows boxes are under powered and do not meet the specs for the project but I've had one running RAH for months with no problems. This new problem of not reporting CPU time just started a few days ago. I wonder if it has something to do with the new version of the application that was released recently?

Charlie

---

-Charlie

Thanks for the replies...
Likewise this problem started a few days ago. Up till then it was fine. Win98 has worked fine for ages. So a switch to the latest version dosent help. Thats not good. I might detach and delete all boinc and reinstall just to see if it fixes it. Else its time to try something else.

---

When I get home tonight I'm going to try installing an older version of the core client to see if that helps. I usually keep the install files around so I might have an older one or two still on my server.

I'm running 99% RAH and 1% SIMAP (as a backup) on my machines. I have not seen the problem with SIMAP although I have only done a couple WUs for that.

Charlie

---

-Charlie

My win98 box has the same problem. This machine only does DC projects. I will not buy a new WinXP license just to run this program.

It ran great at the begining and its my second best machine.

https://boinc.bakerlab.org/rosetta/results.php?hostid=58422
Results for computer

---

http://www.christianboards.org/forum.php
http://usalug.org/phpBB2/index.php

My win98 box has the same problem. This machine only does DC projects. I will not buy a new WinXP license just to run this program.

It ran great at the begining and its my second best machine.

https://boinc.bakerlab.org/rosetta/results.php?hostid=58422
Results for computer

I don't know why this is happening, but we will fix the problem asap and give credit where credit is due. sorry, David

---

So I removed the old copy of boinc set up a new install with the latest version from the download page. Downloaded 10 wu. Result.... 7 with zero cpu time and 3 ok.
Is the science lost too?. Maybe its time to try linux....

Nairb

---

I've switched my two Windows machines over to SIMAP for the time being. Maybe I'll conenct them to RALPH, too so I can help debug this problem. I'll try that tonight.

One thing I've noticed about this problem. When I first start boinc and it starts a RAH workunit, it keeps track of the cpu time just fine. When that one finishes and a new WU is started, it loses track of the CPU time. That one will actually finish as it is supposed to but the cpu time will be recorded as zero. The next WU will also lose track of the time. This will continue like this until I stop and restart boinc. Then the workunit will start counting the cpu time as it should, but then the next and subsequest workunits will repeat the above scenario. Each time I've restarted boinc and the workunit has started counting the cpu time, it has counted up from zero. I don't know if this is becuase I stopped the WU before it reached its first checkpoint or not. I'll have to try this again, bring up the graphics and see if it is on the first model or not.

Charlie

---

-Charlie

I see in Dr. Baker's journal where he says Rom knows where the problem is and will have it fixed soon. Also, the science is valid and credits will be awarded later.

Thank you for that good news, Dr. Baker!

As long as the science is valid, I've just switched my two old Win98SE machines back to RAH. My much faster Linux server continues to crunch RAH as always.

I'm now 99% RAH on all three of my machines, with 1% SIMAP as a backup.

Charlie

---

-Charlie

So the news is good. The science is valid.... and we may get some credit for the zero wus returned. Win 98 may be a pain but its cheaper than win xp or some other version of windozs. Linux is an alternative.

I think as more distro projects come on line they will be judged by their response to problems.

Still crunching...

---

Is there already some news about this issue?
Is the fix already done?

One of our members has the same problem, but with Windows Millenium
(yeah, who's using this anyway ;-))
examples:
https://boinc.bakerlab.org/rosetta/result.php?resultid=16792427
https://boinc.bakerlab.org/rosetta/result.php?resultid=16792426

Validate state Valid
Claimed credit 0
Granted credit 0
application version 4.98

Will he get credits for it?

---

Member of Dutch Power Cows

Sorry for this odd bug. Rom is going to work on a fix as soon as he has time. He is really busy right now preparing for the next boinc client release.

I granted 20 credit units for these errors. The average for the project per result is ~14.

20 credits is very nice. I would have been happy with 14. Was obviously seeing this problem a little. I like the way Rosetta is run. :-)

My 98se box is a legacy computer for several programs. I'm willing to upgrade the memory to 512mb for Rosetta, but not spend any more money on Microsoft OS's. Eventually I will try to use it as a dual boot for 98 and linux, so I can learn linux.

Once I get a couple of personal goals in Seti@home(should be soon) I will be switching more time over to Rosetta.

Keep up the good show.

---

Is there an update on the progress of this?
Does upgrading to any of the recent development versions of Boinc work to get rid of this problem? And if so, which versions get rid of this problem, yet have the fewest bugs/issues?

---

It seemed for a time that credit was being granted on WU's claming 0 credits on a daily basis. I have not seen this happen for a few days now. Have we stopped granting credit for these WU's ?

I still have a couple of machines running Winme still claiming the 0 credit problem.
Is this going to be fixed with 5.06, or should I consider dumping these machines.

https://boinc.bakerlab.org/rosetta/results.php?hostid=192001

one of my machines.

---

SETI.USA