We're not really sure this is our issue since we can't directly modify the behaviour of the internal screens, but it may be a side effect of something we can avoid doing.
Our impression is that it's DisplayLink's issue since the problem does not occur when the DisplayLink drivers are not installed. Can you confirm that the driver team has at least been able to reproduce this problem?
04-02-2012, 06:53 PM
Threaded Mode