NVidia Drivers & Dual Display Support

[Brian M. Amira]

So on to the next step...

With the help of various XPe community members, I now have NVIDIA drivers
v61.77 working in XPe. The next phase of my project is to figure out how to
make dual displays work. I am using dual-headed video cards and need to
enable what NVIDIA refers to as "Dual View" support. Both monitors will run
at 800x600. I need both monitors to display different images, no "cloning"
allowed. I can support either a "spanned" desktop or true multi display.

I have gotten this working by manually setting this up in the display
control panel and the NVIDIA driver options after I boot to a windows
desktop. What I am trying to avoid is any post FBA configuration. I am
looking for a solution to configuring all of this in target designer and/or
component manager.

Any ideas of this one gang?

Thanks!
--Brian

 

[KM]

Brian,

If you were able to do the required changes manually, how about monitoring these changes and just include the related reg.entries in
to your image upfront? use Regomn or Inctrl5/RegSnap tools to capture the reg.entries that are changed.

Also, there might be an appropriate option in the driver INF file(s). Don't have it here right now to check but you can do that by
yourself. More information on what to search for you can get if you monitor the registry change first with a tool like Regmon.

KM

 

[Slobodan Brcin \(eMVP\)]

Brian,

If you have some programming experience then go with:
ChangeDisplaySettingsEx
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/devcons_3tfc.asp

It is more universal and work perfectly with both ATI, and NVIDIA cards. I'm using spanned desktop option since drivers and hardware
at that time did not allowed me to use true multi display mode on one card.

Best regards,
Slobodan

 

[Brian M. Amira]

Unfortunately I am not a programmer, but a Network Systems Architect. I have
programmers working on this project but they do not have time to handle this
portion. I need to get the portion of the project completed in about 1 month
or less and am currently taxing my knowledge of XPe. With that said, I am
willing to pay someone for engineering services. I am looking for someone to
engineer the complete display portion of this build, as well as provide
assistance with random issues that popup. If you are interested, please
e-mail be directly at (e-mail address removed). Anyone who is interested should
feel free to contact me, but please be prepared to provide atleast a basic
list of your qualifications.

Thank you,
--Brian M. Amira

 

[James Beau Cseri]

I was able to create a video driver component for a Matrox adapter with dual
monitor support and was able to put in all of the settings I wanted in the
component using registry resources. I needed both LCD monitors enabled for
desktop spanning at 1024x768. I took a snap shot of everything under the
CurrentControlSet before the driver was installed. I then exectued the the
driver installation/configuration program, which stepped me through the dual
monitor configuration setup. Afterwards, I took another registry snap shot
of CurrentControlSet, extracted the differences with the pre-driver
installation snap shot, and put those registry entries into the component
definition (to help save typing, I put the registry diffs into a .REG file,
saved as Unicode, and imported the file into Component Designer).

 

[Slobodan Brcin \(eMVP\)]

Hi James,

Yup that can work all right, but then Konstantins suggestion of putting these values in inf file is better solution.
Since I guess that changes are in CurrentControlSet\Enum branch, which might be different if he choose different video adapter
revision.

Best regards,
Slobodan

 

[James Beau Cseri]

Sure sounds like it. At the time I did my component, I did it the way I did
because I didn't know exactly how to manipulate the INF file.

 

[Slobodan Brcin \(eMVP\)]

Hi James,

This page is only what you need to modify registry parameters.
http://msdn.microsoft.com/library/d..._950895d3-7881-4470-9be1-2a02aae2ef6d.xml.asp

Please note HKR (Relative root) which among other things can represent PnP position in registry associated with each installed
device driver instance.
Only other way that I know to obtain this registry position is from either driver or SetupApi functions.

Regards,
Slobodan

 

[James Beau Cseri]

Very useful info. Thanks Slobodan!

Hi James,

This page is only what you need to modify registry parameters.
http://msdn.microsoft.com/library/d..._950895d3-7881-4470-9be1-2a02aae2ef6d.xml.asp

Please note HKR (Relative root) which among other things can represent PnP
position in registry associated with each installed
device driver instance.
Only other way that I know to obtain this registry position is from either
driver or SetupApi functions.

Regards,
Slobodan

 

[KM]

Just to add a couple more related and useful links to that:

http://msdn.microsoft.com/library/d..._6f269b4d-a715-4117-8ff3-5d9590dfd2c3.xml.asp

http://msdn.microsoft.com/library/d..._8f5ef1c3-94c3-48d5-8f9a-301b7f453cef.xml.asp
(posted by Slobodan a while ago, contains brief but useful info)