Skip to main content
Share Your Experience: Take the 2024 Developer Survey

Diagnosing problems with retro systems not working as designed. See tag wiki for guidance on troubleshooting questions.

A good troubleshooting question should include:

  • The manufacturer, model and version numbers of all relevant hardware and software, including substantial modifications.
  • A list of all steps performed, including those that (apparently) worked until the point where trouble appeared.
  • The specific failure mode: whether an error message, a completely blank screen, whether the system hangs completely, or simply does not perform the requested action. Avoid merely saying ‘it does not work’.
    • If an error message appears, the exact text of the error message. Mention what video mode (whether e.g. text mode or graphical mode) the message appears in, whether it’s a full-screen message (like a BSoD) or just a regular window or command-line output. You can provide a screenshot instead if it’s too long to comfortably transcribe.
  • Whether any alternative approaches were tried, and how those worked.

In general, it is better to provide too much information than too little. You will save people some time asking for clarifications and further details. If a detail turns out irrelevant, it can be edited out of the question later.