Hi, For me, I had to put it into full screen mode (Control-Command- Return), turn off VoiceOver and hit Command-G. On occasion, though, it seems to automatically just grab the keyboard input in my case when I do this. Not having it in full screen doesn't work for me at all. Good luck.
Regards, Nic Skype: Kvalme MSN Messenger: [email protected] AIM: cincinster yahoo Messenger: cin368 Facebook Profile My Twitter On Nov 2, 2009, at 2:54 PM, Thuy wrote: > > Hi John. I tried to follow your instructions for gaining keyboard > control of the virtual machine, but unfortunately, when I tried to > restart VO, The keyboard stopped working and all I got was a bing > noise. I had no control of the Mac at all and no Voiceover, so the > only solution was to do a hard reset. I am using the Bootcamp > partition as my VM and it seems to boot up fine, but as I said before, > I can't get any keyboard control over it. Any advice would be great? > The VM is an old one that was set up with Leopard and Fusion 2, but > the upgrade to Fusion 3 seemed to be fine and the Virtual machine > boots up and automatically installed the latest VMware tools, which > has messed up the JAWS video intercept, but I'm hoping that will be > easy enough to solve if only my keyboard would work? > > Cheers > > Thuy > > > > > On 01/11/2009, John J Herzog <[email protected]> wrote: >> >> Deborah, >> I'm not exactly sure what you are asking here. >> You are correct that the virtual machine window is the one that >> contains all the settings, at least in the default view. >> So, here's what you can do. >> If on the virtual machine window, VO past the tool bar and before all >> the settings. You will hear voiceover say "progress indicator". Next, >> turn voiceover off briefly, and hit command G. Note, sometimes you >> have to do it twice. This will put the keyboard input through to the >> actual virtual machine. Once this has been done, you can turn >> voiceover back on, and all should work as expected. >> Does that answer your question? If not, could you please be more >> specific? >> >> John >> >> On Oct 31, 2009, at 10:56 PM, Debra Turner wrote: >> >>> >>> Hi John and List, >>> >>> I think this is some of my problem. After the Dvd drive became >>> inactive when >>> trying to install Windows 7, "windows running" as well as shutdown >>> and >>> restart was in the virtual machine menu. How do I highlight the >>> virtual >>> machine window? Is that the window where all the settings for >>> sharing the >>> hard disk and other devices are located? >>> >>> Would I have been more successful had I installed Windows 7 under >>> Fusion 2.0 >>> which is what came in the cd version of the software and then >>> upgraded my >>> Fusion to version 3.0? Has anyone installed any windows under 3.0 >>> yet? >>> >>> Debra >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of John J Herzog >>> Sent: Tuesday, October 27, 2009 5:32 PM >>> To: [email protected] >>> Subject: slight accessibility issue with fusion 3 >>> >>> >>> Hi listers, >>> Having just acquired fusion 3, I thought I would pass my experiences >>> along with voiceover. For the most part, everything remains >>> accessible. However, when running and using your virtual machine, >>> there is no longer a scroll area. Thus, you cannot VO to the area >>> and >>> start using the keyboard to control the VM. Instead, it is necessary >>> to highlight the virtual machine window, turn voiceover off, and hit >>> command plus G to direct input to the virtual machine. After this, >>> turn voiceover back on, and everything works as expected. >>> Note: I seem to have a similar problem even when running win XP in >>> full screen mode. Voiceover does not seem to yield keyboard control >>> initially to the virtual machine. To fix this, turn VO off when you >>> highlight your virtual machine window for the first time. Next, turn >>> it on again, and everything works from there on out. Note: You can >>> even command tab to other applications, and when you come back, the >>> keyboard will control your virtual machine as expected. >>> Kind of quirky, but it works just fine and seems to be a bit faster >>> than version 2 as well. >>> >>> Hth >>> >>> John >>> >>> >>> >>> >>>> >> >> >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en -~----------~----~----~----~------~----~------~--~---
