1 of 1 people found this helpful
Thanks for reporting the issue. I'm not sure how thoroughly tested this extension is in configurations that include hardware from other vendors. It's quite possible this is a bad interaction with drivers or registry entries left on the system. We'll take a look at it and see if we can reproduce the problem.
Thanks for looking on the issue.
Let me know in the case, you would need any additional info from my side (e.g. registry listings, ....).
Just to confirm the status: The problem was resolved in Catalyst 12.3 . It was completely resolved, not a single issue remained. Thanks for the excellent support. I tested it using various conditions and it works!