> And what if the number of SETI/BOINC users goes up from 70,000 to 140,000,
> then what?

I think that's why they are migrating to new servers.

We're still on the old one(s).

---

Uploaded my last WU a couple hours ago.I figured theirs no point in banging on the system so I moved one PC over to predictor and the other I shut down for much needed servicing.Some of the fans were starting to get noisy.This is a perfect opportunity to do a OS reload and change out those fans.I might even consider a CPU upgrade.Maybe kick it up to a 3 ghz from a 2.66 ...Hmmm maybe some more ram to o. Question to anyone that might know,Have anyone had problems with a Viper video card?Specifically a 9600XT 256mb.Screen just seems to blank out like theirs no card at all.Also causing severe crashing to point where I have to physically turn off the computer.No error reports in the XP log.

I did some driver updates recently and that caused my system to start acting strange. I flashed my BIOS with an updated version and that cured my problems. That is something you should check on Flashdrive.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.

> I did some driver updates recently and that caused my system to start acting
> strange. I flashed my BIOS with an updated version and that cured my problems.
> That is something you should check on Flashdrive.


>This thread has now become polymorphic.

Maybe you should try uninstalling the offending drivers, and then reinstalling them. They just might be in the wrong place or something Steve.

I don't know your OS.

> > I did some driver updates recently and that caused my system to start
> acting
> > strange. I flashed my BIOS with an updated version and that cured my
> problems.
> > That is something you should check on Flashdrive.
>
>
> >This thread has now become polymorphic.
>
> Maybe you should try uninstalling the offending drivers, and then reinstalling
> them. They just might be in the wrong place or something Steve.
>
> I don't know your OS.
>

I said updating the Bios fixed my problem, read before you post!

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.

> > > I did some driver updates recently and that caused my system to
> start
> > acting
> > > strange. I flashed my BIOS with an updated version and that cured
> my
> > problems.
> > > That is something you should check on Flashdrive.
> >
> >
> > >This thread has now become polymorphic.
> >
> > Maybe you should try uninstalling the offending drivers, and then
> reinstalling
> > them. They just might be in the wrong place or something Steve.
> >
> > I don't know your OS.
> >
>
> I said updating the Bios fixed my problem, read before you post!

OOPS!>

I think they sould stop sending new work until everyone send there results or every result timeout, then send the results needed to finish the unfinished wu's until all wu are completed .
After this they sould upgrade everything , solve the db slowdown and other possible errors .
In the mean time people sould attach to other project(s).

Like predictor , cpdn (that have lots of work) or even pirates (that have work from time to time) and for the lucky ones einstein.

---

> > > I did some driver updates recently and that caused my system to
> start
> > acting
> > > strange. I flashed my BIOS with an updated version and that cured
> my
> > problems.
> > > That is something you should check on Flashdrive.
> >
> >
> > >This thread has now become polymorphic.
> >
> > Maybe you should try uninstalling the offending drivers, and then
> reinstalling
> > them. They just might be in the wrong place or something Steve.
> >
> > I don't know your OS.
> >
>
> I said updating the Bios fixed my problem, read before you post!
Thanks for the addvice Steve but its definatley the video card.she's a crispy gritter looks like i'll be looking for a new card.

An interesting notion was brought up, whether intentionally or not. That being, the purpose of the Update (Retry Now) option. If it is intended to reconnect the client after it has stopped responding, like Ingleside suggested, then how does the server know if I am hitting Update for the right reason or not?

Perhaps I am hitting Update because my client has stopped responding, yet my internet connection is constant and my computer up until a few moments ago was running BOINC just fine. Then, about a minute later, I hit Update again, because the client has stopped responding, and after that I hit it again because my client has stopped responding, and after that...

My point is, every time you hit Update, the Messanger shows that communication with the scheduler is deferred for X number of minutes before attempting to reconnect. Yet, by hitting Update, you are overriding this time even though it is increasing every time you do so. You are forcing the client to attempt a reconnect to the scheduler, even though the penalty of automatic reconnect keeps getting longer and longer. Where is the harm? You are using a client-side option to override the automatic request to connect to the scheduler, where the penalty is more time before you can connect to the scheduler. Either the client waits to discover this out for itself, or you override the automatic process and discover this out for yourself. Either way, the client will connect to the scheduler or be forced to wait before it can automatically try to connect for itself. In contrast, flooding the server would be an effort to prevent others from connecting, something that repeated use of the Update option has not been proven to cause.

The only obstacle that must be overcome is time, spent trying to connect to the server, or processing a project that was downloaded from the server.

LEX

---