I hate logging on to computers in the morning. When I go to log on, the numlock is default off, so in my early morning daze, fantasizing about the coffee brewing in the break room, I type in my password and hit enter, only to find that numlock is off, and I've got to turn it on and do it again.

The idea is a simple driver that reverses the functionality of the numlock key; numlock off, it types numbers, numlock on, it pages up/down, etc. I don't think I've ever once used the numpad for anything other than numbers.
-- CaptainClapper, Oct 20 2009

here http://support.microsoft.com/kb/154529
[FlyingToaster, Oct 20 2009]

You can change the default state of NumLock in your computer's BIOS settings so that it will be on automatically, if that helps.
-- tatterdemalion, Oct 20 2009


apparently XP/etc. ignores the BIOS (cute): <link>
-- FlyingToaster, Oct 20 2009


[tatter] - Can't get into the bios -- it's a government computer

[21] - it is auto-off, every time you log off, then log back on again, i.e. in the morning, it's off again.

[FT] - I'm using XP computers here - I think Vista keeps the numlock on, but I'm not entirely sure.
-- CaptainClapper, Oct 21 2009


Either use the numbers above the letter keys, change your password not to use numbers, or change your password to be the result of typing your old password with numlock off and then submitting.

Add this to a .vbs file and put it into the startup folder (so it runs at startup):

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

[+] anyway :)
-- vincevincevince, Oct 21 2009


Vista does keep it on.
-- nineteenthly, Oct 21 2009


try <link>.
-- FlyingToaster, Oct 21 2009


[vince³] & [FlyingToaster] - I'll use that on my home computer for sure - thank you! I don't think I can put a vb script on these without repercussions... there's some kind of AFI (rule) against creating unofficial programs, and I think that would fall somewhere within those bounds. Really, they just need to pony up for Vista or Windows 7.
-- CaptainClapper, Oct 21 2009


Put a timer on the coffee machine, load it up before you go home, and then come to work to see a freshly brewed cup waiting for you. Drink the coffee, think straight, and remember to put the numbers lock on. Also if that two line 'unofficial program' is banned, then the driver that this whole idea is suggesting is definitely going to be banned. (Unless somehow drivers are allowed, but 'programs' are not...)
-- vincevincevince, Oct 21 2009


[CC]

dude.

the official M$ fix.

To enable NUM LOCK before a user logs on, follow these steps:

1. Run Registry Editor. 2. Move to HKEY_USERS\.Default\Control Panel\Keyboard. 3. Change the value for InitialKeyboardIndicators from 0 to 2.
-- FlyingToaster, Oct 21 2009


Well, if it's a government computer, they are probably not going to allow you to screw with the start-up files, config.sys, or registry - or install a driver, as your idea suggests.

I'm surprised you can't get into the BIOS, since that's a pre-boot function key access. Your government computer shouldn't know it's a government computer at that point.
-- tatterdemalion, Oct 21 2009


Basically, I can't change anything on the computer without repercussions. I could submit a ticket to the Comms Squadron, but they'll probably just spout out TLAs until I don't understand what we're talking about any more, and eventually hang up, wondering what just happened. Buying an auto coffee machine would be faster, and probably more effective.
-- CaptainClapper, Oct 21 2009


The obvious half-baked solution is a device mounted on the side of your keyboard, with a camera and a small robotic arm, that watches your monitor, detects the XP boot screen, and at the right time, uses the arm to depress your numlock key.
-- tatterdemalion, Oct 21 2009


hardware trumps software every time.

As long as it has lots of whirring gears and cogs, and periodically emits steam, I want it.
-- CaptainClapper, Oct 21 2009



random, halfbakery