Quote:
Originally Posted by Insert_Coin
I was reading another thread, one which DisplayLink is paying attention. From what I understand, the problem lies in the generic ktext that DisplayLink uses to create their display driver for OSX. I don't know specifically what the issue is, but apparently the issue belongs to Apple. The issue is supposed to be fixed in the 10.8.3 update, and I can verify this is true because I installed the 10.8.3 beta update, and my DisplayLink adapter works like a champ again! I would hope that Apple would apologize for any negative feedback that affected display manufacturers have received while their OS has had display driver issues.
|
But J5Create has come up with a driver that works with 10.8.2 and lower, so obviously it's possible to work around this bug. As a result, even if the bug was caused by Apple, the fact that it's possible to work around it tells me that Displaylink needs some better customer service.