Annoyances.org
Home » Windows XP Discussion Forum » Message 1062857627 Search | Help | Home
  
re: Comment about 'Force NumLock to Behave'
Saturday, September 6, 2003 at 7:13 am
Windows XP Annoyances Discussion Forum
Posted by nozero (6 messages posted)


I was referring specifically to this section: ---- "Solution #3 (Windows 2000/XP only): Run the Registry Editor (REGEDIT.EXE). Open HKEY_CURRENT_USER\Control Panel\Keyboard (If the Keyboard key isn't there, add it.) Double-click the InitialKeyboardIndicators value on the right. (If it's not there, select New from the Edit menu, then String Value, and type InitialKeyboardIndicators for the name of the new value.) Change the value to any of the following: 0 - all indicators off 1 - Caps Lock on 2 - Num Lock on 4 - Scroll Lock on Or, combine them by adding the corresponding values: 3 - Caps Lock and Num Lock on 5 - Caps Lock and Scroll Lock on 6 - Num Lock and Scroll Lock on 7 - Caps Lock, Num Lock, and Scroll Lock on Close the Registry Editor when you're done; the change should take effect the next time you start Windows." ---- I am attempting to get the Caps Lock to be on when Windows is started. I tried this on a total of three PCs. One of which was Win 2K, the other two were XP Pro. The registries of all three PCs already had that key, so all I had to do was change that value. I've found that no matter what I enter as the value in the registry, the only thing that is "saved" is the current state of that key when restarting. In other words, if the Num Lock is on when I restart, the key value will be "2" when checked after a restart or if the Num lock is off when I restart, the key value will be "0" when checked. I find your response to be somewhat vague at best. Please enlighten me as to how this is "done properly", and what I could be doing incorrectly?


On Friday, September 5, 2003 at 8:27 pm, Tom Swanson wrote:
>The post is generally universal on what it fixes. The special posts for XP work 
if 
>they are done properly. 
>
>




Written in response to:
re: Comment about 'Force NumLock to Behave' (Tom Swanson: Friday, September 5, 2003 at 8:27 pm)

Responses to this message:
*re: Comment about 'Force NumLock to Behave' (Tom Swanson: Saturday, September 6, 2003 at 9:07 am)

All messages in this thread [show all]
-Comment about 'Force NumLock to Behave' (nozero: Fri, Sep 5, 2003, 3:17 pm)
-re: Comment about 'Force NumLock to Behave' (Tom Swanson: Fri, Sep 5, 2003, 8:27 pm)
-re: Comment about 'Force NumLock to Behave' (nozero: Sat, Sep 6, 2003, 7:13 am)
-re: Comment about 'Force NumLock to Behave' (Tom Swanson: Sat, Sep 6, 2003, 9:07 am)
-re: Comment about 'Force NumLock to Behave' (nozero: Sat, Sep 6, 2003, 4:04 pm)
-re: Comment about 'Force NumLock to Behave' (Tom Swanson: Sat, Sep 6, 2003, 4:27 pm)
-re: Comment about 'Force NumLock to Behave' (nozero: Mon, Sep 8, 2003, 5:21 am)
*re: Comment about 'Force NumLock to Behave' (Tom Swanson: Mon, Sep 8, 2003, 11:49 am)
-re: Comment about 'Force NumLock to Behave' (Red Shadow: Mon, Sep 8, 2003, 2:57 pm)
*re: Comment about 'Force NumLock to Behave' (nozero: Tue, Sep 9, 2003, 4:19 pm)
-re: Comment about 'Force NumLock to Behave' (Red Shadow: Mon, Sep 8, 2003, 12:09 pm)
*re: Comment about 'Force NumLock to Behave' (nozero: Tue, Sep 9, 2003, 4:14 pm)
*re: Comment about 'Force NumLock to Behave' (bb86405: Fri, Feb 11, 2005, 4:27 am)
Return to the Windows XP Discussion Forum

All content at Annoyances.org is Copyright © 1995-2008 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.