It is truly unfortunate to have such an event occur to the Rosetta@Home project. I, and the Rosetta@Home global user community are very proud to be a part of this project from the beginning, and we will be here to assist this project for as long as it is running.

We would like to give a piece of our mind to the vendor of the hardware though... but I think David and the Rosetta@Home team will do a good job giving our piece of mind to them anyway.

David, let us know when everything is up and running.
The Rosetta world community is here to back you up 100%.

Regards,

John Koulouris,(Esq.)

Any idea when my hungry crunchers will have some work? :)

You People at the Project have been doing one heck of a GREAT JOB! We will see you when we see you.

Mike F,

Comet Halley

comet - the song

Colonel Bogey March

fore!

golf

Los Angeles Country Club

playboy mansion

Playboy Clubs

Playboy bunny

easter bunny

Easter Eggs

Milka

Nestle

Swiss Miss (Hot Chocolate)

Swiss Chocolate

Swiss birthday (Swiss National Day: 1st August; Switzerland was founded in the Swiss Alpes)

come on guys, keep it in one thread, how else do you "word link" properly?
swiss weather = swiss alps

do you guys get any information from them or send anything to them from what you have learned on any cancer projects to date or in the future?

Had to reboot my router this morning. Seems I'm getting flooded with connection attempts from srv3.bakerlab.org. Here's a short sample from the first five minutes after rebooting the router.

Mon Jul 23 04:33:40 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57281
Mon Jul 23 04:33:40 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57283
Mon Jul 23 04:33:49 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57293
Mon Jul 23 04:33:52 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57293
Mon Jul 23 04:33:58 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57293
Mon Jul 23 04:33:58 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57297
Mon Jul 23 04:34:01 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57297
Mon Jul 23 04:34:07 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57297
Mon Jul 23 04:34:10 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57293
Mon Jul 23 04:34:19 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57297
Mon Jul 23 04:34:28 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57281
Mon Jul 23 04:34:28 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57283
Mon Jul 23 04:34:34 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57293
Mon Jul 23 04:34:43 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57297
Mon Jul 23 04:35:22 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57293
Mon Jul 23 04:35:31 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57297
Mon Jul 23 04:35:52 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57313
Mon Jul 23 04:35:55 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57313
Mon Jul 23 04:36:00 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57317
Mon Jul 23 04:36:01 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57313
Mon Jul 23 04:36:03 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57317
Mon Jul 23 04:36:09 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57317
Mon Jul 23 04:36:13 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57313
Mon Jul 23 04:36:21 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57317
Mon Jul 23 04:36:37 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57313
Mon Jul 23 04:36:45 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57317
Mon Jul 23 04:37:25 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57313
Mon Jul 23 04:37:33 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57317
Mon Jul 23 04:38:21 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57339
Mon Jul 23 04:38:21 2007 Blocked access attempt from 140.142.20.111:80 to TCP port 57341

bumper sticker on profile...............

Once things settle down I'll update the technical details of everything so that those of you who might be interested can see how we do it here in the Baker Lab - for BOINC and more generally at our datacenters in the Seattle area.

Keith,

I understand you are busy. So, please don't over tax yourself to get us this information. However, I must say, it sounds interesting. I sit anxiously waiting for your post. ;-)

Thanks,

Joel

I wasn't disputing what you said in general, but as a veteran of many boards across many subjects, having a Wiki, FAQ, embedded encyclopedia with all the worlds knowledge, etc., will not stop people asking their question on the boards. It is therefore I only quoted that part of the message.

People are lazy, they don't want to look for information, they want the information to come to them.

For newer projects and their more experimental codes we use our local resources. We have invested a significant amount of money over the past five years into the resources here in Seattle.

Hence Keith's RAC of 120k+!

But then the shocker: "projects are not currently running on BOINC because we don't yet have an efficient queuing system"