If I remote into my computer, it seems to cause massive problems with the graphics driver. This only happens when I am running SETI@Home CUDA.

My CUDA has not ever been stable, but one of the it happens every times is when I Remote into the machine.

That's because Windows Remote Desktop uses its own drivers, which are not compatible with CUDA. You must use something like VNC or another 3rd party remote desktop option that uses the computer's drivers.

---

I must?!?

Beggars can't be choosers. If you want my free processor time you should not dictate the conditions. It should sense the driver switch and shut down. It should never crash the system. I will just turn off CUDA until there is a fix (not a work around).

---

I must?!?

Beggars can't be choosers. If you want my free processor time you should not dictate the conditions.

I think you are taking out of context what was said to you. Stating the limitations of an app isn't dictating conditions. All Ageless did was offer you a solution to use remote desktop while being able to use CUDA. What he gave you wasn't an all or nothing type solution, so obviously if you'd rather not use CUDA that's fine.

The problem goes beyond SETI. It also involves BOINC and Nvidia, so what we and SETI would like from CUDA will take more time.

Edit: spelling

---

I must?!?

Beggars can't be choosers. If you want my free processor time you should not dictate the conditions. It should sense the driver switch and shut down. It should never crash the system. I will just turn off CUDA until there is a fix (not a work around).

Woa... calm down there slugger! When using words you "you", you make it seem like Jord is in charge or something. We're all just volunteers like you are, donating our free resources just as you are. No need to get testy about it.

BOINC is moving as fast as it can to support as many options as it can. There's less than a handful of people on the official BOINC programming team. Between adding new features, fixing bugs, supporting both the BOINC client and the BOINC server-side process, as well as trying to get more support from scientists who need computing power and businesses who can benefit from the platform (if even only on their intranet), its a rather large task to handle.

The guys are doing the best they can with what they have. This is why testy demands are met with a bit of aberration around here, and often the attitude is returned in kind.

---

I must?!?

Beggars can't be choosers. If you want my free processor time you should not dictate the conditions. It should sense the driver switch and shut down. It should never crash the system. I will just turn off CUDA until there is a fix (not a work around).

Wow...........Problem is it is NOT a Boinc problem is it? Problem properly belongs to MS Windows and the MS Remote Desktop software. Remote desktop switching video drivers midstream is not an elegant solution to their problem. And to expect Boinc to cover for a serious MS problem is unreasonable.

The VNC software suggested to you works fine. And you probably owe some people here an apology.

---

Boinc....Boinc....Boinc....Boinc....

you make it seem like Jord is in charge or something.

Me, big boss of BOINC, Seti and all drivers. :-)

All right, substitute "must" for "should". As Geek@Play also explained, it's a Microsoft issue. It has nothing to do with BOINC. Windows remote desktop uses its own videocard driver, which overrides the driver that's on the machine. The only way around it is a 3rd party program that does not use its own videocard driver.

VNC is one, but it's not free. You can try OpenVNC which is a free open source product that does much the same.

---

I use the free version of Real VNC to access my CUDA computer remotely.
http://www.realvnc.com/products/free/4.1/download.html

---

Not only does Seti CUDA fail to work, but also Rivatuner and EVGA Precision utility. It's like they're no longer able to detect the video card. GPU-Z does see the card, but reports the GPU speed as 0 MHZ. Even after disconnecting my Remote Desktop session, things do not return to normal until rebooting the computer at home. Rebootng via Remote Desktop caused BOINC to lose the Seti CUDA application and all its downloaded work units.

I spent over a week trying to figure out why CUDA keeps failing during the day. I normally log in to my home PC from work using Remote Desktop. I initially thought the card was overheating since the windows in the room are closed when I'm not home, creating poor ventilation. Then I finally figured out Remote Desktop was the problem and then searched these forums to find a solution.

I like Remote Desktop since it automatically adjusts the resolution to match the remote client. Based on the description of the problem, I doubt this is something that can be fixed other than using another remote access software. I set up VNC and CUDA is working fine, but now I have to deal with scroll bars to access the whole desktop and I get a sluggish response.

What about TeamViewer ?

http://www.teamviewer.com/

(I never tried any Remote Desktop utils)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

What about TeamViewer ?

http://www.teamviewer.com/

(I never tried any Remote Desktop utils)

I tried it and think TeamViewer is very good.

I connected to my daughter's computer (from Varna to Sofia - Bulgaria, 500 km).

The response is about 0.5 - 1 second delay (between click and the time I see the result of it).

I don't know will it be any difference when the 7 day Trial period is over and the program begin to work in freeware mode.

Connecting is easy (no need for IP address or Windows passwords)
- the program generates ID (9 digits) & session pass
(4 digits to 10 chars - depends on how you set it in options)
which has to be told to the other side (by e.g. phone or Skype)

There is also option for permanent password.

The connection is secure - info from the web site:
http://www.teamviewer.com/products/security.aspx

"
Encryption

TeamViewer includes full encryption, based on RSA private-/public key exchange and AES (256 Bit) session encoding. This technology is based on the same standards as https/SSL and is considered completely safe by today's standards.

The key exchange also guarantees a full client-to-client data protection. This means that even our routing servers will not be able to read the data stream.
"

"free for non-commercial, personal use"

.

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)