Seti@Home optimized science apps and information
		Optimized Seti@Home apps => Discussion Forum => Topic started by: Fredericx51 on 23 Jul 2012, 01:47:45 pm
		
			
			- 
				After upgrading to BOINC 7.0.28,  I noticed the same situation when pauzed/restarted after a 
 change in cmd-line settings,  running High Priority inmediatly after this.  :-\
 
 This also happens when doing a few hundred MW WUs, taking about an hour.
 
 Don't know if anyone noticed this too, but it looks like the very same behavior as BOINC
 7.0.25 !
 Not only on my ATI rig, also on 2 CUDA rigs.
 
 
 
 
 
- 
				What are your cache settings?
 
 Claggy
- 
				After upgrading to BOINC 7.0.28,  I noticed the same situation when pauzed/restarted after a 
 change in cmd-line settings,  running High Priority inmediatly after this.  :-\
 
 This also happens when doing a few hundred MW WUs, taking about an hour.
 
 Don't know if anyone noticed this too, but it looks like the very same behavior as BOINC
 7.0.25 !
 Not only on my ATI rig, also on 2 CUDA rigs.
 
 Whatever your issue may be, it has nothing to do with the subject of this thread.
 
 As of two minutes ago, dont_use_dcf was still not active at SETI main.
- 
				Whatever your issue may be, it has nothing to do with the subject of this thread.
 
 As of two minutes ago, dont_use_dcf was still not active at SETI main.
 
 
 Er - that was when these posts were muddled up in a different thread, with a completely different title.
 
 But to be honest, I don't think it has anything to do with BOINC v7.0.28 either (nor its successor v7.0.31)
 
 There are rumours afoot (see SETI Main message 1263237 (http://setiathome.berkeley.edu/forum_thread.php?id=68694&postid=1263237)) that graphics cards may downclock when they are close to overheating.
 
 And a downclock, not quite severe enough to cause the tasks to fail with EXIT_TIME_LIMIT_EXCEEDED, would still boost DCF to a level where high priority running might be invoked.
 
 Can anyone stand up this rumour with an authoritative source, please?
 
 Oh, and the rumor I heard about the downclock was that it was caused by the 301 driver and related to card temperature. It apparently triggers the downclock at too low a temperature. After a reboot to reset it it runs fine untill the next event. 
- 
				Fred, what is the problem, what are the symptoms, which of your rigs do you mean and why do you think it's a BOINC problem?
			
- 
				How to connect BOINC to it's projects,  as all network traffic appears suspended, but  INET
 works OK?
 
 I've  hundreds of tasks from  6 projects,  waiting to report, but according to BOINC (7.0.28),
 network is suspended?!
 
 I'm about to give up on BOINC, the manager refuses to start unless I start boinc.exe manually.
 Now it refuses to connect, even stating it doesn't need a network connection  :-\
 
 It also appeared that this host was HACKED and C drive was shared with a group
 called Power  Users ?!
 
 I'll do a new BOINC install .  B.t.w.  a Fully Loaded cc_config.xml comes with
 any new install?