The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    T500/XP- Keyboard not responding after sleep

    Discussion in 'Lenovo' started by jkchang, Feb 19, 2009.

  1. jkchang

    jkchang Notebook Enthusiast

    Reputations:
    2
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    15
    T500 running XP 32-bit

    I just started experiencing this problem Wednesday. Once the computer returns from the sleep state, the keyboard will not respond. This only occurs if the sleep state was initiated when the lid is open.

    If the lid is closed and the sleep state is engaged, the keyboard works fine once returning from sleep.

    The finger is being pointed at Lenovo Power Manager OR Microsoft .NET Framework 3.5 - Those are the two items I installed yesterday.

    Any insight would be appreciated. It's a bit annoying to open/close the lid to make sure the keyboard works.

    Note- This is the on-board built-in keyboard. Not an external add-on keyboard.
     
    jkchang, Feb 19, 2009
    #1
  2. jkchang

    jkchang Notebook Enthusiast

    Reputations:
    2
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    15
    Bump- any help would be appreciated
     
    jkchang, Feb 26, 2009
    #2
  3. ZaZ

    ZaZ Super Model Super Moderator

    Reputations:
    4,982
    Messages:
    34,001
    Likes Received:
    1,415
    Trophy Points:
    581
    Why not try uninstalling them to see if they're the culprit.
     
    ZaZ, Feb 26, 2009
    #3
  4. jkchang

    jkchang Notebook Enthusiast

    Reputations:
    2
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    15
    Hmm... SP3 seemed to have fixed it :)

    ZaZ-- You're right... I totally forget to the do the most obvious thing-- hahaha.
     
    jkchang, Feb 27, 2009
    #4