Published app over dual screens

[07974]

Hi,

I have users who both use the same published app and one can view it over dual screens the other can't, I have changed all settings within Appsrv.ini and wfclient but seem to pull down the settings from somewhere and overqwrite, any ideas.?

Thanks in advance.

 

[aatari]

we have users here with 5 monitors.. I change the following reg key on the servers they connect to and it works fine. Follow the below - it works for me everytime!

- aatari

-------------------------------------------
From: Cláudio Rodrigues

Subject: Re: multiple monitors

View: Complete Thread (4 articles)

Original Format

Newsgroups: microsoft.public.win2000.termserv.clients

Date: 2003-04-18 08:05:05 PST





I have no idea if it is already fixed on Windows 2003 as none of my monitors

can handle such resolutions.

And I have only one monitor so I cannot even try multi-monitor setups.

Although Citrix may allow you to do this, it is still limited on the

resolution, color and number of sessions. This means a certain number

(memory allocated to the client) has a maximum value. What means the more

resolution you have, you will not be able to have as many sessions as you

want in high color for example.

More information:



"Citrix says with there Metaframe for W2k and 'Feature Release 1' upgrade,

you can support 'multiple monitors' and 'greater colour resolution'. in

actuality, the correct word is OR not AND ! Which means it can support 8

screens but only in 2-bit colour mode OR 1 screen at 16 million colours.

The reason is due to the amount of memory that Citrix reserves for the video

memory for the client.



By default, it is exactly 7680000, which is the maximum value the Citrix

utility, "TWConfig", will accept. Now this value is out of 16Mb of total

client session memory space. However, running the minimum 3 monitors for

the traders at 16-bit requires 7,864,320 bytes, which is 184320 more than

the default. So, we asked Citrix why their stuff didn't work. Finally

after almost 2 months of playing email tag, they came back with a Registry

entry change.



Here is what they sent us:



Win2k has a session pool limit of 16MB. The ICA pseudo frame buffer comes

out of this session pool, and the maximum size of the frame buffer is

specified by the registry value:

HKLM\System\Current Control

Set\Control\TerminalServer\Wds\icawd\thin16\MaxLVBMem

The MaxLVBMem value specifies (in bytes) the maximum memory that thinwire

will allocate for the frame buffer.

It can be modified using twconfig.exe; however, twconfig will not let you

specify a value larger than 7680000 bytes.

The remaining 8.4 MB is taken up by other things that we have little or no

control over (e.g. GDI itself, printer drivers, etc.).



Microsoft will not modify the 16 mb session limit before WHISTLER.

Now, what we found out is that this key can be modified to other values. So

when we need to support 4 monitors, we calculated the required memory in

bytes (1280 x 1024 x 2 words (or 16-bit) x 4 monitors) and this equals

10,485,760. So, this was the value we entered into this key. And it

worked. So, keep this in mind."



As I said it may be fixed with Windows 2003 but I could not try. Microsoft,

if they read this post, can shed some light on this.



--

Cláudio Rodrigues, MVP

Windows 2000/NT Server

Terminal Services