BOINC startup problem
28 Nov 2005 8:58:32 UTC
Topic 190249
(moderation:
Hi,
I am running BOINC on 2 computers. One is a XP-machine (no problems), the other one Win 2000. BOINC-preferences and options are the same on both machines (Run always, Network activity based on preferences, Automatically detect network connection setting, no proxies). BOINC manager is on both machines placed in autostart group.
On my Win 2000 machine BOINC manager says when coming up in autostart "Connecting to localhost" ... Then after a few seconds a messagebox shows with "Connection failed" and in the lower left corner it shows "Disconnected". After I close BOINC manager und restart it everything is working fine. Connection to localhost is made within seconds.
Many thx for help
Frank
Greetings,
Frank
BOINC startup problem
)
Just guessing: Do you use DHCP? It might be, that the box gets its IP-Address after BOINC starts up. But I am not experianced in Windows, so I do not know how to solve that :-(
Hint again: No team?
RE: Just guessing: Do you
)
No, I am not using DHCP on my win2k machine. DHCP is set up by my wlan-box which also gives the IP-Address to my XP-machine. All my network connections (e.g. between my 2 machines) are made long before BOINC is launched. But, hm, considering your post, there might be something that is missing during BOINC startup. But what?
I switched off my firewall but that didn't fix the problem.
Frank
Greetings,
Frank
RE: there might be
)
This is normally seen when BOINC Manager starts "too quickly" during the startup cycle. Delaying it by a few seconds (or, as you've seen, quitting and trying again) solves it. I know there are utilities to control the order things start, delay them, etc., but I'm not familiar with anything to recommend.
RE: RE: there might be
)
Bill,
Sounds like more ammo for my "Default installer options" wish.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: Sounds like more ammo
)
Yes... is ANYONE still writing DECENT installers? It seems like most of the "wizards", Windows _or_ Mac, give you one option per "page". If someone came up with an installer that could intelligently present sets of options (based on earlier choices), and write some kind of config file that the software being installed could read when it's first run, it'd sell like crazy.
Heck, just _anything_ that "looks" different from the ones everyone is used to "clicking next until it quits" through, might actually make them stop and read and think...
Same problem on a win2000
)
Same problem on a win2000 machine. Same fix too, shut down bionic and restart. Connects right away.
RE: This is normally seen
)
Thx for this information. I found something called "EF StartUp Manager" which allows me to install a startdelay for BOINC. On my system 15 seconds are required. Not a very funny solution, but one that works. Hope someone will find another solution which makes it little bit smarter.
Frank
Greetings,
Frank
RE: Thx for this
)
[rant]The easiest solution is for BOINC to reverse the default installer options, so that by default, it does not start on Windows boot. How many other apps (excepting AV, modem/router. internet, or apps for managing peripherals) have default to the startup folder? Sure, people could have carefully read the install options, thought through what they implied, etc, and then made an informed, intelligent decision, but that's not human nature. Human nature is eager to get underway, so Install sequence is Next, Next, Next...Finish.
What is easier to change - human nature? or one value each in two lines of code?[/rant]
(edit) It is BOINC, not Einstein that is responsible for deciding that we are not intelligent enough to manage our own computers, that we require their intervention to begin crunching as soon or as often as they would prefer. If you want to help out a little, please post here, at BOINC Manager - Defaults for installation, on the BOINC messageboard.
Thank you
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Michael, I don't know that
)
Michael,
I don't know that NOT having BOINC Manager in the Startup group would guarantee to solve the problem. Maybe it would - I don't know. I guess there must be so much firing up at startup that the BOINC daemon is delayed just enough to not be ready when BOINC Manager is trying to find it.
But here is what would solve the problem for all those running Win2K/XP. Install the BOINC daemon as a service so that it's always running before the user gets to the login screen. Then BOINC Manager could be started automatically during login and it would always find a running BOINC. End of problem.
I keep promising myself that I'll write a detailed service install "Howto" one of these days in case people are a bit unsure how to do it.
Cheers,
Gary.
RE: But here is what would
)
Please do so :-)
Frank
Greetings,
Frank