Developing User Interfaces for Microsoft Windows

Since many setup problems result from asking unnecessary or confusing questions, it's useful to summarize the guidelines for asking setup questions. When asking a question in a setup program, consider the following:

• Don't ask a question if you already know the answer.
• Don't ask a question if you can determine the answer. The setup program shouldn't have to ask any questions about the user's system, for example.
• Don't ask a question if the user isn't likely to know the answer. Don't assume the user has read anything before running the setup program. Don't assume the user knows anything about his system configuration.
• Don't present responses or options that are invalid or that will lead to an invalid installation. In such cases, the setup program should automatically make the selections that result in a valid installation. With the exception of invalid serial numbers, registration numbers, and folders, all user input should lead to a valid installation.
• Carefully explain the significance of any responses or options. Make sure the user has enough information to make an informed decision.
• Clearly indicate the recommended response or option and make it the default selection.
• Provide acceptable default values whenever possible. The user should be able to perform all steps that do not require text input by pressing the Enter key or clicking the Next button.
• Verify all input when it is entered. Don't wait until it is used to discover that it is invalid.
• All input folders and file paths should have a browse button.
• If necessary, provide online help to further explain what the user needs to do. But don't assume that the user is going to read it.