Digger,
Where are you looking to find this this?

> > Ever since I DL'ed v. 4.1 I have choppy graphics; that is when the
> program is
> > responding. It seems to lock up and quit process data - v. 4.09 ran like
> a
> > charm.
> >
>
> Thanks PK28... that at least confirms that someone else is having the same
> problem as i am having. When you look at your account after it is updated,
> are these failed work units showing up as client errors? Just curious.
>
> Dig
>

---

Bill McIlwee
wmcilwee@charter.net

> Hi again Ralic. I'm sorry but i'm a bit confused by your suggestion. If we
> had a problem with our hardware (i.e. memory/disk issues) then why did this
> only start happening with version 4.10? OR... are you perhaps simply trying

[going OT]
I have had experience with science apps that have downloaded, passed the MD5 check and churned through wu's throwing errors. These have been resolved by a project reset. Admittedly, these usually throw errors immediately, and not only when invoking specially functionality, like graphics. (it's a long shot)
[/going OT]

Since I'm not able to replicate the problem myself, I'm just offering ideas that I would try myself to resolve the problem.

You'd be surprised how many strange errors can be resolved with a machine reboot. ;-)

---

> You're right, my bad for going OT.

Really no big deal! It's kind of hard to know where "the line" is anyway. :)

> There is an existing bug on this issue, no 97
> I'd be inclined to post a follow-up to that, but indicate in the follow-up
> that you're using SAH v4.10 and as much other detail as you can provide.

Funny, I'd already looked at that and written it off because the subject was losing graphics when going from BOINC 4.19 to 4.25 (mine worked fine with both) were as I "lost it" when going from S@H 4.09 to 4.10, but you guys have been doing this alot longer than me, so I'll go with your suggestion. Thanks.

> For those of you who can't get any graphics at all... try repeatedly hitting
> the "show graphics" option and see if it eventually displays. If it does, do
> you then get a client error? I'm curious about this.

Digger, this definitely was not a problem ! I had heard that 4.10 resolved alot of screensaver issues, so I was looking forward to it (my only issue is no screensaver when password protecting). When I finally got a 4.10 WU and had no graphics at all (a GIANT step backwards to me), I'm afraid I was, shall we say "a little abusive" of the "show graphics" option (my mouse clicking finger is still a little red! ;) I've tried that and the Win screensaver "preview" a number of times and no a hint of anything - but also no client errors either.

Thanks to all of you for your responses - Greg

---

PK28,

If you look at your account page (click the link up above) and then view your results history, are you seeing a lot of Client Errors since you started crunching 4.10 work units? That's what i was asking. You may or may not be, but that is the issue i have been having. :)

Dig

---

> Since I'm not able to replicate the problem myself, I'm just offering ideas
> that I would try myself to resolve the problem.
>
> You'd be surprised how many strange errors can be resolved with a machine
> reboot. ;-)
>
>

No problem, Ralic! I just appreciate your trying to help us all out. I've rebooted my machine a number of times now with the same result. However, i will try a project reset per your suggestion if you feel it might be necessary. I just hate to leave all these work units orphaned, as i know it will delay other folks from recieving their credit (they will have to be sent back out again).

Dig

---

Dig,
I have one Client Error. Note that I have managed to DL only four files since the update. One file reported, one Client Error'd, one is froze at 11.31%, and one is waiting to run.

---

Bill McIlwee
wmcilwee@charter.net

> rebooted my machine a number of times now with the same result. However, i
> will try a project reset per your suggestion if you feel it might be

Considering that the problem is not isolated to one user, the chances of a reset solving the problem is a long shot, which is why I don't suggest everyone try it.

If you've already tried a reboot, then there's probably not much more to try.
Let's hope Rom can narrow it down asap.

---

> Funny, I'd already looked at that and written it off because the subject was
> losing graphics when going from BOINC 4.19 to 4.25 (mine worked fine with
> both) were as I "lost it" when going from S@H 4.09 to 4.10, but you guys have
> been doing this alot longer than me, so I'll go with your suggestion.

There's quite a bit of investigating going on around the graphics issues at the moment. I could ramble all night, but to summarise, that bug (97) seems closest to the problem being reported in the original post, since it covers the following elements BOINC 4.25, Screensaver, Graphics API, recently built client app

It's that "line" issue that you mentioned. With the graphics, it's more like a tree, than a line :)

---

> Dig,
> I have one Client Error. Note that I have managed to DL only four files since
> the update. One file reported, one Client Error'd, one is froze at 11.31%,
> and one is waiting to run.
>

Okay, PK28... thanks! I think this means that it is out of our hands. I'm not going to try a project reset at this point. As long as i stay away from graphics there doesn't seem to be a problem. You might consider staying away from the screensaver and/or "show graphics" options for a while until Berkeley gets this straightened out. If you can, post a link to your results history so that i can compare it to my own. Just so you know, allowing your computer to be 'seen' does not divulge any personal info. Your IP is only visible to yourself. You can click on mine to see what i mean.

Thanks again,

Dig

---

> There's quite a bit of investigating going on around the graphics issues at
> the moment. I could ramble all night, but to summarise, that bug (97) seems
> closest to the problem being reported in the original post, since it covers
> the following elements BOINC 4.25, Screensaver, Graphics API, recently
> built client app
>

Thanks Ralic. Since i've been using BOINC 4.25 all along, and only experienced the graphics 'bug' since SETI 4.10 was downloaded to my machine last night, i'm not sure if that particular bug applies to me, but who knows if they are somehow not all inter-twined? Regardless, i am going to follow your advice and NOT do a reset at this time, since everything seems to be okay as long as i stay away from those graphics. :)

As always, your help is appreciated.

Happy crunching. :)

Dig

---

I got 4.10 yesterday. One WorkUnit crunched OK for about 3,5 hours, then quit do to a client error. The second Unit (waiting for the first to finish) went directly to 100%.

FYI: i did not use the graphics at all!

Hopes this helps the people at the Development department further. For now 4.09 has been reinstalled (see latest news at HomePage), so I can continue crunching.

logging off...

---