G
Guest
W2K and XP both do their own things with regard to NumLock, regardless of
what a user may have set up in their machine's BIOS. Specifically, the state
of NumLock when starting will be the same as when the profile last shutdown,
and there is no provision for discerning whether a laptop happens to be
docked or not.
This is terribly annoying to laptop users who frequently change from docked
to undocked -- no undocked small-keyboard laptop should ever start with
NumLock on. But it is natural to expect a full-sized keyboard to have its
NumLock on.
Many thoughtful manufacturers have recognized this problem and have created
BIOS settings that permit different NumLock conditions for docked and
undocked.
But all this benefit was destroyed when Microsoft "improved" things with the
persistent state disease.
Has Vista returned this choice to the user? Or are we still stuck with the
"eternal wisdom" of some non-laptop user who was responsible for that part of
Windows?
what a user may have set up in their machine's BIOS. Specifically, the state
of NumLock when starting will be the same as when the profile last shutdown,
and there is no provision for discerning whether a laptop happens to be
docked or not.
This is terribly annoying to laptop users who frequently change from docked
to undocked -- no undocked small-keyboard laptop should ever start with
NumLock on. But it is natural to expect a full-sized keyboard to have its
NumLock on.
Many thoughtful manufacturers have recognized this problem and have created
BIOS settings that permit different NumLock conditions for docked and
undocked.
But all this benefit was destroyed when Microsoft "improved" things with the
persistent state disease.
Has Vista returned this choice to the user? Or are we still stuck with the
"eternal wisdom" of some non-laptop user who was responsible for that part of
Windows?