Forum > GPU crunching

Remote Desktop + CUDA

(1/3) > >>

elec999:
I have several seti pcs, I ussualy remote pc into them. Everytime I do so it seems cuda becomes disabled. Is there anyway around this.
Thank you

Geek@Play:
After a lot of investigation I found out that Windows remote desktop loads it's own video drivers overiding any video drivers you are using.  After a lot of messing around I finally disabled Windows remote desktop on my computers.  I then located and purchased VNC viewer and am completely satisfied with it.  Google VNC Viewer, it will show up.

Raistmer:
There is free VNC available too.

And some more hint for using remote desktop while still using CUDA.
BOINC should run under local logged user. Then any other users (and the same one in Win Server systems) can logon via remote desktop - this way it doesn't break CUDA work.
So, all you need is to keep BOINC process running under user account who logged locally.

ThierryH:
The true trouble is logon.scr. With remote desktop, you don't open a "console" desktop. After few minutes, logon.scr is loaded in memory and kill GPU power. I tryed mstsc /console, but it's continuing to not be a true console with GPU control.
So, the easiest way is to open a session with VNC and disable screen saving. After that, you could open a remote desktop on another account and it's running well.

Thierry.

galadriel:
i am using teamviewer and it works well for me. it passes even router/fw and it is free.

rdp is screwing around when you login with it. kick microstift for that

Navigation

[0] Message Index

[#] Next page