One of my fellow knights needs a little help getting 0.19f working on a Windows 7 x64 machine. Below is a post he made on our forum. I've suggested going to 8.12 Catalyst and driver. Does he need to rename and/or move some files? Thanks for any help.

His post below.
Anyone active on MilkyWay willing to play go-between for me? I'm getting an error from their client but can't post on any of their forums because you need a RAC > 0 even in the support forum (which is incredibly stupid).

So here's the initial details, if someone could go make a new thread in the Windows support forum. http://milkyway.cs.rpi.edu/milkyway/forum_forum.php?id=4

OS: Windows 7 x64 RC
BOINC: 6.6.36 x64. Was in protected mode, now reinstalled non-protected, both gave the same message.
GPU: HD4870 w/Catalyst 9.5
The 3 DLLs in System32 have been copied.
App .19f as linked from their forums and zslip. 64 bit version only.

Every unit reports:
6/22/2009 8:46:51 AM Milkyway@home Output file ps_sgr_210F5_3s_hiw_3587556_1245684312_0_0 for task ps_sgr_210F5_3s_hiw_3587556_1245684312_0 absent

http://milkyway.cs.rpi.edu/milkyway/results.php?userid=48206

Looks like it's not finding my GPU as being supported. Need some guidance on what to do about that.
_________________

---

4870 GPU
4870 GPU

OS: Windows 7 x64 RC
BOINC: 6.6.36 x64. Was in protected mode, now reinstalled non-protected, both gave the same message.
GPU: HD4870 w/Catalyst 9.5
The 3 DLLs in System32 have been copied.
App .19f as linked from their forums and zslip. 64 bit version only.

Every unit reports:
6/22/2009 8:46:51 AM Milkyway@home Output file ps_sgr_210F5_3s_hiw_3587556_1245684312_0_0 for task ps_sgr_210F5_3s_hiw_3587556_1245684312_0 absent

http://milkyway.cs.rpi.edu/milkyway/results.php?userid=48206

Looks like it's not finding my GPU as being supported. Need some guidance on what to do about that.
_________________

As you said, according to the task details, no GPU is found.

<stderr_txt>
Running Milkyway@home ATI GPU application version 0.19f by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz (4 cores/threads) 3.26366 GHz (1641ms)

CAL Runtime: 1.4.283
Found 0 CAL device

No supported GPU found!

</stderr_txt>

The CAL interface itself appears to work, it only signals that there is no GPU. There are several reasons for that, one is the protected mode installation. I would recheck that (6.6.2x is better in my opinion than 6.6.3x). Simply disable everything called "protected" or "secure" during the installation (one may have to look at the advanced installation options).

Another possible reason is the access over a remote desktop connection blocking the access to the hardware (Windows loads a virtual display driver for that). It's the same with all other remote access tools, the only difference is that you can disable that "mirror driver" with VNC (but the screen refreshes get slower then), but it is possible to use it that way.

Posted for JerWA


Cluster Physik wrote:
The CAL interface itself appears to work, it only signals that there is no GPU. There are several reasons for that, one is the protected mode installation. I would recheck that (6.6.2x is better in my opinion than 6.6.3x). Simply disable everything called "protected" or "secure" during the installation (one may have to look at the advanced installation options).

I re-installed without the protected option, and there is no BOINC service listed any more. I uninstalled and reinstalled again to verify. There's only one check box for it during install, under advanced options. I don't have a copy of the installer older than 6.6.36, and only this and 6.4.7 are on the Berkley site.

Cluster Physik wrote:
Another possible reason is the access over a remote desktop connection blocking the access to the hardware (Windows loads a virtual display driver for that). It's the same with all other remote access tools, the only difference is that you can disable that "mirror driver" with VNC (but the screen refreshes get slower then), but it is possible to use it that way.

All "Remote" services are Manual start and not running. Remote Desktop is among them. Remote access settings is set to allow none, and allow remote assistance is also off. Not sure what else I should/can do along these lines?
_________________

---

4870 GPU
4870 GPU

I don't have a copy of the installer older than 6.6.36, and only this and 6.4.7 are on the Berkley site.

They are all there at the Berkeley site, one only has to manually change the filename in the links ;)
Try this one for 6.6.21. I'm running that version by myself, albeit on a Win32 host.

Another possible reason is the access over a remote desktop connection blocking the access to the hardware (Windows loads a virtual display driver for that). It's the same with all other remote access tools, the only difference is that you can disable that "mirror driver" with VNC (but the screen refreshes get slower then), but it is possible to use it that way.

All "Remote" services are Manual start and not running. Remote Desktop is among them. Remote access settings is set to allow none, and allow remote assistance is also off. Not sure what else I should/can do along these lines?

The services can run, it's only a problem if there is a remote connection.

But it looks a bit strange it does not see the card. Do you have several cards (or an integrated graphics) in that computer? In such a case one needs to connect a monitor to the card supposed to crunch (or a dummy plug) and activate a display using that card causing Windows to load the driver (it doesn't do it otherwise).

Posted for JerWA

Latest reply (thanks in advance for the data shuffle):

6.6.21 installed, and I let it grab 6 more work units. All 6 died saying they need more permissions, which wasn't happening with .36. And guess what, that was likely the problem the entire time but .36 was suppressing the error? Might be worth forwarding that along so they can try to figure out why .36 is either not generating the correct error or isn't giving the app proper permissions.

Either way, on .21 with BOINC force run as an Administrator I see signs of life! Going to let it churn through the first 8 WUs and see if they validate when I push them back up.

Thanks for the assistance. :-)

---

4870 GPU
4870 GPU

Look I get to reply myself now. Thanks for all the help Cluster. Don't think I would've stumbled onto the permissions problem without it even giving a hint.