[N270 & 945GSE - IEGD 10.0 - XPEmbedded] 2 displays, (1 rotated) - after reboot from a remote desktop session, display resolutions incorrect until after a reboot

[SBout]

N270/945GSE/XP Embeded (POS Ready 2009)

Scenario: User remote-desktops into our device (N270, IEDG 10.0, two displays, one rotated) to perform remote management, and uses windows security to reboot (in the remote desktop session).

The outcome is that after the reboot has completed, the screen resolutions on the login-screen and desktop are lost (in fact, they usually seem to match the resolution of the remote desktop session). This especially affects the second display, of course, because the remote desktop session doesn't have the second display.

This can resolved by rebooting (again) from the desktop (NOT remote desktop), and the configured screen resolutions are returned.

This appears to be a bug in the IEGD 10.0 interraction with remote desktop; we have tried at 10.4 driver and that doesn't show this issue (although it does have other issues and so is currently not a viable option for us to persue).

Is there any patch or configuration that can be applied to resolve this remote desktop issue?

[Kirk_B_Intel]

Remote desktop is not something we overtly test against. That said, it is also not clear if this is a bug in IEGD. Rotation in software is something provided in IEGD with a VERY limited acceptable use case. Rotation is handled by tricking the O/S by giving it a frame buffer that matches the desired rotated resolution, then THAT framebuffer is then re-rendered using the graphics engine to rotate the data for each frame and then that data is shifted out. It is best to avoid using this type of rotations as it causes all sorts of undesirable operation. In very SIMPLE situations it can be made to work, but is not generally recommended because of the compatibility issues and performance degradation that occurs with rotation.

There are also known issues with XP (and XPe) where this scheme will sometimes confuse the Windows manager which ends up only being cleared up with reboots. We definitely update Windows with the new orientation after a change, HOWEVER, Windows does not always recognize it first time out. I think you have found the workaround for this issue with the reboot (or restart). Unfortunately, because the feature is not generally recommended, we are not attempting to enhance the functionality in any way at this time.

My best suggestion would be to either live with the reboots, OR reoirient the rotated screen back to the orientation it was designed to operate in.

Hope this helps. Kirk