i installed vista on my x2 3800+ last night and just installed boinc 5.8.8 a few minutes ago. it seems to be chugging along nicely. the only thing i completely forgot to look into was transferring my WU's before i formatted. is there any way that i can retrieve the WU's already assigned to me so i don't leave all those WU's hanging in the seti system?

---

i installed vista on my x2 3800+ last night and just installed boinc 5.8.8 a few minutes ago. it seems to be chugging along nicely. the only thing i completely forgot to look into was transferring my WU's before i formatted. is there any way that i can retrieve the WU's already assigned to me so i don't leave all those WU's hanging in the seti system?

I would guess if you did a fresh install, since you mentioned formatting, that those work units were hosed. They'll time out and be resent to someone else if necessary. Whenever I plan an OS change, I set that computer to "no new work" in the BOINC manager and let it run dry.

i installed vista on my x2 3800+ last night and just installed boinc 5.8.8 a few minutes ago. it seems to be chugging along nicely. the only thing i completely forgot to look into was transferring my WU's before i formatted. is there any way that i can retrieve the WU's already assigned to me so i don't leave all those WU's hanging in the seti system?

I would guess if you did a fresh install, since you mentioned formatting, that those work units were hosed. They'll time out and be resent to someone else if necessary. Whenever I plan an OS change, I set that computer to "no new work" in the BOINC manager and let it run dry.

thanks
sorry about the lost units. i forgot about them in the excitement of switching to vista.

---

To get back to the orginal topic...

I am also running BOINC on a dual-core pentium with Vista (Ultimate). The "run by preferences" option is being ignored, and the processes are running full time even though my preferences say not to run when the user is active. The XP and 2000 boxes of the same make run correctly.

Yes, this happened to me too when I put BOINC on my Windows Vista Ultimate Edition. It no longer uses the preferences (not the local ones set in the "Simple View" UI, and not the ones set on the website). Like you describe, it just runs full time.

Anyone know what the deal is?

---

Yesterday I installed Vista Home Premium into one of my 3.0 dual core computers, reinstalled Boinc and it is taking about 3,600 seconds to complete the average work unit. This on top of the fact that I haven't had any time to optimize the computer, nor the Seti app.

Anyone else getting the same results?

Compared to what on (say)XP, for the same computer?

---

.

Hello, from Albany, CA!...

To get back to the orginal topic...

I am also running BOINC on a dual-core pentium with Vista (Ultimate). The "run by preferences" option is being ignored, and the processes are running full time even though my preferences say not to run when the user is active. The XP and 2000 boxes of the same make run correctly.

Yes, this happened to me too when I put BOINC on my Windows Vista Ultimate Edition. It no longer uses the preferences (not the local ones set in the "Simple View" UI, and not the ones set on the website). Like you describe, it just runs full time.

Anyone know what the deal is?

This may be a stupid idea... but possibly a port that needs to be opened to communicate the data through?

---

Free Web Directory | Scrabble Resources | Free Whois Tool

To get back to the orginal topic...

I am also running BOINC on a dual-core pentium with Vista (Ultimate). The "run by preferences" option is being ignored, and the processes are running full time even though my preferences say not to run when the user is active. The XP and 2000 boxes of the same make run correctly.

Yes, this happened to me too when I put BOINC on my Windows Vista Ultimate Edition. It no longer uses the preferences (not the local ones set in the "Simple View" UI, and not the ones set on the website). Like you describe, it just runs full time.

Anyone know what the deal is?

This may be a stupid idea... but possibly a port that needs to be opened to communicate the data through?

Seti simply won't run on my new computer with Vista. The Nvidia says <Driver components mis-match>. Exit is the only option. A bit dramatic but slightly better than when it just crashed after 2 seconds. I am fed up of Vista already but I suppose there will be a version of seti for vista eventually? bonzo

---

I upgraded my dual Xeon [edit - host 2901600, if you want to check out the results] from Windows XP Pro (32 bit) to Vista Business over the weekend. All four projects (SETI, SETI Beta, Einstein and CPDN) continue to crunch as normal - didn't lose a WU. Not enough data yet to report on speeds, but subjectively it seems very similar - if there is a change, I doubt it's statistically significant.

Would it help anyone if I wrote up the process? Preparation, procedure, a couple of gotchas I encountered along the way?

Ok I give up! I've finished installing Vista (Ultimate) On my Pentiun 4 660 (Dual Core) 3.6 Ghz which happily chugs along at 3.8+Ghz. Along with a couple of Gig of Mushkin 667 ram, an ATI AX800XT graphics card and a lot of Hard disk in raid 0.
The only problem I had was the need for a new Modem/Router to get on the net. Then I reinstalled Boinc! Crunch3r and the chicken app. Great it runs at a snails pace then grinds to a halt and I get a client error!
I've turned off just about everything I can get away with and still run. And added a 2 gig memory stick for the computer to use as spill over ram and still nothng.
I've been playing with computers since I built my first ZX80 but this has got me beat.
I'm now thinking of burning the next few month budjet and looking at a new mother board, quad core pentium and about 8 gig of ram, but I think that will have to wait a while.
Any suggestions other than revert to Xp would be great. I have to run Vista now for the work I do!

Barry

---

Any suggestions other than revert to Xp would be great. I have to run Vista now for the work I do!

Barry

Throwing more/newer hardware at it isn't going to solve your problem. It might help to know what errors you're receiving (if any), or a detailed description of what's happening (other than simply "it's grinding to a halt"). Also, have you tried without Crunch3r's BOINC client? Another user had problems with it and when he stuck with the standard app, it seemed to work fine.

If you're using Crunch3r's CPU Affinity feature, that may be the reason for your computer grinding to a halt.

---

Any suggestions other than revert to Xp would be great. I have to run Vista now for the work I do!

Barry[/quote]
Just out of curiosity...What will vista do that XP won't? I am not be a jerk but am seriously curious.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Frankly Hiamps as far as I can see absolutely nothing. Especialy from the business pont of view. My problem is I work on Video baed web sites with a guy based in England and we run our computers with identical software setups so we can interchange anything we are working on without having to find what works it and why! Unfortunately he's just bought a new one - top of the range - and it came with Xp Ultimate intalled. So I tried out a dual boot for a few weeks but ended up needing to install either all Vista or a couple more hard drives and as I've running 4 at the moment I took the line of least resistance! Think I got that one wrong as well.
Barry.

---

Hi OzzFan, sorry missed your reply at first, ok I've tried the standard Boinc client, The crunch3r one and optimised one by Chicken coop both SSE3 and SSE2 (which seemed to work a little better). When I say grinding to a halt it does just that, starts crunching with the graphics I've been running to see what it's doing, working in staggers, then it just stops and I get a message SSE2(3) has stopped working - close program. An the last 2 WU's I've done like this have come up Client error and the following message;
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x77732086 read attempt to address 0x10AF7521

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 5.5.0


Dump Timestamp : 04/12/07 03:25:50


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x77732086 read attempt to address 0x2DE9200B

Engaging BOINC Windows Runtime Debugger...



Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x77732086 read attempt to address 0x2DE9200B

Engaging BOINC Windows Runtime Debugger...


</stderr_txt>
]]>

Hope you have an idea what I can do to sort this out as I'm down to crunching on my laptop for now.
Cheers,
Barry.

---

Frankly Hiamps as far as I can see absolutely nothing. Especialy from the business pont of view. My problem is I work on Video baed web sites with a guy based in England and we run our computers with identical software setups so we can interchange anything we are working on without having to find what works it and why! Unfortunately he's just bought a new one - top of the range - and it came with Vista Ultimate intalled. So I tried out a dual boot for a few weeks but ended up needing to install either all Vista or a couple more hard drives and as I've running 4 at the moment I took the line of least resistance! Think I got that one wrong as well.
Barry.

---

An the last 2 WU's I've done like this have come up Client error and the following message;
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x77732086 read attempt to address 0x10AF7521

Engaging BOINC Windows Runtime Debugger... (snip)

According to a web search, the errors you are receiving are due to potentially bad/failing RAM*. Try running MemTest86+ on your system for a few hours or more and see if you start getting errors. If you do, you should take it back and have it serviced if it's still under warranty.

*It was also stated that these errors can also be poorly written drivers for any piece of hardware in your system (chipset, video, nic, sound card, etc). Most commonly though, under XP or Vista, these errors can be caused by Malware/Adware/Spyware on your system. Try running Ad-Aware and Spybot: S&D on your system and remove all threats. This may clear up the problem as well.

---

Frankly Hiamps as far as I can see absolutely nothing. Especialy from the business pont of view. My problem is I work on Video baed web sites with a guy based in England and we run our computers with identical software setups so we can interchange anything we are working on without having to find what works it and why! Unfortunately he's just bought a new one - top of the range - and it came with Vista Ultimate intalled. So I tried out a dual boot for a few weeks but ended up needing to install either all Vista or a couple more hard drives and as I've running 4 at the moment I took the line of least resistance! Think I got that one wrong as well.
Barry.

In addition to Ozzfan's really good suggestion, something 'bout Vista's video subsystem sounds funny, maybe the video drivers might be not quite there yet... I missed whether this has been tried or suggested but... have you tried the "nographics version" of the science app to see if that might be it ? I had no end of problem with the graphics when I started "0xc..." rings some bells, so I ditched it and never looked back.

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Hi Guys, thanks for all the advice, I ran a mem test all night and it all came up 100% thankfully, and cleaned out everything in the way of adware etc, but still no luck. So I'll give up the ghost on this computer for a bit until I can sort out an upgrade, which I think it needs, as even just sitting there it's using 35% of the 2 gig of memory. Might fit an external disk and dual boot to crunch in the mean time! Be back soon.
Barry.

---

FYI.
I read somewhere that BOINC should not be installed to it's default location as vista doesn't want to write to "X:\\program files" directory.
It's supposedly a "security" feature.

Don't know if it's true but it might be worth checking.

Hope this helps. :D

---

Qunpu' lo'taHmo' jIH yItamQo'

FYI.
I read somewhere that BOINC should not be installed to it's default location as vista doesn't want to write to "X:\\program files" directory.
It's supposedly a "security" feature.

Don't know if it's true but it might be worth checking.

Hope this helps. :D

Not true, Vista will Install and run correctly wherever you decide to put it.
When doing default install, it goes to C:\\Program Files (X86)\\.. and on my system I saw slight improvement over Windows X64 install.
Later I reinstalled to a small external drive G:\\Program Files(X86)\\.. under both VISTA and X64 so that whatever OS I boot into, there is no loss or need to merge systems.
I have Vista on SATA Drive Disk(1) and X64 is on identical SATA drive Disk(0).
There are still several annoying things about VISTA that will be worked out with time so untill then I will keep the X64 ticking.

---

When we finally figure it all out, all the rules will change and we can start all over again.

Not true, Vista will Install and run correctly wherever you decide to put it.

This has been my experience as well. So far, I have three Vista systems (two Home Premium x64 and one Ultimate x64), and I installed BOINC into the default C:\\Program Files(x86)\\BOINC folder and have had no issues at all.

---