In my Windows XP virtual machine, I have used keymap.exe from the Windows Server 2003 Resource Kit to remap the command key to "control". This means that I can use "Command" for "Ctrl" in any application, and command key shortcuts in Windows applications generally work the way that I want them to. This worked perfectly in the last version of Fusion (and also when booted from my Boot Camp partition).
In Fusion 2.0, however, something seems to have broken this. I have turned off key mappings in Fusion preferences. Intermittently, however, when I use a command key shortcut (e.g. Command-V meaning Ctrl-V meaning paste), either the command key is ignored (meaning I get "v" inserted in my code instead of paste), or the shortcut works but I also get the key inserted (so I get paste and then "v"). Or, if I use Command-C for Ctrl-C for copy, my selection is freqeuntly replaced by "c" instead of getting "copy".
This is incredibly annoying, and it certainly didn't happen in 1.1.3.
I get the same problem when using Word 2000 and Fusion 2.0.1. Sometimes hitting Command-C copies, sometimes it just inserts the letter 'C'. Same problem with Command-X, Command-V, Command-S. Same problem if use the Control key instead of Command.
Parallels also suffers from the same problem, if that helps! Not sure if it's a problem specific to Word. I'm not using keymap.exe.
Anyone know of a solution/workaround?
More info, after a bit of experimentation:
1. The problem only occurs in Unity mode. In the other two modes, the Command/Control keys are always recognized.
2. The problem occurs immediately after you click in the app window on the guest OS (e.g. to jump to a different paragraph in Word), then press e.g. Command-C. If you use e.g. the arrow keys to navigate around the Word doc, then hit Command-C, then it works OK.
3. If pressing e.g. Command-C produces the letter "C" rather than copying, the problem remains as long as you hold Command down and keep hitting C. Once you release the Command key and do a new Command-C keypress then usually it recognizes the Command key and copies OK.
If anything, the problem is somewhat more frequent than with Parallels.
Yet more info:
I've realised that the problem occurs if you use Command/Control + a shortcut key in Unity mode and you move the mouse at the same time. When you do this, the Command/Control key is ignored, and the alpha key (C, V etc) is entered instead. If you keep the mouse still then the shortcut works as expected.
In fact this issue has been reported by others:
http://communities.vmware.com/thread/160851
I can see that "This bug has been fixed internally." but it's still a problem for me using 2.0.1. Any idea when this fix will be released? It's the only issue I've discovered with this otherwise great product.
Thanks,
Matt