Display resolution settings

[Larry Waibel]

I didn't find anything about the .bat file there but I did see something about
another problem I've been having. I have an XPe driver from Asiliant for their
90000 display adapter but I haven't been able to get it to do higher than
640x480. I just noticed this in the fbalog.txt and wonder if it's some kind of
clue of where to look next:

10:12:50 AM - [FBAChangeDisplaySettings] Settings: [1024, 768, 32, 75]
10:12:50 AM - [FBAChangeDisplaySettings] Settings not found!
10:12:50 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAChangeDisplaySettings

Where is it looking for the settings that aren't found?

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: .bat file in windows\system32
Date: Thu, 24 Mar 2005 16:10:04 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Yes, that is strange.
Just in case, check out FBALog.txt and search there for any FBA generic command

info or just for your .bat file name.

 

[KM]

Larry,

Please read and try this first: http://msdn.microsoft.com/embedded/community/community/tips/xp/videores/default.aspx

--
Regards,
KM, BSquare Corp.

I didn't find anything about the .bat file there but I did see something about
another problem I've been having. I have an XPe driver from Asiliant for their
90000 display adapter but I haven't been able to get it to do higher than
640x480. I just noticed this in the fbalog.txt and wonder if it's some kind of
clue of where to look next:

10:12:50 AM - [FBAChangeDisplaySettings] Settings: [1024, 768, 32, 75]
10:12:50 AM - [FBAChangeDisplaySettings] Settings not found!
10:12:50 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAChangeDisplaySettings

Where is it looking for the settings that aren't found?

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: .bat file in windows\system32
Date: Thu, 24 Mar 2005 16:10:04 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Yes, that is strange.
Just in case, check out FBALog.txt and search there for any FBA generic command

info or just for your .bat file name.

 

[Richard]

I fought this problem for several days before I figured it out. I made
components and kept trying to build images with no luck.

On my system, the Bios had to be set to share at least 8 megs of ram for the
video. Anything less would only do 640 x 480. Once I changed the bios
settings it worked perfect.

You may have other problems but I wanted to offer that tip since it wasn't
obvious to me at the time.

Richard

I didn't find anything about the .bat file there but I did see something
about
another problem I've been having. I have an XPe driver from Asiliant for
their
90000 display adapter but I haven't been able to get it to do higher than
640x480. I just noticed this in the fbalog.txt and wonder if it's some
kind of
clue of where to look next:

10:12:50 AM - [FBAChangeDisplaySettings] Settings: [1024, 768, 32, 75]
10:12:50 AM - [FBAChangeDisplaySettings] Settings not found!
10:12:50 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAChangeDisplaySettings

Where is it looking for the settings that aren't found?

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: .bat file in windows\system32
Date: Thu, 24 Mar 2005 16:10:04 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Yes, that is strange.
Just in case, check out FBALog.txt and search there for any FBA generic
command

info or just for your .bat file name.

 

[Slobodan Brcin \(eMVP\)]

Lary,

In addition to this article check your GART driver whether it is installed
or not.
http://groups-beta.google.com/group...osoft.public.windowsxp.embedded&q=GART&qt_g=1

Regards,
Slobodan

Larry,

Please read and try this first:
http://msdn.microsoft.com/embedded/community/community/tips/xp/videores/default.aspx

--
Regards,
KM, BSquare Corp.

I didn't find anything about the .bat file there but I did see something
about
another problem I've been having. I have an XPe driver from Asiliant for
their
90000 display adapter but I haven't been able to get it to do higher than
640x480. I just noticed this in the fbalog.txt and wonder if it's some
kind of
clue of where to look next:

10:12:50 AM - [FBAChangeDisplaySettings] Settings: [1024, 768, 32, 75]
10:12:50 AM - [FBAChangeDisplaySettings] Settings not found!
10:12:50 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAChangeDisplaySettings

Where is it looking for the settings that aren't found?

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: .bat file in windows\system32
Date: Thu, 24 Mar 2005 16:10:04 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

Yes, that is strange.
Just in case, check out FBALog.txt and search there for any FBA generic
command

info or just for your .bat file name.

 

[Larry Waibel]

Okay, following what's in that article I found this earlier in the FBA log which seems
like it didn't find the driver (that was supplied by Asiliant for XPe, not one I did
myself):

8:15:07 AM - [FBAAddDevInstanceId] DISPLAY\DEFAULT_MONITOR\4&3AB173B3&0&11223344&01&00
8:15:08 AM - [FBAInstallNullDriver] DISPLAY\DEFAULT_MONITOR\4&3AB173B3&0&11223344&01&00

So to check I added 'Display Control Panel' to my configuration, which just boots to a
command shell. When I try to run 'desk.cpl' it says "The file does not have a program
associated with it...". How do I run a control panel applet? Is there some other
dependency that Display Control Panel didn't bring in? Thanks as always for your help!

 

[KM]

Larry,

You would need to make a few things first:
- As Slobodan and Richard suggested - check your GART driver and BIOS settings
- Run the display driver you use through Dependency Walker to see if any dll is missing from your build
- Open \windows\setupapi.log file and check there if any error related to the display driver or etc.. You can attach the log
here if you are using OE as you newsgroup client
- install the driver at run time with devcon tool to see if it works there. Again, SetupApi.log would have some info on the
errors.

For the "Display Control Panel", unless you include the full administrative control panel support ("Administration Support Tools")
you can add "Control Panel Command Line Support" and start the CPL with control.exe.
Also, you can launch some dialogs from the CPL with rundll32.exe tool.

Btw, I'd recommend you to upgrade the "Display Control Panel" with Hotfix Q824704 if you are on SP1.

--
Regards,
KM, BSquare Corp.

Okay, following what's in that article I found this earlier in the FBA log which seems
like it didn't find the driver (that was supplied by Asiliant for XPe, not one I did
myself):

8:15:07 AM - [FBAAddDevInstanceId] DISPLAY\DEFAULT_MONITOR\4&3AB173B3&0&11223344&01&00
8:15:08 AM - [FBAInstallNullDriver] DISPLAY\DEFAULT_MONITOR\4&3AB173B3&0&11223344&01&00

So to check I added 'Display Control Panel' to my configuration, which just boots to a
command shell. When I try to run 'desk.cpl' it says "The file does not have a program
associated with it...". How do I run a control panel applet? Is there some other
dependency that Display Control Panel didn't bring in? Thanks as always for your help!

 

[Larry Waibel]

Thanks! What I've finally determined is that the driver is more capable than the way the
chip is implemented on our board in that I can choose higher settings that won't work. The
best I can get is 1024x768, 16bit color, 60Hz refresh.

Even with the 'Control Panel Command Line Support', it reports that rundll32.exe doesn't
have an association.

From: "KM" <konstmor@nospam_yahoo.com>
Subject: Re: Display resolution settings
Date: Fri, 25 Mar 2005 11:02:17 -0800
Newsgroups: microsoft.public.windowsxp.embedded

Larry,

You would need to make a few things first:
- As Slobodan and Richard suggested - check your GART driver and BIOS settings
- Run the display driver you use through Dependency Walker to see if any dll is missing from your build
- Open \windows\setupapi.log file and check there if any error related to the display

driver or etc.. You can attach the log

here if you are using OE as you newsgroup client
- install the driver at run time with devcon tool to see if it works there. Again,

SetupApi.log would have some info on the

errors.

For the "Display Control Panel", unless you include the full administrative control panel

support ("Administration Support Tools")