OUR NETWORK:MediaSmart Home Sansa Community Explore3DTV TechLore RoboCommunity Dijit Community About UsAdvertiseContact Us

 
Learn about scoring Forum's Raw Score: 99797.4
October 16, 2009 02:24 PM
Rating (0 votes)
  • 1
  • 2
  • 3
  • 4
  • 5
Rate This!

Member Avatar

Rooney

Member
Joined: 10/13/2009

Hello for the first time. Before 10 days I have install window7 on my HP CQ60 laptop and installed all drivers that my laptop needed, but than I found really stupid problem. It is HP Quick Launch Button. When I install this driver my problem, that is mute button doesn't work, still doesn't work. After hours that I was looking for answer I never found one. The funny thing about this problem that when I go to folder where HP QLB installed and click on Setup. When Installing finished mute button works, BUT when I turn of my laptop to next time to use my laptop mute button doesn't work. I know that HP hasn't created this driver for win7 yet but is there a way to solve this problem before that? I hope you will help me and you know the answer for my problem.

Discussion:    Add a Comment | Comments 1-7 of 7 | Latest Comment

October 16, 2009 4:27 PM

Quick Launch Buttons does not control the mute button (I know, it drove me nuts too). Uninstall and reinstall the Realtek Audio Drivers.

October 16, 2009 6:09 PM

PrototypeNM1 said: Quick Launch Buttons does not control the mute button (I know, it drove me nuts too). Uninstall and reinstall the Realtek Audio Drivers.

 If QLB does not control the mute button why than after I install setup of QLB mute button work to next time when I turn on my laptop. And can you explain what is the Realtek Audio Drivers?

October 16, 2009 6:24 PM

PrototypeNM1 said: Quick Launch Buttons does not control the mute button (I know, it drove me nuts too). Uninstall and reinstall the Realtek Audio Drivers.
Nope. Even with HP's realtek driver, it still doesn't work properly due to load order of the QLB, Realteck Audio Driver Notification Handle, and SmartMenu. It's a complex interaction/binding between the three and very dependent on order: Realtek Notification > QLB > SM. Problem is that Windows 7 optimizes the boot sequence to its liking (for speedier startup) and the necessary parts of the audio notification get loaded later as a result. When you log off the audio driver components are not unloaded; only the Registry's 'Run' key components are. Then when you log on back, things happen in the correct order and mute works. If you got Windows 7 loading things correctly at your end, touch wood, and it's prolly cause u have a number of startup items causing a 'sweet' delay. Here I have nothing (I boot in 30 sec), hence the issue. Some components load much faster/earlier then they should.

October 17, 2009 12:32 PM

Rooney said:
PrototypeNM1 said: Quick Launch Buttons does not control the mute button (I know, it drove me nuts too). Uninstall and reinstall the Realtek Audio Drivers.
 If QLB does not control the mute button why than after I install setup of QLB mute button work to next time when I turn on my laptop. And can you explain what is the Realtek Audio Drivers?
In the case of cq50, the audio driver is Conexant High-Definition SmartAudio 221 Driver - cq50 does not have a realtek audio. But you would still need to have the correct QLB / Conexant magical load order!

October 18, 2009 10:03 AM updated: October 20, 2009 12:02 PM

SOLVED:
There is a service called 'Com4Qlb'. The default mode for it is 'Manual'. If you change this to 'Automatic (Delayed Start)' (or 'Automatic' depending on your existing startup load) it will fix the issue I described above about load order. Now my Mute button works perfectly as it was meant to be and changes color red/white. The setting sticks and no need to log on/off or do any trick. It will always work from a cold start!

October 19, 2009 7:37 AM

Nice find CyrenesFriend =)

Moderator - Creator of Tx2 Touchsmart All in one Installer.
Touchsmart Tx2z Laptop: AMD ZM-87 CPU, 4gb Corsair DDR2 2x2gb, 256gb Corsair Performance SSD, Windows 7 Ultimate Signature Edition.

November 8, 2009 2:01 AM

Hey - I tried your solution and it still doesn't work. Although the logging off and logging back in seems to do the fix. But it would be nice to work with a cold reboot. Any suggestions?

Discussion:    Add a Comment | Back to Top | Comments 1-7 of 7 | Latest Comment

Add Your Reply

(will not be displayed)

Email me when comments are added to this thread

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window