Install latest build, VM screwed, 0x0000007E = angry and confused

Yesterday, parallels was running fine. Then I installed the latest build. Then I tried to restart my computer, booting into Bootcamp. Got the "can't find hal.dll" error. That's funny I said to myself, I thought I shut down Parallels correctly.

So I reboot into OSX, try to start my Bootcamp VM and I get the Blue Screen telling me that my machine can't be started. STOP error number 0x0000007E.

So to summarize: I can't start Window in Bootcamp because parallels didn't clean up correctly, and I can't start the VM in parallels so it can clean up correctly to allow me to boot in bootcamp.

Parallels has been like a high maintanance girlfriend. I love it at times, but other times I'm damned one way or the other, and it's starting to get old.

Anyone have any idea how I can get out of this mess. I've already tried downgrading to 5160 with no luck.

 

Forgot to mention that my VM is Windows XP.

 

Uninstall and reinstall of 5582 fixed the problem

Frustration subsiding....maybe this will work out. We've had some great times....

 

Yea, doing a un-install, restart, install cleans out the gremlins frequently.