Since I've upgraded to build 5160, Parallels seems to have a lower success rate of properly restoring my Windows XP virtual machine after having suspended it. Reading many of the posts in this forum, I know many people have suggested to properly shut down Windows to avoid these problems, but for me that makes using Windows that much more inconvenient. After all, if you only use Windows for a few applications, you don't want to have to go through Window's long startup just for brief access to one app. Anyway, I just though I would mention it. Previous builds on Parallels would sometimes fail to bring back up a suspended VM, but it seems to happen more often now. It seems like a proper APM driver is needed so that Parallels and Windows can better coordinate a proper standby.
Well, I also have minimalist installations that I use for testing/development. These are usually just Windows, Windows updates and a few other applications such as WLM and Wireshark, no anti-virus - really, barebones. These VMs sometimes hang as well when restoring a suspended session. When this does happen, I can still usually switch from coherence mode back to single window and I then notice that I have a desktop but no sign of the taskbar (even though it's set to be visible in single window mode) and sending ctrl-alt-del doesn't do anything either.
Hmm... What happens if you close all the applications prior to suspending? Or do you do that already?
Oh, and just noticed in your post history that you posted in something discussing a Leopard build's compatibility with Parallels, are you running the troublesome VMs on Leopard or X.4?
