![]() ![]() Can folks please reply back with what exact macOS version they're running, from About This Mac > Overview? What exact version of macOS are you hitting this with? I think I saw someone suggest maybe this problem was only happening on macOS High Sierra Beta 2 (10.13.2 Beta (17C67b)). Can I please get some more information from folks who are hitting this? Hey guys, so sorry to hear you're hitting problems with the caps lock between macOS hosts and VMs. If you're wondering, I'm running VMWare Fusion 10.0.1 on OS X 10.13.1. It's not a great workaround, but hopefully this relieves the frustration of not knowing WTF is happening w/ caps lock while you're trying to get some real work done. Go to SYSTEM PREFERENCES > KEYBOARD >, and select 'No action' for the caps lock key.Ĭlick again & re-enable the caps lock key.Īlways turn caps lock off before switching to the VM.Īlways use the 'Virtual Machine' menu to send caps lock to the VM. Turn off caps lock in the host OS by hitting the caps lock key. Make sure Caps lock is off in the VM (send Caps lock from the 'Virtual Machine' menu in VMWare). WORKAROUND (sort of) until VMWare fixes the issue: If you then turn caps lock off in the host OS and switch back to the VM, everything seems OK until you go back to the host OS. If you enable caps lock in the host OS, switch to the VM, and then switch back to the host, caps lock turns off while in the VM and caps lock will come back on when switching to the host OS. ![]() (VMWare reading the same variable it's writing for caps lock functionality?) I also can't get the VM to obey the keyboard caps lock, I have to send it from the menu this may or may not be related. ![]() Please understand that this opinion is not a form of racism or supremacy, it just reflects our society's total lack of education in problem solving and that it's not going to improve anytime soon because complexity and information are growing exponentially.It appears that VMWare is trying to keep track of the caps lock state of the host OS so it can put it back when you switch away from the VM, and it's failing. When they come to a dead end, they flood the support forums with noise, asking vague questions and end up either blaming the product or bitching at the helpful people who struggle to understand their mess. These people can't even understand what a System Restore or a Snapshot is for. I am fully behind software companies' decision to not document every option and every switch, because there is always a class of users who still think that asking questions is a sign of weakness and proceed to experiment with settings, without keeping a proper log of what they're doing, eventually rendering their system non-repairable. The existence of search engines made things much, much worse because by their nature they promote minimal effort solutions. The solutions are just hard to find, because of too much noise, too much overlap and principally because we have not been taught in schools how to search for relevant information in this Information Age. The Communities are a treasure trove of information because all methods of solving a problem that work for more than one person are documented here, and ideally they should be listed separately in the Documents section ( Workstation Pro ). It is impossible to have a complete, exhaustive documentation for every aspect of a program having a history of decades behind its development (applies to OSs too). To add to wila's point of view, my personal view is that a forum (this Community) is a chapter of Documentation, namely its Troubleshooting section, and this is one of the two main reasons it exists - the other being providing peer support.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |