Note that the 221 is on a P4D/XP created today, which may or may not be the same hardware as one or both of the P4Ds Henri has been running XP_64 on. Only Henri can answer that one: his message log will have the answer to the 221, too.

I have one computer: Pentium D 920 (dual core). It has two different OSes: 32-bit Windows XP Home and 64-bit Windows XP Professional x64.

I had some migration problems with BOINC 6.1.8, so I decied to do a clean install. Now my 32-bit BOINC 6.1.8 is attached to four projects: Project TANPAKU, SETI@home, SETI@home Beta and World Community Grid.

Oddly, I haven't got any World Community Grid WUs. Are the WCG servers down or something?

Henri.

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

I think we're getting to the bottom of it now. See my edit to the previous post.

Ok.

Henri.

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

I have one computer: Pentium D 920 (dual core). It has two different OSes: 32-bit Windows XP Home and 64-bit Windows XP Professional x64.

I had some migration problems with BOINC 6.1.8, so I decied to do a clean install. Now my 32-bit BOINC 6.1.8 is attached to four projects: Project TANPAKU, SETI@home, SETI@home Beta and World Community Grid.

Oddly, I haven't got any World Community Grid WUs. Are the WCG servers down or something?

Henri.

I don't run WCG, so I can't say what the problem is there.

A couple of more questions about your basic setup:

1.) Do you run from a single BOINC folder in both XPH and XPP-64?

2.) Do you have BOINC installed as a service in both XPH and XPP-64?

Alinator

1.) Do you run from a single BOINC folder in both XPH and XPP-64?

They are in different folders.

Windows XP Home: G:\\Program Files\\BOINC
Windows XP Professional x64: C:\\Program Files\\BOINC

2.) Do you have BOINC installed as a service in both XPH and XPP-64?

They are both service installs.

HTH, HTH. (Hope This Helps, (my initials).)

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

Hmmm...

OK, let me think about this some.

FWIW, I run a dual boot setup under a common HID (2K/98SE) without problem. However the difference is you can't run a service in 9x. So what I did was install as a service in 2K on a FAT32 partition, and I just run in command line or single user mode directly from the BOINC folder when I boot into 9x. IOW, BOINC is not even 'installed' as far as 9x is concerned.

Alinator

I had some migration problems with BOINC 6.1.8, so I decied to do a clean install. Now my 32-bit BOINC 6.1.8 is attached to four projects: Project TANPAKU, SETI@home, SETI@home Beta and World Community Grid.

Oddly, I haven't got any World Community Grid WUs. Are the WCG servers down or something?

WCG is using secure connections, and this relies on a certificate. Due to a bug in v6.1.x, this certificate isn't handled correctly, and therefore WCG doesn't work. This particular bug should be fixed in v6.1.9, but there's likely many other bugs...

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

That appears to be something that shouldn't have happened. I don't see anything that would have cancelled this workunit.

What is with this WU? It says "Redundant result".

We think that something reasonable has happened (spawned new host CPID), but that it has been wrongly reported on the web tasks page.

We think that something reasonable has happened (spawned new host CPID), but that it has been wrongly reported on the web tasks page.

Agreed, the task was not technically a 221 Redundant Result.

It was dumped on an unconditional abort from the project because it was assigned to a different HID/CPID, and is displayed inaccurately on the summary page for the current HID.

The part I don't completely understand is why this happened. From Henri's description of his dual boot setup, there are two separate BOINC installations on different partitions. So assuming he had booted into XPH, I don't see why BOINC should have cross linked the two accounts when he did the install on the XPH partition.

Alinator

Yep, you're right. My bad. BOINC just doesn't have enough error code states to distinguish between "cancelled due to redundancy" and "cancelled because the host reset or detached and reattached" and "cancelled because the project decided to cancel that workunit and associated results".

I recently had a CPID change happen to a BOINC update from 5.X to 6.X. Apparently some XML file is not being copied properly from the "c:\\Program Files\\BOINC" location to the "c:\\Documents and Settings\\..." location. I've let Rom know about that problem, but I'm not sure it's related to this. Those were not service installations. You might want to drop Rom (or boinc_dev) a line on this one to let them know there may be a problem. Assuming you haven't already.

When I get back home from KPNO, I'm going to try a 5.X to the latest 6.X update on another machine.

Eric

---

@SETIEric@qoto.org (Mastodon)

WCG is using secure connections, and this relies on a certificate. Due to a bug in v6.1.x, this certificate isn't handled correctly, and therefore WCG doesn't work. This particular bug should be fixed in v6.1.9, but there's likely many other bugs...

Now I got a WCG workunit (Help Conquer Cancer) and I am still using BOINC 6.1.8.

---

Manned mission to Mars in 2019 Petition <-- Sign this, please.

WCG is using secure connections, and this relies on a certificate. Due to a bug in v6.1.x, this certificate isn't handled correctly, and therefore WCG doesn't work. This particular bug should be fixed in v6.1.9, but there's likely many other bugs...

Now I got a WCG workunit (Help Conquer Cancer) and I am still using BOINC 6.1.8.

Yeah we might need to look into the secure access code some more. I have gotten a few WCG tasks since updating to the 6.1.x clients, however none of them have successfully returned and validated. Even though occasionaly things get through enough is blocked to prevent it.

---

BOINC WIKI

BOINCing since 2002/12/8