I find that sometimes when I think the debugger is unresponsive, its
actually busy doing stuff that only shows up when I enable verbose mode.
Maybe some modules are being loaded, and its simply not done yet? another
thing that happens from time to time is having the baudrate not the same
on both machines. I check this quickly by going to the WinDbg menu and
cycling baudrate. If the baudrates were different, when I hit the baudrate
that is correct for both systems, I then begin seeing output in the
command window.
Good luck;
Tony