Bootcamp, bootcamp in parallels, repairs now functions swapped

I had initially has my bootcamp partition available to both a true bootcamp boot as well as the partition available for quick access in parallels. I never setup multiple hardware profiles or anything special. It just worked for quite sometime. After not booting native into bootcamp for quite some time, and quite a few windows updates, I had need for accelerated graphics and true windows native. When I booted the machine, I got the dreaded hal.dll error and the machine refused to boot native. Of course, it would boot as a vm in parallels 3 no problem. I searched out the fix and located it here, read when I needed to use the vm config editor and "clean" out parallels out of the bootcamp. I followed the directions and cleaned the install. I then rebooted with windows natively and used the XP pro's "Repair installation feature from within 1 step shy of a fresh install, right after it searched the disk for previous XP installs". It went fine, I had to re-install my key (nothing new, I use this procedure all the time on 100% windows machines in the office).

First note, on 2nd reboot, I got the windows protection routines where it wants to use the sp2 disk to recover authentic windows files into the install. I re-inserted my sp2 xp install disk and it quickly repaired whatever it was complaining about, it didnt require a reboot.

I continued to follow the instructions from this parallels artice (http://kb.parallels.com/en/4672) and like I said, I got bootcamp booting natively just fine, now I attempted to follow these directions for making it all work in parallels when I need fast access to it.

I created the 2nd hardware profile (mind, you I am in a native bootcamp boot of windows), I copied the existing profile, made sure to configure it as a laptop, docking status unknown).

I then booted into osx, loaded parallels and attempted to boot the partition as a vm. At first boot I got the quick first boot screen with parallels config (or whatever it says), I didnt touch it, overlayed on the entire screen is the Dont touch anything here until parallels tools is installed, blah blah blah. the next screen came up allowing me to choose my 2 hardware profiles, I selected the new one created for parallels up above, and it booted, still with the dont do anything with host or guest until parallels tools loads. The logon screen comes up, tells me to hit ctrl-alt-delete, but I cant get this sent to the host. Clicking on the screen the mouse in the vm is frozen, ctrl-alt-delete does nothing, sending ctrl-alt-delte from the menu does nothing. I see the hard drive icon flashing as the disk in vm is being accessed, the network icon flashes too. I thought it was hung, but left it while I ate and came back to the screen saver active, again clicking on the screen or sending keys does nothing. I have a bluetooth key/mouse and my system is a laptop so I used the parallels control to send the internal (laptop) keyboard to the vm, and lost the kb/mouse until using the bluetooth to turn it back over to osx control.

Anyone have any ideas. I cant just start over (I can, but have months into this bootcamp partition, and would really like to use it as designed).

Thanks, if I am not clear, please ask, and I will try to explain better.

Thanks again...

John

 

As a first step start Parallels Desktop holding Command key and in Configuration Editor -Hard Disk 1- Advanced click Clear
Note: you need to reactivate Windows