Keep Num Lock on after start-up

Those numbers indicate that Caps Lock is the second bit in a flags

structure, ie 2^1 (which equals 2 if you remember from school).

2^0 =1

2^1 =2

2^2 =4

The official documentation for decades say 0 and 2 are the only values.

--

..

--

"Saint_Bernard" wrote in message

news:36a93b1b-d242-4004-a00f-07588ffbf6a3...

>I propose a challenge. I tested all of the numbers from zero to seven in

>the 'InitialKeyboardIndicators' registry. First I locked each value; then I

>did not lock the values. It is my opinion that Windows 7 has a bug --

>actually several but I shall only discuss one of them here. I challenge

>anyone out there to prove to me that the results I am about to produce do

>NOT indicate the existance of a bug in Windows 7. As my reference point I

>am using: http://www.tipstrs.com/tip/2776/Boot-with-the-Num-Lock-enabled

>

> I assigned the 'InitialKeyboardIndicators' key every single value, and

> tested each value in two states: Num Lock On and Num Lock Off. When I

> locked each value my results where as follows: 0 - Off, 1 - Off, 2 - On,

> 3 - On, 4 - Off, 5 - Off, 6 - On, and 7 - On. NO OTHER KEY'S STATE WAS

> AFFECTED! Granted, there is a pattern but why was ONLY the status of the

> 'Num Lock' affected? Correct me if I am wrong but would it not make more

> sense to have the indicator values produce the same results as in the

> website I have referred to in the preceding paragraph?

>

> When I did not lock the values zero to seven Windows 7 ALWAYS REPLACED MY

> VALUE WITH A VALUE OF TWO! Now, according to the preceding paragraph a

> value of '2' should turn the 'Num Lock' state 'On' but once again either I

> can no longer think straight because it is 3:30 a.m. and I have been up

> since 7:00 a.m. or Windows 7 HAS A BUG because THIS WAS NOT THE CASE!

> Every single value left the 'Num Lock' status unchanged! Goodnight, and I

> wish I could say good riddens to Microsoft...

> --------------------------------------------------------------------------------

> Programmer for Visual C++ 6.0, and Microsoft Office including Access

I propose a challenge. I tested all of the numbers from zero to seven in the 'InitialKeyboardIndicators' registry. First I locked each value; then I did not lock the values. It is my opinion that Windows 7 has a bug -- actually several but I shall only discuss one of them here. I challenge anyone out there to prove to me that the results I am about to produce do NOT indicate the existance of a bug in Windows 7. As my reference point I am using: http://www.tipstrs.com/tip/2776/Boot-with-the-Num-Lock-enabled

I assigned the 'InitialKeyboardIndicators' key every single value, and tested each value in two states: Num Lock On and Num Lock Off. When I locked each value my results where as follows: 0 - Off, 1 - Off, 2 - On, 3 - On, 4 - Off, 5 - Off, 6 - On, and 7 - On. NO OTHER KEY'S STATE WAS AFFECTED! Granted, there is a pattern but why was ONLY the status of the 'Num Lock' affected? Correct me if I am wrong but would it not make more sense to have the indicator values produce the same results as in the website I have referred to in the preceding paragraph?

When I did not lock the values zero to seven Windows 7 ALWAYS REPLACED MY VALUE WITH A VALUE OF TWO! Now, according to the preceding paragraph a value of '2' should turn the 'Num Lock' state 'On' but once again either I can no longer think straight because it is 3:30 a.m. and I have been up since 7:00 a.m. or Windows 7 HAS A BUG because THIS WAS NOT THE CASE! Every single value left the 'Num Lock' status unchanged! Goodnight, and I wish I could say good riddens to Microsoft...

Programmer for Visual C++ 6.0, and Microsoft Office including Access

If Windows alters the value of the 'InitialKeyboardIndicators' value it means that you have placed an incorrect lock on the 'Keyboard' key. After setting the 'InitialKeyboardsIndicators' value right-click the 'Keyboard' key. Next click 'Permissions...' (NOTE: The 'Permissions for Keyboard' Window should Appear.) In the section titled 'Permissions for RESTRICTED' click the button labelled 'Advanced.' (NOTE: The 'Advanced Security Settings for Keyboard' Window should Appear.) In the list box titled 'Permission entries:' there should be at least four lines of data. Look at the column of data headed: Name. Select the top-most entry of the form: <Your Name>(<Computer Name>&lt;Your Name>). Click the button labelled 'Edit...' located beneath the list box. (NOTE: The 'Permission Entry for Keyboard' Window should Appear.) In the list box titled 'Permissions:' there should be an entry named: Set Value. This value should have two check boxes to its right. Set the right-most check box. Click: OK. Click: Apply OK. Repeat the last step. On my computer the value for 'InitialKeyboardsIndicators' is set to '1' and 'Num Lock' is always 'Off.'

There is a table in another forum which indicates the eight values which 'theoretically' can be assigned to the 'InitialKeyboardsIndicators' value. These values range from ''0' to '7.' Fortunately the posting provided the address of the website from which these values were taken. I looked at the values on the website. The website indicated that the values were for 'Windows XP.' I tried a couple of the values and discovered that THEY DID NOT APPLY to Windows 7. If I remember correctly a value of '2' supposedly turns on both 'Caps Lock' and 'Num Lock.' In Windows 7 this does not hold. A value of '3' also does not adhere to the settings for Windows 7 either.

Please note that if you would like to lock the 'InitialKeyboardsIndicators' value for several users you will need to set and lock the value for each user individually. There is no setting which will let you set the value for all users.

I have not had the chance to test this routine on a computer with multiple users. Under Windows XP each user was assigned a unique ID consisting of something like 25 characters. Whenever a user logged in the values for that user were copied into HKEY_CURRENT_USER. If Windows 7 does likewise locking the 'keyboard' key in HKEY_CURRENT_USER might not be enough. In my registry my own personal data is stored in: HKEY_USERS\S-1-5-21-1633903244-1207972891-1032356077-1003. If you were to go to 'Control Panel\Keyboard' you would find that the 'keyboard' key is locked in the manner I have described above. (NOTE: Stay away from registries ending in '_Classes.' For example '...6077-1003_Classes.') You may have to set and lock the 'keyboard' key for each individual user.

If you have multiple users with different desires this should theoretically be possible. If a user likes the default behaviour of Windows 7 then do not lock the 'Keyboard' key for that particular user. Make sure that the 'Keyboard' key in HKEY_CURRENT_USER matches the 'Keyboard' key settings and lock for the corresponding key for that user's registry settings!

Now we come to what might seem to be a difficult situation to solve: How does one discover which HKEY_USERS' key belongs to which user? This is tedious, but quite simple. Get out of the registry and follow the following steps:

1. Open Windows Explorer
2. Click: Organize 'Folder and search options'
3. NOTE: The 'Folder Options' Window should Appear
4. Select the 'View' Tab
5. In the 'Advanced settings:' Section under 'Files and Folders' there should be Two Radio Buttons under the 'Hidden files and folders' Subsection
6. Select the Radio Button labelled: Show hidden files, folders, and drives
7. Click: Apply OK
8. NOTE: The 'Folder Options' Window should Vanish
9. VERY IMPORTANT: Click: Organise Close
10. Open Windows Explorer
11. Go to: Users&lt;Name of the User>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
12. Click: 'New folder'
13. Provide a Unique Name for the Folder which Contains the <Name of the User> (i.e. St Bernard Registry Locator Menu Folder)
14. Repeat Steps 11 - 13 for Each User
15. Click: Organize Close
16. Open the Windows' Registry
17. Search the Keys for One of the Folders that were Created
18. The search will take you into the registry data for that particular user
19. NOTE: Do Not Remove the Folder!

After you have appropriately set the initial 'Num Lock' status for each individual user and insured that the setting in HKEY_CURRENT_USER is set to mirror the setting for the current user exit the registry.

Now, go into Windows Explorer and remove the folders you created. Next:

1. Click: Organize 'Folder and search options'
2. NOTE: The 'Folder Options' Window should Appear
3. Select the 'View' Tab

4) Click: 'Restore Defaults'

5. Click: Apply OK
6. NOTE: The 'Folder Options' Window should Vanish

7) Click: Organise Close

NOTE: ALTERING THE REGISTRY IS EXTREMELY DANGEROUS AS ERRORS CANNOT ALWAYS BE CORRECTED. I ONCE REMOVED AN INCORRECT KEY AND MY COMPUTER LOCKED. AFTER UNPLUGGING AND PLUGGING THE COMPUTER BACK IN WINDOWS REFUSED TO BOOT. I HAD TO REFORMAT MY HARD DRIVE.

---

Programmer for Visual C++ 6.0, and Microsoft Office including Access

Yes I have found this out. I had a system image to go back to.

1 is nothing, 2 is on.

HKEY_CURRENT_USER\Control Panel\Keyboard

InitialKeyboardIndicators REG_SZ Number

Specifies initial values for keys. 0 means that NumLock is turned off after

the user logs on; 2 means Numlock is turned on after the user logs on. This

value is set during log off or shutdown to preserve the state of the Numlock

key at that time.

Default: 0

InitialKeyboardIndicators

HKCU\Control Panel\Keyboard

Data type Range Default value

REG_SZ 0 | 2 0

Description

Determines whether the NUMLOCK key is on or off when the computer starts.

The system stores the state of the NUMLOCK key in this entry during logoff

and shutdown, and then uses this value to restore the state when the user

logs on.

Value Meaning

0 NUMLOCK is off.

2 NUMLOCK is on.

--

..

--

"markhoppe" wrote in message news:443eb0fb-32c2-4052-9879-79bf742ef1dd...

> I have followed these instructions and I will check it the next time I

> reboot. Interestingly my InitialKeyboardIndicators was set to 2 when I

> opened the key. Was does the "2" indicate? I know "0" is off and "1" is

> on.

>

>

> Mine are set at 2 also, and when I try to change it, it changes it back to

> 2.