1. Something (possibly Parallels Compressor) deleted the image files from c:\windows\system32\oobe. In the event that you have to reactivate Windows, there are red X's where the images should be, making reading the code to the guy on the phone impossible. 2. As reported in another thread, I've had an immediate and random shutdown. 3. I was running two VMs. This was thrashy and slow, but worked. I minimized one of them and the system kernel paniced. 4. I get a lot of "beach ball" pauses when switching tasks in Windows that I didn't get on previous builds. I've been able to work around it to some degree by adding a second virtual hard disk of fixed size, using it exclusively for paging, and disabling the Parallels Coherence service. 5. Related to Coherence...I'm a developer and when building applications my target exe sometimes can't be written to in VS.NET 2005. Disabling the Parallels Coherence service fixes this. (Is coherence constantly "touching" the exes in order to make them work with the new OSX taskbar integration?) 6. This is the most frustrating one - Unable to Allocate Virtual Memory. I get this very frequently and it requires a reboot to fix. I have tons of disk space available so I don't know why this happens. My machine is a Mac Pro 4x2.66 with 3G of ram. Despite the hiccups in this release, I am a happy user and I am continually impressed with the features that are cranked out so rapidly! Please contact me if you need additional information.
