More fun with Win7...

[Chappy]

Hey

I've used an HP Multimedia KB for a couple years, even tho my system is Home built and no HP parts, but it works great and has what I need.
Unfortunately tho, the HP drivers refused to install on W7, since the installer checks the OS version and the max version was 6.1 (Vista). So the install immediately rolled back and I can't get all my multimedia and multi-function keys....AArrghhhh!!!!

Well today I got inspired, I can't say if it was by boredom or stupidity...but it was an inspiration at least. I was going to "Decompile" that stupid HP installer, and rebuild it again to suit my needs.

So I ran the installer and waited until it had "unpacked" it's contents, but I didn't go any further. I then went into the hidden temp directory and Copied the unpacked files to another directory. This was necessary because as soon I tell the HP installer to continue, it recognizes an Invalid OS and rolls back the install, deleting the unpacked files. So I let it do just that now, but I have a copy of the installation files....HAHA!!
Take THAT you HP B#st#rds!!!!

Well I now have more work that I intended, I had to go thru about 50 or so files to make sure there wasn't anything that was going to affect this install, and strip the PS2 dll's.
Made a Batch file to make a directory and copy the HP Program folders, run the embedded silent exe's, add the registry keys (29) and register the required dll's and ActiveX .ocx's that were needed. I had to make some edits with Hex Toolbox to strip HP Branding from some things, and all in all it took me around four hours to get this all done and make sure it was correct before starting it. First time I found I forgot the CSS files...oops, second time I couldn't get my DVD drives to open & close with the KB keys (another hex edit did the trick), and the third time seems to be the Charm!
So far, all my programmable keys are, 1st...showing up in Control Panel - Keyboard, Buttons tab (which is built with the CSS files...), and then programmable and work, and have the On-Screen display work. Both DVD trays open & close properly, all my buttons launch what I want them too, and I'm happy...and tired. My eyes are dead after going thru so much Hex!!
But sometimes it's worth it..

 

[Dzomlija]

Wow. All that for a keyboard? I'm not sure if I should be happy for you, or if I should cry!

You must seriously like that keyboard to go through that much effort to get it working in Windows 7. Me, I'd have just replaced it with something else a long time ago.

Then again, I try to avoid HP products like the plague, so I would not have had that problem anyway.

Well done Dave.


OT:
You think maybe you could hack a Canon Lide25 Vista x64 Scanner driver for me so I could use it with my Canon Lide20? (I never could get a x64 driver for it...)

 

[Chappy]

Hiya Peter

Like I said...I was either VERY bored or VERRRY stoopid..

It worked perfectly in Vista but the HP driver used build number for a check process and so failed since build 6.2 (7000) is too high.
I thought it would be easier when I started but it turned into a rather drawn out affair.
Other thing is, this is my only current KB, I gave my Logitech wireless to my Mom when I gave her that HP machine, after I built this one. It was a "stop-gap" machine I bought after my last MoBo fried up and before I fully decided what I was going to build. I robbed that HP of some nice pieces cause my Mom would never use them and the HP KB had some features the other didn't so I ended up with this hodge-podge.

Check your PM on the Latter

 

[garbanzo]

i would have just used my hotkey app to map the buttons. that way i wouldn't have yet another process running in the background. in fact, that is exactly what i have done with my keyboard

i don't know why drivers always come as executables anyway. i usually just unpack the installers and keep just the driver files neatly organized on a drive someplace, then set up my hardware manually in the device manager. more work, but tidier in the end...

 

[Saltgrass]

Chappy, since you probably tried running the compatibility wizard on the install, do you know why it wouldn't work? I read that W7 didn't use a 7 for the kernel for that very reason, so I would think the wizard could handle a 6.2. But on the other hand, maybe Microsoft did not think any 6.x kernel would cause problems.

 

[Chappy]

Hi Saltgrass

Yah, what I meant is that W7 is 6.2, so the installer didn't recognize it, since Max version was 6.1.
It all depends on if the installer uses a version check or not. Allot like Firefox addons but at least you can easily edit them to whatever version you want in the .rdf file and they work in the new V3x. This one would not be so easy without rebuilding the entire installer, so I went another route...I thought it would be easier but it turned out Not to be...