the fail is not understanding that such rare "problems" do not justify nerfing your entire desktop usage experience. dropping down to half resolution because you constantly need to id your m/b is nonsense, who are you kidding anyways.
*Facepalm* If he were doing other things, he be encountering
other problems... other problems ALSO caused by the DPI setting. HOW MUCH CLEARER DOES THAT NEED TO BE?! Every users does SOMETHING that the majority of users don't, so every user does something you would dismiss as "rare" but it would cause problems none the less. Something that 90+% of users do, like Facebook, does not mean that 90% of users only do that thing. Like I said, take a statistics class. While you're at it, learn how to do market research, usability testing, and technical writing.
Your confusion is easily seen when you say that he doesn't need to "constantly ID his motherboard." Duh. But he is constantly doing SOMETHING and he is constantly encountering these problems seemingly no matter what he does. Even if you think something uncommon doesn't count, how many millions of people have iPhones, iPods, and thus, iTunes? What was your argument there? They have to be techies to know why they can't read their UDID to the tech support guy or when changing the license on their app to another device. To top it off, fixing it once (still?) required a restart even if they knew what was going on.
This is the very essence of usability testing and it is failing hard. Just accept that. Microsoft is FAIL for not going to a vector-based system that applications are completely unaware of and simply texturing old legacy apps at the default DPI and scaline the entire app (it won't look pretty = more incentive to support objects and libraries using native HW accel vector-based rendering).