Actually surprisingly, Win XP had been working solidly on my mac pro since installing it some months ago. Today I booted into it, thinking maybe I'l play me some Total Annihilation, which had previously been running flawlessly. Oops, what's this? It suddenly doesn't work? I'm presented with a black screen with some strange white blocks scattered across it. Pressing Return exits back to Windows. Huh. I then tried to run the Photoshop CS3 beta, and I know it's a /beta/ but, it also didn't work (launched momentarily, and then exited without any errors). Then I discovered there was some problem with the audio drivers, because iTunes was polite enough to tell me as much (the only error I ever got during this whole ordeal and it was actually useful). I tried to play some music and yeah, there was just silence. No sound in anything else either. In retrospect the Total Annihilation error could have been related to the audio driver problem too, but I really can't tell. Anyway, not knowing where to start (feeling that it was more than just a driver issue) I just wanted to go back to OS X. Only Windows froze while shutting down, so I had to force the power off. Then I powered on and before even the Apple logo appeared, it kernel panicked. The first time I've seen a KP on my Mac Pro aside from the issues with earlier builds of Parallels Desktop. Well... after another power off/on... OS X appears to be working. Disk Utility told me the Volume Header needed minor repair, which I went ahead and repaired successfully (I don't know if that damage was already there or not). No other problems, but, I don't trust my install of Windows anymore, even if it's still fixable. Since I don't need it ATM, I might just wait until Vista is out (and maybe Apple updates Boot Camp to accommodate it) and go with that, or reinstall XP and make as few modifications and software installs as possible. Maybe then it would work with Parallels finally too! So the point of this post... er... rant, is that I hate Windows because it randomly breaks. I'm a competent Windows user and I definitely didn't do anything to cause tonight's behavior (other than install the dang thing in the first place ).