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.

    Windows 7 driver for DV5z remote control

    Discussion in 'HP' started by tpaxadpom, Jul 8, 2010.

  1. tpaxadpom

    tpaxadpom Notebook Geek

    Reputations:
    19
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
    I did a clean install of Windows 7 on my DV5-1125NR and noticed that not all buttons work on the remote control that came with laptop. I can navigate and it will launch the Media center but it doesn't respond to other commands, the most important one being display change. I use my laptop as HTPC and have my universal remote programmed. I install ECE driver from HP web site and even tried installing Vista 64-bit driver for quick launch buttons there is no driver for Windows 7. Same problem. Also volume control pad used to work fine but not anymore (same crap as with Vista). Once I adjust the volume it starts bouncing around like crap until I hit the stop button. At least it's not making that crazy clicking sound...
    Any ideas as to what I should try?
     
  2. Th3_uN1Qu3

    Th3_uN1Qu3 Notebook Deity

    Reputations:
    214
    Messages:
    1,192
    Likes Received:
    0
    Trophy Points:
    55
    For the volume bar you can uninstalling ALL quickplay/quicklaunch/quick-thing software and let Windows handle it. It should work just fine.

    For the remote, i'll see what can be done. That is if i remember where i put mine.
     
  3. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    You need all 3 of these:

    SP45889 Quick Launch driver
    SP45058 Quick launch buttons
    SP44983 ENE CIR driver win 7

    You can find it here in HP softpaq FTP
    ftp://ftp.hp.com/pub/softpaq/
     
  4. tpaxadpom

    tpaxadpom Notebook Geek

    Reputations:
    19
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
    Much appreciated guys. It's bizarre but I noticed today that mute is changing color though I went and installed 64-bit Quick Launch software once again and now I have a working display button. The only thing left is to find out a way to customize Quick Play button.
     
  5. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    Edit the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard\HP Quick Launch Buttons

    In Qaction, add the location of the program you want the Q button to load.

    For instance to load Windows Media center, you path would be:

    C:\Windows\ehome\ehshell.exe
     
  6. tpaxadpom

    tpaxadpom Notebook Geek

    Reputations:
    19
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
    2.0,

    wow you are fast. Thank you once again. Now I can finally enjoy this laptop. Too bad they don't make DV5 first gen anymore. I really like the layout and 16:10 aspect ratio.
     
  7. 2.0

    2.0 Former NBR Macro-Mod®

    Reputations:
    13,368
    Messages:
    7,741
    Likes Received:
    1,022
    Trophy Points:
    331
    Glad you're all sorted out. Cheers! :)
     
  8. tpaxadpom

    tpaxadpom Notebook Geek

    Reputations:
    19
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
    Discovered a new problem with Windows 7. Sometimes I loose the ability to control the dimming of the display. Restart fixes this problem but is there a way to have a permanent fix?
     
  9. tpaxadpom

    tpaxadpom Notebook Geek

    Reputations:
    19
    Messages:
    94
    Likes Received:
    0
    Trophy Points:
    15
    The fix turned out to be Catalist 10.7 drivers. Apparently 10.6 had a bug.