Can't Change Screen Resolution

[Bob Spidell]

Hello to All,

I'm an experienced software developer but new to XPE and this group. I'm
hoping one of you gurus can help me out.

Target:
Gigabyte 8-TRS300M with ATi Radeon 9100 Chipset with integrated grapics
512 MB RAM
Compact Flash

After a steep learning curve, I'm able to build a running system but am
unable to change screen resolution from the
(apparent default) of 640X480 (VGA). This graphics core supports about
1200X1024/32bits but I'd be happy
with 1280X768. I've dowloaded the graphics driver and control panel app
from ATi ... they seem to install except for the
error "No GUID on Video Section" when installing the graphics support.

Anyone know how to get screen resolution to change? The ATi control panel
put an icon on the screen but when I click
on it the CF "disk" light thrashes for a bit but nothing else happens.

Regards,
Bob

 

[KM]

Bob,

Are you "installing" a new ATi driver or you integrating it in to the image (importing .INF and etc.)?
Read this tip: http://msdn.microsoft.com/embedded/community/tips/xp/videores/default.aspx
How do you change the screen resolution?
At any point, you may try to use ChangeDisplaySettings[Ex] API.

 

[Guest]

So far, I'm just installing the ATi driver and apps after FBA runs. Haven't mastered Component Designer enough to be a able to include a graphics driver/control panel (was hoping for a quick-and-dirty solution, not having much experience with XPE).



bs

 

[Guest]

Further, my graphics core (ATi Radeon) doesn't show up in the Component list from a TAP import. It appears to be too new to be supported by the "canned" graphics drivers.

 

[KM]

Bob,

You won't need my expertise to componentize the driver. You will just need to unpack the install package, import INF file, create
SLD component and import it in XPE database. This may help:
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconTutorialBuildingRun-timeImage.asp.

Another thing you can do is just copy the driver's files to an appropriate directories (windows\Inf, \system32\driver, etc.) in
pre-FBA image and let FBA PnP do the job.

If you do that on post-FBA image and you see problems, check %Systemroot%\SetupApi.log file for display related errors.

Also, you haven't mentioned how you change the resolution. Control Panel/Display applet, the API, or ATi application agent?

--
KM,
BSquare Corporation

So far, I'm just installing the ATi driver and apps after FBA runs. Haven't mastered Component Designer enough to be a able to

include a graphics driver/control panel (was hoping for a quick-and-dirty solution, not having much experience with XPE).

 

[KM]

Bob,

Are you sure? "ATI RADEON" (5.13.01.3120 (ReleasedBinaries.010715-1631)) is in XPe database.

In case you need a new version of the driver, you better create a new component - either import .INF or just create a simple
component that copies all the files to appropriate directories).

--
KM,
BSquare Corporation

Further, my graphics core (ATi Radeon) doesn't show up in the Component list from a TAP import. It appears to be too new to be

supported by the "canned" graphics drivers.

 

[Guest]

OK, found it (I was looking for a specific model number--9100--before). Maybe this will work ... building.

 

[Guest]

Well, that didn't work either. Came up in VGA and stayed there ... no way to change res post-boot. No errors from FBA, either. Trying another ATi driver, but this is starting to not make sense ...

 

[KM]

Bob,

When you included the driver and saw it in the Configuration, have you changed the component's display settings (click on the
component's Setting node in the tree and change the display setting on the right panel).

In the FBA log, do you see [FBAChangeDisplaySettings] lines?

--
KM,
BSquare Corporation

Well, that didn't work either. Came up in VGA and stayed there ... no way to change res post-boot. No errors from FBA, either.

Trying another ATi driver, but this is starting to not make sense ...

 

[Guest]

Yeah, I've chaged the Settings to 1024X768, which the adapter can certainly support. Doing a build now ... I'll check the log and get back to you. BTW, thanks for the help

 

[KM]

Bob,

When you included the driver and saw it in the Configuration, have you changed the component's display settings (in TD click on the
component's Settings node in the configuration tree and change the display setting on the right panel).

In the FBA log, do you see [FBAChangeDisplaySettings] lines?

--
KM,
BSquare Corporation

Well, that didn't work either. Came up in VGA and stayed there ... no way to change res post-boot. No errors from FBA, either.

Trying another ATi driver, but this is starting to not make sense ...

 

[Guest]

Success! Well, not exactly what I expected, but by including the Control Panel component I was able to set a higher resolution ... default settings still didn't work, though.

Yes, I got the "settings not found" message from FBA, but the adapter and monitor both certainly support XGA and 60Hz ... any idea what I'm missing?

 

[KM]

E.g., "PnP (User-mode)" component.

Now you are ready to read this: http://msdn.microsoft.com/embedded/community/tips/xp/videores/default.aspx

--
KM,
BSquare Corporation

Success! Well, not exactly what I expected, but by including the Control Panel component I was able to set a higher resolution

.... default settings still didn't work, though.

Yes, I got the "settings not found" message from FBA, but the adapter and monitor both certainly support XGA and 60Hz ... any idea

what I'm missing?

 

[Guest]

Practically have it memorized ;

Anyway, with the Radeon DDR driver installed I was able to get the ATi control panel to work ... so I can set whatever res I want. Before, I got "No GUID on Video Section" which I attribute to not having all the PnP components installed

Still didn't get the default settings to take and, yes, I changed visibility to confirm I had all the components according to that FAQ

Thanks again for the help

bs

 

[KM]

Bob,

If you followed the tip and made sure to get required PnP component, and if
you sure the adapter and monitor support the mode you set, the I don't know
what could be the cause of the error.

You have options, though:
1. Check you FBALog.txt and SetupAPI.log file to see any error related
to the problem,
2. You can remotely connect KD to the target device to see if anything
suspicious happens during FBA,
3. You may end up launching your own small app that calls to
ChangeDisplaySettings API to change the display settings.

KM

Practically have it memorized

Anyway, with the Radeon DDR driver installed I was able to get the ATi

control panel to work ... so I can set whatever res I want. Before, I got
"No GUID on Video Section" which I attribute to not having all the PnP
components installed.

Still didn't get the default settings to take and, yes, I changed

visibility to confirm I had all the components according to that FAQ.

 

[Slobodan Brcin \(eMVP\)]

Hi do all the things Konstantin already said.
Also you should add component "Device: Display"

Remove all other display related components.
Copy files manually to your image folders (You can make component that will
do this).

Check setupapi.log for info about missing files. If driver is installed it
will be around phase 3000.

Device: Display will change settings at phase 6100. If your driver is
working but this component is not then you can rise phase above 8500 so
after the first restart resolution will change. (I never had any need to
change this).

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Practically have it memorized

Anyway, with the Radeon DDR driver installed I was able to get the ATi

control panel to work ... so I can set whatever res I want. Before, I got
"No GUID on Video Section" which I attribute to not having all the PnP
components installed.

Still didn't get the default settings to take and, yes, I changed

visibility to confirm I had all the components according to that FAQ.