video settings from a custom shell using minlogon

[Guest]

Hi.

I have a XPe build that uses a custom shell and minlogon. I am using an
nVidia Quadro FX 560 card and I need to be able to set the video properties
of this device. I have created a component for the 560 using an *.inf from a
97.* revision of the unified driver, but I'm not entirely sure it worked.
After FBA, the resolution is never what I set it to in target designer.
Device manager also indicates it's a generic device, but I'm not sure what I
could be doing wrong.

I've also tried to using the win32 API function ChangeDisplaySettingsEx, but
this only works if I've already called explorer.exe from a command prompt.
Does anyone know if explorer.exe does any initialization to enable this
function?

On top of that I need to be able to set antialiasing and anisotropic
filtering, but due to customer requirements I cannot have the nVidia control
panel included in my image to set these properties. Does anyone know how I
can fix this?

 

[Mike Warren]

Hi.

I have a XPe build that uses a custom shell and minlogon. I am using
an nVidia Quadro FX 560 card and I need to be able to set the video
properties of this device. I have created a component for the 560
using an *.inf from a 97.* revision of the unified driver, but I'm
not entirely sure it worked. After FBA, the resolution is never what
I set it to in target designer. Device manager also indicates it's a
generic device, but I'm not sure what I could be doing wrong.

I've also tried to using the win32 API function
ChangeDisplaySettingsEx, but this only works if I've already called
explorer.exe from a command prompt. Does anyone know if explorer.exe
does any initialization to enable this function?

On top of that I need to be able to set antialiasing and anisotropic
filtering, but due to customer requirements I cannot have the nVidia
control panel included in my image to set these properties. Does
anyone know how I can fix this?

I've been told that this information is undocumented and different for
each card type.

The way I would solve this sort of problem is to include the control
panel and delete the files after it was set up.

Also, make sure you include the help files for the driver. A lot of
video drivers don't work if the help files are not included.

 

[MrJodie]

Sean, you said that the driver is from '97? There's no way that's
going to register the component into Device Manager correctly. You'll
need to find a driver for, at the very least, Windows 2000 and then
create the component from the .INF. The main problem is that the
Windows directory tree changed so it's putting the catalog files for
the component in a completely different place. Does that make sense?

The other reason the resolution won't load with the device is that
once it loads as an unknown it will automatically set to your default
resolution. You may need to change that. However, if it's a
resolution that isn't recognized as being available on the device, it
will revert to the standard resolution again.

I hope that helps.

Jodie

 

[Guest]

No, this is not a driver from 1997. It is a 97.* revision of the nVidia
driver for Windows XP, which is the latest version for this piece of hardware.