Solved Num Lock in XP won't start in ON condition

November 19, 2013 at 14:00:51
Specs: Windows XP Pro, Pentium/3Gb
I have use the VB script and I have set the InittialKeyboardIndicators registry entry to 2 but it reverts to zero every time I restart the computer.
How can I make it stay at 2?

See More: Num Lock in XP wont start in ON condition

Report •

#1
November 19, 2013 at 15:00:03
IF I had to guess there are multiple keys arguing with each other as InitialKeyboardIndicators can be found in multiple locations

HKEY_USERS->.Default->Control Panel->Keyboard
HKEY_CURRENT_USER->Control Panel->Keyboard

on my computer one is set to 0 and the other 2. I am not sure which overides the other.

::mike


Report •

#2
November 19, 2013 at 18:07:53
Look at this site,
right side panel,
fourth line from the top,
might give you some ideas:

http://www.kellys-korner-xp.com/xp_...

MIKE

http://www.skeptic.com/


Report •

#3
November 19, 2013 at 19:16:43
✔ Best Answer
Is there a bios option for 'numlock on at startup'?

Report •

Related Solutions

#4
November 20, 2013 at 00:42:03
Is there a bios option for 'numlock on at startup'?

There is on my PC and that is where I would start if I was the poster!


Report •

#5
November 20, 2013 at 15:33:50
There are two separate items in the registry for this condition and they were different.
But changing them both to "2" did not solve the problem.
There is a setting in BIOS for NumLock at startup and it was set to OFF

Thanks for all the responses.


Report •

#6
November 20, 2013 at 19:17:57
You're welcome. I guess that worked out then? There was an old dos command--'numlock=on' or 'numlock=off' you could put in autoexec.bat but I don't think it'll work with XP.

Report •

#7
November 20, 2013 at 20:01:30
Yes, the problem is resolved by the change to the BIOS.
Probably an autoexec.bat entry wouldn't work but one could create a batch file that could run in the Startup folder. That is assuming XP would respond to a numlock=on command.

Thanks again


Report •

#8
November 21, 2013 at 05:08:32
I would have thought that the registry entry would over ride the bios once windows loaded.

::mike


Report •

#9
November 21, 2013 at 06:31:21
I also thought the registry would over-ride the BIOS but once Windows started, I found the registry entry had been changed back to zero from 2.
Must have been the BIOS entry that did that because after altering the BIOS, the NumLock is ON at startup.

Report •

#10
November 21, 2013 at 07:06:45
my other thought is that you could have used a script
support.microsoft.com/kb/314879

::mike


Report •

Ask Question