http://blogs.msdn.com/b/debuggingtoolbox/archive/2008/06/10/special-command-logging-commands-output-and-commands-history.aspxIf you’ve been following my blog you know I use .logopen and .logclose quite a lot, mainly in PowerDbg . Using these pairs of commands you can save a log file that has all output from the debugger. Usage: .logopen [ Options ] [ FileName ]en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/debuggingtoolbox/archive/2008/06/10/special-command-logging-commands-output-and-commands-history.aspx#8589949Tue, 10 Jun 2008 17:20:26 GMT91d46819-8472-40ad-a661-2c78acb4018c:8589949Jason Haley<img src="http://blogs.msdn.com/aggbug.aspx?PostID=8589949" width="1" height="1">http://blogs.msdn.com/b/debuggingtoolbox/archive/2008/06/10/special-command-logging-commands-output-and-commands-history.aspx#8589508Tue, 10 Jun 2008 12:18:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:8589508a-foton &raquo; Special Command???Logging Commands Output and Commands History<p>PingBack from <a rel="nofollow" target="_new" href="http://blog.a-foton.ru/2008/06/10/special-command%e2%80%94logging-commands-output-and-commands-history/">http://blog.a-foton.ru/2008/06/10/special-command%e2%80%94logging-commands-output-and-commands-history/</a></p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=8589508" width="1" height="1">