Now about that "Scroll Lock"

What an interesting question. This has been one of the banes of personal computers since their inception.

But it's a much more complex question than it seems. Non-proprietary keyboards all have their own communication processors that autonomously boot-up to a certain state when power is applied. Another way to ask your question is, "Is there some way to have the host computer ignore or change the asserted state of an attached, generic keyboard?" I'm sure there are other knotty situations, but if a host (I don't mean just an EOS) is malfunctioning, it's not clear that this would be a good idea.

What an interesting question. This has been one of the banes of personal computers since their inception.

But it's a much more complex question than it seems. Non-proprietary keyboards all have their own communication processors that autonomously boot-up to a certain state when power is applied. Another way to ask your question is, "Is there some way to have the host computer ignore or change the asserted state of an attached, generic keyboard?" I'm sure there are other knotty situations, but if a host (I don't mean just an EOS) is malfunctioning, it's not clear that this would be a good idea.

We ARE adding a setup option in the next release that disables the space bar from acting as a Go.  Regardless of the wakeup state of the alpha numeric keyboard, this has been requested for the design team at an RVI or client, who don't need to be pressing Go.

:-)

a

Tim,

On a windows based systems the caps lock, num lock, and scroll lock states are handled by the OS.  In fact, there an option in most windows versions to set the numlock state on startup.

Anne, would that setup option also handle Record, Update, Delete etc in the same way? For the same reasons for those not needing to be pressing Go?

No, actually, we aren't going to take it that far as a setup option..  The rest of that will be handled through security log in, when we implement it.  

Thanks!

a