Search results

Wow, amazing. For me, it was because I had another nonstandard monitor driver (for a remote desktop app). I have been dealing with this for months now, so this is great to finally fix. Odd that you'd have posted this when you did, given the thread activity and stuff. Maybe earlier in 2015 a...