Click above to get retro games delivered to your door ever month!

  
  You can use the CLD.LIB version of the debugger, which you
  link as described in the section "Compiling and Linking" (you
  can't use CLD.EXE because it's a DOS-only program).  However,
  don't expect too much from CLD.LIB: it has almost no idea that
  it is running in a window under Windows, and does its best to
  operate the way it would under DOS.  Inevitably this leads to
  problems, but the alternative is probably no debugger!
  
  Generally speaking, programs using the Clip-4-Win event
  system, i.e. calling ChkEvent(), are the easiest to debug.
  Window subclassing adds some complications, and using the
  "traditional" Windows programming model, i.e. GetMessage() ...
  DispatchMessage(), adds more complications.
  
  Any time you're having problems it's a good idea to trace the
  messages your program is receiving.  Here are some ways to do
  this:
  
  (a)  have a separate window just for debugging output
  (b)  keep a trace in an array, the way DIALOG.PRG does if
       compiled with SEE_MESSAGES defined (you may want to make a
       particular keystroke or mouse action display the array, so
       that you can examine it whenever you like)
  (c)  write messages out to a file