@IKS said:
The "problem" is not the changing of the resolution itself - obviously, you had no problems in storing the desired setting. It is rather recovering from an invalid state with no input what so ever, where the user was warned about possible consequences. I am not aware of a possibility to achieve that.
So in other words, your telling him the same thing apple told people - the antenna in their iphone was fine, but the users fat hand was blocking reception. Give us a break. The problem isn't with my car's suspension, sir, its the gaping pothole in the road.
Maybe instead of some blurb about "Possible Consequences" Industry standard best practice should be applied, and if a user fails to interact with an object oriented confirmation dialog, it reverts/defaults back to its previous resolution. We could maybe spend some money, and implement that common sense measure representative of good practice and common sense, maybe along with working drivers and low level pre boot access, or we can sit here and argue semantics on an internet forum (supposed to be for technical support) about whether or not he can "Change His Resolution" when after he does so it bricks his device, and moreover, his entire install.
Why haven't reasonable measures been taken to implement working drivers, optimizations and such industry standard best practices? The Answer is simple - the critical mass of requisite engineering expertise and technical resources required to do aren't there - and someone either isn't making enough to hire the help they need, or flat out doesn't care - and honestly believes every user who has these problems are fabricating them from the ether.
