This morning I remote desktopped to my home PC from work and I think it caused the milkyway ATI app to light itself on fire. Between then and now when I logged back in on the console, it chewed through a couple thousand work units, all giving the error "No supported GPU found!"

I suspect that when you remote desktop, certain hardware (sound and video in particular) is virtualized by windows so that the output can be captured to the remote client. I know that directX games do not work in a remote desktop connection (they complain about lack of hardware support as well) so I suspect something similar is happening to the BOINC app that is running under my user.

I maxed out my daily quota for today already so I won't be able to see if logging in on the console fixes it until late tomorrow. I'm also wondering if installing BOINC as a service would help this problem or not. Is there a way for milkyway to detect this situation and suspend computation so as not to burn through work?

This morning I remote desktopped to my home PC from work and I think it caused the milkyway ATI app to light itself on fire. Between then and now when I logged back in on the console, it chewed through a couple thousand work units, all giving the error "No supported GPU found!"

I suspect that when you remote desktop, certain hardware (sound and video in particular) is virtualized by windows so that the output can be captured to the remote client. I know that directX games do not work in a remote desktop connection (they complain about lack of hardware support as well) so I suspect something similar is happening to the BOINC app that is running under my user.

I maxed out my daily quota for today already so I won't be able to see if logging in on the console fixes it until late tomorrow. I'm also wondering if installing BOINC as a service would help this problem or not. Is there a way for milkyway to detect this situation and suspend computation so as not to burn through work?

You are right if you use RD or several other tools the video driver is virtualized and is gone until a reboot. So, you will burn through tons of tasks. You can use most versions of VNC to remotely log onto the system if you need to do this in the future.

I run 8 of my PCs via Tightvnc, 4 running MW on ati cards, without problem.

---

Cheers,

PeterV

.

Installing as a service is not an option for gpu-crunching on all windows past XP and W2k3. Read about the "Session 0 isolation" in the middle of the Nvidia CUDA & ATI Stream (CAL) FAQ.

---

I use "Real VNC". There are probably others that are better, but it works without killing things so I just keep using it.

Yo-

Looks like a reboot is not required, just logging in on the console again, at least for Windows 7. I got some more work units just now and it is destroying them! (in a good way this time) It looks like this box got some GPU units a few days ago and completed them but I didn't notice until they were erroring out yesterday. I hadn't really been paying much attention to this computer or this project however this being my first GPU app on BOINC, it has kind of captured my attention.

I might look at installing VNC on here although I really just use windows for gaming most of the time. All my serious work is done in linux so I usually get access to my home network remotely through ssh and use of remote desktop is pretty rare.