SDK Resources > KVM Application Developers Guide > KVM Topics > Dealing with a Secondary Display

Dealing with a Secondary Display

When the remote platform is configured to use two displays in extended mode, the Intel AMT hardware KVM does not support displaying the mouse in the extended display. The KVM hardware does not know the relative positions of the two displays or which display is primary and which is secondary. The host operating system configures the upper left corner of the two displays as the origin (0, 0) for mouse positioning, independent of which display is the primary or secondary display.

For example, here are three setups of primary and secondary displays:

The origin for all of the above arrangements is the upper left corner. The remote viewer is set to look at only one of the displays. Mouse positioning at the remote viewer are relative to the origin of the local display. If it is set to the display that is not at the origin, mouse movements will be sent relative to the display that is at the origin.

If the remote viewer is set to the secondary display, then, in the first two cases above, mouse movements on the viewer will be translated to positions on the primary display.

If the cursor does not appear on the returned image, switch displays. See Changing Default Screens with the F1 Key.

There is no problem when the displays are in duplicate mode (both displays showing the same image).

When a remote platform is configured to use multiple displays, during a remote assistance session, moving objects in the secondary display screen causes the primary remote display screen to flicker throughout the duration of the object movement. This flickering can be very disruptive to the local operator.  To reduce the flickering impact, disable the Windows option Show window content while dragging.

Copyright © 2006-2013, Intel Corporation. All rights reserved.