My completely unsubstantiated sheer guess is that Quicktime is mucking about at a low level to implement some underhanded shenanigans. In other words, one way to cause this sort of train-wreck would be attempting to write some kind of magic cookie (maybe to document the presence or absence of Quicktime Pro) to some "unused" area of the first hard drive, invisible to the filesystem, and doing so in such a low-level way (BIOS calls?) that it escapes the notice of the RAID drivers, which then come along and see unmirrored data and panic.
I thought that type of low level access wasn't allowed under NT based systems unless you have a kernel level driver installed to allow such access. Every low level mucking SAN product I worked with on Windows had to do this, and the code in that area had to be bullet proof to avoid blue screens.
As for Quicktime Pro licensing, it's just stored in one of the settings files it creates. I used to just back that file up and dump it back when I installed a new machine, instead of having to key in the code.
Previous Topic
Index
