I have a question about Force NumLock to Behave:

Is there a way to have NumLock status change on a per user basis? My wife and I have different profiles on a Win98SE machine, and I use NumLock 100% of the time, and she uses it 0%. Is there a utility, batch file, or magic spell to get Numlock to go to a certain state, either on or off? I could then drop it in Startup in each of our profiles and be done with it. TIA Roger

[Reply or follow-up to this message]

Sorry, but NumLock is a setting in BIOS, not in Windows, so a .bat file won't fix it.

[Reply or follow-up to this message]

well, it can be done with config.sys (numlock=on/off) but that won't be on a per-user basis.

interestingly enough, this can be done with a simple registry edit in nt/2000.

currently searching for a utility (you could do the same if you're so inclined ;).

[Reply or follow-up to this message]

should do: lock numlock.

edit the ini per someone's liking, then place a shortcut to the executable in the startup folder of that user.

[Reply or follow-up to this message]

change the bios setting to be the opposite of the program's setting.

[Reply or follow-up to this message]

Excellent - if it works as per the Readme, it's exactly what I was looking for. I'll post back when I try it at home. I did a Google search but this didn't come up. BTW, there is a utility on the MS website (.vbs) that's a simple toggle. It's close to what I needed, but I'm hoping the one you provided is right on. RY


On Monday, October 22, 2001 at 11:03 pm, amaralliya e. thenardier wrote:
>should do: lock numlock.
>

>edit the ini per someone's liking, then place a shortcut to the executable in the
>startup folder of that user.

[Reply or follow-up to this message]

Roger,

If you want to turn Numlock off when your wife uses the system I would recommend 
doing the following.
1. Open notepad and type the following into a new doc.

set WshShell = CreateObject("WScript.Shell")
WshShell.SendKeys "{NUMLOCK}" 

2. Save this file as NUMLOCK.VBS
3. Copy this file into the startup group for your wife's profile so it gets executed 
ONLY when she logs on.
4. Verify the BIOS is set to turn the Numlock on when booting.

Now, when the computer is booted up Numlock will be on and you can log in with it 
on.  If you wife logs onto the computer the NUMLOCK.VBS file will be executed which 
will toggle the state of the numlock key therefore turning it off.

Problem solved and both of you are happy.

[Reply or follow-up to this message]

If you have two user profiles, you can alter a setting in the registry, unique for you and your wife. Under HKEY_CURRENT_USER/Control panel/Keyboard you should have a string value called "InitialKeyboardIndicators". If not, create it. Then, to set the Num Lock to On, edit the value, and set it to "2". This will do the trick. If yuor wife logs in, and her NumLock happens to be on, just edit the data while she's logged in, and set it to "0". These setting will never collide, and mess it up for eachother. Cheers /z


On Monday, October 22, 2001 at 11:42 am, Roger wrote:
>I have a question about Force
>NumLock to Behave:

>
>Is there a way to have NumLock status change on a per user basis? My wife and I
>have different profiles on a Win98SE machine, and I use NumLock 100% of the time,
>and she uses it 0%. Is there a utility, batch file, or magic spell to get Numlock
>to go to a certain state, either on or off? I could then drop it in Startup in each
>of our profiles and be done with it.
>
>TIA
>Roger

[Reply or follow-up to this message]

YOUR WRONG EINSTEIN... IT CAN BE SET IN OTHERWAYS THAN BIOS.......DUMBASS


On Monday, October 22, 2001 at 4:29 pm, Dave357 wrote:
>Sorry, but NumLock is a setting in BIOS, not in Windows, so a .bat file won't fix
>it.

[Reply or follow-up to this message]

create a *.vbs file and edit it and put in the following XP only set WshShell = CreateObject("WScript.Shell") WshShell.SendKeys "{NUMLOCK}"


On Tuesday, November 12, 2002 at 7:21 pm, RAINMAN wrote:
>
>
>YOUR WRONG EINSTEIN... IT CAN BE SET IN OTHERWAYS THAN BIOS.......DUMBASS
>

[Reply or follow-up to this message]

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

• Report abuse of the forum