Skip to main content

Hi All

i am moving a group of users from a Terminal Server (MTS) environment to a Citrix (Xenapp) one.  We have an application that runs under Rumba 9.2 (7.4 in MTS).   I am not very familiar with Rumba and wondered if someone can help me please.  

The display size defaults to 24 x 80 in both environments however in MTS when a user runs something that requires 27 x 132 the screen changes automatically to accomodate the larger display size required.   In the Citrix it doesn't do that.   i have tried everything to change it for me and save it as a session but it is not working.   Since it does it automatically in MTS there must be a setting or something somewhere I can adjust to make it happen automatically in Citrix.  I can't find anything.   Hoping someone can help please.

Thanks

Sandra


#Rumba

Hi All

i am moving a group of users from a Terminal Server (MTS) environment to a Citrix (Xenapp) one.  We have an application that runs under Rumba 9.2 (7.4 in MTS).   I am not very familiar with Rumba and wondered if someone can help me please.  

The display size defaults to 24 x 80 in both environments however in MTS when a user runs something that requires 27 x 132 the screen changes automatically to accomodate the larger display size required.   In the Citrix it doesn't do that.   i have tried everything to change it for me and save it as a session but it is not working.   Since it does it automatically in MTS there must be a setting or something somewhere I can adjust to make it happen automatically in Citrix.  I can't find anything.   Hoping someone can help please.

Thanks

Sandra


#Rumba

Hi Sandra,

Have you set an alternate screen? Under "Options" | "Display Options", click on the "Advanced" tab. Select "Term1" in the "Terminal Type" list. Uncheck the "Host Select" checkbox, set the "Primary Screen" to "Mod2 -- 24x80". Next set the "Secondary Screen" to "Mod5 - 27x132". You may or may not need the "Support Graphics" checkbox enabled. Next click "OK" then save your session profile. Restart it and hopefully that should do the trick.

If the above fails to resolve then issue you should open a support incident so we can examine the host datastream to see what is going on.

Terms & ConditionsAccessibility statement