Folding Forum

Point taken. Still seems a bit disingenuous to add the option, to all appearances fully-functional, when it actually does nothing, but I suppose that's the best choice. I suppose I'm just to used to the modern software lifecycle, where versions releases are frequent and incremental and updating is a...

One, the cause feature is not active yet, so you see even that is not easy to do. (Supported at client level, not yet supported at the server level) Two, core 15 is not v6 only. Core types are not client specific. New features ARE client specific. Support for core 17 was a new feature in V7. If you...

You're not the only one having trouble with the current drivers. They're the responsibility of ATI, not Stanford. Yes, and I'm not suggesting Stanford can or should be the one to fix the underlying problem. However, until the problem is fixed, I have a mostly-idle GPU which I wish to donate but can...

Are there any plans to fix the OpenCL driver from AMD? You would have to ask that on the AMD forum. This is a driver issue, not a fahcore issue. We don't typically recommend beta drivers, but please try the Cat 14 beta drivers. They seem to work better for some people according to initial reports, ...

Is there any plans to change or fix this, then?
Also, if I'm not the only one having problems running Core_17 WUs on this model of GPU, maybe someone should change the master GPUs.txt file.

Still - I was running V7 for months with no failed WU, then suddenly I am failing every WU. What changed?
Also - could I edit GPUs.txt to say it can't do them?

You can guaranty no Core_17 (p8900) by using v6 of the client. Has it been p8900 since V7 came out, though? Because I had been using V7 successfully for months before the errors started. I know its been 8900 every time I've looked since then, but I don't know whether it was 8900 before then. Also, ...

I am having the same problem. I'm using an AMD Radeon HD 5450, no overclocking. I have the latest drivers installed, and I don't think it's a driver issue; everything was working fine up until a couple months ago, then it suddenly started happening, and I did not update my drivers at that time AFAIK...