Ok, found a workaround - only 64 bit mstsc crashes when it remote
controls or gets remote controlled (from) a *freerdp session - so I
force mstsc into its 32 bit mode using the method described in comment 4
on
http://www.davidmoore.info/2009/12/02/running-32-bit-remote-desktop-conn
Tried wfreerdp to remote control a xfreerdp session - this works fine
right until the resolution of the to be controlled session is higher
than the controlling session, resizing was discussed in April 2011
(http://sourceforge.net/mailarchive/forum.php?thread_name=BANLkTinQjLopm
First strange thing: -a 16 results in 16 bit color depth session, -a
24 creates 16 bit session, too (why?) --a 32 creates a 32 bit session
(all against 2008 R2 SP1 server, xfreerdp git clone).
Second strange thing: Session created with-a 16 or -a 24 can be remote
controlled from Windows XP,