I've been a Windows technician for several years, and I'm quite familiar with the Windows Debugging Tools' ability to analyze a minidump after a system has BSODed. It's quite useful. I'm taking on some of the administrative roles for my company's 20-25 Apple computers. All but one are integrated in AD and running Tiger. The machine that I just set up as the first 10.5 box in our environment is currently being used for some of our Creative department employees who need to run a script to convert images created/edited in various applications to JPG. I'm not extremely clear on the utility of the script, but as I'm 50% of the support for these users, I'm taking a crash course in AppleScript. (I was curious to learn it anyway, but now I'm being paid to do so! Victoly!) Anyway, the Mac Pro with Leopard has been deployed and has been crunching images for a few days with no issues. However, I just received an e-mail from one of the Mac users informing me that the machine experienced a kernel panic while running our Make JPG script. I'm in an interesting position, as I'm not yet well-versed enough in AppleScript to run through the script and determine if there's some difference between Tiger's AppleScript and Leopard's that's causing the problem (though that seems quite unlikely to me). I will likely pursue hardware diagnostics to be on the safe side, but does anyone know 1) if the OS X kernel dumps any useful information upon panicking and 2) of a tool or method for parsing that dump file and determining what may've caused the crash? Thanks!