I have a question about Force NumLock to Behave:

I don't want XP to touch my NumLock state at all. My Dell Latitude has a BIOS setting to that allows you set set numlock to on for only one docking state, and off for the other. This is useful, because I want NumLock on when docked (using a 101 keyboard), but off when undocked (because on the laptop keyboard, NumLock turns keys U,I,O,P,J,K,L,; into a numeric keypad. Annoying! So how do I stop XP from overriding the NumLock state at logon?

[Reply or follow-up to this message]

In the registry, be sure that you have this value : HKEY_USERS\.DEFAULT\Control Panel\Keyboard InitialKeyboardIndicators = 0 HKEY_CURRENT_USER\Control Panel\Keyboard InitialKeyboardIndicators = 0 This should solve your problem.


On Sunday, July 13, 2003 at 6:24 pm, Pete wrote:
>I have a question about Force
>NumLock to Behave:

>
>I don't want XP to touch my NumLock state at all.
>
>My Dell Latitude has a BIOS setting to that allows you set set numlock to on for
>only one docking state, and off for the other. This is useful, because I want NumLock
>on when docked (using a 101 keyboard), but off when undocked (because on the laptop
>keyboard, NumLock turns keys U,I,O,P,J,K,L,; into a numeric keypad. Annoying!
>
>So how do I stop XP from overriding the NumLock state at logon?

[Reply or follow-up to this message]

Yeah, I tried that one. It always sets NumLock off at startup, which is not what I'm after. Thanks anyway.


On Wednesday, September 17, 2003 at 1:03 pm, François wrote:
>In the registry, be sure that you have this value :
>
>HKEY_USERS\.DEFAULT\Control Panel\Keyboard
>InitialKeyboardIndicators = 0
>
>HKEY_CURRENT_USER\Control Panel\Keyboard
>InitialKeyboardIndicators = 0
>
>This should solve your problem.
>
>

[Reply or follow-up to this message]

Set it to 2 instead. That should work. --Matt M.


On Wednesday, September 17, 2003 at 4:24 pm, Pete wrote:
>Yeah, I tried that one. It always sets NumLock off at startup, which is not what
>I'm after.
>Thanks anyway.
>
>

[Reply or follow-up to this message]

Thanks Matt, But I don't want it to be always on, always off, or to depend on the previous state. I want the numlock state to depend on the laptop's docking state. The BIOS handles it, but WindowsXP always overrides one way or the other. It's an annoyance I've learned to live with :-)


On Monday, November 17, 2003 at 8:47 am, Matt M wrote:
>Set it to 2 instead. That should work.
>
>--Matt M.
>

[Reply or follow-up to this message]

I'm having the same problem.  Have you found a solution yet?

BTW, I even decided that I could settle for Numlock always being off, but I can't 
even get THAT to work.  My BIOS turns it off, but when XP loads it restores the previous 
state of the keyboard.  I've tried setting ALL of the "InitialKeyboardIndicators" 
in the registry to 0 (as described in this thread), but when I log off, XP simply 
replaces those values with whatever value it thinks should be there...  

Has anyone been able to turn Numlock OFF in XP?





On Sunday, July 13, 2003 at 6:24 pm, Pete wrote:
>I have a question about Force 
>NumLock to Behave:

>
>I don't want XP to touch my NumLock state at all.
>
>My Dell Latitude has a BIOS setting to that allows you set set numlock to on for 
>only one docking state, and off for the other. This is useful, because I want NumLock 
>on when docked (using a 101 keyboard), but off when undocked (because on the laptop 
>keyboard, NumLock turns keys U,I,O,P,J,K,L,; into a numeric keypad. Annoying!
>
>So how do I stop XP from overriding the NumLock state at logon?

[Reply or follow-up to this message]

I'm also having this problem as well. I have a thinkpad t20 and for some reason, out of nowhere, this started happening. The thinkpad keyboard doesn't have a numpad section.. it's part of the regular keys. When I press "m", I get "0", "p" I get "*". I've tried everything I could possibly find out about this. "InitialKeyboardIndicators" being changed from "2" to "0" doesn't work because it always goes back to "2" after rebooting. Adding a key to another section as suggested from another site didn't work either. My bios doesn't have anything that helps this either. How is this notepad just decided to turn its numpad on and stay like that?


On Thursday, January 29, 2004 at 7:36 pm, Carter wrote:

>I'm having the same problem.  Have you found a solution yet?
>
>BTW, I even decided that I could settle for Numlock always being off, but I can't 
>even get THAT to work.  My BIOS turns it off, but when XP loads it restores the 
previous 
>state of the keyboard.  I've tried setting ALL of the "InitialKeyboardIndicators" 
>in the registry to 0 (as described in this thread), but when I log off, XP simply 
>replaces those values with whatever value it thinks should be there...  
>
>Has anyone been able to turn Numlock OFF in XP?
>

[Reply or follow-up to this message]

Hmm. I'm experiencing the same problem with a Thinkpad T40. I wonder if it's a Thinkpad-related problem...


On Sunday, February 29, 2004 at 10:54 am, out-there wrote:
>I'm also having this problem as well. I have a thinkpad t20 and for some reason,
>out of nowhere, this started happening.
>
>The thinkpad keyboard doesn't have a numpad section.. it's part of the regular keys.
>When I press "m", I get "0", "p" I get "*". I've tried everything I could possibly
>find out about this.
>
>"InitialKeyboardIndicators" being changed from "2" to "0" doesn't work because it
>always goes back to "2" after rebooting. Adding a key to another section as suggested
>from another site didn't work either. My bios doesn't have anything that helps this
>either. How is this notepad just decided to turn its numpad on and stay like that?
>
>

[Reply or follow-up to this message]

I was poking around in "programs", then "accessories", then "accessibility" and I found "On-Screen Keyboard". I clicked on it and what do I see? A keyboard with "NLK" highlighted! So, I clicked on it and it grays out. Problem solved!! Go figure!!


On Sunday, February 29, 2004 at 1:54 pm, Carter wrote:
>Hmm. I'm experiencing the same problem with a Thinkpad T40. I wonder if it's a
>Thinkpad-related problem...
>
>

[Reply or follow-up to this message]

Yeah, but it only works for the current session. Reboot, and it's back on. It only does what the .vbs script does that M$ publicizes; they suggest you put it in your startup, which I do -- but it comes on *after* it's processed. Running the script after logging in turns it off. Until I reboot again... BTW, I'm running XP on a Dell Latitude. It's not just a Thinkpad problem.


On Sunday, February 29, 2004 at 8:28 pm, out-there wrote:
>I was poking around in "programs", then "accessories", then "accessibility" and I
>found "On-Screen Keyboard". I clicked on it and what do I see? A keyboard with "NLK"
>highlighted! So, I clicked on it and it grays out. Problem solved!! Go figure!!
>
>
>

[Reply or follow-up to this message]

I had the same problem. The numlock would turn on as soon as the Windows wallpaper 
would load. Since I change the wallpaper to the company logo, I knew where to look.

Open regedit.exe and locate

HKEY_Users\.Default\Control Panel\Keyboard\

InitialKeyboardIndicator should = 0 not 2

This works for me, I hope it works for you too.

Good luck,
                Kirk







On Tuesday, April 6, 2004 at 10:23 am, Dan wrote:

>Yeah, but it only works for the current session.  Reboot, and it's back on.  It 
only 

>does what the .vbs script does that M$ publicizes; they suggest you put it in your 

>startup, which I do -- but it comes on *after* it's processed.  Running the script 

>after logging in turns it off.  Until I reboot again...

>

>BTW, I'm running XP on a Dell Latitude.  It's not just  a Thinkpad problem.

>

>

> 

[Reply or follow-up to this message]

On a T20 I tried: HKEY_USERS\.DEFAULT\Control Panel\Keyboard InitialKeyboardIndicators = 0 HKEY_CURRENT_USER\Control Panel\Keyboard InitialKeyboardIndicators = 0 Worked after the reboot too. --- T


On Monday, May 3, 2004 at 11:21 am, Kirk wrote:
>I had the same problem. The numlock would turn on as soon as the Windows wallpaper
>would load. Since I change the wallpaper to the company logo, I knew where to look.
>
>Open regedit.exe and locate
>
>HKEY_Users\.Default\Control Panel\Keyboard\
>
>InitialKeyboardIndicator should = 0 not 2
>
>This works for me, I hope it works for you too.
>
>Good luck,
> Kirk
>
>
>

[Reply or follow-up to this message]

Mine started (always on numlock state) after I plugged in a PS/2 mouse. I have an IBM Thinkpad G40. I just did the = 0 thing since I don't care about the numlock ever being on. That worked for me.


On Sunday, May 9, 2004 at 11:23 am, Thomas Gregory wrote:
>On a T20 I tried:
>HKEY_USERS\.DEFAULT\Control Panel\Keyboard
>InitialKeyboardIndicators = 0
>
>HKEY_CURRENT_USER\Control Panel\Keyboard
>InitialKeyboardIndicators = 0
>
>Worked after the reboot too. --- T
>
>
>
>
>

[Reply or follow-up to this message]

Create a .reg file
Open notepad copy and paste the following
-------------------------under-----------------------
REGEDIT4

[HKEY_CURRENT_USER\Control Panel]

[HKEY_CURRENT_USER\Control Panel\Keyboard]
"InitialKeyboardIndicators" = "0"

----------------------------------------------------above

save file as
whatever.reg
go to the location and run that file





On Tuesday, May 11, 2004 at 9:24 am, Brad wrote:

>

>Mine started (always on numlock state) after I plugged in a PS/2 mouse.  I have 
an 

>IBM Thinkpad G40.  I just did the = 0 thing since I don't care about the numlock 

>ever being on.  That worked for me.

>

>

> 

[Reply or follow-up to this message]

I stumbled across another registry setting that allowed me to disable the numlock 
on startup in XP Pro on our Sony Vaio :

HKEY_USERS\.DEFAULT\Control Panel\Keyboard

I set the "InitialKeyboardIndicators" key to "0"

This worked for me ..... 








On Tuesday, May 25, 2004 at 9:01 am, uidiot wrote:

>Create a .reg file

>Open notepad copy and paste the following

>-------------------------under-----------------------

>REGEDIT4

>

>[HKEY_CURRENT_USER\Control Panel]

>

>[HKEY_CURRENT_USER\Control Panel\Keyboard]

>"InitialKeyboardIndicators" = "0"

>

>----------------------------------------------------above

>

>save file as

>whatever.reg

>go to the location and run that file

> 

[Reply or follow-up to this message]

THANK YOU FOR THIS TIP It fixed my xp home numlk problem, which had stopped me from being able to even use my new laptop. IT happened after attempting to make the program work in a network environment with XP professional.


On Sunday, February 29, 2004 at 8:28 pm, out-there wrote:
>I was poking around in "programs", then "accessories", then "accessibility" and I
>found "On-Screen Keyboard". I clicked on it and what do I see? A keyboard with "NLK"
>highlighted! So, I clicked on it and it grays out. Problem solved!! Go figure!!
>
>
>

[Reply or follow-up to this message]

If you're talking about it switching the NUMLOCK on at the logon prompt, try this. Toggle the NUMLOCK lamp off using the NUMLOCK key. Restart. Next time the machine comes to the logon prompt it's got the NUMLOCK off. My WinXP-Pro machine started turning the NUMLOCK on at boot (and when shutting down - the clue!) after desktop support installed an application that required a LONG registration number be punched in. I suspect they used the NUMLOCK on that priveledged account, the same that's used at the logon prompt?! Changing the NUMLOCK at the prompt and restarting reset it. At least, that's my theory. I'm no big Windoze whiz. Just a determined button pusher :)

[Reply or follow-up to this message]

On IBM Thinkpads, you have to press Shift+Nlk to get rid of the numlock. We have T22s, T23s, T30s, and T41s, here at work, and they are all the same !!


On Sunday, February 29, 2004 at 10:54 am, out-there wrote:
>I'm also having this problem as well. I have a thinkpad t20 and for some reason,
>out of nowhere, this started happening.
>
>The thinkpad keyboard doesn't have a numpad section.. it's part of the regular keys.
>When I press "m", I get "0", "p" I get "*". I've tried everything I could possibly
>find out about this.
>
>"InitialKeyboardIndicators" being changed from "2" to "0" doesn't work because it
>always goes back to "2" after rebooting. Adding a key to another section as suggested
>from another site didn't work either. My bios doesn't have anything that helps this
>either. How is this notepad just decided to turn its numpad on and stay like that?
>
>

[Reply or follow-up to this message]

Did you find a fix for this? Our entire T series does the same despite the numlock status or the registry settings after a suspend happens.

[Reply or follow-up to this message]

Unsure if you are using an external keyboard or docking station, but the IBM laptops 
remember the NumLock status if you have a keyboard plugged in with NumLock enabled 
via the keyboard. Some of our users don't turn on NumLock at all, for fear that they 
will forget to disable it when they have to use the laptop keyboard.

When we received our first batch of laptops, we were fine until our laptop users 
went to travel. Since their first keyboard function was to put their password in, 
which is only visible as a group of asterix, they couldn't see that their letters 
entered on the right hand side of their keyboard were numbers. After we found the 
problem, I had them check by typing their password on the username line to verify 
it was off.







On Sunday, February 29, 2004 at 10:54 am, out-there wrote:

>I'm also having this problem as well. I have a thinkpad t20 and for some reason, 

>out of nowhere, this started happening.

>

>The thinkpad keyboard doesn't have a numpad section.. it's part of the regular keys. 

>When I press "m", I get "0", "p" I get "*". I've tried everything I could possibly 

>find out about this. 

>

>"InitialKeyboardIndicators" being changed from "2" to "0" doesn't work because it 

>always goes back to "2" after rebooting. Adding a key to another section as suggested 

>from another site didn't work either. My bios doesn't have anything that helps this 

>either. How is this notepad just decided to turn its numpad on and stay like that?

>

>
 

[Reply or follow-up to this message]

So does my Dell. I think it's a function of Windows, and not the hardware. As Windows boots, whatever state the machine is in by BIOS setup changes if it was last different for Windows. I don't know how accounts work in Windows XP Pro, but apparently the one the machine boots in is different (a login account?) from the one a user logs in with. If the logged in user has their NUMLOCK ON, it doesn't appear to change the "login account". Just based off my observations. I may be totally out to lunch... Would be nice if Windows noticed there wasn't an external keyboard, and went with the setup used last time it wasn't there. That's why it's an "annoyance". mdr


On Wednesday, February 9, 2005 at 4:55 am, smikwily wrote:
>Unsure if you are using an external keyboard or docking station, but the IBM laptops
>remember the NumLock status if you have a keyboard plugged in with NumLock enabled
>via the keyboard.

[Reply or follow-up to this message]

You need read no further. I have the fix. Instead of messing with all those icky 
registry keys, there is a simpler solution. (prepare to bang head on wall)

to permenently change the NumLock state at startup simply put NumLock in the state 
of preference (On/Off) and then, when you log off, instead of using Start/Log Off,
 Press "Ctrl + Alt + Del", and click on Shut down, and click Log Off from the drop 
down menu. This PERMENANTLY sets the NumLock state at Startup.
(At lest it did on my Dell 3000 w/ XP Home Ed.)
"Ctrl + Alt + Del" the Key Combo of 102 uses :-)








On Sunday, July 13, 2003 at 6:24 pm, Pete wrote:

>I have a question about Force 

>NumLock to Behave:


>

>I don't want XP to touch my NumLock state at all.

>

>My Dell Latitude has a BIOS setting to that allows you set set numlock to on for 

>only one docking state, and off for the other. This is useful, because I want NumLock 

>on when docked (using a 101 keyboard), but off when undocked (because on the laptop 

>keyboard, NumLock turns keys U,I,O,P,J,K,L,; into a numeric keypad. Annoying!

>

>So how do I stop XP from overriding the NumLock state at logon? 

[Reply or follow-up to this message]

After banging my head on the wall many times about this, going through all the suggestions 
posted above didn't help. I checked all the registry "InitialKeyboardIndicators" 
entries were set to "0", I deleted the user profiles from the "Document and Settings" 
so that they are recreated and everything started fresh AND STILL the Numlock came 
on at Logon. 

However, eventually I figured out that I had a group policy buried somewhere in my 
domain controller's Active Directory running a vbs script to turn on the numlock... 
DUH! I forgot I had added this a long time ago to my Active Directory so I just restricted 
the username that logs on to the laptops so that the policy doesn't apply to that 
user. However, I want the other users on regular desktop computers to have Numlock 
on automatically. But for the laptop user, adjusting the group policy properly took 
care of this annoying problem.

I just think this is something to look at in case anyone of you has a domain environment.

[Reply or follow-up to this message]

I had this type of episode this week with an IBM ThinkPad R51, changing the bios setting had no desirable effect, the NUMLK was on at boot and windows logon, however the desired state was attained once a physical change was made to the hardware, in my case docking the laptop had that positive effect and I could not recreate an undesirable one. This took several hours of testing to finally reach this position, and it has happened more than once with this model unit in my workplace, but this is one side of the coin that might be tried.


On Sunday, July 13, 2003 at 6:24 pm, Pete wrote:
>I have a question about Force
>NumLock to Behave:

>
>I don't want XP to touch my NumLock state at all.
>
>My Dell Latitude has a BIOS setting to that allows you set set numlock to on for
>only one docking state, and off for the other. This is useful, because I want NumLock
>on when docked (using a 101 keyboard), but off when undocked (because on the laptop
>keyboard, NumLock turns keys U,I,O,P,J,K,L,; into a numeric keypad. Annoying!
>
>So how do I stop XP from overriding the NumLock state at logon?

[Reply or follow-up to this message]

you can switch off the numKeys by pressing shift NumLk key on the keyboard of your IBM laptops. - Sanjeev Hasiza


On Thursday, April 7, 2005 at 9:44 am, Mario wrote:
>After banging my head on the wall many times about this, going through all the suggestions
>posted above didn't help. I checked all the registry "InitialKeyboardIndicators"
>entries were set to "0", I deleted the user profiles from the "Document and Settings"
>so that they are recreated and everything started fresh AND STILL the Numlock came
>on at Logon.
>
>However, eventually I figured out that I had a group policy buried somewhere in my
>domain controller's Active Directory running a vbs script to turn on the numlock...
>DUH! I forgot I had added this a long time ago to my Active Directory so I just restricted
>the username that logs on to the laptops so that the policy doesn't apply to that
>user. However, I want the other users on regular desktop computers to have Numlock
>on automatically. But for the laptop user, adjusting the group policy properly took
>care of this annoying problem.
>
>I just think this is something to look at in case anyone of you has a domain environment.

[Reply or follow-up to this message]

Falcon's virus/malware cleanup routine

Amazing, a two year thread agonizing over ways to make NumLock behave. Is it really 
so difficult to press the NumLock key if the light is lit and you don't want it? 

I've seen this same discussion in many places but have never understood the rational 
behind it. To each their own I guess :-)

Repair install WinXP  

Clean install WinXP

[Reply or follow-up to this message]

The only place I worry about it is the emulated machine QEMU creates. Unfortunately, when using it, NumLock turns the host's numlock status on and off, not the emulated machine's, and entering the command in QEMU's monitor window to simulate the keypress isn't fun.

My Malware Removal Instructions

Perform the following:

1. Disable System Restore ^*
2. Perform an online virus scan ^{* * * *} .
3. Download, update, and run these tools:
   • Spybot Search & Destroy ^*
   • Lavasoft Adaware ^*
   • CWShredder ^*
   Repeat as necessary until clean.
4. If you still experience problems after doing these steps, download HijackThis ^* and post a log to this forum.
5. To protect against reinfection, download and use these:
   If at all possible, I recommend that you use alternative software, particularly web browsers and email clients:
   • Web Browsers ^{* * *}
   • Email Clients ^{* *}
   If this is not a viable option, or for additional protection, use these:
   • Javacool's SpywareBlaster ^*
   • Javacool's SpywareGuard ^*
   • Malware-blocking HOSTS file ^*
   • IE-SPYAD ^* , Internet Explorer only
6. Optionally Reenable System Restore ^* . Better alternatives to System Restore.

If you encounter any broken links, please inform me of them. Also note that these links direct through my web server to allow me to keep them up-to-date or post additional info. If you are unable to use the links above, click the stars instead, which are a direct link to the page in question.

[Reply or follow-up to this message]

You can try this link to Set or Unset NUM LOCK in Windows: http://www.somacon.com/p339.php There are two freeware utility programs that will force the numlock key to the desired state. If nothing else works for you, then you can configure these to run at logon.

[Reply or follow-up to this message]

Probably because people find this to be nothing more than an annoyance. It appears that this issue is resolved with a previous post. Start the computer up, but DO NOT log on. Toggle the num-lock so that it is OFF. Reboot the computer, and the num-lock should remain off.


On Wednesday, July 20, 2005 at 12:01 pm, Rich Kurtz wrote:
>
>Falcon's virus/malware cleanup routine

>Amazing, a two year thread agonizing over ways to make NumLock behave. Is it really
>so difficult to press the NumLock key if the light is lit and you don't want it?
>
>I've seen this same discussion in many places but have never understood the rational
>behind it. To each their own I guess :-)
>

[Reply or follow-up to this message]

Having this problem on a Dell c600 laptop...

Noticed this:

After logging on as the local admin = Numlock off, everything's cool.

After logging on as domain user/admin = Numlock on, u=4,i=5, etc. DOH!

Logged in as local admin, went to user profiles (control panel, system), copied local 
admin profile to one of the user profiles..

Restart...

Works! Numlock stays off. (Did this in Win2k, but cant imagine WinXP is much different.

[Reply or follow-up to this message]

Ok, I will combine ALL of the posts here into one successful solution.  I tried several 
of the above posts and had moderate success on different occasions.  But recently 
I joined a different domain than usual on my laptop and this NumLock problem cropped 
up again...and now I have the solution.

First the reason:  I beleive one of the previous posts is correct, this is due to 
a domain policy usually.  But, I am not the admin so I can't change that policy for 
my user.  I do not usually log into this domain, so once I disconnected from the 
domain and did the steps below, I was able to resume normal NumLock behavior.

1. - Log on to Windows with your normal user.  Turn off numlock, and use Ctrl-Alt-Del 
and LOGOFF, NOT Shutdown.
2. - Notice now that you are back to the login window and NumLock is ON again.  Turn 
it off and then hit Ctrl-Alt-Del again and choose Restart.

By turning it off in both of these locations and in this order, you can be assured 
that it shouldn't be on anymore.  Doing it in any other order left me with Numlock 
on in just about any combination of the steps above in previous posts.

That said, if you have to log into this domain all the time you will still likely 
have to deal with this NumLock policy even when not connected to a docking station. 
 My suggestion at that point is to learn a little C# or VB.Net programming.  You 
can easily write a service that starts up at the Windows login screen and turns off 
NumLock for you, and then have it run at startup again once windows starts.  This 
service can turn NumLock off for you.  For the non-programmers out there, it may 
not be worth the time to learn, but it'll only take 10 minutes of research to figure 
out how for the programmers.

If you ask me, the domain policy really has no business forcing NumLock ON.  That's 
why the BIOS and Windows have the settings that they do...so the USER can choose!






On Wednesday, September 28, 2005 at 8:47 am, Steve wrote:

>Having this problem on a Dell c600 laptop...

>

>Noticed this:

>

>After logging on as the local admin = Numlock off, everything's cool.

>

>After logging on as domain user/admin = Numlock on, u=4,i=5, etc. DOH!

>

>Logged in as local admin, went to user profiles (control panel, system), copied 
local 

>admin profile to one of the user profiles..

>

>Restart...

>


>Works! Numlock stays off. (Did this in Win2k, but cant imagine WinXP is much different. 

[Reply or follow-up to this message]

Well Done Jay- that works very well. on Asus L1400 Laptop Win XP. BTW: The regedit setting was 0 on the machine and changing it to 2 meant the machine would not boot, (and "2"made no sense!)


On Friday, December 23, 2005 at 6:45 pm, Jay McMunn wrote:
>Ok, I will combine ALL of the posts here into one successful solution. I tried several
>of the above posts and had moderate success on different occasions. But recently
>I joined a different domain than usual on my laptop and this NumLock problem cropped
>up again...and now I have the solution.
>
>First the reason: I beleive one of the previous posts is correct, this is due to
>a domain policy usually. But, I am not the admin so I can't change that policy for
>my user. I do not usually log into this domain, so once I disconnected from the
>domain and did the steps below, I was able to resume normal NumLock behavior.
>
>1. - Log on to Windows with your normal user. Turn off numlock, and use Ctrl-Alt-Del
>and LOGOFF, NOT Shutdown.
>2. - Notice now that you are back to the login window and NumLock is ON again. Turn
>it off and then hit Ctrl-Alt-Del again and choose Restart.
>
>By turning it off in both of these locations and in this order, you can be assured
>that it shouldn't be on anymore. Doing it in any other order left me with Numlock
>on in just about any combination of the steps above in previous posts.
>
>That said, if you have to log into this domain all the time you will still likely
>have to deal with this NumLock policy even when not connected to a docking station.
> My suggestion at that point is to learn a little C# or VB.Net programming. You
>can easily write a service that starts up at the Windows login screen and turns off
>NumLock for you, and then have it run at startup again once windows starts. This
>service can turn NumLock off for you. For the non-programmers out there, it may
>not be worth the time to learn, but it'll only take 10 minutes of research to figure
>out how for the programmers.
>
>If you ask me, the domain policy really has no business forcing NumLock ON. That's
>why the BIOS and Windows have the settings that they do...so the USER can choose!
>
>

[Reply or follow-up to this message]

Accessories/Accessibility solved it for me. I think I developed the NumLock problem when I logged off when connected to my office network through a docking station and then logged on at home (no network, no docking station). I was able to unlock the NumLock by following a tip provided by a reader almost 2 years ago: "On Sunday, February 29, 2004 at 8:28 pm, out-there wrote:
>I was poking around in "programs", then "accessories", then "accessibility" and I
>found "On-Screen Keyboard". I clicked on it and what do I see? A keyboard with "NLK"
>highlighted! So, I clicked on it and it grays out. Problem solved!! Go figure!!" There may be multiple reasons why this lock happens, but this an easy solution for me.

[Reply or follow-up to this message]

Sanjeev, you are my hero. Your sentence just saved me an hour's commute back to work. THANK YOU.


On Wednesday, July 20, 2005 at 10:37 am, Sanjeev Hasiza wrote:
>you can switch off the numKeys by pressing shift NumLk key on the keyboard of your
>IBM laptops.
>
>- Sanjeev Hasiza

[Reply or follow-up to this message]

All of this is a piece o'cake unless you're a laptop user that is constantly docking and undocking. Here's what I want... the BIOS in my DELL is smart enough to detect an external keyboard and turn NUMLOCK on or off based on its presence. I only want an OS to can defer to the BIOS. Is there a Windows setting that says "DON'T SECOND GUESS THE BIOS"? That's all I want... and fries too! Wouldn't it be a shame if Bill resigned from MS because not even he could get the XP folks to figure this out??? Now for y'all who don't think it's a big thing to constantly check and adjust the setting, dink with the registry or write tons o' code to outsmart the OS, just remember that it was a whiner like me that brought you the remote control. So when y'all feel inclined to post, be sure to include the last time you got up an MANUALLY changed the channel on your TV.


On Friday, January 6, 2006 at 4:26 am, e wrote:
>
>
>Sanjeev, you are my hero. Your sentence just saved me an hour's commute back to
>work. THANK YOU.
>
>
>

[Reply or follow-up to this message]

Hi Tom, thank you for help me solving the same problem. Best Irina


On Thursday, December 29, 2005 at 6:01 pm, Tom wrote:
>Accessories/Accessibility solved it for me.
>
>I think I developed the NumLock problem when I logged off when connected to my office
>network through a docking station and then logged on at home (no network, no docking
>station). I was able to unlock the NumLock by following a tip provided by a reader
>almost 2 years ago:
>
>"On Sunday, February 29, 2004 at 8:28 pm, out-there wrote:
>>I was poking around in "programs", then "accessories", then "accessibility" and
>I
>>found "On-Screen Keyboard". I clicked on it and what do I see? A keyboard with "NLK"
>>highlighted! So, I clicked on it and it grays out. Problem solved!! Go figure!!"
>
>
>
>There may be multiple reasons why this lock happens, but this an easy solution for
>me.
>

[Reply or follow-up to this message]

I have the same issue with my Compaq nc6000. With previous OS, such as WinNT, I remember that the Hardware profiles would solve this problem..detect an external keyboard and if it's there, enable NumLock. Since this is a company-issued machine, I have been finding many group policies set that even our 'great' IS guys don't know about (like saved user names for use in programs like Frontpage), I guess I'll have to resign myself to this pain-in-the-...sorry, annoyance. It's not a case of lazyness, it's a frustration that we seem to go backwards in functionality whenever new 'features' are introduced. GIVE ME BACK CONTROL OVER THE BOX!!!


On Sunday, June 18, 2006 at 3:33 pm, Charlotte Irishman wrote:
>All of this is a piece o'cake unless you're a laptop user that is constantly docking
>and undocking. Here's what I want... the BIOS in my DELL is smart enough to detect
>an external keyboard and turn NUMLOCK on or off based on its presence. I only want
>an OS to can defer to the BIOS. Is there a Windows setting that says "DON'T SECOND
>GUESS THE BIOS"? That's all I want... and fries too! Wouldn't it be a shame if
>Bill resigned from MS because not even he could get the XP folks to figure this out???
>
>Now for y'all who don't think it's a big thing to constantly check and adjust the
>setting, dink with the registry or write tons o' code to outsmart the OS, just remember
>that it was a whiner like me that brought you the remote control. So when y'all
>feel inclined to post, be sure to include the last time you got up an MANUALLY changed
>the channel on your TV.
>
>
>

[Reply or follow-up to this message]

To All: See Above (Randy: Wed, Aug 11, 2004, 8:29 am) This was the only solution to my problem. XP Pro on TP T30.


On Sunday, July 2, 2006 at 2:08 pm, irina kotcheva wrote:
>Hi Tom,
>thank you for help me solving the same problem.
>Best
>Irina
>
>
>

[Reply or follow-up to this message]

For novice users do not try to modify your registry or bios. These are extremely dangerous and could result in alot of unexpected consequences. There is a much simpler and less dangerous way to get the num lock to be set at logon. In fact I would suggest expert users use this as well. Just a few easy steps. 1. Turn off machine 2. Start-up machine 3. When Ctrl+Alt+Del prompt comes on make sure num lock is set to desired setting (either on or off) 4. Press Ctrl+Alt+Del 5. Select Options button 6. Turn off Machine Your done. Next time you turn on the machine, right before the Ctrl+Alt+Del prompt comes on the Num lock will go to your desired setting.


On Sunday, July 13, 2003 at 6:24 pm, Pete wrote:
>I have a question about Force
>NumLock to Behave:

>
>I don't want XP to touch my NumLock state at all.
>
>My Dell Latitude has a BIOS setting to that allows you set set numlock to on for
>only one docking state, and off for the other. This is useful, because I want NumLock
>on when docked (using a 101 keyboard), but off when undocked (because on the laptop
>keyboard, NumLock turns keys U,I,O,P,J,K,L,; into a numeric keypad. Annoying!
>
>So how do I stop XP from overriding the NumLock state at logon?

[Reply or follow-up to this message]

What Ctrl+alt+Del prompt? I've never seen one.

[Reply or follow-up to this message]

For added security, you can have the logon require a ctrl+alt+del prior to entering your password. If your computer does not already do this, you can do the following 1. Turn off machine 2. Turn on machine 3. At Logon screen set computer to desired numlock position. 4. Shut down machine You should be done at this point. Next time you turn on your machine this should work.

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum