Just got WU "1ogw__topology_sample_207_14327_6" with Report Deadline 3 days ago. (12/19).

just look at my imput drop

and in another message:

I have just abouted over 800 defalut WU's

You don't see anything that might possibly be RELATED in those two statements? If you would quit aborting WUs, perhaps you would get credit for them!

I would guess I have about 1000 of the failed jobs over the last few days

I would believe it. You have been aborting all the GOOD ones, leaving nothing for your computers to spend their time on but the BAD ones. At 30 seconds apiece, you can go through a bunch of those in a hurry.

My beef is the the WU's clock just stops and if rebooted you lose all or most of the time that was put into that job

We've already been through this - and you STILL have not given any explanation for why you would CONCEIVABLY reboot. You haven't answered any of the questions you have been asked. Do you WANT help? Or do you just want to whine?

I do not have the time to read this website to see if a problem is or is Not Fied If this project can not produce Good WU's I and other just will not run it

But you have time to reboot 50 systems and abort 800 WUs for no reason...

The staff has said - YOU WILL GET CREDIT for the 'DEFAULT_xxxxx_205" WUs they have sent out. Period. Good or bad. Of course, you will ONLY get credit for the ones you have LET RUN. If there is a "DEFAULT_xxxxx_205" in there, you will get credit for however much time you spent on it before aborting it. All these _other_ WUs you have been aborting FOR NO REASON, you will NOT get credit for.

Why is this so hard for you to understand? If you have a problem - describe the problem and ask for help. We will help you. But we CANNOT help you if all you say is "I had to reboot", and won't answer "Why?", and continue to do things you have been told you should not do!

Just got WU "1ogw__topology_sample_207_14327_6" with Report Deadline 3 days ago. (12/19).

Dimmerjas, your computers are hidden, so we can't look at this WU. Can you either unhide your computers or provide a link to the one in question?

Just got WU "1ogw__topology_sample_207_14327_6" with Report Deadline 3 days ago. (12/19).

Dimmerjas, your computers are hidden, so we can't look at this WU. Can you either unhide your computers or provide a link to the one in question?

[b]"I'm trying to maintain a shred of dignity in this world." - Me[/b]

It seem you have a vary bad aditude About giveing help I am sory I my not be as smart as you on in the IT field SSo it is hard for me But it is clear you wold rather insult me then help me So be it I will uninstall your software So I will not be a bother to you I wish you and your project the best of luck

It seem you have a vary bad aditude About giveing help I am sory I my not be as smart as you on in the IT field SSo it is hard for me But it is clear you wold rather insult me then help me So be it I will uninstall your software So I will not be a bother to you I wish you and your project the best of luck

My computer is now unhidden.
Have just got antoher WU with Report Deadline 3 days ago. (12/19).
That one too finished with error:
"22-12-2005 20:06:58|rosetta@home|Computation for result DEFAULT_1n0u_218_538_1 finished".

And yet another one. It seems they come, and go, endlessly right now.

Bill, I have one here:

12/22/2005 6:49:54 PM|rosetta@home|Unrecoverable error for result 1ogw__topology_sample_207_12019_6 ( - exit code -1073741819 (0xc0000005))

My computer is now unhidden.
Have just got antoher WU with Report Deadline 3 days ago. (12/19).
That one too finished with error:
"22-12-2005 20:06:58|rosetta@home|Computation for result DEFAULT_1n0u_218_538_1 finished".

And yet another one. It seems they come, and go, endlessly right now.

I found that one here - the deadline on it however is JANUARY 19, 2006... Where are you seeing the invalid deadlines? In the Work tab? In the message you posted above, is the 20:06:58 your local time or UTC time? If UTC, is your system clock set correctly?

If you get another one of these, can you check your Messages tab for any "your computer is overcommitted" warnings? If the deadline as "seen" by BOINC is already passed, you should be getting this warning.

The errors you have appear to be two different types; the "short WU" problem from the "bad batch", and _possibly_ the "leave applications in memory when preempted = no" bug. Please check that preference and make sure it's set to "yes"...

Ups! - You are right about the date. It IS 01/19 2006. How could I miss that? Maby becouse the Deadline is extra long for Rosetta? Compared to other BOINC-projects. - (This was a joke). - Since I start to complain about passed Deadlines. I'm SO sorry about making a fuss for no reason.

I have changed the preference for leaving applications in memory when preemted from "no" to "yes". I have used the "no"-preference for the other projects using BOINC, I'm taking part in, without any problems. So I will se what effect this change has.

After this I better stay low for a while?

You raise a valid concern about the WU clock stopping. Sadly, you distract attention away from that concern with the rest of your post.

You are right about the date. It IS 01/19 2006. How could I miss that? Maby becouse the Deadline is extra long for Rosetta?...
After this I better stay low for a while?

Bill, I have one here:

12/22/2005 6:49:54 PM|rosetta@home|Unrecoverable error for result 1ogw__topology_sample_207_12019_6 ( - exit code -1073741819 (0xc0000005))

Fuzzy, you know as much about this stuff as I do... but since that one is erroring off in a few seconds for everyone, I'm sure it's just one of the "bad batch". The deadline on it according to the web page is January - are you saying that you showed it as being December also? If so, maybe something in the "internationalization" of the dates is messed up?

[b]"I'm trying to maintain a shred of dignity in this world." - Me[/b]

Oh, I'm sorry, Bill, I didn't pay much attention, I thought I should report the bad WU's here! My bad! :-(

I don't know what the date said, as I wasn't at home, while it was in my cache.

But what concerns me is, that the WU I linked to, apperently keep on going out to people, and a poor innocent person is having it right now! :-(

I don't think there is anyone physically _at_ Rosetta today that knows how to kill them; I think that probably would require getting info from someone at SETI that has had to do it a few times. If there's anyone _there_... U.S. colleges are all on break.

[b]"I'm trying to maintain a shred of dignity in this world." - Me[/b]

Then we can be happy that they just run for less than a minute, right!? :-)

Then we can be happy that they just run for less than a minute, right!? :-)

And that so far, when staff at THIS project has said they're going to do something, like grant credit for the big monsters you abort or that error out after 11 hours, they've actually done it... which gives a lot of hope that they will follow through this time too.

Unlike a certain two _other_ projects I could name...

[b]"I'm trying to maintain a shred of dignity in this world." - Me[/b]

I seem to be having a problem with work units that have 207, not 205 (plus a few random ones with neither # in them). I haven't received credit since Dec. 18th.

I seem to be having a problem with work units that have 207, not 205 (plus a few random ones with neither # in them). I haven't received credit since Dec. 18th.

You seem to be having all different _kinds_ of errors. You have a bunch of the "short WU" errors yesterday and today, but before that you have a bunch of errors that I would normally attribute to having "leave applications in memory when preempted" set to "no" (that must be "yes" due to a known bug still being chased), AND, you have a couple with "exit code -1", or the "126" error.

The bad part of all this is that some of these, such as this one, ran for several HOURS and got no credit, and not just for you... and this one has a state I've never seen before; instead of "client error - downloading", or "client error - computing", it is "client error - done". The _other_ person to have that WU had the SAME ERROR, but with no "exit code", and GOT CREDIT!

There are a few things that you need to check; the "leave in memory" setting, and I think I would also check the temperature of your CPU, see if you may be overheating, and I'd run a good memory test. But I think some of these problems are going to have to be looked at on the Rosetta side, because they just don't make sense.

EDIT:: None of these _appear_ to be related to WinME...