Tom Warren said to All in the Fido OS2 Programming conference on
03-16-1996:

TW> Hi, I run OS2/WARP at the shop and as I understand it has a bug in
TW> it where it changes the state of your numlock key. 

I'm not sure that IBM considers it a bug -- they seem to think we're
all nostalgic for the old 84-key keyboard.  As one who believes there
should never have been a need for a numlock key in the first place,
though, I agree with you.

TW> I understand I can use a small batch file called "numlock"
...
TW> Right not I have the command in the OS{at} autoexec.bat and it
TW> doesn't seem to keep the numlock on all of the time.

Does it work for DOS sessions?  AUTOEXEC.BAT affects only DOS
sessions, not OS/2 sessions.  I use a utility called WILLUTIL, which
puts programs in both AUTOEXEC.BAT for DOS sessions and STARTUP.CMD for
OS/2 sessions that let you turn on numlock and keep it on.  It works
mostly.

BTW, IBM has promised that Merlin will include the option to turn on
numlock and keep it on.

    -Jerry

---
 þ KWQ/2 1.2i þ El toro loco: the crazy lawnmower.