It seems to me that there are a lot of problems with BOIC, judging from the many messages out here, and I myself experience scheduler request failures. While the bugs may be in the process of being worked out, the old SETI@Home was much simpler to download and execute adn I RARELY had any communication problems whatsoever.

Just my opinion...

---

It seems to me that there are a lot of problems with BOIC, judging from the many messages out here, and I myself experience scheduler request failures. While the bugs may be in the process of being worked out, the old SETI@Home was much simpler to download and execute adn I RARELY had any communication problems whatsoever.

There is some merit to this. But when there was a problem you had exactly zero information on what it might be.

And yes, SETI@Home Classic was much simpler. But, it was also a one-of-a-kind thing so when projects wanted to be added, or new applications, using the old structure, everything would have to have been hand crafted for that specific project.

BOINC was designed to be modular and supportive of ALL DC projects so that the basic platform could be used by an unlimited number of projects and problems discovered by one project would eventually benefit all.

This lowers costs, makes more projects practical, and has, over time, been improving the quality of the DC project support.

Just my opinion...

Yes. And well put.

---

The one thing that I miss about classic seti is the screen saver. Although I rarely ran the screen saver, i would occassionally pull up the graphics just to watch them run for a few minutes. Kinda like a kalidescope (sp?)

I know the boinc version can approximate the classic graphics, I still thinnk the classic graphics were much "prettier".

ahh... the old days. LOL

Jim

---

I sometimes look at them too. the best thing from my perspective is that now I can have graphics from several projects. CPDN, Einstein@Home, Rosetta@Home, SETI@Home ... more to come?

---

I sometimes look at them too. the best thing from my perspective is that now I can have graphics from several projects. CPDN, Einstein@Home, Rosetta@Home, SETI@Home ... more to come?

I like LHC's screensaver. It has nothing to do with the actual crunched data - but the optics are nice.

---

I miss the old SETI becuase it was simple to use, worked through my firewall without problems and very rarely went wrong.

BOINC is a step backwards IMO.

---

I miss the old SETI becuase it was simple to use, worked through my firewall without problems and very rarely went wrong.

BOINC is a step backwards IMO.

I miss OS/2 and was seriously disappointed when Microsoft shafted their partner IBM to release a less effective windows 3 ...

---

I miss the old SETI becuase it was simple to use, worked through my firewall without problems and very rarely went wrong.

BOINC is a step backwards IMO.

I miss OS/2 and was seriously disappointed when Microsoft shafted their partner IBM to release a less effective windows 3 ...

Do you know how to get BOINC working through a strict firewall in Windows. I cannot open any ports (not up to me), the proxy settings are greyed out.

Therefore as far as I can see BOINC is as much use as a chocolate teapot. Classic SETI worked first time, everytime I set it up on the same system.

I'd be most grateful if there is a simple answer to this. I'd like to continue to participate, but at the moment it doesn't look likely.

Do you know how to get BOINC working through a strict firewall in Windows. I cannot open any ports (not up to me), the proxy settings are greyed out.

If the owner of the PC will not allow you to run BOINC (which means opening ports), you are violating the terms and conditions by running it. So - don't run it on that PC.

---

Do you know how to get BOINC working through a strict firewall in Windows. I cannot open any ports (not up to me), the proxy settings are greyed out.

If the owner of the PC will not allow you to run BOINC (which means opening ports), you are violating the terms and conditions by running it. So - don't run it on that PC.

Which is basically my point. Old SETI worked fine, BOINC doesn't. Therefore BOINC = backwards step IMO.

Do you know how to get BOINC working through a strict firewall in Windows. I cannot open any ports (not up to me), the proxy settings are greyed out.

If the owner of the PC will not allow you to run BOINC (which means opening ports), you are violating the terms and conditions by running it. So - don't run it on that PC.

Which is basically my point. Old SETI worked fine, BOINC doesn't. Therefore BOINC = backwards step IMO.

My Boinc and all 4 projects work fine. Always have. I am very happy with Boinc. Its actually quite progressive I think and has let me learn a lot more about other areas of science. I commend it to all.

---

Do you know how to get BOINC working through a strict firewall in Windows. I cannot open any ports (not up to me), the proxy settings are greyed out.

If the owner of the PC will not allow you to run BOINC (which means opening ports), you are violating the terms and conditions by running it. So - don't run it on that PC.

Which is basically my point. Old SETI worked fine, BOINC doesn't. Therefore BOINC = backwards step IMO.

Hmm,

So SetiClassic was better because...it allowed you to hijack someone else's computer so that you could gain credit at their expense - computer cost+power+maintenance? I don't think that the sort of illegal and unethical parasitic purposes you have in mind will find much sympathy here, we don't really want to become your co-conspirators.

---

"The arc of history is long, but it bends toward Justice"

Do you know how to get BOINC working through a strict firewall in Windows. I cannot open any ports (not up to me), the proxy settings are greyed out.

If the owner of the PC will not allow you to run BOINC (which means opening ports), you are violating the terms and conditions by running it. So - don't run it on that PC.

Which is basically my point. Old SETI worked fine, BOINC doesn't. Therefore BOINC = backwards step IMO.

Hmm,

So SetiClassic was better because...it allowed you to hijack someone else's computer so that you could gain credit at their expense - computer cost+power+maintenance? I don't think that the sort of illegal and unethical parasitic purposes you have in mind will find much sympathy here, we don't really want to become your co-conspirators.

No you misunderstand. Several colleagues and myself ran classic SETI on PCs at work. Using the time when the PCs were in screensaver to do something useful rather than sit there doing nothing except burn electricity. There were no issues with this with my employer. However, they will not (understandably for security reasons) open ports for BOINC despite me working for a scientific research establishment.

Therefore by moving to BOINC we will no longer be able to contribute. I'm sure BOINC is wonderful (I run it at home, but seems a bit flaky to me) and has vast improvements over classic SETI. But for the basic function of actually working then it fails for us at work over classic SETI.

---

Which is basically my point. Old SETI worked fine, BOINC doesn't. Therefore BOINC = backwards step IMO.

Neither project wants participants to run the system on computers not owned by the participants. As others have said, use of BOINC or SETI@Home classic on a computer for which you do not have permission to run these programs is out of the bounds of intended use.

---

Which is basically my point. Old SETI worked fine, BOINC doesn't. Therefore BOINC = backwards step IMO.

Neither project wants participants to run the system on computers not owned by the participants. As others have said, use of BOINC or SETI@Home classic on a computer for which you do not have permission to run these programs is out of the bounds of intended use.

Sigh.

"You may use this software on a computer system only if you own the system or have the permission of the owner."

I did have permission of the owner to run SETI classic, I do not have permission to run BOINC (because it requires opening of ports violating our security policies). Therefore SETI classic worked, BOINC doesn't. Ergo in my opinion and for me personally BOINC = backwards step because I and colleagues can no longer participate. Therefore (original post subject) I miss SETI classic.

"I don't think that the sort of illegal and unethical parasitic purposes..."

I'm sure that SETI is grateful for all the worktime donated to it by organisations allowing their computers to be used for their work.

---

I don't understand how SETI Classic could work without open ports. It had to "call home" to get work and to upload finished results, the same as BOINC does... BOINC may require _more_ particular ports be open, ie; 1043 for internal communication _IF_ you want to run BOINC Manager, instead of just port 80.

---

Sigh.

"You may use this software on a computer system only if you own the system or have the permission of the owner."

I did have permission of the owner to run SETI classic, I do not have permission to run BOINC (because it requires opening of ports violating our security policies). Therefore SETI classic worked, BOINC doesn't. Ergo in my opinion and for me personally BOINC = backwards step because I and colleagues can no longer participate. Therefore (original post subject) I miss SETI classic.

"I don't think that the sort of illegal and unethical parasitic purposes..."

I'm sure that SETI is grateful for all the worktime donated to it by organisations allowing their computers to be used for their work.

iochta,

Thank you for the explanation of permissions, and I withdraw my "scold", in your case.
I suppose it is likely that the old Seti used ports that were commonly on the "approved" map, though I never looked into that during the time I did SetiClassic. I t is understandable that your employer has tight restrictions on port use, and unfortunate that policy doesn't allow for them to make exceptions for BOINCing. Perhaps your IT Manager could be persuaded by a well-organized proposal, including a look at some of the larger "farms" that run BOINC-based projects? To the best of my knowledge (limited to the BOINC and Einstein boards), there has never been a situation where these ports have been exploited for a security compromise.

Regards,

Michael

---

"The arc of history is long, but it bends toward Justice"

Perhaps your IT Manager could be persuaded by a well-organized proposal, including a look at some of the larger "farms" that run BOINC-based projects? To the best of my knowledge (limited to the BOINC and Einstein boards), there has never been a situation where these ports have been exploited for a security compromise.

Best make him use TCP port 31416 then, as 1043 is dropped in the latest alpha versions. The port doesn't need to be open, just open when needed (stealthed).

---

All

Sorry to hijack this thread, but as a BOINC "virgin", I'm still struggling to get the SETI@home project up and running on my home PC, and I was hoping that one of you could help me out.

I've downloaded the BOINC manager s/ware, and every time I run it, I get as far as the Project URL pane, where I'm asked to insert the URL of the project I want to connect to.

Thing is, everytime I insert http://setiathome.berkeley.edu (with or without a terminating slash at the end of the URL) the system comes back and tells me that this is not the URL of a BOINC-based project, despite the fact that that's the URL quoted on the SETI@home pages - and in all the Emails I've received from SETI@home advising me that I need to move from Classic to BOINC.

Is this a known problem - or am I just unlucky?

Can any of you suggest a fix / point me in the right direction to get this problem sorted?

Thanks in anticipation!

---

- If you want to connect to the Seti project, go to Your Account.
- Change your password, type it in twice and hit the Change Password button.
Start Boinc Manager if it isn't open yet.
At the top menu bar, you see Projects (not the tab, but the menu bar), press it.
Select Attach to project.
- Type in, or copy & paste: http://setiathome.berkeley.edu
- Press Next.
- Press the radio button before "Use existing account"
- Fill in your email address (top of the page) and the password you just set at the Seti page.
- Press Next.

That should attach you to Seti.

---