My Windows 7 64b VM running under Parallels 7.0.15054 was working fine with proper keyboard mapping WITHOUT the BootCamp drivers installed - which I thought a bit odd. But I also have an XP VM which did have BootCamp 3.0 installed. So I installed BootCamp 3.0 off my OS X disk into the W7 VM, then upgraded to 3.1, then 3.2, heading toward 3.3 which is a Windows 7 specific version of BootCamp. After the 3.2 reboot all my keyboards were ignored - both the MBP built in and my Apple USB tethered keyboard. This meant I could not log in as I couldn't type my Windows password. When I tried to use the onscreen keyboard from the accessibility menu it said that it wasn't available. I'm pretty sure that I tried Ctl+Alt at this point but nothing happened. Carramba! Stuffed! The trackpad and a mouse were both fully operational. I couldn't enter Windows so I couldn't add/remove the drivers, nor do a system restore. I tried restarting Windows. I tried restarting OS X. I couldn't do a repair install from the Windows CD because OS X swallowed the CD on insert - it never made it to the VM because Windows wasn't logged in. The BootCamp stuff I could start under OS X couldn't touch the drivers on the VM. I could find noone with a similar problem on the web. Once Windows had started, the keyboard was always nearly dead. I say nearly because shift-lock still worked and so did Esc. But that was all (that I could see) oh, yes, the Fn keys still did their usual Mac functions. In the end I hit the Del key while restarting the VM and got the Windows boot menu. From here I pressed Ctl+Alt to release the keyboard, then F8 to enter the diagnostic menu and was then able to run System Restore to just before I installed BootCamp. It worked. I got my keyboard back. There is a small but. On my UK system the " and the @ are reversed compared to a US keyboard. They work perfectly everywhere in Windows EXCEPT IN THIS EDIT BOX ON THE PARALLELS SITE where they are swapped!!! Just thought this might: a/ Help someone in the same situation b/ Alert Parallels to a potential problem Hope it helps.
BootCamp 3.3 is no better... Just for the record, after regressing back out of trouble (though only the penultimate restore point would work, the latest one simply generated a "Catastrophic" error) I cloned the VM so I could mess around some more. I removed my password so I could log in using only the mouse, then upgraded all the way up to BootCamp 3.3 - the keyboards were ignored as before, so no improvement, and didn't come back with 3.3. What was problematic was all this activity confused System Restore so I couldn't regress back to a working system, ALL restore points now resulted in a "Catastrophic" error. I deleted the VM and am now using the clone (phew!) with no BootCamp, but it has been regressed and the later restore points may or may not work. Hope this is of some use to somebody someday.
