Everything so far looks like the page really needs signed graphic drivers :/ Unfortunately this means that there isn't an easy workaround, but we will have a look at it, and check if we can fix this somehow. We cannot promise anything, because it isn't possible to create such a certificate ourself, but we would have to find some way to reuse existing certificates or make the pages itself use a lower DRM protection instead - don't know yet if any of these methods would work in practice.
For other readers that stumple upon this bug report: For most other pages downgrading to Silverlight 5.0 solves this problem completely, this bug only affects pages, that completely refuse to work without MS graphic drivers.
Everything so far looks like the page really needs signed graphic drivers :/ Unfortunately this means that there isn't an easy workaround, but we will have a look at it, and check if we can fix this somehow. We cannot promise anything, because it isn't possible to create such a certificate ourself, but we would have to find some way to reuse existing certificates or make the pages itself use a lower DRM protection instead - don't know yet if any of these methods would work in practice.
For other readers that stumple upon this bug report: For most other pages downgrading to Silverlight 5.0 solves this problem completely, this bug only affects pages, that completely refuse to work without MS graphic drivers.
Sebastian