Microsoft switches to a generic, non-CUDA, driver when remote desktop is invoked. The solution is to use another - any other - remote desktop utility instead. People speak highly of VNC - free versions are available.

Microsoft switches to a generic, non-CUDA, driver when remote desktop is invoked. The solution is to use another - any other - remote desktop utility instead. People speak highly of VNC - free versions are available.

In fact, this is what I am using (I have been using all sorts of the VNC family solutions).
I however find that VNC is slower than RD, at least in my network situation.
And, worst of all, FireFox does not work with VNC protocols any more. You end up with a static unresponsive window (for FF only, control of the rest of the remote PC is OK). This is not a problem of VNC, but of FF. Nevertheless, it is a problem.
Therefore, I must use Opera, which is however still not my main browser (problem when you follow links from other programs remotely).

I only very seldom use TeamViewer, which works great, in order not to breach their private use licence.

Quite a complicated issue to tackle for me. Not that I have not find a way, but I feel it is not the best I would like to get.

Microsoft switches to a generic, non-CUDA, driver when remote desktop is invoked. The solution is to use another - any other - remote desktop utility instead. People speak highly of VNC - free versions are available.

In fact, this is what I am using (I have been using all sorts of the VNC family solutions).
I however find that VNC is slower than RD, at least in my network situation.
And, worst of all, FireFox does not work with VNC protocols any more. You end up with a static unresponsive window (for FF only, control of the rest of the remote PC is OK). This is not a problem of VNC, but of FF. Nevertheless, it is a problem.
Therefore, I must use Opera, which is however still not my main browser (problem when you follow links from other programs remotely).

I only very seldom use TeamViewer, which works great, in order not to breach their private use licence.

Quite a complicated issue to tackle for me. Not that I have not find a way, but I feel it is not the best I would like to get.

Sleepy

TightVNC is free for both personal and commercial usage.Those who cannot remember the past are condemned to repeat it.
--- George Santayana

Besides being slow, TightVNC is severely limited (as well as other *VNCs). Doesn't work past login screen in Win 7. Doesn't work with lock screen in Win 7. It all worked in XP.
Being unable to logout or even lock screen is a huge drawback for me and I can't use it to access my computer at work.
But then again I hear CUDA crunching in BOINC has the same awful drawbacks in Win7 so this might not be problematic in your case.

I said that I have used all sorts of VNC engine based software. Of course, TightVNC included.
I am presently using UltraVNC, which allows to lock keyboard and blank screen on the remote system and has a quite effective embedded file transfer module.

Still, Remote Desktop gives me a quicker response and works with Firefox.

I am still using XP64, therefore I do not know about problems with Win7. But try to use Remote Desktop and subsequently use any VNC based software.
I must make a remote reboot, otherwise no go.

If you login via RDP and then launch VNC it will give no solution to no correct driver under RDP issue.
And regarding reboot why not to use shutdown command with appropriate switches from VNC-based remote console ?SETI apps news
We're not gonna fight them. We're gonna transcend them.

If you login via RDP and then launch VNC it will give no solution to no correct driver under RDP issue.
And regarding reboot why not to use shutdown command with appropriate switches from VNC-based remote console ?

I meant: I start an RDP session. Close it. Open a VNC session. Windows login screen appears. Login. Login accepted. Back there to login, square one, no joy.
Other variations can happen (VNC not responding any more. Same cure applies).

Reboot. All good. But remote reboots are always a dangerous thing to do (though this is what we hope Eric or Matt do ASAP whenever something wrong is on at SETI headquarters ;-) ).
I made remote reboots from all corners of the world, though.

You can start the reboot however you like. I usually do it from windows task manager (or from the login screen. Or via RDP, if everything else fails). Seems to me the most reliable thing to do.

The point is that starting with windows Vista the video drivers are not anymore accesible from any app that runs as a service...
Any software doing a remote desktop that is able to run on the computer prior to any user has loged in needs to use a custom display... and while doing this you will lose the GPU crunching abilities...

If the remote desktop uses the hardware drivers then it needs to run as normal app so it need to start after the user has logged in...

I use RealVNC (in my headless crunchers) but Ive set all the remote computers to automatically login at start and to automatically start the VNC server in user mode...
Also I had to disable the secure desktop because when Windows enter in that mode RealVNC gets blocked... Not a very secure way, I know, but this computers are not accesible from outside my local network (neither they have much more than BOINC and some trivial stuff...)

To do a remote reboot I just do through the start menu... I cant do a power cycle, but then I just need to walk a bit and push the power buttons... :b

The point is that starting with windows Vista the video drivers are not anymore accesible from any app that runs as a service...
Any software doing a remote desktop that is able to run on the computer prior to any user has loged in needs to use a custom display... and while doing this you will lose the GPU crunching abilities...

If the remote desktop uses the hardware drivers then it needs to run as normal app so it need to start after the user has logged in...

I use RealVNC (in my headless crunchers) but Ive set all the remote computers to automatically login at start and to automatically start the VNC server in user mode...
Also I had to disable the secure desktop because when Windows enter in that mode RealVNC gets blocked... Not a very secure way, I know, but this computers are not accesible from outside my local network (neither they have much more than BOINC and some trivial stuff...)

To do a remote reboot I just do through the start menu... I cant do a power cycle, but then I just need to walk a bit and push the power buttons... :b

I'm not sure I follow you here, but I will just observe that I use logmein on my Win7 i7 box and it does not stop the GPU crunching.DavidSitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Ive tried with LogMeIn and it needs an app running on the host, and this app starts after the user has logged-in... AFAIK you cant access a host with LogMeIn if a user has not initiated a session... (at least not the last time Ive tried it)

Anyway, LogMeIn is a good option, the only drawback, for me, is that it leads the whole conection through internet which in my case makes everything really, really slow compared to VNC using just the LAN...
Of course if the remote host is in another location then the internet path is unavoidable...

Ive tried with LogMeIn and it needs an app running on the host, and this app starts after the user has logged-in... AFAIK you cant access a host with LogMeIn if a user has not initiated a session... (at least not the last time Ive tried it)

Not any more, at least not for me.
SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Anyway, LogMeIn is a good option, the only drawback, for me, is that it leads the whole conection through internet which in my case makes everything really, really slow compared to VNC using just the LAN...
Of course if the remote host is in another location then the internet path is unavoidable...

Every time I've used it, it uses the internet to start the connection and connect the two computers. Then all traffic is through the LAN, if the PCs are on the same LAN. I can set graphics quality to high with no slowdowns.

It seems that LogMeIn has changed a lot since the last time Ive used it...
Ive retested it and it seems that they use a clever workaround: they use their custom drivers when there is no user logged in and then they switch to a hook on the hardware drivers when they become available after you start the session... (or something like that...)

But It is still really slow compared to VNC even when I do the conection from the local lan... not sure why... as it seems that, as Tazz said, there was not traffic through the router while I was testing it... I guess it is related to the use of the browser as viewer which adds another layer of convertions...

Please evaluate SplashTop 2. It is free, fast and does not interfere with nVidia or AMD video driver detection. SETI works great and all other applications as well, like Photoshop, etc. Moreover, it has mobile apps so I can remote in from my iPad or iPhone - anywhere there is a wireless signal.

Very slick indeed..."History is a pack of lies about events that never happened told by people who weren't there." - Santayana

Please evaluate SplashTop 2. It is free, fast and does not interfere with nVidia or AMD video driver detection. SETI works great and all other applications as well, like Photoshop, etc. Moreover, it has mobile apps so I can remote in from my iPad or iPhone - anywhere there is a wireless signal.

Very slick indeed...

Can you provide a link to where we can get it?DavidSitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.