> Lo and behold!!!
>
> I deleted then non working BOINC and deleted the folder, rebooted and
> downloaded the 4.25 again (this time off the main BOINC site). I shut down my
> firewall and antivir and ran the install after which to my great suprise it
> actually seems to work! wow... It still wont run on my PIII, but atleast the
> Athalon is now doing some good work.

Congratulations and welcome to the Club. Good luck with the P3.

Lo and behold!!!

I deleted then non working BOINC and deleted the folder, rebooted and downloaded the 4.25 again (this time off the main BOINC site). I shut down my firewall and antivir and ran the install after which to my great suprise it actually seems to work! wow... It still wont run on my PIII, but atleast the Athalon is now doing some good work.

---

> Hello Miika Turtiainen,
>
> This is maybe not the ideal moment to try something drastically different due
> to the connectivity problem, but why not. If V4.19 was working, why should it
> not work again?
>
> I suggest following: uninstall Boinc, delete the full Boinc folder, restart
> the PC, install v4.19 again and, why not, attach to <a> href="http://einstein.phys.uwm.edu/">Einstein@Home[/url] as a test.
>
> Good luck.
>
>

Inspired by the persistancy of some people here I'm going to do the whole works again tomorrow. Uninstall, delete, reboot, install and see what happens. and AGAIN... after (I belive) the first 2 or 3 version of v4 (It's been a while, I'm not 100% on which it was) I havent had a workind BOINC on any of my computers (AMD Athalon 2000, PIII 866 as main computers).

---

> Ok, I might (propably was) over reacting when I posted. Sure. I'll admid it: I
> was pissed off. Alot.
>
> But did you even read what I said? I said I had changed to 4.19 and I couldn't
> get that one to run either, because of a different set of problems. I've done
> everything I can think of to make the damn thing work to no avail. I've even
> done complete hard drive sweep/re-install a couple times. It's been like this
> ever since version 4 came out and I'm feeling down because I really loved
> running BOINC and every minute it doesnt work is a waste of time.

Hello Miika Turtiainen,

This is maybe not the ideal moment to try something drastically different due to the connectivity problem, but why not. If V4.19 was working, why should it not work again?

I suggest following: uninstall Boinc, delete the full Boinc folder, restart the PC, install v4.19 again and, why not, attach to Einstein@Home as a test.

Good luck.

---

Read the News at the homepage
Have a look at the Technical News
Look if your question is not answered at the Boinc Wiki

Best greetings, Thierry

> >
> I don't recall anyone forcing the change to 4.25...why not just go back to
> 4.19 and just skip the latest version?
> Here is the link:
> http://boinc.berkeley.edu/dl/boinc_4.19_windows_intelx86.exe
>
>

Ok, I might (propably was) over reacting when I posted. Sure. I'll admid it: I was pissed off. Alot.

But did you even read what I said? I said I had changed to 4.19 and I couldn't get that one to run either, because of a different set of problems. I've done everything I can think of to make the damn thing work to no avail. I've even done complete hard drive sweep/re-install a couple times. It's been like this ever since version 4 came out and I'm feeling down because I really loved running BOINC and every minute it doesnt work is a waste of time.

---

> I don't disagree. My point is, if 4.25 still had some issues then it should
> have been left in the beta state and not put out as a full release.

That's the joy of software- often many of th eissues with it aren't found till it's released, even though a million or os people have tried it without problem you can bet that the next million to try it will come across problems the first group didn't.

---

Grant
Darwin NT

This appears to be a problem with BOINC.exe starting. The root cause has not been figured out yet, but one suspect is that some other program is using port 1043 which IANA granted to BOINC for the control protocol.

---

BOINC WIKI

Maybe I was a little too hasty with my first post, but I was running v4.25 on two machines, one of them 24/7 and had no problems from the time I upgraded from v4.24 to the time I upgraded to v4.26. I have had one instance of what you seem to be describing with v4.26 though. At the time, I posted this and after waiting an hour or so of the computer doing absolutely nothing, I removed it from the queue manually using the "Abort" option from the side panel. At the time, I thought it might be down to a rogue WU, as we have had them in the past. SETI seemed to then behave perfectly normally and has done since. After re-reading this thread today, maybe I briefly stumbled on this bug.

System specs of the box that stopped...
Athlon64 FX53(S939) 2400+
1Gb RAM
200Gb HDD (Mirrored SATA RAID).

SETI ID :- 218386
BOINC :- v4.26
Cruncher :- v4.09

Perfectly capable of punting WUs at the rate of one every two hours or so. As far as the connection status that somebody mentioned here, it was quite happily crunching other work. Just when it got to SETIs runtime the whole thing just stalled. CPU went idle and did nothing. BOINC GUI seemed to think it was connected to something and the CPU time went up (was approx 2hrs by the time I cancelled it), though the %age indicator stayed subbornly at zero. The "View Graphics" option in the side panel was also hidden while this WU was being crunched although I can usually view the GFX without any hitches. Exiting and re-starting the BOINC client software didn't seem to cure the problem, though I must admit, I didn't try the re-boot option here.

BTW DragonStar... Love the sig!

---

> > I'm with Dragonstar on this one. It should have stayed beta. If only one
> or
> > two people put up a post about this then I would say that something is
> wrong
> > with their systems or how they setup the program, but look at all the
> post and
> > reply's of others having the same problem. I myself have six systems
> running
> > BOINC 4.25 and not one of them works anymore with the seti project. If I
> > release software for my company that was this buggy, I'd be out of a job.
> No
> > one should have to work so hard to get a RELEASED version of a software
> > package to work.
> >
> > Sorry guys, but BOINC 4.25 or the servers that supply the seti work units
> need
> > to be tested more throughly with the seti project.
> >
> > So what do we do? If we keeping running BOINC 4.25 then Setiathome looses
> out.
> > If we uninstall it and go back to the classic Seti then other projects
> loose
> > out.
> >
> I don't recall anyone forcing the change to 4.25...why not just go back to
> 4.19 and just skip the latest version?
> Here is the link:
> http://boinc.berkeley.edu/dl/boinc_4.19_windows_intelx86.exe
>
>

I don't disagree. My point is, if 4.25 still had some issues then it should have been left in the beta state and not put out as a full release.

> I'm with Dragonstar on this one. It should have stayed beta. If only one or
> two people put up a post about this then I would say that something is wrong
> with their systems or how they setup the program, but look at all the post and
> reply's of others having the same problem. I myself have six systems running
> BOINC 4.25 and not one of them works anymore with the seti project. If I
> release software for my company that was this buggy, I'd be out of a job. No
> one should have to work so hard to get a RELEASED version of a software
> package to work.
>
> Sorry guys, but BOINC 4.25 or the servers that supply the seti work units need
> to be tested more throughly with the seti project.
>
> So what do we do? If we keeping running BOINC 4.25 then Setiathome looses out.
> If we uninstall it and go back to the classic Seti then other projects loose
> out.
>
I don't recall anyone forcing the change to 4.25...why not just go back to 4.19 and just skip the latest version?
Here is the link:
http://boinc.berkeley.edu/dl/boinc_4.19_windows_intelx86.exe

---

I'm with Dragonstar on this one. It should have stayed beta. If only one or two people put up a post about this then I would say that something is wrong with their systems or how they setup the program, but look at all the post and reply's of others having the same problem. I myself have six systems running BOINC 4.25 and not one of them works anymore with the seti project. If I release software for my company that was this buggy, I'd be out of a job. No one should have to work so hard to get a RELEASED version of a software package to work.

Sorry guys, but BOINC 4.25 or the servers that supply the seti work units need to be tested more throughly with the seti project.

So what do we do? If we keeping running BOINC 4.25 then Setiathome looses out. If we uninstall it and go back to the classic Seti then other projects loose out.

> Yeah... Some people... What I'd say, is that if all these newbies did indeed
> pack it in with their computers then I wouldn't have a job!! ;-)
>
> Well... To start with, you need to attach to a project (In this case SETI). To
> attach to a project, you need to have signed up on the project's web site and
> have recieved an e-mail msg from the project in question ontaining the URL of
> the project and your unique account key.
>
> When you have this information, you need to enter it into the BOINC GUI using
> the "link" provided on client v4.22 or later. For v4.19 and earlier versions,
> select "Attach to Project" from the file menu. (These instructions asume you
> are using the Windows BOINC software. As I've never used these other OSes
> leave alone the BOINC client for them, I can't help.)
>
> Copy the information from the e-mail you recieved from the project into the
> relevant fields of the resulting dialog box, click OK and sit back and relax
> in the knowledge that your PC is helping to find alien life on other worlds.
>
> P.S:- Try in the future not to be quite so quick to judge something you
> obviously don't understand. We are quite happy to help newbies here. All you
> have to do is ask.
>
>
I have the same problem and when he means blank he means blank. Miika is not a new user you can see that he has ran BOINC before, so there is no reason to enter the project number even if he could. When you enter the info in the email BOINC 4.25 just sits there. Same thing happened to me even though I had 3 units still to work on. The only solution was to reboot the computer and low-and-behold BOINC discovered that it had work to do. This is not a good solution because everytime I reboot my computer only 50% of the time will it actually do anything. The one difference I see with the BOINC manager is that when it works it shows in the bottom right hand corner that it is connected to Localhost and if it doesn't work it shows Disconnected. The only solution is a reboot.

But I don't call that a solution either. Look at the majority of posts and you'll see that there is definitely something not right with version 4.25. Maybe Miika over-reacted but I agree with him. I believe 4.25 should have stayed beta.

---

Dragonstar
----------
Vegetarians eat vegetables.
Beware humanitarians.

> Sure a lot of us running this BUGGY code all right, I have 3 puters running
> and not one problem, so may I suggest that you start over, uninstall, PAY
> attention, reinstall, PAY attention.
>
> Make sure you do not have any old BOINC installed
>

I did not have any BOINC software running. I sintalled the version I downloaded and it just sits there, even after giving it all the info.

---

Yeah... Some people... What I'd say, is that if all these newbies did indeed pack it in with their computers then I wouldn't have a job!! ;-)

Well... To start with, you need to attach to a project (In this case SETI). To attach to a project, you need to have signed up on the project's web site and have recieved an e-mail msg from the project in question ontaining the URL of the project and your unique account key.

When you have this information, you need to enter it into the BOINC GUI using the "link" provided on client v4.22 or later. For v4.19 and earlier versions, select "Attach to Project" from the file menu. (These instructions asume you are using the Windows BOINC software. As I've never used these other OSes leave alone the BOINC client for them, I can't help.)

Copy the information from the e-mail you recieved from the project into the relevant fields of the resulting dialog box, click OK and sit back and relax in the knowledge that your PC is helping to find alien life on other worlds.

P.S:- Try in the future not to be quite so quick to judge something you obviously don't understand. We are quite happy to help newbies here. All you have to do is ask.

---

Sure a lot of us running this BUGGY code all right, I have 3 puters running and not one problem, so may I suggest that you start over, uninstall, PAY attention, reinstall, PAY attention.

Make sure you do not have any old BOINC installed

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Ok. I just downloaded the latest BOINC and install it. I gave it full network permissions on my firewall and proceed to get all my project details (I used to run BOINC, but havent for some months). Now I enter the project details and try to attach it, but it just sits there and nothing happens. all the tabs are empty and it shows disconnected. all the proxy and socks options are greyed out so I cant touch them, but none of my programs have needed proxies before anyway. I tried running benchmarks as well and nothing happens. What gives?

EDIT: Wow. Just look at the shear amounth of posts about the lates BOINC. How the hell did they publish something like that? I'm embarassed for the programmers to let something like this out... Anyway. I figured I'm experiencing the same problem as everyone else and uninstalled and the installed 4.19. Fix? Hell no... I get the same issue I had that caused me to stop running BOINC in the first place some 6 months ago. I run BOINC, it goes to sys tray. I move mouse cursor over BOINC and the program shuts down. No matter what I do I cant get it opened so I could attach projects and actually have it run. What a piece of junk this thing is... I'd love to participate as I think BOINC (in theory) does good work, but I just dont feel like fighting the buggy code to get it to do something...

---