Intel disables .scr and .SCR OpenGL hardware acceleration! Is this a push from Intel now to kill OpenGL?
I know M$ has been trying to kill OpenGL for a long time, but Intel?
This has been reported by other people on this site. Apparently some popular screen savers back in the i8xx series crashed their drivers so they did this hack.
I think it is resolved in newer chipsets/drivers, or you can search on this forum for a work-around. (I think it involves having your .scr file start a separate exe process that actually does the rendering)
I just don’t understand why a company would do such a thing.
Allow me to rant (no need to reply):
Why not simply update the drivers with a fix rather than updating the drivers by refusing to render OpenGL screen savers?
It seems to me that M$ has sucessfully bribed Intel.
Why not simply update the drivers with a fix rather than updating the drivers by refusing to render OpenGL screen savers?
That would require spending, ya know, effort. If you don’t care about your GL support (and I’d love to see someone successfully argue that Intel does), it makes sense to do as little as necessary.
This has been a problem for a long, long time.
I have written to Intel about this problem a couple times, but they have never responded.
Here’s what Intel has to say about this issue: http://support.intel.com/support/graphics/sb/CS-004684.htm
Here’s a hack that I have used to work around Intel’s hack: http://www.reallyslick.com/faq.html#6
This topic was automatically closed 183 days after the last reply. New replies are no longer allowed.