Thanks, that was it. I believe I may have set this at the start of my eval period when looking for a way to revive monitors which had gone dark because of a timeout in power settings. Unlike moving or clicking the local mouse, similar actions on the Primary do not make the screen contents appear.
I did not notice this issue until upgrading to Pro build 00090 from the evaluation version, but it may have been there. When using a secondary KVM machine when it is NOT under the control of another machine, a second mouse cursor is present under the local mouse cursor. When moving the mouse cursor, the ghost cursor follows it, but with a time-lag of about one second. This is extremely distracting. expecially when trying to move the mouse cursor accurately