another thing to try is would be to run a memory test application to see if your memory is still good. One application is memtest86 (if memory serves me correctly).
Thanks i will try this. Seti never errors. i had einstein and seti running on one system and was fine then einstein and rosetta fails when adding rosetta. on another system i had seti and rosetta running fine then added einstein and rosetta and einstein fails
one system is 1.4 ghz the other is 600 mhz have tested ram and is okay.
Quote:
Quote:
... By the way it only started when i added a 3rd project, rosetta, and both rosetta and einstein fail. ... Doesn't it seems strange that the instruction would call its own memory location to be read?
If you're running rosetta also, be sure that you have the "leave applications in memory while preempted" option under your general preferences set to "yes". Rosetta requires this, and I don't know if it could be related or not, but perhaps if rosetta isn't being left in memory it's not properly releasing something then einstein and rosetta are conflicting over a memory address issue.
I'm brand new and confused. I know just enough about computers to really screw things up. (I was pretty good at DOS, but Windows has escaped me, and I don't have the time or youth to figure it out.)
All that said, I have been with SETI for years, but only just found out about the others when the changeover to BOINC came about. I elected to start with just Einstein in addition to SETI until I could get used to BOINC. I have completed and submitted one Einstein unit, but I'm not getting any new data to work on. My requests for further work go unfilled. Is it something I'm doing, or is the site locked out pending elimination of a bug?
It would help if you could give us some information. For example, can you give us copies of the exact error message. Also, if we could know things like type of computer, OS, BOINC version, the "connect every 'x' days" setting, and other such similar items.
Welcome to BOINC and to Einstein. I hope we can get this problem fixed for you. There is a whole new world of projects for you to enjoy.
Jim
You and Mike give me far too much credit. It took me two weeks just to find my way back this board again.
In trying to copy you the error message, my usual request to update did not go unfilled this time(!) so I have only my imperfect memory to relate "scheduler request: not receiving new workunits or ...posting?... results," I can't remember exactly. The only thing I can remember tinkering with was the .... response time? .... I set something from 0.1 day to 1.0 day. But that was several manual requests ago.
JUst to report from
)
JUst to report from here:
I am running win XP with multiple projects (einstein, seti, LHC and rosetta) on an Xp3000 AMD processor and I have had no trouble at all!
And I've been running Albert units for some time now.
Good work!
another thing to try is would
)
another thing to try is would be to run a memory test application to see if your memory is still good. One application is memtest86 (if memory serves me correctly).
Jim
I had an Albert WU that sat
)
I had an Albert WU that sat and went for almost 4 1/2 hours with 0% at all. I aborted the WU. WU is Here
Jeremy
RE: I had an Albert WU that
)
Two other users have successfully completed the same WU, so there is probably nothing intrinsically wrong with it.
Director, Einstein@Home
RE: RE: I had an Albert
)
Hmm, i dunno why it sat there for 4 1/2 hours with no progress at all on it. I'll watch the next ones that I got and see.
Thanks Bruce.
Jeremy
Thanks i will try this. Seti
)
Thanks i will try this. Seti never errors. i had einstein and seti running on one system and was fine then einstein and rosetta fails when adding rosetta. on another system i had seti and rosetta running fine then added einstein and rosetta and einstein fails
one system is 1.4 ghz the other is 600 mhz have tested ram and is okay.
RE: RE: I'm brand new and
)
You and Mike give me far too much credit. It took me two weeks just to find my way back this board again.
In trying to copy you the error message, my usual request to update did not go unfilled this time(!) so I have only my imperfect memory to relate "scheduler request: not receiving new workunits or ...posting?... results," I can't remember exactly. The only thing I can remember tinkering with was the .... response time? .... I set something from 0.1 day to 1.0 day. But that was several manual requests ago.
Anyway, I'm crunching again! Thanks!
Fletcher