Chicken 2.4 does not work on Vista, the optimizers are looking for the problem.

The stock app 5.27 you now use is faster then the old stock app because some of the optimisations have been build into the stock app.

Well, that explains the weirdness (Vista hangups) and the funky acceleration (woohoo!).

Also explains why the number of waiting WU's has increased :).

---

The drop in your average time per core can also be accounted for by the very short WU's Berk was sending out. They sent a whole herd of them all at once.

See this post about them http://setiathome.berkeley.edu/forum_thread.php?id=41845

---

PROUD MEMBER OF Team Starfire World BOINC

Well, my problem with v5.27 is that it keeps my CPU at 100% utilization whether it is actually running and crunching data sets or not. This slows my PC and sometimes the PC will power down due to excess heating. Prior SETI version never did this. I have to go to XP's Process Viewer and kill v5.27 process to cool the CPU. Anybody know how to fix this bug??? Thankx!!!!
(XP Pro, 1.5 Gig RAM, AMD Athlon XP 3000+,2.16 Ghz).

Chicken 2.4 does not work on Vista, the optimizers are looking for the problem.

The stock app 5.27 you now use is faster then the old stock app because some of the optimisations have been build into the stock app.

Well, that explains the weirdness (Vista hangups) and the funky acceleration (woohoo!).

Also explains why the number of waiting WU's has increased :).

---

"It is often darkest just before it turns completely black."

Well, my problem with v5.27 is that it keeps my CPU at 100% utilization whether it is actually running and crunching data sets or not. This slows my PC and sometimes the PC will power down due to excess heating. Prior SETI version never did this. I have to go to XP's Process Viewer and kill v5.27 process to cool the CPU. Anybody know how to fix this bug??? Thankx!!!!
(XP Pro, 1.5 Gig RAM, AMD Athlon XP 3000+,2.16 Ghz).

Chicken 2.4 does not work on Vista, the optimizers are looking for the problem.

The stock app 5.27 you now use is faster then the old stock app because some of the optimisations have been build into the stock app.

Well, that explains the weirdness (Vista hangups) and the funky acceleration (woohoo!).

Also explains why the number of waiting WU's has increased :).

If it is not processing any WUs, what processes are showing as using all of the cpu cycles? Boincmgr? Boincexe?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Well, my problem with v5.27 is that it keeps my CPU at 100% utilization whether it is actually running and crunching data sets or not. This slows my PC and sometimes the PC will power down due to excess heating. Prior SETI version never did this. I have to go to XP's Process Viewer and kill v5.27 process to cool the CPU. Anybody know how to fix this bug??? Thankx!!!!
(XP Pro, 1.5 Gig RAM, AMD Athlon XP 3000+,2.16 Ghz).
...

If i understand your complaint correct your computer is overheating, while crunching seti@home workunits with stock v5.27. If that would be a bug, many more would have reported the same problem here in the Number Crunching forum. So, it seems this problem is singular only to your computer.
The first thing that comes to my mind is dust: when did you clean your cooling system the last time (fans, coolers, filters P.S.U.) ?
My second idea would be overclocking, but 2.16GHz seems normal for XP3000+.
Third there is a setting under "Your Account/General Preferences" called "Use at most", which is active since BOINC CC v5.6.x . It gives you the possibilty to lower the maximum usage of an application run by BOINC. Set it below 100% and see if it helps with your problem.

---

_\|/_
U r s

Well, my problem with v5.27 is that it keeps my CPU at 100% utilization whether it is actually running and crunching data sets or not. This slows my PC and sometimes the PC will power down due to excess heating. Prior SETI version never did this. I have to go to XP's Process Viewer and kill v5.27 process to cool the CPU. Anybody know how to fix this bug??? Thankx!!!!
(XP Pro, 1.5 Gig RAM, AMD Athlon XP 3000+,2.16 Ghz).

Chicken 2.4 does not work on Vista, the optimizers are looking for the problem.

The stock app 5.27 you now use is faster then the old stock app because some of the optimisations have been build into the stock app.

Well, that explains the weirdness (Vista hangups) and the funky acceleration (woohoo!).

Also explains why the number of waiting WU's has increased :).

If it is not processing any WUs, what processes are showing as using all of the cpu cycles? Boincmgr? Boincexe?

The image name is "setiathome_5.27_windows_intelx86.exe" under the Process Tab.
Here is what I observe: BOINC will load the process and start it when the screensaver comes ready. This is normal operation. CPU will go to 100% as expected. Here are the 2 intermittents: Sometimes, when BOINC stops running it will leave the setiathome process loaded and the CPU will stay at 100% load. Sometimes I see 2 (TWO) "setiathome_5.27_windows_intelx86.exe" processes in the image name list. I kill one to return the CPU to its average lower load. But sometimes seti is a stuck process and only 1 (ONE) copy will cause 100% CPU. Of course, I check BOINC to make sure that File|Run based on preferences is selected. That is the case. I need to play with this, just observe it some more, or try some tests of some kind. This is intermittent and I have not found out the cause yet. Your suggestions appreciated.

---

"It is often darkest just before it turns completely black."

The image name is "setiathome_5.27_windows_intelx86.exe" under the Process Tab.
Here is what I observe: BOINC will load the process and start it when the screensaver comes ready. This is normal operation. CPU will go to 100% as expected. Here are the 2 intermittents: Sometimes, when BOINC stops running it will leave the setiathome process loaded and the CPU will stay at 100% load. Sometimes I see 2 (TWO) "setiathome_5.27_windows_intelx86.exe" processes in the image name list. I kill one to return the CPU to its average lower load. But sometimes seti is a stuck process and only 1 (ONE) copy will cause 100% CPU. Of course, I check BOINC to make sure that File|Run based on preferences is selected. That is the case. I need to play with this, just observe it some more, or try some tests of some kind. This is intermittent and I have not found out the cause yet. Your suggestions appreciated.

Maybe a dumb question, but did you happen to install BOINC as a service? This would explain why you can exit the BOINC manager and it still runs the SETI application. If you did, you need to stop the BOINC client by clicking "Advanced" and "Stop connected client" in the BOINC manager program before closing it. BOINC is two separate programs, the "client" which actually does all of the scheduling, etc. and the BOINC "manager" which is the control program you actually see onscreen and interact with. It connects to the client to obtain information and issue control commands. If it is installed as a service, closing the manager (the actual onscreen program) would *not* stop the "client* from running.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

...
Here is what I observe: BOINC will load the process and start it when the screensaver comes ready. This is normal operation. CPU will go to 100% as expected. Here are the 2 intermittents: Sometimes, when BOINC stops running it will leave the setiathome process loaded and the CPU will stay at 100% load. Sometimes I see 2 (TWO) "setiathome_5.27_windows_intelx86.exe" processes in the image name list. I kill one to return the CPU to its average lower load. But sometimes seti is a stuck process and only 1 (ONE) copy will cause 100% CPU. Of course, I check BOINC to make sure that File|Run based on preferences is selected. That is the case. I need to play with this, just observe it some more, or try some tests of some kind. This is intermittent and I have not found out the cause yet. Your suggestions appreciated.

You might try upgrading to a current version of BOINC. You seem to be using 4.25 which was obsolete when I started using BOINC in June of 2005, perhaps some of the other users here will recall something about it. If nothing else, others users will be happier if you go to a version 5.2.7 or later so your host can report the fpops_cumulative value used for credit calculations now.

                                                               Joe

4.25 was a wonderful version, if memory serves. it was post 4.19 and pre 4.35 (jm7's first work fetch scheduler verion). It required manual massaging to ensure deadlines were met. It worked really good for it's day. I thought it was a rock solid platform (that and 4.32)Unfortunately, they dropped sorting by columns with 4.20 and subsequent ones until recent alpha version brought it back. It might be in the 5.10.13??

Anyway, that's what I remember about it.

Oh yeah, it uses benchmark scores. Note: Fpops has been in use since May 6th 2006, so it's probably time for a change. Not to mention you'll get more credits for yourself.

versions 4.19 and earlier had the description "PakageForTheWeb stub" and were approx 1.61 meg in size. Starting with 4.20 the MSI installer was use and file size jumped to 10 meg. And it's description is "provides all the infrastructure for Boinc to Download work units". I could email you a copy of 4.25 if you want(or any version back to 4.05).

Here's what it looks like. Note: to attach you had to use your Account KEY (not password and email). I showed it with the pulldown menu open so you can see all your options. The other two menu items only have one listing.

Here's 4.19. Note: NO left hand box, very little options, and no status column. website options were very limited in that day. This is pretty much what 4.05-4.19 looked like.

...
Here is what I observe: BOINC will load the process and start it when the screensaver comes ready. This is normal operation. CPU will go to 100% as expected. Here are the 2 intermittents: Sometimes, when BOINC stops running it will leave the setiathome process loaded and the CPU will stay at 100% load. Sometimes I see 2 (TWO) "setiathome_5.27_windows_intelx86.exe" processes in the image name list. I kill one to return the CPU to its average lower load. But sometimes seti is a stuck process and only 1 (ONE) copy will cause 100% CPU. Of course, I check BOINC to make sure that File|Run based on preferences is selected. That is the case. I need to play with this, just observe it some more, or try some tests of some kind. This is intermittent and I have not found out the cause yet. Your suggestions appreciated.

You might try upgrading to a current version of BOINC. You seem to be using 4.25 which was obsolete when I started using BOINC in June of 2005, perhaps some of the other users here will recall something about it. If nothing else, others users will be happier if you go to a version 5.2.7 or later so your host can report the fpops_cumulative value used for credit calculations now.

                                                               Joe

Yup. I checked and it IS BOINC v4.25. Do you have a link to the upgrade?
This is a good place to start. Thanks for the tip.

---

"It is often darkest just before it turns completely black."

The image name is "setiathome_5.27_windows_intelx86.exe" under the Process Tab.
Here is what I observe: BOINC will load the process and start it when the screensaver comes ready. This is normal operation. CPU will go to 100% as expected. Here are the 2 intermittents: Sometimes, when BOINC stops running it will leave the setiathome process loaded and the CPU will stay at 100% load. Sometimes I see 2 (TWO) "setiathome_5.27_windows_intelx86.exe" processes in the image name list. I kill one to return the CPU to its average lower load. But sometimes seti is a stuck process and only 1 (ONE) copy will cause 100% CPU. Of course, I check BOINC to make sure that File|Run based on preferences is selected. That is the case. I need to play with this, just observe it some more, or try some tests of some kind. This is intermittent and I have not found out the cause yet. Your suggestions appreciated.

Maybe a dumb question, but did you happen to install BOINC as a service? This would explain why you can exit the BOINC manager and it still runs the SETI application. If you did, you need to stop the BOINC client by clicking "Advanced" and "Stop connected client" in the BOINC manager program before closing it. BOINC is two separate programs, the "client" which actually does all of the scheduling, etc. and the BOINC "manager" which is the control program you actually see onscreen and interact with. It connects to the client to obtain information and issue control commands. If it is installed as a service, closing the manager (the actual onscreen program) would *not* stop the "client* from running.

Thanks and I am not sure how it installed. I just downloaded it and it installed. I don't find Advanced on the main menu, submenu, or on the left hand side options. But, an earlier post noted that I am obsolete BOINC V4.25. This seems like a good place to start - get the upgrade and take it from there.

---

"It is often darkest just before it turns completely black."

Well, my problem with v5.27 is that it keeps my CPU at 100% utilization whether it is actually running and crunching data sets or not. This slows my PC and sometimes the PC will power down due to excess heating. Prior SETI version never did this. I have to go to XP's Process Viewer and kill v5.27 process to cool the CPU. Anybody know how to fix this bug??? Thankx!!!!
(XP Pro, 1.5 Gig RAM, AMD Athlon XP 3000+,2.16 Ghz).
...

If i understand your complaint correct your computer is overheating, while crunching seti@home workunits with stock v5.27. If that would be a bug, many more would have reported the same problem here in the Number Crunching forum. So, it seems this problem is singular only to your computer.
The first thing that comes to my mind is dust: when did you clean your cooling system the last time (fans, coolers, filters P.S.U.) ?
My second idea would be overclocking, but 2.16GHz seems normal for XP3000+.
Third there is a setting under "Your Account/General Preferences" called "Use at most", which is active since BOINC CC v5.6.x . It gives you the possibilty to lower the maximum usage of an application run by BOINC. Set it below 100% and see if it helps with your problem.

Well actually it appears that the image name "setiathome_5.27_windows_intelx86.exe" gets stuck in the Processes list after crunching a workunit. So, the CPU stays at 100%. The overheating crash is unique to this emachines W3080 PC. I know of one person whose emachines just burned out the mother board. My protection still seems to work. I don't think I will be getting another emachines. If the CPU stays at 100% for a long time on a hot day (like we have been having lately), protection kicks in and Windows tells me it is shutting down after a huge diagnostic dump. The stuck process keeps me stuck on 100% CPU too long. So, that is my little individual heating problem here.

I am more worried about the software malfunction. And an earlier post noted that I am at obsolete BOINC v4.25. So, I best get it in gear and download the latest. That seems like the place to start. Thank you for the help.

---

"It is often darkest just before it turns completely black."

...
Here is what I observe: BOINC will load the process and start it when the screensaver comes ready. This is normal operation. CPU will go to 100% as expected. Here are the 2 intermittents: Sometimes, when BOINC stops running it will leave the setiathome process loaded and the CPU will stay at 100% load. Sometimes I see 2 (TWO) "setiathome_5.27_windows_intelx86.exe" processes in the image name list. I kill one to return the CPU to its average lower load. But sometimes seti is a stuck process and only 1 (ONE) copy will cause 100% CPU. Of course, I check BOINC to make sure that File|Run based on preferences is selected. That is the case. I need to play with this, just observe it some more, or try some tests of some kind. This is intermittent and I have not found out the cause yet. Your suggestions appreciated.

You might try upgrading to a current version of BOINC. You seem to be using 4.25 which was obsolete when I started using BOINC in June of 2005, perhaps some of the other users here will recall something about it. If nothing else, others users will be happier if you go to a version 5.2.7 or later so your host can report the fpops_cumulative value used for credit calculations now.

                                                               Joe

Yup. I checked and it IS BOINC v4.25. Do you have a link to the upgrade?
This is a good place to start. Thanks for the tip.

Oooops, never mind. I found the upgrade link on BOINC. boinc_5.10.13_windows_intelx86.exe download in progress. Silly me.

---

"It is often darkest just before it turns completely black."