Please post any bugs regarding the new minirosetta application here (version 1.09).

This version now includes graphics, but only for windows machines. A mac version of the graphics also exists but in version 1.09 is unfortunately nonfunctional. The new graphics are still a work in progress, and as such are going to be different from what everyone is used to.

We have two goals for this release. The first is to verify how some of rosetta's key protocols have survived the move into minirosetta, and the second is to test new protocols that our switch to minirosetta has made possible. Both sets of protocols will be tested on targets that we consider to be scientifically useful.

For now there will only be a gradual increase in work units running minirosetta, in case we missed any significant bugs during our tests on ralph.

Eset Smart Security is still blocking the download.
http://srv3.bakerlab.org/rosetta/download/minirosetta_1.09_windows_intelx86.exe probably a variant of Win32/Statik application connection terminated - quarantined

I understand that this release has graphics correct?, well the "show graphics button" is greyed out for me in boinc.
cheers, kp.

Me too, I don't see any graphics button. Am running the newest BOINC Windows client.

I'm having the same problem. The client downloaded the new graphics fine but the "show graphics" button shows gray.

---

Eset Smart Security is still blocking the download.
http://srv3.bakerlab.org/rosetta/download/minirosetta_1.09_windows_intelx86.exe probably a variant of Win32/Statik application connection terminated - quarantined

Same thing happened to me. I have sent a pm to Dekim over @ ralph with my Eset log file re this problem.

I'm having the same problem. The client downloaded the new graphics fine but the "show graphics" button shows gray.

I'm having the same problem

Speedy

---

Have a crunching good day!!

Like others who have recently reported -- Minirosetta looks to be recognized as being a virus -- as I reported a couple of months ago, for me this is with the latest definitions from NOD32. So it looks like the loop wasn't closed (on one side or the other) either with the ESET folks or the coding folks at Rosetta.

Is their any way to configure at our end to specify we don't want the Minirosetta work units? If I am not at a workstation to clear it, it stops BOINC for ALL projects. In that context, rather than loose processing for all projects, I believe the approach would be to put them on hold outbound at the server. Elsewise, I will need to suspend Rosetta on my workstations pending a fix.

Thanks

Barry

---

I can download the app no problem but can't see any graphics. I am using an ATI Radeon X800 graphics card in this machine.

---

Like others who have recently reported -- Minirosetta looks to be recognized as being a virus -- as I reported a couple of months ago, for me this is with the latest definitions from NOD32. So it looks like the loop wasn't closed (on one side or the other) either with the ESET folks or the coding folks at Rosetta.

Is their any way to configure at our end to specify we don't want the Minirosetta work units? If I am not at a workstation to clear it, it stops BOINC for ALL projects. In that context, rather than loose processing for all projects, I believe the approach would be to put them on hold outbound at the server. Elsewise, I will need to suspend Rosetta on my workstations pending a fix.

Thanks

Barry

Since this is false-positive,everybody concered should contact maker of AV.
And I do not think it is possible to opt-out of Minirosseta(it will replace completly old app).
(Bug maker often enough and they will correct this,if not you should just migrate to other AV.Like AVG :-) )

EDIT:Latest AVG 7.5(not 8.0) is saying nothing about Minirosseta...

hi, I run Rosetta on a couple of hosts including a very old win98 pc; although not guaranteed it has been quite happy - if slow - with most applications, 5.82, the recent 5.93 & 5.95 running fine. Minirosetta v.1.07 didn't throw up any problems on the few wus that came my way. Sadly I've had 2/2 "compute error" failures with the new v.1.09 reporting a missing library file:

on resultid=148185328

<core_client_version>5.10.30</core_client_version>
<![CDATA[
<message>
CreateProcess() failed - One of the library files needed to run this application cannot be found. (0x485)
</message>
]]>

the other wu was exactly the same.

I don't expect win98 to be specifically supported so if this doesn't solve itself as minirosetta develops I guess I'll have to retire the machine from this project and find a similar folding application perhaps on WCG etc. I can only sensibly do small work units on it.
as long as there are plenty of 5.95s around I'll be fine but if I start trashing a significant percentage of wus then I'd better suspend things.

meanwhile all looks ok on the main XP pc - graphics button apart of course.

Reporting an compute error with Mini-Rosetta:

Taskid: 148180840
workunit: 135111854
name: score13_hb_multitest62_A_1opd__2983_200_0

I got this error:

<core_client_version>5.10.20</core_client_version>
<![CDATA[
<stderr_txt>
Created semaphore
Created semaphore
Created semaphore
Created semaphore
======================================================
DONE :: 1 starting structures 5656.09 cpu seconds
This process generated 1 decoys from 1 attempts
======================================================

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...
called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>score13_hb_multitest62_A_1opd__2983_200_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>
]]>

Is this something I did or a problem with Mini-Rosetta??

---

--hedera

Never be afraid to try something new. Remember that amateurs built the ark. Professionals built the Titanic.

Actually I've had two very similar errors:

Task ID 148193868
Name score13_hb_envtest62_A_1ubi__2980_771_0
Workunit 135123822
Created 14 Mar 2008 22:37:12 UTC
...

<core_client_version>5.10.20</core_client_version>
<![CDATA[
<stderr_txt>
Created semaphore
Created semaphore
Created semaphore
Created semaphore
Created semaphore
Created semaphore
======================================================
DONE :: 1 starting structures 5614.69 cpu seconds
This process generated 1 decoys from 1 attempts
======================================================

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...
called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>score13_hb_envtest62_A_1ubi__2980_771_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>
]]>

It almost looks as though the workunit succeeded and then the file transfer failed, which is really frustrating if true.

---

--hedera

Never be afraid to try something new. Remember that amateurs built the ark. Professionals built the Titanic.

We all could, but then the sequence would be -- we report to ESET -- they tell us that we should contact the developer so that they (ie Rosetta) could coordinate with ESET to resolve the problem. That is -- that would only lengthen the corrective action. Further, if you'd track back on the Minirosetta reports, the project here had previously queried ESET -- but had (that is the Rosetta folks) suspended sending out additional minirosetta work based on trouble reports (including a number of us reporting the ESET issue here. I'm surprised that the Rosetta folks restarted sending out minirosetta without confirming that they were no longer generating 'false postives' (and not only with ESET).

There seem to be a number of possible approaches here.

1) Rosetta suspend sending out minirosetta until they, in concert with the AV folks resolve and verify the false positive reports.

2) The rosetta folks allow the ability to configure to not receive Minirosetta work.

3) Users individually work personally with the ESET and Rosetta developers to help both sides write code that can be written.

4) Users only install Rosetta on the systems they can frequently observe and terminate the trouble causing download.

5) Users suspend Rosetta on all workstations and await notice from Rosetta that the issue has been resolve.


In my my, solution 1 seems the best choice. Solution 2 is also reasonable. Solution 4 will also work -- but will reduce Rosetta work being done AND increase end user effort to maintain. Solution 5 is quite effective, but will reduce the science performed.

Solution 3 is something close to what you are suggesting, and something I suspect neither Rosetta nor the AV developers are likely to support.

There are of course other solutions, like having Rosetta fund users purchasing other AV software, but that's something I suspect will be something not in the best interests of Rosetta, the users, and the AV folks.

Note, this is the only particular work unit type out there (of any of the BOINC projects I've supported) causing this problem. So to me, the effort to correct the problem is on the Rosetta project, working in coordination with the AV developers directly.

What bothers me most (the inconvenience is a pain as well), is that the Rosetta folks first stopped releasing the client (a good move) after the got feedback of the problem, and then (apparently without confirming that the problem was resolved), started releasing the workunits, EVEN though they were aware of the prior reports. That strikes me as less than responsible behavior, as it adversely affects both the end user/volunteer AND other BOINC projects as well. A prime concept behind the BOINC project to shared computing is NOT to have one projects actions adversely affect all other BOINC projects.

Barry

Since this is false-positive,everybody concered should contact maker of AV.
And I do not think it is possible to opt-out of Minirosseta(it will replace completly old app).
(Bug maker often enough and they will correct this,if not you should just migrate to other AV.Like AVG :-) )

EDIT:Latest AVG 7.5(not 8.0) is saying nothing about Minirosseta...

---

Name 1npsA_BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1npsA-_2984_216_0
Workunit 135171828

<core_client_version>5.10.30</core_client_version>
<![CDATA[
<message>
- exit code -529697949 (0xe06d7363)
</message>
<stderr_txt>
Created semaphore
# cpu_run_time_pref: 28800


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812A5B

Engaging BOINC Windows Runtime Debugger...

---

16/03/2008 03:20:22|rosetta@home|[error] Can't link projects/boinc.bakerlab.org_rosetta/minirosetta_1.09_windows_intelx86.exe to slots/4/minirosetta_1.09_windows_intelx86.exe
Is this my computer or is it Minirosetta
Task ID 147849143
Name score12_hb_envtest62_A_1cg5B_2935_26343_1
Workunit 133041769
Created 13 Mar 2008 15:27:07 UTC
Sent 13 Mar 2008 15:27:23 UTC
Received 16 Mar 2008 10:46:07 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -185 (0xffffff47)
Computer ID 234726
Report deadline 23 Mar 2008 15:27:23 UTC
CPU time 0
stderr out <core_client_version>5.10.30</core_client_version>
<![CDATA[
<message>
Can't link input file
</message>
]]>


Validate state Invalid
Claimed credit 0
Granted credit 0
application version 1.09
this is from task details page

---

If you can't take a joke you should never have joined.

The "Show graphics" button is greyed out for me, too. Boinc Manager version 5.10.45, if it matters.

I'm not sure we have an ENTIRELY AV problem here: of the two problems I reported with mini-Rosetta, one WU was rerun successfully; the other, WU 135123822, says it's still rerunning - which is odd because all the tasks showing in BOINC manager are Rosetta 5.95. Also, I'm not running ESET (whatever that is) - I have ZoneAlarm Internet Security Suite with the Kaspersky anti-virus, and it hasn't reported any problems with any of the Rosetta programs.

---

--hedera

Never be afraid to try something new. Remember that amateurs built the ark. Professionals built the Titanic.

I'm running Linux (32-bit SuSE 10.2, with 32-bit 5.10.42 BOINC).

So far, some 15 Minirosetta version 1.09 workunits have been downloaded to my system.
__EVERY ONE__ of them has failed with a segment violation.
.

I've had this one fail, first one in a while.

wuid=135185075

3/16/2008 9:20:36 PM|rosetta@home|Starting 1r69__BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1r69_-_2984_372_1
3/16/2008 9:20:36 PM|rosetta@home|[error] Process creation failed: One of the library files needed to run this application cannot be found. (0x485)
3/16/2008 9:20:37 PM|rosetta@home|[error] Process creation failed: One of the library files needed to run this application cannot be found. (0x485)
3/16/2008 9:20:37 PM|rosetta@home|[error] Process creation failed: One of the library files needed to run this application cannot be found. (0x485)
3/16/2008 9:20:38 PM|rosetta@home|[error] Process creation failed: One of the library files needed to run this application cannot be found. (0x485)
3/16/2008 9:20:38 PM|rosetta@home|[error] Process creation failed: One of the library files needed to run this application cannot be found. (0x485)
3/16/2008 9:20:39 PM|rosetta@home|Computation for task 1r69__BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1r69_-_2984_372_1 finished
3/16/2008 9:20:39 PM|rosetta@home|Output file 1r69__BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1r69_-_2984_372_1_0 for task 1r69__BOINC_ABINITIO_IGNORE_THE_REST-S25-9-S3-3--1r69_-_2984_372_1 absent

I have added a app info file to rosetta to stop it using 1.09, it's working.

pete.

---

I'm not sure we have an ENTIRELY AV problem here: of the two problems I reported with mini-Rosetta, one WU was rerun successfully; the other, WU 135123822, says it's still rerunning - which is odd because all the tasks showing in BOINC manager are Rosetta 5.95. Also, I'm not running ESET (whatever that is) - I have ZoneAlarm Internet Security Suite with the Kaspersky anti-virus, and it hasn't reported any problems with any of the Rosetta programs.

Small clarification:Eset is maker of NOD32 AV.