Similar results here. Windows 7 RC-1 x64 with XP SP3 32-bit as the guest. When I kick XP into Unity, I can use apps here and there, but after a while I can get an app window to show up, but not respond to any clicks unless I drop out of Unity, then I can use the app. Similarly, I just had an instance where the XP app was minimized, but I couldn't get back to it with Unity engaged.
Not sure if it's a 64-bit thing or not. Mine is on a high-end notebook with an external monitor attached, so I've been chalking it up to the dual displays and changes in the way the Windows 7 taskbar works. About to undock and do a bit more testing to see if I can narrow it down. I'd love to use Windows 7 as my primary notebook OS, as it will really give me a feel for how it works real-world, but I also depend on XP utilities and apps that I have to have available throughout the day.
Beyond these issues, if we could get Unity to engage automatically upon starting a VM (which I have to do from a batch file dropped in the Startup program group), it would be far more seamless. I've tried suspending the VM, then rebooting, but when the VM starts back up, it will not go into Unity mode on its own. Strangely enough, the VMWare Fusion Mac version does work by way of suspending the VM. In fact, if I fire off a Mac OS X restart, it will suspend the VM automatically, restart, then fire it all back up with a big red bow wrapped around it... works great!
Come on, VMWare... love the products, but how about some catch-up now that Win7 is out there in healthy numbers? Get a jump on compatibility before release of 7... sounds like there are other Unity issues beyond just Win7, as well! Microsoft's XP Mode is a very poor effort, so now is your chance to really make Unity shine, making XP Mode irrelevant. In fact, I'd love to see a similar FREE release that slims down some of the full client features. Beat MS at their own game... can't be that hard, really.
