I just noticed that when I remote access my home computer from my laptop that GPU WU's list as GPU missing. It seems to have something to do with my laptop display overriding the home box's drivers or something, from what I can tell (though I'm certainly out of my depth around here when it comes to computer knowledge).

Is there any way to override this switch when I remote to my home box, or am I stuck with BOINC holding up all my GPU WU's when I have to access that computer from elsewhere?

---

If you are using Remote Desktop then yes it will through your GPU out.

Logmein was good, but apparently that has gone commercial, but this thread should give you some other alternatives to use.

http://setiathome.berkeley.edu/forum_thread.php?id=73874

Cheers.

Thanks!

---

I'm pretty happy with Teamviewer. I've been using it all day to manage multiple (too many to count) restarts for Windows updates that kept failing.

You may also find that Boinc can't find your GPU if it starts automatically when the computer starts up. If that happens, in Boinc Manager go to File > Exit, wait a bit (10-15 seconds) and start Boinc again. I put a shortcut on my desktop to make this easier to do.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Remote Desktop will stop GPU processing. MS Remote Desktop video drivers are not compatible. You do have to go to a 3rd party remote access. (I have switched to TeamViewer as well and it does all, and then some, that I need)

The computer will work fine, doing CPU and GPU processing as long as you do not access it using Remote Desktop (personal experience).

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Has anyone checked out the new version of Remote Desktop MS is pushing as a Windows Update (to make Vista and 7 compatible with 8)? Does it still kill the GPU?

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Another way to avoid the RDP problem is by use of a VNC, there are several.

I use TightVNC who is very light and free for non comercial users. It don´t use a central server to autenticate as Teamviewer. Remember the Logmein example they could simply drop the free service when they want without any warning.

But be aware VNC is not easy to use as Teamviewer and requires you reconfigurate your routers to allow the right port access go to the right host.

On other hand, you could configurate the VNC in a way that the user never even knows you remotely access his hosts, (something not possible with teamviewer) that could be good or bad depends on how you use it, allways remember you need to respect the other users privacity, and you could do that only if you have the autorization, or you could end in troubles.

Not sure about this, IIRC the problem is in the Nvidia driver we use on the gforces, not the windows itself, since other NV GPUs like Tesla who use a diferent type of driver does not have the problem so you could use RDP with them. Maybe someone could explain that better to us.

---

(...) Not sure about that, IIRC the problem is in the Nvidia driver we use on the gforces, not the windows itself, since other NV GPUs like Tesla who use a diferent type of driver does not have the problem so you could use RDP with them. Maybe someone could explain that better to us.

This is, because the Tesla devices can be configured to run in non-display-mode (TCC-mode), so not conflicting with the ms-driver for remote desktop. See here:
http://docs.nvidia.com/cuda/cuda-getting-started-guide-for-microsoft-windows/index.html#driver-model

---

Aloha, Uli

Thanks for the info Uli, i allways try to find why, now i know.

Note: NVIDIA GeForce GPUs do not support TCC mode.

---

Thanks for the info Uli, i allways try to find why, now i know.

Note: NVIDIA GeForce GPUs do not support TCC mode.

Which might cross over to the "Headless Ubuntu Linux Rig" thread. I wonder if anyone has hacked that yet, for either platform?

You may also find that Boinc can't find your GPU if it starts automatically when the computer starts up.

David - that is NOT true (for me, at least). On one of my machines, I have a slightly flaky 680 that seems to cause a crash every few days or so, and everything (including GPU processing) starts up when the machine reboots itself. In fact, I haven't bothered to do anything about it since it doesn't affect my overall processing hardly at all.

---

You may also find that Boinc can't find your GPU if it starts automatically when the computer starts up.

David - that is NOT true (for me, at least). On one of my machines, I have a slightly flaky 680 that seems to cause a crash every few days or so, and everything (including GPU processing) starts up when the machine reboots itself. In fact, I haven't bothered to do anything about it since it doesn't affect my overall processing hardly at all.

I've never known it be a problem in Windows - even on those XP machines where I can run GPUs "as a service", so they start up even before the desktop is ready.

But it's regularly reported as a problem in Linux.

Has anyone checked out the new version of Remote Desktop MS is pushing as a Windows Update (to make Vista and 7 compatible with 8)? Does it still kill the GPU?

It will always kill the GPU, as the driver used in WRD just does not contain silly things such as OpenCL, OpenGL, CUDA or whatever else support. Only a rather basic DirectX, mostly geared towards 2D and a little 3D for desktops. This to make it compatible with all of the computer systems out there, without requiring the user to install a special WRD compatible video driver for his videocard.

So any fixes in WRD are fixes in WRD, not in the driver used.

---

You may also find that Boinc can't find your GPU if it starts automatically when the computer starts up.

David - that is NOT true (for me, at least). On one of my machines, I have a slightly flaky 680 that seems to cause a crash every few days or so, and everything (including GPU processing) starts up when the machine reboots itself. In fact, I haven't bothered to do anything about it since it doesn't affect my overall processing hardly at all.

I've never known it be a problem in Windows - even on those XP machines where I can run GPUs "as a service", so they start up even before the desktop is ready.

But it's regularly reported as a problem in Linux.

It happens to me every time in 7, but come to think of it I'm not sure it does in XP.

Anyway, I did say he *may* find...

If it's an issue that was fixed in a newer version of Boinc, that may be enough reason for me to update it finally.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

For the startup issue:

How about using

 <start_delay>nseconds</start_delay>
    Specify a number of seconds to delay running applications after client startup.

in cc_config.xml or passing

--start_delay N
    Specify a number of seconds to delay running apps after client startup.

as command line parameter?

---

Aloha, Uli

For the startup issue:

How about using

 <start_delay>nseconds</start_delay>
    Specify a number of seconds to delay running applications after client startup.

in cc_config.xml or passing

--start_delay N
    Specify a number of seconds to delay running apps after client startup.

as command line parameter?

start_delay won't help, because BOINC itself has to be running to delay-start the applications.

And it's BOINC which has to detect the GPU when *it* starts.