| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: WCG Screen Saver & TeamViewer |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
john@schneider.name
Cruncher USA Joined: Oct 8, 2005 Post Count: 11 Status: Offline Project Badges: 
|
Running a PC with Windows 7 Ultimate 64-bit. I have WCG set as my screensaver, which kicks in after 15 minutes of idle time. Recently started using TeamViewer to remotely access that PC.
I've had a problem accessing that PC remotely and worked with TeamViewer support. They were unable to find the problem. However, today, after looking at the logs from the client PC (which is trying to access that Win 7 host), I found this line: 2015/04/24 11:37:55.544 4188 9116 G1!! DisableScreenSaver: failed with error 1260, Errorcode=1260 I then disabled the screensaver completely and now can remote into it without any problems. Anyone seen this issue before? Any idea what makes the WCG screensaver work differently than the others? Is there a setting I can change? Thanks |
||
|
|
Emilio Lopez
Cruncher Joined: Nov 23, 2005 Post Count: 18 Status: Offline Project Badges: 
|
I have never seen this issue, but my instincts tell me that the GPU is been used by the Boinc program and causing a conflict with TeamViewer.
Try disabling GPU crunching and try to remote in with TeamViewer. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7687 Status: Offline Project Badges: 
|
I would just leave the screensaver disabled. If you have to remote into it, probably no one is watching it anyhow. Besides the screensaver uses a few cpu cycles which could be used by the WU. And if it is in a remote location, why would the monitor be on (or connected) anyway ? Maybe I am missing something.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
john@schneider.name
Cruncher USA Joined: Oct 8, 2005 Post Count: 11 Status: Offline Project Badges:
|
I have never seen this issue, but my instincts tell me that the GPU is been used by the Boinc program and causing a conflict with TeamViewer. Try disabling GPU crunching and try to remote in with TeamViewer. Thanks for the reply, but I can't see how to do that. I'm running BOINC Manager v6.10.58. Where is that setting? |
||
|
|
john@schneider.name
Cruncher USA Joined: Oct 8, 2005 Post Count: 11 Status: Offline Project Badges:
|
I would just leave the screensaver disabled. If you have to remote into it, probably no one is watching it anyhow. Besides the screensaver uses a few cpu cycles which could be used by the WU. And if it is in a remote location, why would the monitor be on (or connected) anyway ? Maybe I am missing something. Cheers This is my home PC and I occasionally remote into it from work. I don't mind BOINC running when I'm not at the machine. BTW, what is "WU"? |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7687 Status: Offline Project Badges:
|
WU = Work Unit
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The BOINC screensaver is different from most other 'standard' in that it connects to the running jobs to fetch the data to plot onto the screen. This is done with RPC over default port 31416. If multiple jobs are running, the screensaver cycles through connection to each of them. Don't know the frequency.
The SS can be set to a number of frames and % of CPU cycles in the device profiles under Custom > Graphics section. Don't know what the default is... 3 or 5% [of one core], but the lower, the more computing cycles for the jobs processed. As to the problem, a question to ask ATT is if BOINC is running as a service or at user level. My experience with Teamviewer is that I have set it to even allow to sign in after a boot. The Esc key usually opens that sign-in screen. Occasionally the screen locks up and a message that displaying cant be refreshed due to too fast switching. Also in Teamviewer you can set the quality of the remote displaying. Suggest to look at the quality custom settings... Animations / Aero... would you need those? And then remoting from work into a home PC. Securities could be interfering. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BTW, though WCG has no GPGPU work, believe to have read that the combination of GPGPU processing with 'active' screensavers is not recommended [some projects have optimized for this, some haven't], but usually they come -without- a screensaver part. Competition for the same resources. See for more reading: http://boinc.berkeley.edu/dev/forum_thread.php?id=8606&postid=50463
----------------------------------------[Edit 1 times, last edit by Former Member at Apr 26, 2015 8:42:58 AM] |
||
|
|
john@schneider.name
Cruncher USA Joined: Oct 8, 2005 Post Count: 11 Status: Offline Project Badges:
|
Thanks for all the great information. I just changed the screensaver to one of the standard Windows ones. Problem solved. After all, if I'm not going to be at the PC, why have one that I can't see anyway?
|
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: 
|
I have never seen this issue, but my instincts tell me that the GPU is been used by the Boinc program and causing a conflict with TeamViewer. Try disabling GPU crunching and try to remote in with TeamViewer. I run Team Viewer while GPU's are in full swing. Never had a conflict there. The screensavers are typically turned off though as it does cause conflicts with some work units. With that said, Team Viewer also has its own video display drivers and shows up as a device under task manager so that it doesn't require your GPU's performance.     |
||
|
|
|