OpenGL and D3D support and Matrox

[Jon P. Inghram]

I don't get it... if the different graphics interfaces require the drivers to do x when program y calls for x, why can't Matrox get the drivers to do x? Is the problem that program y and z don't use the same process to call for x? Is it a basic flaw in DirectX and/or OpenGL? Is Matrox too lazy to start over from scratch and write correct OpenGL drivers instead of the never ending patched ICD's? Are the game programmers cutting corners and not following the rules?

[Rags]

Errmmm...Fixing up/optimizing an ICD is an ongoing process for ALL mfrs....what are you thinking?