Hi,

I have a Windows 2003 server that, under Device Manager displays a
question mark under the Vieo Controller. The Video card within the
server is an ATI Radon X550. If I install the ATI supplied drivers the
installation runs well yet Remote Desktop fails.

If I uninstall the ATI driver, Remote Desktop works yet I get the
question mark. Searching through the internet, it seems that Windows
2003 supplies its own ATI drivers.

Is there a way I can reset this without having to reinstall the entire
server.

Thank You,
Al

Re: Video Controller not found in Windows 2003 by Ivan

Ivan
Sun Oct 14 11:53:07 PDT 2007

If you are running a non PAE, non /3G booted x86 machine,
then, you might try to carefully enlarge the fragment of the session
space used for image mapping, moving it from 8Megs, to 9 or 10 megs.
Don't be creative and try 16 megs first.
Actually, if you cannot get it working with 10 or 12,
I would try a different video card.

By twicking this registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
SessionImageSize = DWORD 0x10

The general theory is the following:
on x86, the session space is statically configured by knonw hard-coded
values
and few overrides from registry.
In the session pace, the portion reserved for image mapping is used by
the display drivers of the system, meaning tsddd.dll, rdpdd.dll, and your
vendor
specific display driver.
ATI is knonw to have HUGE display driver, that are in memory even bigger
than they are on disk, because they use huge zero-initialized data
(AKA, a global array several megabytes big).
If you have etherogenous display drivers, or, for certain configuration
of remote and local display driver, that space may not be sufficient.

If you are running x64/IA64, there are no practical limitation to the
session space.
If you are running /PAE or /3G, then, the system defaults to hard-coded
values,
to preserve functionality.

--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"acb" <chribonn@gmail.com> wrote in message
news:1192379553.651708.127360@t8g2000prg.googlegroups.com...
> Hi,
>
> I have a Windows 2003 server that, under Device Manager displays a
> question mark under the Vieo Controller. The Video card within the
> server is an ATI Radon X550. If I install the ATI supplied drivers the
> installation runs well yet Remote Desktop fails.
>
> If I uninstall the ATI driver, Remote Desktop works yet I get the
> question mark. Searching through the internet, it seems that Windows
> 2003 supplies its own ATI drivers.
>
> Is there a way I can reset this without having to reinstall the entire
> server.
>
> Thank You,
> Al
>



Re: Video Controller not found in Windows 2003 by Tim

Tim
Mon Oct 15 21:15:07 PDT 2007

"Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote:
>
>If you have etherogenous display drivers, or, for certain configuration
>of remote and local display driver, that space may not be sufficient.

Do you mean "heterogeneous"? "Ethergenous" seems like it should be a word,
but it isn't, and I'd hate to have our non-native-English speakers hurt
themselves trying to look it up.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.

Re: Video Controller not found in Windows 2003 by Ivan

Ivan
Mon Oct 15 23:04:20 PDT 2007

Yes, that should have been what you said.
Sorry about that.
I'm a non native speaker myself.

--

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Tim Roberts" <timr@probo.com> wrote in message
news:nge8h39gv9arj5p151grols29vcq4lqtnj@4ax.com...
> "Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote:
>>
>>If you have etherogenous display drivers, or, for certain configuration
>>of remote and local display driver, that space may not be sufficient.
>
> Do you mean "heterogeneous"? "Ethergenous" seems like it should be a
> word,
> but it isn't, and I'd hate to have our non-native-English speakers hurt
> themselves trying to look it up.
> --
> Tim Roberts, timr@probo.com
> Providenza & Boekelheide, Inc.