¡¡¡ Let's Make ALL QuickLaunch Buttons Work in a Clean Windows Installation !!!

Hi!

Let me introduce myself. I just got a HDX 9200 last week and all this time I've been fiddling with tweaking the original HP image, installing clean Vista OSes (like twenty times by now), trying different drivers, running drivers-update scammers (like DriverDetective, RadarSync, etc.) just to look at the newest version number of the drivers, then crawling the web to manually find and try them, and so, and so on.

Of course, in the need of having a clean Windows Vista installation (since the HP image has a lot of crap, slowdowns, outdated drivers, not SP1 slipstreamed, etc.) I had to start from scratch.

After installing the clean Vista setup and all the drivers, I found that the QuickLaunch buttons were given me problems. What happened is, at the end, that everyone of them works BUT the TV button. I'm running on the QuickLaunch Buttons drivers 6.40, also QuickTouch installed for OSD, and QuickPlay 3.7 (updated from CyberLink) and still, when touching the TV button, nothing happens. Not even a click is hear like with the others. The strangest thing is that, if I turn the computer on by pressing the TV button instead of the power, it boots... and then it opens the TV module in the QuickPlay app.! Just as it should!

So... let me tell you that I've tried pretty much everything to make it work without luck:

- I installed like a zillion versions of the QuickLaunch buttons drivers

- I installed the original QuickPlay that came with the HP image

- I copied some keys over from the original HP imaged registry, namely the "Profile" in HKLM that has the action "ACTION_ID_LIVE_TV" (or something like that) which is the responsible for opening the module in QuickPlay. While in the original HP image, if I renamed that key to something else (so that the drivers won't find it), it efectively stopped the TV button from working. Then, renamed it correctly back, and the button worked again; so that sums that it was the responsible for making it work. But when copying those keys to the clean Vista, it didn't do anything!

- I copied the whole QuickLaunch folder in Program Files from HP Image -> Clean Vista, overwriting the installed 6.40 QuickLaunch buttons drivers. Guess what; the TV button worked with every version of QuickPlay! (also needed to add that previous registry key), but then the Fn + F7, F8, etc. (backlight, lock, sleep, etc.) stopped working! So that was even worse than not having a TV button functional

- I then tried to copy every file from that folder separately, and merging both the registry keys from the original HP image with the 6.40, in order to have the best of both worlds, but it still didn't to anything.

- I even trying defining a program to execute in the registry key (you know, that key has various entries: .dll that the action uses, function name, displayed text, etc.). Apparently, one of them ("Assignment") takes a path to a file and it's supposedly to execute it when the button is pressed. So my idea was to made a .bat, assign it there, and have it running the QuickPlay.exe with parameters to open the TV module, but the action still wouldn't execute when pressing the button! I think it has something to do with the fact that in Vista you can't configure the buttons, while in XP you can assign different actions. I even found a web site giving out macros for the buttons in the form of .bat, and stating that they wouldn't work in Vista, since there you couldn't change the actions (I had to try though...!)

- At the very last, and after countless hours of trying, I found out that the responsible for recognizing either the TV button or the Fn+ keys was the .exe QLBCL.exe. If I copied the file from the HP image, TV button worked, but stopped the Fn. If I had the 6.40 one, TV didn't work and everything else did. Another strange thing was the fact that in the original image EVERY button worked, be it TV or Fn+ keys! So why not in the clean Vista? Maybe something is still missing

Well, after that... I just gave up. I talked with AspenWiedii that I read in one of his posts that he made the TV button work by copying some keys or something, but I don't know if that was correct after all.

Well... I guess I've tried all that came to my mind. Now I'm with a clean Vista installtation, with everything working but the TV button, and I think that is better than having a bloated installation but with a TV button working. Even so, you don't even realize how much I'd like to make this work and claim to have a 100% fully working system!

Looking forward to hear from you... maybe we can do something about this, and help not only me, but every other user that wants a clean installation with a 100% working system. Thanks in advance!

 

Might be a stupid question, but I couldn't gather the info from your post. Have you tried a program that lets you see if your computer even recognizes it when it's pressed?

 

Is it a Service Pack issue?
Can you make it work on a clean installed Vista non-SP1?
After all, it seems like the QL drivers at hp.com are older than SP1.

 

@Pbottie: I don't know what you meant... which program? The button clearly works since A) It works when the computer is of; it starts Vista and then the QuickPlay's TV module and B) If I copy over the old QLBCL.exe from the HP image, the button works (but breaks all the Fn+ keys)

@Mats: I haven't tried a non-SP1 Vista. And what drivers do you refer to? The sad thing is that HP doesn't even list the QuickLaunch Buttons Drivers in its support page downloads! All there is is the Security Fix for them, but without the drivers themselves, it's pretty useless! But yes, the QL drivers from the HP image ARE older indeed. Anywhere I can get that version installation file?

 

They're right there, dated december 2007?
Under "Software - Solutions"

http://h10025.www1.hp.com/ewfrf/wc/softwareList?os=2093&lc=en&dlc=en&cc=us&product=3636789

Edit: It seems like it was just an update. Have you tried it?

 

So first you have Fn buttons, then you copy that file and then they stop working.
Doesn't it sound like a conflict?
Is it the QLBCL which controls the Fn as well on a original install maybe?
And when you install Vista retail it uses it's own drivers for Fn, then you add the file and you have a conflict.
Sounds like you have to manually disable the Fn buttons somehow before adding the file.
Just guessing here. .

 

@Mats: Yes... it's just an update; the security fix I commented about in the first post; it doesn't do anything at all.

When I install retail Vista, it STILL doesn't control the Fn+ keys; I've tried. Pressing to increase / decrease backlight, etc. doesn't do anything until I install the QL drivers.