Cool! Thanks a lot for this information! It looks like scripting is the simplest and quickest way to automate many repetitive debugging and crash dump analysis operations.

Originally I needed arguments for a script that would save a memory range in a file and then convert it to a .wav by launching Dump2Wave tool

Thanks,
Dmitry

I was browsing debugging blogs and found your blog. I must say, it’s a very cool blog!
A few days ago I learned how to use parameters when running a script and I’m glad to know the documentation for the new Windbg version added it. I wished to know this feature before.
As an example of usage I have a script using it: http://blogs.msdn.com/debuggingtoolbox/archive/2007/05/03/windbg-script-get-portable-executable-headers.aspx

Thanks