DE> Every time OS/2 Boots, it turns off the numlock. I like the
 DE> numlock on but I hate turning it on for each session.

 DE> Is there something I can tweak in the config.sys or somewhre
 DE> that will leave the numlock ON?

You are questioning IBM's opinion that your NUMLOCK should be off?

No, there's nothing in OS/2 to tweak for it; but there are some
TSR utilities about that do a pretty good job of it.  What I use
is from the WILLUTIL package of OS/2 utilities by Will E. Rose,
1218 Leith Ave., Waukegan, IL  60085

I've been using it for three or four years, so don't know if that
address is still good.  I think I got the shareware version from
MUST HAVE software archives, but you may have to search around.

Here's a bit from the docs:

  Numlockd.exe controls the NUMLOCK key in the PM session.  This
  includes all PM applications, and all windowed OS/2 VIO applica-
  tions.  It will not interfere with windowed DOS sessions, or
  seamless WINOS2 sessions.  NUMLOCK control for full-screen OS/2
  sessions is provided by WILLUTIL.EXE.  NUMLOCK control for DOS
  and WINOS2 sessions is provided by NUMLOCK.EXE.

  Numlockd.exe is the next generation of NUMLOCK technology.  The
  problem with previous implementations of NUMLOCK control stems
  from the way OS/2 handles virtual keyboards.  When switching
  between full-screen sessions and PM, the NUMLOCK key may loose
  synchronization in the PM session.  Numlockd overcomes this
  problem.

  What Numlockd does is to watch the PM keyboard for activity on
  the NUMLOCK key.  If anything (An application, the Session Man-
  ager, or the user's finger) tries to turn the NUMLOCK key off,
  Numlockd turns it back on.  (If you like to play tag with your
  computer, repetedly hit the NUMLOCK key and watch Numlockd turn
  it back on.)

  Once it's started, you can completely ignore it.  It uses only
  6KB or RAM, and it runs at a special priority to ensure compat-
  ibility with screensavers, as well as those pesky seamless-
  windows sessions with idle-detection disabled.

  When used in conjunction with WILLUTIL.EXE for OS/2 and
  NUMLOCK.EXE for DOS, Numlockd will keep your NUMLOCK key on all
  the time, come hell or high water.

Shows that the problem is a bit more complex than one would expect,
doesn't it?

Jack P.

 
~~~ Blue Wave/QuickBBS
500/3