View Single Post
  #7 (permalink)  
Old 01-28-2007, 05:37 PM
luv2chill's Avatar
luv2chill
Retired Staff
Offline
Location: Lawrence, KS
 
Join Date: Nov 2006
Posts: 1,524
Reputation: 143
luv2chill is keeping up the good workluv2chill is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via ICQ to luv2chill Send a message via AIM to luv2chill Send a message via MSN to luv2chill Send a message via Yahoo to luv2chill Send a message via Skype™ to luv2chill
Hmmm... that's odd. OK I'm still on AKU2.2 so maybe someone can double-check that this is still the correct registry value to modify the button lock. I just opened up the buttonlock cab and this is the only thing it adds to the registry:

[HKEY_LOCAL_MACHINE\HARDWARE\OEM\KEYBD]
"KeyLock"=dword:00000001

It does it via xml, so if the registry value itself hasn't changed in 3.x I wonder if for some reason the xml file isn't being parsed correctly when installing that cab.

Can someone running 3.3 test this? Look in the registry for that value, change it to 0 and then look in the buttons applet to see if it's been changed to "Do not lock buttons" (might require a soft reset first).

If the buttons applet doesn't change then there are two possible reasons. Either:

1. The value and/or key to control this setting is different
or
2. The setting isn't controlled by the registry anymore.

You could check #1 by dumping the registry then changing the setting in the buttons applet and then dumping again and doing a diff on the files.

Hope it's not #2, as that would be a regression back to the way WM 2003SE did it (I spent hours looking for this setting in the registry on my PPC6600 and discovered it didn't exist. It must have been set inside the button driver or something).

OK well hopefully it's just something easy.
Reply With Quote