ROSETTA FAIL TWICE DURING THE RUN PART OF THE UNIT ABOUT 1 HOUR INTO IT EACH TIME I TRIED TO RUN A FILE FROM THEM. SO I WILL NOT BE GETTING ANYMORE FROM THEM. SORRY GUYS AND GALS.

well, the error rates are much lower than they used to be

did you check the important announcements thread, do you possibly have one of those WUs?

is your computer stable?
no good blaming the project when it's your computer that's at fault

the whole idea of BOINC is that you just let it get on with it, if a WU fails boinc will just download another one, problem solved

unit is stable after running over 2000 wu. no I did not check the list on that but if they wished to have wu fail then it is a waste of computer time , but that is just my oppion

Well, there could also be something going on with his computer (as many people had noticed on climate under some very specific system configs or something). If that's the case, it might actually be doing the project a favor to allow those units to go directly to someone else, who's system can complete them. Not sure what's going on, on his system.

I'm tracking one down myself, though I know it's specific to my computer, or should I say having installed Windows Vista beta 2 onto it. Einstein@home crunched normally, reported back, and got credit (well except for 1 unit, not sure what happened then as I noticed it after the fact). Rosseta hasn't given me a successful crunch under Vista beta yet, and I know that it isn't just Rosseta. Rossetta's developing their app, and Vista is still beta and in development so is being developed from the Microsoft side of the fence...

For now, I decreased the time setting on Rossetta, and then suspended new work fetch on Rossetta, but enabled it on RALPH. RALPH units successfully completed however so increased the time setting, though whatever issue was happening between Rossetta 5.22 and Vista might be resolved in RALPH 5.23. I'll try to get the debugging info back to the project staff so they can make use of it. That said, I know that Vista isn't an immediate term priorty; because even though the beta was made public, it won't retail before next year. Will give a heads up though If I can get it all to play (well from my end), I'll certainly try, as well as provide the necessary bug reports to Microsoft as well as the project people as needed...

That is so true! ;-D


It's not very often a Rosetta WU crash for me anymore, and when I have one, that does, I report it in the thread for that app, and when the devs come to it, I get the credit for it anyway.

But they had some problems with the CASP7_ABRELAX_SAVE_ALL_OUT_BARCODE WU's a little while ago, and it was kind of weird as I had a CASP7 WU from Ralph at the same time, that ran fine, but my Rosetta CASP7 WU crashed...

Holly, something you might know...

i'm curious as to why the rosetta staff have requested that users post app errors/failures in a forum thread, because project admins have access to a set of tools, one of which lists all failed WUs/results in the DB

not everyone posts in the forum, so not all errors are going to be reported in the thread anyway, but all will be shown by the admin/management tool,
so i don't get it

well i think you hit the nail on the head, the fact that MS still has it's latest botch, sorry "Windows Operating System", in beta is the main thing here, and things might still change, so there's no point changing the app for the beta (which by definition isn't a public release yet) if vista is gonna be different for the release version, because you'll just have to change the app again, so i think that rosetta are taking the right approach with vista here

on the other hand, the main rosetta project is now using v5.25, so is there any difference with the current beta version of vista? (ie, does the new 5.25 version run on vista now?)