Having recently installed the latest version of Boinc (6.10.17) everything was running fine, then suddenly Seti detached from Boinc, work in progress was lost, and the only resolution was to re-attach and download new work units.

I am also running Rosetta on the machine, but the two projects always ran happily together before.

Does anyone else have experience of this, or is it possibly just a random event on my machine?

Regards

Peter

---

I didn't have this particular problem, but another related to this version of BOINC. When I installed 6.10.17 on my multi-processor machines, periodically the amount of processors being used would drop, e.g.- on a 4 processor machine only 2 would be in use. Never saw this with a previous version, so I went back to 6.6.41. I'm running XP and Vista(32 and 64-bit). Saw the problem on both XP (Q6600) and Vista 64-bit (i7 920).

---

Steve,

Thank you for your response.

Boinc has been running for a few hours now and all seems to be in order. both the CPU and GPU (CUDA) units are running fine. The dual core CPU is showing 2 units running, and Cuda is also running when the machine is idle.

Reading the forum threads, it seems that the new version was well tested before widespread launch so perhaps this was just a glitch on my machine, however, we will see if any others report such problems.

Regards

Peter

---

I didn't have this particular problem, but another related to this version of BOINC. When I installed 6.10.17 on my multi-processor machines, periodically the amount of processors being used would drop, e.g.- on a 4 processor machine only 2 would be in use. Never saw this with a previous version, so I went back to 6.6.41. I'm running XP and Vista(32 and 64-bit). Saw the problem on both XP (Q6600) and Vista 64-bit (i7 920).

Are you attached to a project that uses multiple CPUs if available?

---

BOINC WIKI

Hello
I put the 6.10 on,and only the XP box caught it. The Win Vista, and the Win 7 puter still show that 6.6 is running. I tried first just running the 6.10 .exe, no go. Then I deleated 6.6 and ran the 6.10 .exe. Yep, no go. Any one know what I messed up.
celttooth
P.S. I hope this is the right form for this post!

---

I tried first just running the 6.10 .exe

How do you 'just run the 6.10 .exe'? BOINC comes with its own installer, don't you run that? It'll be named alike this: boinc_6.10.17_windows_intelx86.exe

You will have to explain a tiny bit better what you are trying to do.

---

Hi:
Sorry I have misspoken, I downloaded the 6.10.17 program from the server and ran it first with out uninstalling the old 6.6... program. This only worked on my Intel P4 puter running Win XP. My two Intel Quads one running Win 7, and the other running Win Vista sill would not install 6.10.17 even after I tried to uninstall 6.6...
Can any one think where I am going wrong?
celttooth

---

Yes, John, I do. However, I confirmed that those projects (AQUA is all that I know of that I'm attached currently) were not running when I observed this behavior. I do, however, think that this project had recently finished a computation cycle (currently set at 60 min per standard preferences). I do have 'leave in memory' also set. I have not seen this on my 4 X 2 Xeon machine, which does not run AQUA. Please convey any information you have pertaining to this phenomenon. I'd be happy to try it again if their is a problem that needs characterization.

---

and the other running Win Vista sill would not install 6.10.17 even after I tried to uninstall 6.6...

What kind of error message do you get? Or if you don't see any errors, what behaviour do you see?

Any latest entries in the stderrdae.txt file (which you can find in your BOINC data directory)?

We don't see what you see, you will have to tell us. But it is difficult to help you if all you say is that it doesn't install.

---

similar problem.
boinc will not comunicate (app needs to close)
on the task bar i noticed a red dot in boinc, checked to see and boinc can't com with server.
and detetched, when't to re-attach(only highlighted)and all my WU's (seti/milk)returned, started crunching for ten seconds and then repeated same problem (app needs to close)

ps: windows system reports no problem with boinc
the boinc app is approx 4 months old running flawlessly
this problem i noticed yesterday the 6th nov....ver 603

---

I install 6.10.17 on a new win 7 install, no problems.Updated to 6.10.17 on another,was running, then everything disappeared and could not attach again.. Reinstalled 6.6.38 and connected right away.
Something is screwy with 6.10.17 !!

---

KenW

I install 6.10.17 on a new win 7 install, no problems.Updated to 6.10.17 on another,was running, then everything disappeared and could not attach again..

Please post the BOINC start-up messages of around that time. You can find those in your stdoutdae.txt file in the BOINC Data directory. Then we can see what you mean with "everything disappeared".

---

Too late now, but in the Advanced view all work units were gone. There were work units in the \setiathome.berkeley.edu folder.

---

KenW

Too late now...

No, all messages are stored in stdoutdae.txt (and if that already changed over, the previous messages are in stdoutdae.old). So you can look up that part and post it here.

---

Yes, John, I do. However, I confirmed that those projects (AQUA is all that I know of that I'm attached currently) were not running when I observed this behavior. I do, however, think that this project had recently finished a computation cycle (currently set at 60 min per standard preferences). I do have 'leave in memory' also set. I have not seen this on my 4 X 2 Xeon machine, which does not run AQUA. Please convey any information you have pertaining to this phenomenon. I'd be happy to try it again if their is a problem that needs characterization.

If Aqua has one in the queue that is second in line to run, you will have n-1 CPUs idle because of a problem with the CPU scheduler.

---

BOINC WIKI

Hi:
I tried to find the files you wrote about in your other post, but my skill on computers has taken a very hard hit while I have been ill. I am doing my best to get caught up on all of this, so there may be a lag in my relearning. I don't know how to get to the stdoutdae.txt file or the stdoutdae.old file. I will post them if there is an easy way to find them. Please bear with me. I do still believe in the goals of the project, and dearly wish to contribute again.
celttooth

---

The log files (stdoutdae.txt and stdoutdae.old) can be found in your BOINC Data directory. By default found in C:\ProgramData\BOINC\ under Vista and Windows 7, or C:\Documents and Settings\All Users\Application Data\BOINC\ under Windows 2000 and XP.

This directory may well be hidden, so either put the path to it directly into Windows Explorer, or instruct Windows Explorer to show hidden files and folders.

For Windows 2000 + XP: See here.
For Windows Vista: See here.
For Windows 7: See here.

Don't post the whole log! By default it's 2 megabytes large. So open it in Notepad and find the time and date you started BOINC 6.10.17, then only copy those start-up messages and post them here.

---

It's only a minor thing, but 6.10.17 seems very generous in calculating GPU GFLOPS. It rates my 2 8600GT's at 76 GFLOPS each and even my poor old 8400GS is credited with 22 GFLOPS.

It's very flattering but a bit hard to believe seeing as the crunching times haven't changed :-)

Brodo

Those are the peak amounts your GPUs can do, as reported by your videocards. BOINC isn't calculating anything, just detecting this through the Nvidia API.

The hardware didn't change, just the formula with which the amount of FLOPs are calculated. So your run times stay the same.

---

The new Nvidia API that BOINC 6.10 uses has a minimum driver set of CUDA 2.2, 185.85.

If your present drivers are below this version, update first.
If your present drivers are below this and they're the last available for your hardware, you cannot update to 6.10; stay at the last 6.6.x version for your OS.

Spread the word.

---