Quote: Originally Posted by johngalt
OK, so you cannot manually power off the VPC b/c of some sort of error - what exactly is that error?
Also, when you force the VPC off via the task manager, you're not allowing it to close, among other things, its NAT shared network connections - that will almost always give you a BSOD (as the same thing has happened to me from both VMWare Workstation 6.5 Beta as well as Virtual Box).
So, when you told the Virtual machine to hibernate, it hibernated successfully, or it actually *powered* off instead of hibernating? Or did you tell your *host* machine to hibernate?
Unless I intentionally causing it to blue screen, which I'm not willing to do as it's a works laptop and the hard drive doesn't like that kind of treatment, I shall I have to just refer to my original description of the message which was related to resources being released that did not belong to the application causing the BSOD.
"The error is something along the lines of "An application attempted to release a resource that did not belong to it", that isn't the exact phrase but something very close to it."
I don't use shared NAT I just use the network interface that the laptop is using, typicall WiFi, but occasionally I will use LAN. I have disabled the one I'm not using.
You're saying "force the VPC off via task manager"? Can you please reinterate on this a little, I'm referring to the "Shut Down" options in task manager which correctly log the user off, shuts down services, then windows etc. This is just the same as shutting down from the start menu with the exception that it actually works. At the moment Virtual PC is under the impression that my PC is permanently locked so refuses to shutdown via the "Action" menu.
I'm not entirely certain you should be comparing the app to VMWare and VirtualBox but I understand what you're saying. The previous incarnation of Virtual PC worked fine under these circumstances.
I am about to start rebuilding a VM from scratch using the beta to see if that helps matters.