Strange Num Lock problem

[Guest]

I have an unusual num lock problem with W2K SP4.

In the Administrator account there's no problem, but in my personal account
when ever I log on the num lock turns on. I have read through quite a few num
lock threads and have tried the Reg Edit which is set to 0. When I turn Num
Lock off and restart it doesn't save the setting as it should and always
turns back on when I log on my personal account. Like I said, there is no
problem with the admin account.
There is also no setting in the bios for num lock. (Dell L400 A09 Bios)

Would anyone have any suggestions please?

Regards,
Kevin

 

[Pegasus \(MVP\)]

I have an unusual num lock problem with W2K SP4.

In the Administrator account there's no problem, but in my personal account
when ever I log on the num lock turns on. I have read through quite a few num
lock threads and have tried the Reg Edit which is set to 0. When I turn Num
Lock off and restart it doesn't save the setting as it should and always
turns back on when I log on my personal account. Like I said, there is no
problem with the admin account.
There is also no setting in the bios for num lock. (Dell L400 A09 Bios)

Would anyone have any suggestions please?

Regards,
Kevin

This might help: http://www.jsifaq.com/SF/Tips/Tip.aspx?id=0023
If it does not then a new profile would fix it.

 

[Newbie Coder]

Kleefarr,

Myabe you have a policy changing the setting back when you login

When you say your login. Are you a network user using a roaming profile or a
local user using a limited account?

 

[Guest]

Wireless network. My personal account is local user set up with admin
privileges.

 

[Guest]

Have already checked that Pegasus - "have tried the Reg Edit which is set to 0"

 

[Pegasus]

I was aware that you had checked the registry but since the
average registry contains 10,000 or more entries, it was difficult
to guess what exactly you had done.

Try creating a new profile for yourself.

 

[Guest]

I was aware that you had checked the registry but since the
average registry contains 10,000 or more entries, it was difficult
to guess what exactly you had done.

Try creating a new profile for yourself.

 

[Guest]

Pegasus,

I tried the new profile option and I get the same result, even before I have
set anything up in the new profile.
Strange???

Kevin

 

[Guest]

This is the nly thing that has recently worked for me...

To configure a script to change the NUM LOCK state, use the following steps:
1. Start Notepad.
2. Copy and paste the following data into the text file:set WshShell =
CreateObject("WScript.Shell")
WshShell.SendKeys "{NUMLOCK}"


3. Save the file as Numlock.vbs. This properly creates the file with the
..vbs extension.

NOTE: The icon changes from a Notepad icon to a script icon. If the icon
doesn't change, the file was probably saved as a text file. To change the
icon, rename the file using the .vbs extension.
After you create the script, you can run the script at startup or by using
Group Policy.

Running the Script at Startup
To configure the script to run locally using the Startup folder, copy the
Numlock.vbs file to the user's startup folder that is normally found in the
user's profile path. To configure the script to run for all users, put the
script in the Startup folder in the All Users profile.

The following example shows the default path for this folder:
Documents and Settings\All Users\Start Menu\Programs\Startup

http://support.microsoft.com/kb/262625

Hope this helps someone else.

Kevin