Hi all,
Unfortunately this issue is caused by the latest AMD drivers released a week or so ago. We are working on resolving this incompatibility ASAP which should form the basis of our next release. Note this is not related to our latest release although it happened at about the same time - the same message would be displayed with older DisplayLink software running on the same system as this AMD driver.
Thanks,
Paul
|