Kept forgetting to use ultra vnc. All it takes is one instant of "remote desktop" connect and CUDA is disabled and within seconds I run the the available CUDA WU's and then run thru my gpugrid quota limit for the day with all WU's reporting computation error.

According to MSDN, Microsoft's RDP grabs a copy of the display for each session. VNC does not gets its own display or uses the same session so that seems why VNC works and RDP does not.

I figured out a way to stop runaway computation errors here but the current WU is still ruined.

Kept forgetting to use ultra vnc. All it takes is one instant of "remote desktop" connect and CUDA is disabled and within seconds I run the the available CUDA WU's and then run thru my gpugrid quota limit for the day with all WU's reporting computation error.

According to MSDN, Microsoft's RDP grabs a copy of the display for each session. VNC does not gets its own display or uses the same session so that seems why VNC works and RDP does not.

I figured out a way to stop runaway computation errors here but the current WU is still ruined.

If all you want to do is monitor BOINC on the remote machines you could use BoincView. I use it to monitor the "farm", which includes BOINC versions 6.5.0, 6.4.5 and 6.2.19. My monitoring machine is a Vista (32bit) laptop and the crunchers are XP (32bit).

Kept forgetting to use ultra vnc. All it takes is one instant of "remote desktop" connect and CUDA is disabled and within seconds I run the the available CUDA WU's and then run thru my gpugrid quota limit for the day with all WU's reporting computation error.

According to MSDN, Microsoft's RDP grabs a copy of the display for each session. VNC does not gets its own display or uses the same session so that seems why VNC works and RDP does not.

I figured out a way to stop runaway computation errors here but the current WU is still ruined.

If all you want to do is monitor BOINC on the remote machines you could use BoincView. I use it to monitor the "farm", which includes BOINC versions 6.5.0, 6.4.5 and 6.2.19. My monitoring machine is a Vista (32bit) laptop and the crunchers are XP (32bit).

The BoincView web site is not available, it says under construction ... but, who knows ... Hmm, now the whole url is unavailable because the server is missing ...

If all you want to do is monitor BOINC on the remote machines you could use BoincView. I use it to monitor the "farm", which includes BOINC versions 6.5.0, 6.4.5 and 6.2.19. My monitoring machine is a Vista (32bit) laptop and the crunchers are XP (32bit).

The BoincView web site is not available, it says under construction ... but, who knows ... Hmm, now the whole url is unavailable because the server is missing ...

Yea, I noticed that last week and asked about it on the BOINC forum. I checked here http://www.denic.de/webwhois/index and it indicated the domain name boincview.amanheis.de is invalid. The last time I looked at their forum, the developer has not posted for a year or more and people were asking where he was.

I do not know if this remote desktop problem is unique to VISTA or not. It clearly shows up on the nvidia cuda forum, but under CUDA for VISTA.

we have been discussing it here in the same forum- RDP and CUDA for the last few days. It is clearly a RDP thing, all flavors of Windows.

---

Team Starfire World BOINC
IRC- irc//irc.teamstarfire.net:6667/team_starfire

Ditto :(
Took me awhile to sort this..not knowing
Please put it in the instructions for new users.

edit to add:
nope, using XP here

---

Kept forgetting to use ultra vnc. All it takes is one instant of "remote desktop" connect and CUDA is disabled and within seconds I run the the available CUDA WU's and then run thru my gpugrid quota limit for the day with all WU's reporting computation error.

According to MSDN, Microsoft's RDP grabs a copy of the display for each session. VNC does not gets its own display or uses the same session so that seems why VNC works and RDP does not.

I figured out a way to stop runaway computation errors here but the current WU is still ruined.

If all you want to do is monitor BOINC on the remote machines you could use BoincView. I use it to monitor the "farm", which includes BOINC versions 6.5.0, 6.4.5 and 6.2.19. My monitoring machine is a Vista (32bit) laptop and the crunchers are XP (32bit).

The BoincView web site is not available, it says under construction ... but, who knows ... Hmm, now the whole url is unavailable because the server is missing ...

One of guys from Seti put up BoincView 1.42 (last release version), and the latest beta version up so that others can download it in the mean time. I'll have a hunt around and see if I can find the link...

Try this link

Keep in mind that this is a stop gap in that even the last versions of BOINC View do not handle all of the later BOINC features well ...

Sadly when the originator went away, stopped, died, what ever happened, because he made the tool closed source this is not something that someone else can pick up and start supporting.

Some times I wish that there were more computer languages available because I have never been able to think in "C" or any of its derivatives ...