<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - keyboard stops working... system beeps</title>
    <link>http://communities.vmware.com/community/vmtn/desktop/fusion?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 20 May 2008 16:20:29 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-05-20T16:20:29Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/949296?tstart=0#949296</link>
      <description>&lt;br /&gt;
FYI - Firefox 3.0RC was the culprit for me - thanks for letting us know!&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Trevor</description>
      <pubDate>Tue, 20 May 2008 16:20:29 GMT</pubDate>
      <author>TrevorHart1</author>
      <guid>http://communities.vmware.com/message/949296?tstart=0#949296</guid>
      <dc:date>2008-05-20T16:20:29Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/927786?tstart=0#927786</link>
      <description>I am running Mac OS X 10.5.2 and Fusion 1.1.2 and experienced the same problem. Turned out to be the Last.fm-client, just as in benpoole's case. When the client was shutdown the input from the keyboard worked again in vmware.&lt;br /&gt;
&lt;br /&gt;
These applications works fine together mostly, as long I don't change any preferences in the last.fm client.. But I will inform last.fm about this issue and hopefully this will be solved in their client in a future release.. Thanks for the tips!</description>
      <pubDate>Mon, 28 Apr 2008 07:06:15 GMT</pubDate>
      <author>erking</author>
      <guid>http://communities.vmware.com/message/927786?tstart=0#927786</guid>
      <dc:date>2008-04-28T07:06:15Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/865679?tstart=0#865679</link>
      <description>Great tip, thank you. I was able to identify the errant process on my machine causing this too. For the record, the audio scrobbling client, last.fm, was responsible!</description>
      <pubDate>Mon, 18 Feb 2008 09:16:37 GMT</pubDate>
      <author>benpoole</author>
      <guid>http://communities.vmware.com/message/865679?tstart=0#865679</guid>
      <dc:date>2008-02-18T09:16:37Z</dc:date>
      <clearspace:dateToText>1 year, 9 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/848154?tstart=0#848154</link>
      <description>Thanks for the info.  I think I can get by until then.  Take care.&lt;br /&gt;
&lt;br /&gt;
p.s. I also noted the EA version burns quite a bit of CPU. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
Best regards,&lt;br /&gt;
&lt;br /&gt;
Charles E. Johnson&lt;br /&gt;
Information Systems Manager, Schenker Inc.&lt;br /&gt;
telephone: 516.403.5405</description>
      <pubDate>Fri, 25 Jan 2008 14:36:13 GMT</pubDate>
      <author>cej</author>
      <guid>http://communities.vmware.com/message/848154?tstart=0#848154</guid>
      <dc:date>2008-01-25T14:36:13Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/848165?tstart=0#848165</link>
      <description>The fix isn't in the EA for Leopard but I'm told it will be in the GA (Mid-March is the latest I've heard for GA).</description>
      <pubDate>Fri, 25 Jan 2008 14:25:58 GMT</pubDate>
      <author>chillyjim</author>
      <guid>http://communities.vmware.com/message/848165?tstart=0#848165</guid>
      <dc:date>2008-01-25T14:25:58Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/847121?tstart=0#847121</link>
      <description>Hi chillyjim. Is this fix also available for the pre-release SecureClient for Leopard, or is it just for 10.4?  I just got the pre-relase and am running Leopard.  As you suggested, switching to Unity resolves the issue, but I prefer to work in full screen mode.</description>
      <pubDate>Thu, 24 Jan 2008 13:47:59 GMT</pubDate>
      <author>cej</author>
      <guid>http://communities.vmware.com/message/847121?tstart=0#847121</guid>
      <dc:date>2008-01-24T13:47:59Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/809409?tstart=0#809409</link>
      <description>Sorry I should have posted this a while ago. There is a fix to the Check Point SecureClient  problem. If you contact support they can supply you the updated client. The version I got is SecureClient_B612008001_1.pkg.zip.&lt;br /&gt;
&lt;br /&gt;
Also when in "Unity" mode the keyboard does work.&lt;br /&gt;
&lt;br /&gt;
-jlh</description>
      <pubDate>Mon, 03 Dec 2007 15:03:59 GMT</pubDate>
      <author>chillyjim</author>
      <guid>http://communities.vmware.com/message/809409?tstart=0#809409</guid>
      <dc:date>2007-12-03T15:03:59Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/783634?tstart=0#783634</link>
      <description>Just to let folks know, we are painfully aware of this issue, and we're sorry for the inconvenience.  The problem is that &lt;i&gt;any&lt;/i&gt; program, like Checkpoint, Quicken, etc. can disable raw keyboard input system-wide—not just to VMware Fusion, but also to any game or accessibility application that needs to read the keyboard directly.&lt;br /&gt;
&lt;br /&gt;
We've spent several months trying to get Apple to provide us a workaround; they wrote a Technical Note that we've been sending to the application vendors telling them how to use the keyboard disabling API correctly:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://developer.apple.com/technotes/tn2007/tn2150.html"&gt;http://developer.apple.com/technotes/tn2007/tn2150.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
We proposed a new API to be included in Mac OS X 10.5, but that didn't happen.&lt;br /&gt;
&lt;br /&gt;
It's going to take some serious rearchitecting of our keyboard support to no work around this issue, and unfortunately that didn't happen in time for VMware Fusion 1.1.</description>
      <pubDate>Wed, 31 Oct 2007 16:55:41 GMT</pubDate>
      <author>bgertzfield</author>
      <guid>http://communities.vmware.com/message/783634?tstart=0#783634</guid>
      <dc:date>2007-10-31T16:55:41Z</dc:date>
      <clearspace:dateToText>2 years, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/783513?tstart=0#783513</link>
      <description>&lt;br /&gt;
After tearing my hair our, letting it grow back, and then tearing it out again, rebooting, rebooting, and then rebooting, I decided I needed to come up with a better solution.&lt;br /&gt;
&lt;p /&gt;
I dug around a little, and figured out that Opera (running on the Mac) is causing my keyboard to stop working in VMWare Fusion.  Simply closing Opera (not just minimizing it)  solved my problem.&lt;br /&gt;
&lt;p /&gt;
I hope that helps anyone else out there that is also losing their hair.</description>
      <pubDate>Wed, 31 Oct 2007 15:16:18 GMT</pubDate>
      <author>AustinJane</author>
      <guid>http://communities.vmware.com/message/783513?tstart=0#783513</guid>
      <dc:date>2007-10-31T15:16:18Z</dc:date>
      <clearspace:dateToText>2 years, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/780543?tstart=0#780543</link>
      <description>I have the same problem, but only if I have Parallels and VMWARE open at the same time.  I have two servers running and it would beep when I tried to input anything except the command button.</description>
      <pubDate>Sun, 28 Oct 2007 02:25:57 GMT</pubDate>
      <author>weezerkiley</author>
      <guid>http://communities.vmware.com/message/780543?tstart=0#780543</guid>
      <dc:date>2007-10-28T02:25:57Z</dc:date>
      <clearspace:dateToText>2 years, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/711676?tstart=0#711676</link>
      <description>Other than this issue, we love the VMware Fusion product.&lt;br /&gt;
&lt;br /&gt;
However, this is a show-stopper for several people at my company.&lt;br /&gt;
&lt;br /&gt;
System administrators, developers, consultants, etc. need access to customers' networks or their own through VPN's such as Check Point VPN-1 with Secureclient/Securemote.&lt;br /&gt;
&lt;br /&gt;
I'm not sure if this is Check Point's issue to resolve.  However, they have IMHO been slow to update their Mac OS X VPN client, and Parallels Desktop does not have this compatibility issue with Check Point's software.&lt;br /&gt;
&lt;br /&gt;
So could VMware at least acknowledge the seriousness of this bug/compatibility issue, and perhaps give us an ETA for fixing it?&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
David</description>
      <pubDate>Wed, 01 Aug 2007 22:14:20 GMT</pubDate>
      <author>ddigioia</author>
      <guid>http://communities.vmware.com/message/711676?tstart=0#711676</guid>
      <dc:date>2007-08-01T22:14:20Z</dc:date>
      <clearspace:dateToText>2 years, 3 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/674467?tstart=0#674467</link>
      <description>Are there plans to have the keyboard operate without having to disable Quicken Scheduler or the other programs?</description>
      <pubDate>Tue, 19 Jun 2007 01:44:07 GMT</pubDate>
      <author>taxman</author>
      <guid>http://communities.vmware.com/message/674467?tstart=0#674467</guid>
      <dc:date>2007-06-19T01:44:07Z</dc:date>
      <clearspace:dateToText>2 years, 5 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/632777?tstart=0#632777</link>
      <description>It seems my issue is related to VPN, however not from OS X. I have a Parallels VM with Win XP SP2 installed. When I login to our corp LAN using the Contivity VPN Client from Nortel within the Parallels VM, I have the keyboard lockout issue ONLY in VMWare VMs. I can have multiple instances of Parallels VMs (Linux, Windows, etc) without issue. I also do not have a problem with using the keyboard in OS X. The lockout (system beeps) only occur in VMWare VMs. Any suggestions are greatly appreciated!</description>
      <pubDate>Fri, 27 Apr 2007 17:57:13 GMT</pubDate>
      <author>pingaiter</author>
      <guid>http://communities.vmware.com/message/632777?tstart=0#632777</guid>
      <dc:date>2007-04-27T17:57:13Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/617424?tstart=0#617424</link>
      <description>No problem.  I've written to Checkpoint, and they said they would release a fixed version of the client.</description>
      <pubDate>Mon, 09 Apr 2007 16:55:40 GMT</pubDate>
      <author>bgertzfield</author>
      <guid>http://communities.vmware.com/message/617424?tstart=0#617424</guid>
      <dc:date>2007-04-09T16:55:40Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/617423?tstart=0#617423</link>
      <description>This was just what I needed.  The checkpoint SecureClient program was preventing my keyboard from working properly.  I stopped the VPN client (on my Mac side) and then I was able to use the keyboard again.  Thanks so much for your help!</description>
      <pubDate>Mon, 09 Apr 2007 16:49:15 GMT</pubDate>
      <author>wesochuck</author>
      <guid>http://communities.vmware.com/message/617423?tstart=0#617423</guid>
      <dc:date>2007-04-09T16:49:15Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/616384?tstart=0#616384</link>
      <description>This means some application (usually Quicken or CheckPoint Secure Client VPN-1) has disabled keyboard input systemwide.&lt;br /&gt;
&lt;br /&gt;
You'll notice that while this happens, if you go to System Preferences &amp;gt; International &amp;gt; Input menu and enable the "Keyboard Viewer", that Keyboard Viewer no longer works.&lt;br /&gt;
&lt;br /&gt;
Are you running either Quicken or CheckPoint Secure Client VPN-1?&lt;br /&gt;
&lt;br /&gt;
If you're running Mac OS X 10.4.9 when this happens, can you run the following from a Terminal (from the /Applications/Utilities folder)?&lt;br /&gt;
&lt;br /&gt;
ioreg -l -w 0 | grep SecureInput&lt;br /&gt;
&lt;br /&gt;
You should see something like:&lt;br /&gt;
&lt;br /&gt;
"IOConsoleUsers"  = ({"kCGSSessionGroupIDKey"=20,"kCGSSessionOnConsoleKey"=Yes,"kCGSSessionIDKey"=256,"kCGSSessionUserNameKey"="admin","kCGSessionLoginDoneKey"=Yes,"kCGSessionLongUserNameKey"="admin","kCGSSessionSystemSafeBoot"=No,"kCGSSessionLoginwindowSafeLogin"=No,"kCGSSessionConsoleSetKey"=0,"kCGSSessionUserIDKey"=501,"kCGSSessionSecureInputPID"=311})  "IOConsoleUsersSeed" = &amp;lt;14000000&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Let me know what you see for the "kCGSSessionSecureInputPID" value.  Can you note down the number, then run:&lt;br /&gt;
&lt;br /&gt;
ps auxwww | grep 311&lt;br /&gt;
&lt;br /&gt;
(where 311 is that number)&lt;br /&gt;
&lt;br /&gt;
so we can see what application has enabled secure input?&lt;br /&gt;
&lt;br /&gt;
Thanks!</description>
      <pubDate>Fri, 06 Apr 2007 22:01:30 GMT</pubDate>
      <author>bgertzfield</author>
      <guid>http://communities.vmware.com/message/616384?tstart=0#616384</guid>
      <dc:date>2007-04-06T22:01:30Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>keyboard stops working... system beeps</title>
      <link>http://communities.vmware.com/message/616359?tstart=0#616359</link>
      <description>I've seen a few posts circulating with no resolution regarding this so I thought I'd add my observations. My situation is similar to what I've read with others. Mysteriously Fusion guest OSes will lose keyboard functionality. This is consistent with all OSes I currently have configured (Solaris 10-64, XP SP2, Ubuntu 6.10 Server). With Solaris it seemed to happen right before I could type the domain name during the system install procedure. There doesn't seem to be a similar pattern with XP SP2 and Ubuntu. Funny thing is in XP, pressing the Command key will trigger the opening of the Start menu, however no other keys will work. Pressing any other key in any OS results in an OS X system beep with no output to the Fusion VM. All other OS X applications respond normally to the keyboard, including VMs running in Parallels!&lt;br /&gt;
&lt;br /&gt;
On a whim, I've closed all my Parallels VMs and proceeded to reinstall Solaris. I did get past all initial screens and the install appears to be proceeding normally. Perhaps there is a conflict with Parallels and Fusion with grabbing keyboard input. Any thoughts?&lt;br /&gt;
&lt;br /&gt;
Oh, I'm using Fusion beta 3, and Parallels build 3188 in case anyone's curious.&lt;br /&gt;
&lt;br /&gt;
---------------------------------------------------------&lt;br /&gt;
Macbook Pro 2.33 C2D | 3GB Ram | 160 GB HD | OS X 10.4.9</description>
      <pubDate>Fri, 06 Apr 2007 21:30:54 GMT</pubDate>
      <author>pingaiter</author>
      <guid>http://communities.vmware.com/message/616359?tstart=0#616359</guid>
      <dc:date>2007-04-06T21:30:54Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>16</clearspace:replyCount>
    </item>
  </channel>
</rss>

