Allen Pike posted on the silliness of Yes/No and OK/Cancel a few days ago. Today, I saw the best example ever of poorly-named buttons. This is pretty typical of installers, sadly.
See, the problem here is not so much the buttons as the question. It’s true that people rarely read the question, but this is probably one of the cases where you can make it simple enough that they would.
“Stop installing?”
“Yes” “No”
But wait: Why has the user clicked this button? How likely is it that a user really wants to stop the installer completely, as opposed to being unhappy with a choice they made?
“Stop install without finishing?”
“Quit Installer” “Start Over” “Keep Going”
As an aside, decide on your terminology and stick with it. In the above, we have cancel and abort. Abort’s real world meaning is potentially a painful reminder to users. This never should have entered the software developer’s lexicon as an acceptable user term. Standardize on stop when an action can’t be rolled back and cancel when it can.