Subject says it all really. Wondering when it will be fixed. Anyone know? I realise it being close to Xmas and all it is not likely to be done till January but just hoping to get an approximate time. Thanks.

Greg.

Ok, what are you talking about? I am running BOINC on two boxes both of which have dual AMD cpu's. It runs just fine. I also am rinning BOINC on a small farm of eight pc's. Both linux and windows. BOINC runs just fine on "multiple CPU's" for me just fine.

---

Running Sparc and Intel(non HT) dual processors here with no problems...

---

<img src="http://boinc.mundayweb.com/seti2/stats.php?userID=2259&amp;team=off">

@Greg

I have been running Boinc/Seti since the Beta stage using 3 different Dual Xeon CPU PCs, all with Hyperthreading, and all upgraded to XPSP2. I have never had a problem with selecting how many Cpus are used.
Sorry i cant help you with your problem, just letting you know I never had problems with the Boinc Software.

---

<img src="http://boinc.mundayweb.com/seti2/stats.php?userID=2036&amp;trans=off"><img src="http://www3.telus.net/seti/teamtest1.gif">

>Boinc for multiple CPUs. When will it be fixed?

it more looks like the fix(es) must be done on your client side.


*my* HT based clients are doing the job very well. With several client releases.

(os w2k / XP home + server / Windows Server 2003)

Excluding the delayed validation at seti, I cant find a reason to complain

---

<img src=\"http://www.setisynergy.com/images/stats/comb-207.jpg\">
multi Project BOINC Stats
<a href=\"http://www.setisynergy.com/stats/teams.php\">Team</a>
<a href=\"http://www.setisynergy.com/stats/individuals.php\">Individual</a>

> Subject says it all really. Wondering when it will be fixed. Anyone know? I
> realise it being close to Xmas and all it is not likely to be done till
> January but just hoping to get an approximate time. Thanks.
>
> Greg.
>
Are you selecting multiple cpus in your setup uder my account, general preferences?

---

> Ok, what are you talking about? I am running BOINC on two boxes both of which
> have dual AMD cpu's. It runs just fine. I also am rinning BOINC on a small
> farm of eight pc's. Both linux and windows. BOINC runs just fine on "multiple
> CPU's" for me just fine.
>

Running it on a P4 3.4ghz with XP and it DOESNT run fine. Also run it in a P3 1.13Ghz with XP and it DOES run fine. I run it on a P3 600 and a P2 400 both on 98SE and it runs fine until the moment you want to shut the machine down, reboot or have some other prog reboot then it shits itself and wont let the system reboot.

THAT is fine? Not really!

Thanks anyway.

Greg.

> > Subject says it all really. Wondering when it will be fixed. Anyone know?
> I
> > realise it being close to Xmas and all it is not likely to be done till
> > January but just hoping to get an approximate time. Thanks.
> >
> > Greg.
> >
> Are you selecting multiple cpus in your setup uder my account, general
> preferences?
>
>

Not any longer. The prog still shits itself and I have reinstalled it to be sure it didnt have some sort of corruption I couldnt readily identify. It doesnt appear to have that at least.

Once I went down to 1 allowed CPU only it seemed to run better but still often doesnt exit gracefully, doesnt show anything at all existing in the manager etc. Not really good.

Greg.

> @Greg
>
> I have been running Boinc/Seti since the Beta stage using 3 different Dual
> Xeon CPU PCs, all with Hyperthreading, and all upgraded to XPSP2. I have never
> had a problem with selecting how many Cpus are used.
> Sorry i cant help you with your problem, just letting you know I never had
> problems with the Boinc Software.
>

Version?

Same here gregh, I run 7 PC's & all are HT Capable with no problems, they all have XP Pro OS's some with SP1 & some with SP2 ... I'm using client version 4.13 ...

---

I have 7 dual xeons with HT, 1 single xeon with HT, 2 dual PIII and 1 dual PII. No problems here either. Running version 4.13

Dunc

---

> Running it on a P4 3.4ghz with XP and it DOESNT run fine. Also run it in a P3
> 1.13Ghz with XP and it DOES run fine. I run it on a P3 600 and a P2 400 both
> on 98SE and it runs fine until the moment you want to shut the machine down,
> reboot or have some other prog reboot then it shits itself and wont let the
> system reboot.
>
> THAT is fine? Not really!
>
> Thanks anyway.
>
> Greg.
>


Had a similar problem on an older machine once (single processor). If i wanted to re-boot I had to suspend seti first. Then I updated my display drivers and the problem went away. Don't know if that will work for you but it may be something worth looking at.

Kevin

I run intel p4 3.40 HT and it works Fine.
Two seti wu completed in 3.5 hrs
My 2.53 intel p4 non HT completes a seti wu in 3.75 hrs

It's probably the hardware upgrade you did [replace the 1.6 with the 3.4]

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

my one single HT p4 530 runs fine, my dual pII celeron 466s run fine.

and just a thought, please don't create 4 threads with the same question, and then tell everyone that tries to help you that they are wrong.
and yes, _I_ have been working and running businesses in this field for 14 years too.

---

S@h Berkeley's Staff Friends Club

Okay, lets try and attack this from a different angle, if you start a command shell and type 'set' and hit enter, how many processors does Windows report?

Example:
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 7, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0207

This is from my computer, and all two HT processors are humming right along.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

If you want things fixed I suggest you collect your information and post it for Rom. He is one of the seti programmers. Wrote the new interface (4.5xx) and is primary windows coder.

oK HERE IS MY INTEL 3.40 P4 HT INFORMATION
THE SAME ONE AS GREGH?
WORKS OK HERE

NUMBER_OF_PROCESSORS=2
OS=Windows_NT
OSVER=winXPH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0209

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

> If you want things fixed I suggest you collect your information and post it
> for Rom. He is one of the seti programmers. Wrote the new interface (4.5xx)
> and is primary windows coder.
>

that is exactly what I did or didnt you read that?

> my one single HT p4 530 runs fine, my dual pII celeron 466s run fine.
>
> and just a thought, please don't create 4 threads with the same question, and
> then tell everyone that tries to help you that they are wrong.

So when they tell me:

1) Reinstall the OS when only 2 progs cause problems.

2) Your computer hardware is at fault as it is incompatible even though I am using that computer to post with

....YOU think *I* am wrong? Sigh....

> and yes, _I_ have been working and running businesses in this field for 14
> years too.
>

That would make you my junior by a long shot but let's not compare those sorts of notes. If you have something constructive, go for it. If you dont, then dont.

> Okay, lets try and attack this from a different angle, if you start a command
> shell and type 'set' and hit enter, how many processors does Windows report?
>

2, as expected. The only thing that changed on this machine was the CPU. Before the update it was a 1.7Ghz P4 which seemed to go OK with the Boinc stuff. The 3.4 just doesnt get on with it. However, when I alter my prefs on the web site here to use only 1, things arent quite as bad. They still do things like Boinc Manager starting up showing no connected projects, no work etc while the task manager shows Boinc, Boinc Manager and a Seti WU running. They still cause intermittent faults that never occur when Boinc Manager 4.56 isnt running. This is atypical "cant get on with the processor" behaviour. Using 1 or 2 processors, when probs occur and I kill off Boinc and Seti stuff in task manager, the problems go away.

As for Win98SE on 2 other machines, still getting those damned interrupts by Boinc Manager 4.56 which wont allow shutdown without first exiting Boinc Manager.