Posts by nexusis

1) Message boards : Number crunching : Boinc 5.4.11 is now the recommended version (Message 393347) Posted 9 Aug 2006 by nexusis Post: The primary port change took place between 5.3.17 to 5.3.31. If it's really important I might be able to find it. In this post on rosetta Q&A I give some info you might find interesting related to ports, TCP, Firewall permissions, etc. I don't know how to manually change the port. This might also be a good read How to control Boinc on remote computers. This link is to the boinc wiki. Is this helping? tony PS 4.72 used 1043 well, sorta... it gave me an idea at least :) Link on Rosetta wasnt really that relevant - it's not a firewall issue or anything - another 4.45 machine is still able to connect - its got to be the change in port number thats the issue. Based on that, I took a clue from the Wiki and tried to use HOST:1043 as the remote computer name in the "Select Computer" dialogue... but that didnt work either. So, I did some more digging and installed Boincview from this website to see if that got me anything. It sort of 3/4 gets me there. For the most part, it lets me keep my laptop as 4.45, so I wont run into problems connecting to the other machines at work. There's only been a couple of weird things I've noticed so far - worst was that it doesnt completely remove the "snooze" state if manually triggered on a client (had to re-enable the network manually)... but since my network runs 7x24 anyways, its rare to disable any machine unless I'm sitting in front of it so I'm not going to worry about that little gotcha. So I guess I will leave my work machines as 4.45 (or maybe 4.72 - though that was never considered stable, was it?) and keep 5.4.11 running here on my home machines.
2) Message boards : Number crunching : Boinc 5.4.11 is now the recommended version (Message 393261) Posted 9 Aug 2006 by nexusis Post: Release notes indicate to hold off until the NTLM proxy issue is fixed if you need proxy support... does anyone have any idea when issue be fixed in the 5.x series? This functionality was working fine in 4.45... I've got a set of machines that I cant upgrade past 4.45 until this is fixed... and all of them are running McAfee products, so could very well be hit by the issue that caused the 5.4.11 release. Hate to find out that when I get back to work next week that half of my machine base is DOA.... you should be fine, "recommended version" doesn't mean required minimum version. As far as I know they tried extracting curl from 5.5.10, and it caused problems, so they put it back in in 5.5.11. I know they are working on a fix for you. Boinc version 4.72 should also work for you and has the first edition DCF included, which means your estimates to completion should be closer to reality. boinc version 4.72 for windows tony Thanks for the pointer... Question though... when I installed 5.4.11, I noticed that the port for remote access changed (well, I noticed that I couldnt connect to a machine across the room anymore - and a little digging on google confirmed it... the remote access port is now 31416.. heh... math humour.. someone at berkely must be laughing) What I cant seem to find is what version of boinc first introduced the change... Generally, I like to keep all my machines on the same version - easier to maintain them. But this port thingy throws a wrench into things. a 4.45 client cant talk to a 5.4.11 client now. So I'm wondering if there's a way to force the remote control port that the clients use, or (possibly better) wether this 4.72 version was a 31416 port version....
3) Message boards : Number crunching : Boinc 5.4.11 is now the recommended version (Message 393131) Posted 9 Aug 2006 by nexusis Post: Release notes indicate to hold off until the NTLM proxy issue is fixed if you need proxy support... does anyone have any idea when issue be fixed in the 5.x series? This functionality was working fine in 4.45... I've got a set of machines that I cant upgrade past 4.45 until this is fixed... and all of them are running McAfee products, so could very well be hit by the issue that caused the 5.4.11 release. Hate to find out that when I get back to work next week that half of my machine base is DOA....
4) Questions and Answers : Windows : Install on new T2400 based machine stopped processing 5.12 WUs (Message 308094) Posted 17 May 2006 by nexusis Post: I've got a new latop based on the Dual Core Intel T2400 CPU. Boinc 4.45 installed (to match the rest of my machines). This Laptop is not running any optimized versions of code - its running the stuff downloaded from S@H... S@H was running fine for about 2-3 days and then as of monday night, all 5.12 WUs flowing through have resulted in: <core_client_version>4.45</core_client_version> <message> - exit code -1073741515 (0xc0000135) </message> 4.18 WUs are working fine. I can see lots of errors listed on the wiki - but this one I cant find. I've uninstalled and reinstalled a number of times. Boinc is running as a service - I've tried running under my own user account, my machine admin account, and a network raised priveledged account - no luck. Any 5.12 WUs downloaded cycles through with the error... and since there seem to be a lot more 5.12WUs than 4.18s, I reach my quota VERY quickly. Is there a problem with 5.12 supporting the T2400 chip? Do I need to reconfig BOINC to work on this machine? Have I just had an extraordinaryily long streak of bad WUs? All help appreciated...

©2020 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.