I have run Classic 3.08 with Seti Monitor for many years. Last year I installed BOINC when it came out, but I stopped using it since it's not very friendly for us modem people.

Anyway, I have tried to upgrade to 5.2.8 now, and I can't get it working. I appear to have all the account stuff figured out, but when I try to attach to the project, it asks for my proxy server (I don't use one). No matter what I put in here, it's never happy.

I have the proxy server boxes unchecked in the Options menu. The Wiki guide says you need to paste in the project http: and your code, but 5.2.8 only asks for the http:. I use the Windows firewall, and I have added both BOINC programs to my exception list. Even turning off the firewall does not help. I have also tried rebooting, to no avail. Any other suggestions for me?

I wondered if I'm supposed to have something in the Select Computer part, but I haven't found any instructions for that in the Wiki guide. I also tried running benchmarks (the Wiki implies that this is necessary, but doesn't say to do it), but they won't run. I get no messages to help in troubleshooting.

---

Hi, please go to the seti website, log in, click on "your account", then create a password, stay logged in.

then in the boinc manager select "projects", "Attach to projects", then enter the url

http://setiathome.berkeley.edu

then enter the email addy and password you just created.

let me know if this works. I keep giving out this advise and either people are getting attached and not leaving feedback or they're mad and leave.

thanks

tony

The proxy prompt is sort of an issue. Might be that 'modem people', as you call yourself, feel more of this issue than others. But in these days it's one of the most asked questions.
To make it short: If you have no proxy, this prompt should not appear.

I have no 100% answer.

But there are reports which say that it will work when you log on to Seti with your webbrowser, THEN start BOINC and do the attachment procedure.
Others claimed that it worked after a reboot of the machine.
And a third said that he had to modify the registry.

In your place I'd try the first.

:-)= Greybeard

---

All about BOINC: BOINC-Wiki (by Paul D. Buck)

BOINC Manager is designed to control server farms, and you need to tell it that you want to control the computer on which it is actually running. This essential undocumented step goes as follows...

Start BOINC manager and (menu) File..Select Computer, then enter "localhost" without the quotes (the password is automatic - dont alter it). Press OK.
When I did it it dumped me straight into the attach project wizard which then worked perfectly.

HTH, Duncan

---

BOINC Manager is designed to control server farms, and you need to tell it that you want to control the computer on which it is actually running. This essential undocumented step goes as follows...

Start BOINC manager and (menu) File..Select Computer, then enter "localhost" without the quotes (the password is automatic - dont alter it). Press OK.
When I did it it dumped me straight into the attach project wizard which then worked perfectly.

HTH, Duncan

Success!!! When I entered localhost, the password input itself automatically as you said. It just immediately tryng to download work. I had already been through the attach project wizard, apparently. However, the downloads would not continue. I was the message that said "missing account key", but I couldn't find anywhere to put an account key in. So I tried attaching to Rosetta instead, which seemed to work, but it wouldn't download anything either. Then I remembered to run the benchmarks, and once they completed, the downloads actually started.

Thank you very much for the help! This really needs to go into the Wiki guide!

Here's my message list, if anyone is interested...
11/25/2005 2:24:19 PM||Starting BOINC client version 5.2.8 for windows_intelx86
11/25/2005 2:24:19 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
11/25/2005 2:24:19 PM||Data directory: C:\\Seti@home\\BOINC
11/25/2005 2:24:19 PM||Processor: 2 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.60GHz
11/25/2005 2:24:19 PM||Memory: 510.98 MB physical, 1.22 GB virtual
11/25/2005 2:24:19 PM||Disk: 38.28 GB total, 22.83 GB free
11/25/2005 2:24:19 PM|SETI@home|Computer ID: 1759566; location: home; project prefs: default
11/25/2005 2:24:19 PM||General prefs: from unknown project http://climateprediction.net/ (last modified 2005-03-20 21:51:04)
11/25/2005 2:24:19 PM||General prefs: using your defaults
11/25/2005 2:24:19 PM||Remote control not allowed; using loopback address
11/26/2005 8:54:28 AM||request_reschedule_cpus: project op
11/26/2005 8:56:04 AM||Fetching config info from http://boinc.bakerlab.org/rosetta/get_project_config.php
11/26/2005 8:56:07 AM||Missing account key
11/26/2005 8:59:50 AM||Running CPU benchmarks
11/26/2005 9:00:48 AM||Benchmark results:
11/26/2005 9:00:48 AM|| Number of CPUs: 2
11/26/2005 9:00:48 AM|| 1099 double precision MIPS (Whetstone) per CPU
11/26/2005 9:00:48 AM|| 1016 integer MIPS (Dhrystone) per CPU
11/26/2005 9:00:48 AM||Finished CPU benchmarks
11/26/2005 9:00:49 AM||Resuming computation and network activity
11/26/2005 9:00:49 AM||request_reschedule_cpus: Resuming activities
11/26/2005 9:00:49 AM||Using earliest-deadline-first scheduling because computer is overcommitted.
11/26/2005 9:00:50 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11/26/2005 9:00:50 AM|SETI@home|Reason: Requested by user
11/26/2005 9:00:50 AM|SETI@home|Note: not requesting new work or reporting results
11/26/2005 9:00:51 AM|SETI@home|Started download of setiathome_4.18_windows_intelx86.exe
11/26/2005 9:00:51 AM|SETI@home|Started download of better_banner.jpg
11/26/2005 9:00:54 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
11/26/2005 9:00:54 AM|SETI@home|General preferences have been updated
11/26/2005 9:00:54 AM||General prefs: from SETI@home (last modified 2005-11-25 14:11:12)
11/26/2005 9:00:54 AM||General prefs: using your defaults
11/26/2005 9:00:59 AM|SETI@home|Finished download of better_banner.jpg
11/26/2005 9:00:59 AM|SETI@home|Throughput 1001 bytes/sec
11/26/2005 9:00:59 AM|SETI@home|Started download of setiathome_4.18_windows_intelx86.pdb

---

My last message count on the word proxy yielded over a hundred requests to solve the proxy socks problem. The other project boards are probably getting hit hard too as this is a common problem. This one is written for SETI. Insert any other project name and the directions are the same.

Solution is quite simple. Do not open up the Boinc manager. If the manager was open at any time during this session, close it. Log onto your SETI account on the internet. After and only after you have logged in open Boinc. Now you can connect to the project and the proxy and socs request window will not show up.

The reason the proxy request shows up is because the user is not logged into the work URL beforehand. This has nothing to do with the speed of the servers. It has to do with authentication.

Once the user logs onto the web, they can open Boinc and the proxy request will not come up. They will be able to get in instantly!

Galeon 7

PS: When logging on the web check the box to stay on line otherwise repeat these steps. Stayin logged on will get you in automatically every time Boinc and/or your computer is restarted.

---

I am a Geek. We surf in the dark web pages no others will enter.
We stand on the router and no one may pass.
We live for the Web. We die for the Web.

My last message count on the word proxy yielded over a hundred requests to solve the proxy socks problem. The other project boards are probably getting hit hard too as this is a common problem. This one is written for SETI. Insert any other project name and the directions are the same.

It seems like more.. lol...
Actually, the other projects wouldn't be seeing this. They don't have the thousands of new users all at once trying to connect. SETI@Home has nearly four times the users of the next largest project, and in the last day has had 90% of the new user accounts set up of the public BOINC projects. (Numbers from BOINCStats)
There is a new version again, 5.2.12, which should be addressing some of the communications issues we've been seeing.

MJ

---

what is the instructions for connecting by proxy server

---