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.

    NP 5160 HotKey AP Problem

    Discussion in 'Sager and Clevo' started by mont3, Mar 30, 2011.

  1. mont3

    mont3 Notebook Enthusiast

    Reputations:
    0
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    5
    After installing the drivers for the computer I started noticing the the cursor would freeze for 2-4 seconds after logging in when turning the computer on or coming back from sleep.

    It turns out that the driver listed as "HotKey AP" in the driver utilities CD is the cause of the problem. Normally I would disregard it and move on; however, without it, I can't use any of the hot keys like the "VGA" that switches between integrated and discrete graphics.

    Has anyone had any problem like this in the past? I tried looking for an updated version of the driver but was unsuccessful. The version I am using is 3.3017. I was also wondering if there was a way to manually set these hot keys to do what I want. Any help is appreciated.

    Edit: I forgot to mention that the battery life indicator only shows the percentage and not the time for some reason.
     
    mont3, Mar 30, 2011
    #1
  2. othonda

    othonda Notebook Deity

    Reputations:
    717
    Messages:
    798
    Likes Received:
    15
    Trophy Points:
    31
    othonda, Mar 31, 2011
    #2
  3. mont3

    mont3 Notebook Enthusiast

    Reputations:
    0
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    5
    It seems like the problem is only with the touchpad. I tried replicating my problem with a mouse and didn't see anything wrong. Unfortunately the updated drivers didn't fix it either :( Any other suggestions?
     
    mont3, Apr 1, 2011
    #3