Interesting, i have don a few workunits with no problems, but this evening i activated the screensaver and i got the same error massage as you. Maybe the screensaver is having problems switching between Einstein@home and Seti@home.
For the bughunters, the workunit was: w1_0647.0_0647.2_0.1_T03_S4hA_1
The specs of my machine are
AMD Athlon 2600+
512 RAM
ATI 9800 PRO 128 MB
Catalyst version 05.5
2D version 6.14.10.6546
driver version 8.132-050503a2-022511C-ATI
configuration version 6.14.10.5154
Well this boinc has given me a headache. I spent all day yesterday trying to get it to run e@H; find out about open gl; try to convert my graphics card; see a beta test version on offer; try that... etc. it was very frustrating and at the end of the long, trying session - no einstein!
today - a different story - I have a universe and it is running the screensaver - I am delighted - although I have no idea which step worked - after several crashes and retries - who can say?
Was having trouble with graphics due to ATI video card, so I switch to beta. The graphics are working fine now, but when they are up Einstein seems to run slower. Instead of time to complete droping by a few seconds at a time, it now increases a few seconds when graphics are open. No other troubles so far.
Same problem, very slow with screensaver:
Installed on old machine with Win 2000, 1 GHZ, ATI Rage Pro.
Regular version of Einstein did run, but very slow once the screensaver graphics went on. In non graphics mode, percentages increased by 0.01 by every few seconds. Once screensaver goes on, this takes about 5-10 minutes.
I couldn't find any other reason for the slowdown compared to the "official" App than a slight change in the priority settings, i.e. I think that people noticing a slowdown have something else running on their machines taking time the Ap has previously gotten. I know that the BOINC people changed this for good reasons, i.e. the computer becoming unresponsive when running BOINC in the background, so I would rather leave it that way.
I couldn't find any other reason for the slowdown compared to the "official" App than a slight change in the priority settings, i.e. I think that people noticing a slowdown have something else running on their machines taking time the Ap has previously gotten.
Interesting then that so many people are reporting a 2,000 second difference. I would expect a more random time variation.
Same problem, very slow with screensaver:
Installed on old machine with Win 2000, 1 GHZ, ATI Rage Pro.
Regular version of Einstein did run, but very slow once the screensaver graphics went on. In non graphics mode, percentages increased by 0.01 by every few seconds. Once screensaver goes on, this takes about 5-10 minutes.
Please see the Frequently Asked Question page. It sounds as if you are not using a desktop graphics mode that has accelerated OpenGL graphics. Without this the screensaver uses a lot of CPU time. You may be able to enable acceleration with the right graphics driver or desktop settings.
Validate state =
)
Validate state = Invalid
Looks like it didn't compare well with the other results returned.
Interesting, i have don a few
)
Interesting, i have don a few workunits with no problems, but this evening i activated the screensaver and i got the same error massage as you. Maybe the screensaver is having problems switching between Einstein@home and Seti@home.
For the bughunters, the workunit was: w1_0647.0_0647.2_0.1_T03_S4hA_1
The specs of my machine are
AMD Athlon 2600+
512 RAM
ATI 9800 PRO 128 MB
Catalyst version 05.5
2D version 6.14.10.6546
driver version 8.132-050503a2-022511C-ATI
configuration version 6.14.10.5154
RE: error massage I
)
I wonder who of the crew here does those. Bernd maybe? Where can we apply and does it hurt? ;)
(Nothing against you, Albert. Just kidding. :))
Well this boinc has given me
)
Well this boinc has given me a headache. I spent all day yesterday trying to get it to run e@H; find out about open gl; try to convert my graphics card; see a beta test version on offer; try that... etc. it was very frustrating and at the end of the long, trying session - no einstein!
today - a different story - I have a universe and it is running the screensaver - I am delighted - although I have no idea which step worked - after several crashes and retries - who can say?
I just subscribed to
)
I just subscribed to Einstein, and did not see any graphics (ATI Mobility Radeon 9700, 64 MB) Switched to beta - there you go...very nice...!
Was having trouble with
)
Was having trouble with graphics due to ATI video card, so I switch to beta. The graphics are working fine now, but when they are up Einstein seems to run slower. Instead of time to complete droping by a few seconds at a time, it now increases a few seconds when graphics are open. No other troubles so far.
http://www.boincstats.com/signature/user_217868.gif
Same problem, very slow with
)
Same problem, very slow with screensaver:
Installed on old machine with Win 2000, 1 GHZ, ATI Rage Pro.
Regular version of Einstein did run, but very slow once the screensaver graphics went on. In non graphics mode, percentages increased by 0.01 by every few seconds. Once screensaver goes on, this takes about 5-10 minutes.
I switched to beta without effect.
Andi
I couldn't find any other
)
I couldn't find any other reason for the slowdown compared to the "official" App than a slight change in the priority settings, i.e. I think that people noticing a slowdown have something else running on their machines taking time the Ap has previously gotten. I know that the BOINC people changed this for good reasons, i.e. the computer becoming unresponsive when running BOINC in the background, so I would rather leave it that way.
BM
BM
RE: I couldn't find any
)
Interesting then that so many people are reporting a 2,000 second difference. I would expect a more random time variation.
RE: Same problem, very slow
)
Please see the Frequently Asked Question page. It sounds as if you are not using a desktop graphics mode that has accelerated OpenGL graphics. Without this the screensaver uses a lot of CPU time. You may be able to enable acceleration with the right graphics driver or desktop settings.
Director, Einstein@Home