SLinCA@Home

[STE\/E]

I think we need a sub-forum for this project.


1) The app names say "blah blah checkpoint 2hrs blah" To me, that means it checkpoints every 2 hours, but I guess it could mean it check points once, 2 hours in. But according to BT, the task has run for 10 hours, and it check-pointed last 9 hours ago. So "2hr" means neither once at 2 hours, or every two hours. Has anyone tested it? Does it restart from scratch? Or from 1 or 2 hours? from the start? Or no more than 2 hours from the cumulative run time?

2) Just FYI, a few windows machines can run it, but not all. It looks like a problem with the zip file. In any case, if you want to run it, it must be linux for now.

I found running under Windows all pretty much in Error on the zip file but running under Linux they seem to finish & report okay. Any shut down of the BOINC Client will reset the the Wu's back to 0:00 no matter how much time has past. I've lost more Hr's between the SLinCA & RNA Project than any Projects before, probably in the Thousands because I keep forgetting about the Wu's going back to 0:00 Time when you Exit BOINC ...

[Duke of Buckingham]

More than 115,000 seconds of crunching to trash, I have just remembered why I did canceled the first tasks, now I just did the same.

[Fire$torm]

I think we need a sub-forum for this project.


1) The app names say "blah blah checkpoint 2hrs blah" To me, that means it checkpoints every 2 hours, but I guess it could mean it check points once, 2 hours in. But according to BT, the task has run for 10 hours, and it check-pointed last 9 hours ago. So "2hr" means neither once at 2 hours, or every two hours. Has anyone tested it? Does it restart from scratch? Or from 1 or 2 hours? from the start? Or no more than 2 hours from the cumulative run time?

2) Just FYI, a few windows machines can run it, but not all. It looks like a problem with the zip file. In any case, if you want to run it, it must be linux for now.

Your request has been granted....

[zombie67]

It turns out that the developer of the app had his zip app in a non-standard folder, and wrote the apps to look for it in the wrong place. So we users saw the error, yet he could not reproduce it. D'oh!

The solution:

Thanks to the work of fellow volunteer Ananas, we now have a work around solution for the people who can't get Windows work units to complete successfully with the "Can't open Zip Local File" error.

Using any compiled zip.exe from the http://www.willus.com/archive/zip64/ into a folder and extract it (the Win binaries package).
Copy the extracted zip.exe file to the WINDOWS folder/directory. This adds the zip fuction to the computers PATH statement, as Windows already is in the PATH you don't have to do anything else. No reboot required.
That is all there is to it.

Ananas has had heaps of successful work units and now I have my first successful works unit credited with points since May 2011.

(You could probably use any zip executable but this one we know works.)

(Still no word on the recalculated points for past Windows work units)

Conan