1)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 49087)
Posted 12 May 2013 by Dukefrukem Post: I wanted to come back and say I got it working. How or why is really questionable at this point. I didn't do anything after my last post. I gave up. Frustrated. The only reason I really kept BOINC installed was because uninstalling it (or exiting out of it) would cause my fan speed to drop to a RPM that made a weird kind of humming noise. Don't ask. It was just the idle processes of BOINC that kept the fan speed above normal. Anyway, I ran into an additional issue with nvidia PhysX and the game Homefront. I was asking am nvidia rep how to uninstall PhysX safely. He recommended I install DRIVE FUSION to uninstall PhysX. http://treexy.com/thanks?file=http://download.cnet.com/Driver-Fusion/3000-2086_4-75748005.html?part=dl-&subj=dl&tag=button&dlm=0 I followed his directions, restarted my PC and the first thing that pops up was BOINC manager asking me which project I wanted to attach to. So I picked SETI@home and it appears I am up and running. So how bout that? |
2)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48124)
Posted 9 Mar 2013 by Dukefrukem Post: I made the changes to the boincmgr shortcut, and now I get a popup that says: Removing the detach console brings up the Boinc Manager. But again, it's in the same state as it always was: "Connecting to Host" I have no other security software installed, other than Microsoft Security Essentials (built in). BOINC is not listed under the quarantined items. |
3)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48118)
Posted 9 Mar 2013 by Dukefrukem Post: If I don't put quotes around the dir, it says "The name 'C:\Program' specified in the Target box is not valid. Make sure the path and file name are correct. But I verified that double clcking the boinc shortcut I created, does start BOINC.Exe in my task manager. I made the changes to the boincmgr shortcut, and now I get a popup that says: "Unknown long option 'detach_console' |
4)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48115)
Posted 9 Mar 2013 by Dukefrukem Post: OK, at least that shows me that there's nothing on TCP port 31416, the port that BOINC uses to communicate between parts. The only thing I changed was I put quotes around the path in the shortcut: "C:\Program Files\BOINC\boinc.exe" --gui_rpc_port 31416 --detach_console "C:\Program Files\BOINC\boincmgr.exe" --gui_rpc_port 31416 --detach_console Double Cliking on BOINC shortcut did nothing as far as I could see. Double Clicking on BOINC MGR gave me a popup: "Option 'gui_rpc_port' requires a value, '=' expected Then a second popup screenshot below. http://i148.photobucket.com/albums/s36/Dukefrukem/Boinc_zps12d190e8.jpg |
5)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48114)
Posted 9 Mar 2013 by Dukefrukem Post: EDIT: nevermind. one moment. |
6)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48106)
Posted 8 Mar 2013 by Dukefrukem Post: Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:554 0.0.0.0:0 LISTENING TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING TCP 0.0.0.0:10243 0.0.0.0:0 LISTENING TCP 0.0.0.0:17500 0.0.0.0:0 LISTENING TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING TCP 0.0.0.0:49160 0.0.0.0:0 LISTENING TCP 0.0.0.0:49161 0.0.0.0:0 LISTENING TCP 0.0.0.0:61472 0.0.0.0:0 LISTENING TCP 127.0.0.1:19872 127.0.0.1:49180 ESTABLISHED TCP 127.0.0.1:39123 0.0.0.0:0 LISTENING TCP 127.0.0.1:49180 127.0.0.1:19872 ESTABLISHED TCP 127.0.0.1:49816 0.0.0.0:0 LISTENING TCP 127.0.0.1:49816 127.0.0.1:49825 ESTABLISHED TCP 127.0.0.1:49817 0.0.0.0:0 LISTENING TCP 127.0.0.1:49825 127.0.0.1:49816 ESTABLISHED TCP 127.0.0.1:50699 127.0.0.1:31416 SYN_SENT TCP 192.168.1.138:139 0.0.0.0:0 LISTENING TCP 192.168.1.138:2869 192.168.1.108:35841 TIME_WAIT TCP 192.168.1.138:49175 204.236.136.111:443 CLOSE_WAIT TCP 192.168.1.138:49192 204.236.136.111:443 CLOSE_WAIT TCP 192.168.1.138:49219 204.236.140.85:443 CLOSE_WAIT TCP 192.168.1.138:49221 204.236.140.85:443 ESTABLISHED TCP 192.168.1.138:49227 173.194.68.125:5222 ESTABLISHED TCP 192.168.1.138:49262 205.158.153.149:5222 ESTABLISHED TCP 192.168.1.138:49263 199.47.218.150:80 ESTABLISHED TCP 192.168.1.138:49272 208.88.178.49:25999 ESTABLISHED TCP 192.168.1.138:49275 205.158.153.164:5222 ESTABLISHED TCP 192.168.1.138:49284 205.188.8.207:443 ESTABLISHED TCP 192.168.1.138:49289 64.12.104.224:443 ESTABLISHED TCP 192.168.1.138:49290 205.188.13.70:443 ESTABLISHED TCP 192.168.1.138:49554 23.3.106.155:80 TIME_WAIT TCP 192.168.1.138:49573 74.125.226.214:443 ESTABLISHED TCP 192.168.1.138:49574 173.194.75.147:443 ESTABLISHED TCP 192.168.1.138:49578 173.194.68.125:5222 ESTABLISHED TCP 192.168.1.138:49592 173.194.43.5:443 ESTABLISHED TCP 192.168.1.138:49610 173.194.43.38:443 ESTABLISHED TCP 192.168.1.138:49712 74.125.226.199:80 ESTABLISHED TCP 192.168.1.138:49818 67.228.168.216:80 ESTABLISHED TCP 192.168.1.138:49852 173.194.67.120:443 ESTABLISHED TCP 192.168.1.138:50040 216.52.242.80:80 TIME_WAIT TCP 192.168.1.138:50055 23.48.113.244:80 TIME_WAIT TCP 192.168.1.138:50056 23.48.113.244:80 TIME_WAIT TCP 192.168.1.138:50058 23.48.113.244:80 TIME_WAIT TCP 192.168.1.138:50059 23.48.113.244:80 TIME_WAIT TCP 192.168.1.138:50060 23.48.113.244:80 TIME_WAIT TCP 192.168.1.138:50071 23.48.116.163:80 TIME_WAIT TCP 192.168.1.138:50100 216.52.242.80:443 TIME_WAIT TCP 192.168.1.138:50269 217.18.19.155:443 CLOSE_WAIT TCP 192.168.1.138:50318 74.125.226.229:443 ESTABLISHED TCP 192.168.1.138:50352 23.3.106.8:443 ESTABLISHED TCP 192.168.1.138:50376 173.194.43.8:80 ESTABLISHED TCP 192.168.1.138:50381 74.125.226.207:80 ESTABLISHED TCP 192.168.1.138:50415 74.125.226.197:80 ESTABLISHED TCP 192.168.1.138:50430 23.48.222.185:80 ESTABLISHED TCP 192.168.1.138:50431 74.125.226.230:80 TIME_WAIT TCP 192.168.1.138:50432 74.125.226.230:80 TIME_WAIT TCP 192.168.1.138:50436 74.125.226.198:80 ESTABLISHED TCP 192.168.1.138:50437 74.125.226.198:80 ESTABLISHED TCP 192.168.1.138:50438 74.125.226.198:80 ESTABLISHED TCP 192.168.1.138:50447 184.25.109.88:80 ESTABLISHED TCP 192.168.1.138:50449 207.171.163.131:443 ESTABLISHED TCP 192.168.1.138:50450 205.251.251.109:80 CLOSE_WAIT TCP 192.168.1.138:50452 184.25.109.120:80 ESTABLISHED TCP 192.168.1.138:50453 184.25.109.88:80 ESTABLISHED TCP 192.168.1.138:50454 184.25.109.88:80 ESTABLISHED TCP 192.168.1.138:50455 184.25.109.88:80 ESTABLISHED TCP 192.168.1.138:50456 184.25.109.88:80 ESTABLISHED TCP 192.168.1.138:50457 184.25.109.88:80 ESTABLISHED TCP 192.168.1.138:50479 204.93.223.148:80 TIME_WAIT TCP 192.168.1.138:50480 204.93.223.148:80 TIME_WAIT TCP 192.168.1.138:50481 205.251.251.29:80 TIME_WAIT TCP 192.168.1.138:50482 205.251.251.29:80 TIME_WAIT TCP 192.168.1.138:50483 205.251.251.29:80 TIME_WAIT TCP 192.168.1.138:50488 205.188.28.118:80 ESTABLISHED TCP 192.168.1.138:50490 69.194.36.221:80 TIME_WAIT TCP 192.168.1.138:50491 72.21.81.253:80 TIME_WAIT TCP 192.168.1.138:50492 72.21.81.253:80 ESTABLISHED TCP 192.168.1.138:50538 65.55.13.90:80 ESTABLISHED TCP 192.168.1.138:50539 184.25.108.9:80 ESTABLISHED TCP 192.168.1.138:50541 157.56.77.156:443 ESTABLISHED TCP 192.168.1.138:50543 184.25.108.56:80 ESTABLISHED TCP [::]:135 [::]:0 LISTENING TCP [::]:445 [::]:0 LISTENING TCP [::]:554 [::]:0 LISTENING TCP [::]:2869 [::]:0 LISTENING TCP [::]:5357 [::]:0 LISTENING TCP [::]:10243 [::]:0 LISTENING TCP [::]:49152 [::]:0 LISTENING TCP [::]:49153 [::]:0 LISTENING TCP [::]:49154 [::]:0 LISTENING TCP [::]:49157 [::]:0 LISTENING TCP [::]:49160 [::]:0 LISTENING TCP [::]:49161 [::]:0 LISTENING UDP 0.0.0.0:123 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:1900 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5004 *:* UDP 0.0.0.0:5005 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:17500 *:* UDP 0.0.0.0:56390 *:* UDP 0.0.0.0:56391 *:* UDP 0.0.0.0:56392 *:* UDP 0.0.0.0:56393 *:* UDP 0.0.0.0:56394 *:* UDP 0.0.0.0:56395 *:* UDP 0.0.0.0:56396 *:* UDP 0.0.0.0:56397 *:* UDP 0.0.0.0:56398 *:* UDP 0.0.0.0:56399 *:* UDP 0.0.0.0:56400 *:* UDP 0.0.0.0:56401 *:* UDP 0.0.0.0:56402 *:* UDP 0.0.0.0:56403 *:* UDP 0.0.0.0:56404 *:* UDP 0.0.0.0:56405 *:* UDP 0.0.0.0:56406 *:* UDP 0.0.0.0:56407 *:* UDP 0.0.0.0:56408 *:* UDP 0.0.0.0:56409 *:* UDP 0.0.0.0:57674 *:* UDP 0.0.0.0:57675 *:* UDP 0.0.0.0:61451 *:* UDP 0.0.0.0:64078 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:41242 *:* UDP 127.0.0.1:44301 *:* UDP 127.0.0.1:45454 *:* UDP 127.0.0.1:52327 *:* UDP 127.0.0.1:53654 *:* UDP 127.0.0.1:55293 *:* UDP 127.0.0.1:57984 *:* UDP 127.0.0.1:57985 *:* UDP 127.0.0.1:58199 *:* UDP 127.0.0.1:58200 *:* UDP 127.0.0.1:58201 *:* UDP 127.0.0.1:58202 *:* UDP 127.0.0.1:58232 *:* UDP 127.0.0.1:58233 *:* UDP 127.0.0.1:58242 *:* UDP 127.0.0.1:58243 *:* UDP 127.0.0.1:61464 *:* UDP 127.0.0.1:61465 *:* UDP 127.0.0.1:61489 *:* UDP 192.168.1.138:137 *:* UDP 192.168.1.138:138 *:* UDP 192.168.1.138:1900 *:* UDP 192.168.1.138:61463 *:* UDP [::]:123 *:* UDP [::]:500 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:5004 *:* UDP [::]:5005 *:* UDP [::]:5355 *:* UDP [::]:61452 *:* UDP [::1]:1900 *:* UDP [::1]:61461 *:* UDP [fe80::100:7f:fffe%12]:1900 *:* UDP [fe80::100:7f:fffe%12]:61462 *:* UDP [fe80::a2:3c4f:4b6f:9b14%10]:1900 *:* UDP [fe80::a2:3c4f:4b6f:9b14%10]:61460 *:* UDP [fe80::f8ad:4364:3644:ba8b%11]:1900 *:* UDP [fe80::f8ad:4364:3644:ba8b%11]:61459 *:* |
7)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48098)
Posted 8 Mar 2013 by Dukefrukem Post: What kind of firewall program do you use? I don't use any firewall software (windows firewall is turned off). I have a router though. |
8)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48093)
Posted 7 Mar 2013 by Dukefrukem Post: OK I've now tried both iterations (32 bit and 64 bit) of the 7.0.52 and 7.0.28. I currently have the 64 bit version of 7.0.28 installed in C:\Program Files\BOINC. "Connecting to local host" for ∞ |
9)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48089)
Posted 7 Mar 2013 by Dukefrukem Post: The x86 version should be installed to C:\Program Files (x86)\BOINC and not C:\Program Files\BOINC which is for the 64bit version. (on a 64bit OS)bump OK I've now tried both iterations of the 7.0.52 and 7.0.28. |
10)
Message boards :
Questions and problems :
boinc manager 7.0.28 wont connect- Windows 7 64bit
(Message 48087)
Posted 7 Mar 2013 by Dukefrukem Post: Looks like I will just have to dream about using BOINC since I cannot get it to work properly. It's worked fine on my same build for years until recently. So odd. |
11)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 48086)
Posted 7 Mar 2013 by Dukefrukem Post: bump I uninstalled, deleted my data dir, installed 7.0.52 x86, it put BOINC in C:\Program Files\BOINC and my data dir is in C:\ProgramData\BOINC |
12)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 47988)
Posted 1 Mar 2013 by Dukefrukem Post: bump Done. Still did not fix the issue. |
13)
Message boards :
Questions and problems :
boinc manager 7.0.28 wont connect- Windows 7 64bit
(Message 47987)
Posted 1 Mar 2013 by Dukefrukem Post: I tried this and my problem is not resolved. Having the same problem. I've done everything and it still won't connect. |
14)
Message boards :
Questions and problems :
boinc manager 7.0.28 wont connect- Windows 7 64bit
(Message 47986)
Posted 1 Mar 2013 by Dukefrukem Post: edit: whoops dupe. you can delete this |
15)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 47950)
Posted 24 Feb 2013 by Dukefrukem Post: bump |
16)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 47745)
Posted 14 Feb 2013 by Dukefrukem Post: I get "can't connect to local host" (in the command prompt) There are not two data dirs on my system. |
17)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 47736)
Posted 14 Feb 2013 by Dukefrukem Post: bump |
18)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 47726)
Posted 12 Feb 2013 by Dukefrukem Post: yes the manager is what I mean... advanced >> read config file I restart my PC daily. Ever single time it boots, in the system tray, the BOINC manager has a red circle (more like a dot) that says "Connecting to localhost" and it never, ever, ever changes... ever. these three are running in task manager BOINC.exe BOINCMGR.exe BOINCTRAY.exe |
19)
Message boards :
Questions and problems :
boinc manager 7.0.28 wont connect- Windows 7 64bit
(Message 47723)
Posted 11 Feb 2013 by Dukefrukem Post: Nothing yet? |
20)
Message boards :
Questions and problems :
Something wrong with BOINC Manager?
(Message 47722)
Posted 11 Feb 2013 by Dukefrukem Post: I've exited the client, ended the processes in task manager, and started the client. I've also loaded the "read config file" from the client and I still do not have anything in my stdoutdate. My config file is indeed in the data_dir. (located in ProgramData\BOINC.. not program files...) There is no event log view at the start of the client. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.