Skip to main content
Inspiring
February 15, 2019
Answered

Keyboard stopped working

  • February 15, 2019
  • 3 replies
  • 2172 views

Recently my keyboard stopped working in FrameMaker only.  The mouse works fine, and if I put the cursor in a window such as a marker window, the keyboard will work.  If I open a document to edit, the keyboard doesn't work.   I tried rebooting, reloading the program, nothing brings the keyboard back.  It works ok in other programs and in Windows.  The KEYBOARD WORKS OK, except to edit a document in FrameMaker.

    This topic has been closed for replies.
    Correct answer Dennis Vied

    Checking through the preferences, I found that "Lock file on Network" was checked.  I unchecked it, and the keyboard now works.  I don't understand all I know about that.  I am not accessing the file on the network, but, the problem is solved.

    3 replies

    Participant
    September 15, 2020

    Same symptoms with me. Keyboard does not work only in Framemaker! 

    But after that "Lock file on Network" was unchecked, keyboard started to work in FM.

    Bob_Niland
    Community Expert
    Community Expert
    February 16, 2019

    re: Recently my keyboard stopped working in FrameMaker only.

    Did you happen to try the arrow keys? I suspect they still worked. That's been my experience with read-only documents.

    re: The mouse works fine

    But I'll bet that highlight and right-click Cut did not.

    On the other hand, when just the "S" key on my [cordless] keyboard stops working, then I know that the batteries need to be replaced.

    Inspiring
    February 16, 2019

    No, the arrow keys didn't work.  Nothing on the keyboard worked, but only in a document.

    Dennis ViedAuthorCorrect answer
    Inspiring
    February 15, 2019

    Checking through the preferences, I found that "Lock file on Network" was checked.  I unchecked it, and the keyboard now works.  I don't understand all I know about that.  I am not accessing the file on the network, but, the problem is solved.

    December 18, 2020

    I had the exact same problem. I was so relieved to discover this simple solution here, which I never would have found on my own. Thanks for fixing it for me!