FBA PNP not finding device

[DPM]

I've got an interesting problem: MB with VIA Northbridge, S3G IGP. TAP
finds it's PNP ID as "PCI\VEN_1106&DEV_3230", and that's what's in the
inf file. So I imported the inf and added the component. But when FBA
runs, I never see the above PNP ID listed in the log.

Why would TAP find it and FBA not?

Any help gratefully received!

Thanks,
Dean

 

[KM]

Dean,

How did you run TAP? Was it on XP Pro install on the device or under WinPE?
If the first, the device might have been discovered and set up there manually or by dedicated installer.

It is still weird though that the PnP device doesn't get at least discovered by FBA PnP. Did you check SetupAPI.log on the device
after FBA completes?
Also, what happens if you, after FBA, manually at run time launch command like "devcon rescan"? (grab devcon from MS Support website
first). Does it discover new devices? Check SetupAPI.log here as well.

There was also a nice tool in NT/XP Resource Kit - PnpEnum. I can't seem to find where to download it from now. It would help you to
analyze PnP registry data.

 

[DPM]

KM,

Thanks for the setupapi.log tip: in it I found that the driver was not
installing because the inf was trying to copy help files. Modifying it not
to do so solved that problem.

But the effective problem still remains: the component allows me to set
default screen settings, and FBA (in the log) declares that these settings
cannot be found.

How does the component communicate those settings? Would you expect
registry keys? What does FBA mean when it declares that the settings
"cannot be found"?

Regards,
Dean

 

[KM]

Dean,

With the same setupapi.log you can find out if your video driver was installed properly. If it didn't, window backed up to standard
VGA driver that might not support the display settings you set up in TD.

Also, check if you got "PNP (User-mode)" component in your image config. (this component often is left out an XPe image)
Monitor component is also a thing to check in your image.

These and other relevant tips you can find on this page: http://msdn2.microsoft.com/en-us/embedded/aa731224.aspx

 

[DPM]

KM,

Thanks for the tips. Despite all I've tried, FBA still reports:
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings: [800, 600, 32, 60]·
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings not found!·

Now, here's what I know:
1. The driver is installed successfully; it's reported as successful in
setupapi.log, and if I run DeviceManager at runtime the display adapter is
shown correctly;
2. Nowhere in FBALOG.TXT does the PnP ID of the display adapter appear; it
only appears in setupapi.log, which I think is odd but may not matter;
3. All required PnP components are included in the build: PnP kernel mode,
PnP User mode and FBA: PnP;
4. I'm using the Default Monitor component;
5. If I run the desktop control panel at runtime I can manually change the
settings to 800, 600, 32, 60 with no trouble. Unfortunately, in my
application there is no access to the control panel, and I really don't want
to provide a hack and require that my production personnel manually change
the settings on each box.

I'm stuck. Do you have any other wisdom or suggestions?

I appreciate your help.

Thanks,
Dean

 

[KM]

Dean,

That's weird that it fails to set the right resolution when the right driver has been installed properly. Perhaps another bug of FBA
(you may want to report this to Microsoft through the product feedback alias page).

At this point I can only recommend to add some code to your application to "manually" change the resolution at the first launch. You
can certainly create more complex logic in the app to read the default display settings off the registry or INI file. But then you
should call the ChangeDisplaySettingsEx API (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/devcons_3tfc.asp).
The API call should work if the resolution is supported.

--
=========
Regards,
KM

KM,

Thanks for the tips. Despite all I've tried, FBA still reports:
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings: [800, 600, 32, 60]·
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings not found!·

Now, here's what I know:
1. The driver is installed successfully; it's reported as successful in setupapi.log, and if I run DeviceManager at runtime the
display adapter is shown correctly;
2. Nowhere in FBALOG.TXT does the PnP ID of the display adapter appear; it only appears in setupapi.log, which I think is odd but
may not matter;
3. All required PnP components are included in the build: PnP kernel mode, PnP User mode and FBA: PnP;
4. I'm using the Default Monitor component;
5. If I run the desktop control panel at runtime I can manually change the settings to 800, 600, 32, 60 with no trouble.
Unfortunately, in my application there is no access to the control panel, and I really don't want to provide a hack and require
that my production personnel manually change the settings on each box.

I'm stuck. Do you have any other wisdom or suggestions?

I appreciate your help.

Thanks,
Dean

Dean,

With the same setupapi.log you can find out if your video driver was installed properly. If it didn't, window backed up to
standard VGA driver that might not support the display settings you set up in TD.

Also, check if you got "PNP (User-mode)" component in your image config. (this component often is left out an XPe image)
Monitor component is also a thing to check in your image.

These and other relevant tips you can find on this page: http://msdn2.microsoft.com/en-us/embedded/aa731224.aspx

 

[DPM]

KM,

What's the possibility of adding registry values in key
HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\VIDEO\{<GUID>}\0000?
As long as the GUID of the video adapter does not change build to build and
I can update the key values late enough this should work. I could even do
it at startup in my custom shell script.

Regards,
Dean

Dean,

That's weird that it fails to set the right resolution when the right
driver has been installed properly. Perhaps another bug of FBA (you may
want to report this to Microsoft through the product feedback alias page).

At this point I can only recommend to add some code to your application to
"manually" change the resolution at the first launch. You can certainly
create more complex logic in the app to read the default display settings
off the registry or INI file. But then you should call the
ChangeDisplaySettingsEx API
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/devcons_3tfc.asp).
The API call should work if the resolution is supported.

--
=========
Regards,
KM

KM,

Thanks for the tips. Despite all I've tried, FBA still reports:
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings: [800, 600, 32, 60]·
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings not found!·

Now, here's what I know:
1. The driver is installed successfully; it's reported as successful in
setupapi.log, and if I run DeviceManager at runtime the display adapter
is shown correctly;
2. Nowhere in FBALOG.TXT does the PnP ID of the display adapter appear;
it only appears in setupapi.log, which I think is odd but may not matter;
3. All required PnP components are included in the build: PnP kernel
mode, PnP User mode and FBA: PnP;
4. I'm using the Default Monitor component;
5. If I run the desktop control panel at runtime I can manually change
the settings to 800, 600, 32, 60 with no trouble. Unfortunately, in my
application there is no access to the control panel, and I really don't
want to provide a hack and require that my production personnel manually
change the settings on each box.

I'm stuck. Do you have any other wisdom or suggestions?

I appreciate your help.

Thanks,
Dean

Dean,

With the same setupapi.log you can find out if your video driver was
installed properly. If it didn't, window backed up to standard VGA
driver that might not support the display settings you set up in TD.

Also, check if you got "PNP (User-mode)" component in your image
config. (this component often is left out an XPe image)
Monitor component is also a thing to check in your image.

These and other relevant tips you can find on this page:
http://msdn2.microsoft.com/en-us/embedded/aa731224.aspx

--
=========
Regards,
KM


KM,

Thanks for the setupapi.log tip: in it I found that the driver was not
installing because the inf was trying to copy help files. Modifying it
not to do so solved that problem.

But the effective problem still remains: the component allows me to set
default screen settings, and FBA (in the log) declares that these
settings cannot be found.

How does the component communicate those settings? Would you expect
registry keys? What does FBA mean when it declares that the settings
"cannot be found"?

Regards,
Dean

Dean,

How did you run TAP? Was it on XP Pro install on the device or under
WinPE?
If the first, the device might have been discovered and set up there
manually or by dedicated installer.

It is still weird though that the PnP device doesn't get at least
discovered by FBA PnP. Did you check SetupAPI.log on the device after
FBA completes?
Also, what happens if you, after FBA, manually at run time launch
command like "devcon rescan"? (grab devcon from MS Support website
first). Does it discover new devices? Check SetupAPI.log here as well.

There was also a nice tool in NT/XP Resource Kit - PnpEnum. I can't
seem to find where to download it from now. It would help you to
analyze PnP registry data.

--
=========
Regards,
KM


I've got an interesting problem: MB with VIA Northbridge, S3G IGP.
TAP finds it's PNP ID as "PCI\VEN_1106&amp;DEV_3230", and that's
what's in the inf file. So I imported the inf and added the
component. But when FBA runs, I never see the above PNP ID listed in
the log.

Why would TAP find it and FBA not?

Any help gratefully received!

Thanks,
Dean

 

[KM]

Dean,

Unfortunately, that GUID will change when you re-install a video driver. In other words, when you run FBA on the same device second
time the GUID will be different.
Also, changing that registry you will have to re-initialize the driver either by creating another reboot in the sequence or by
messing with the driver status. Bring in more code than the API I suggested.

API is definitely better and cleaner way than setting up the registry. It id documented and supported approach.

Btw, I am positive there are utilities (freeware) on the Web that utilize the API and work in command line mode. You may want to
google if you like to use such tools instead of API.

--
=========
Regards,
KM

KM,

What's the possibility of adding registry values in key HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\VIDEO\{<GUID>}\0000?
As long as the GUID of the video adapter does not change build to build and I can update the key values late enough this should
work. I could even do it at startup in my custom shell script.

Regards,
Dean

Dean,

That's weird that it fails to set the right resolution when the right driver has been installed properly. Perhaps another bug of
FBA (you may want to report this to Microsoft through the product feedback alias page).

At this point I can only recommend to add some code to your application to "manually" change the resolution at the first launch.
You can certainly create more complex logic in the app to read the default display settings off the registry or INI file. But
then you should call the ChangeDisplaySettingsEx API
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/devcons_3tfc.asp). The API call should work if the
resolution is supported.

--
=========
Regards,
KM

KM,

Thanks for the tips. Despite all I've tried, FBA still reports:
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings: [800, 600, 32, 60]·
·8:12:41 AM - ·[FBAChangeDisplaySettings] Settings not found!·

Now, here's what I know:
1. The driver is installed successfully; it's reported as successful in setupapi.log, and if I run DeviceManager at runtime the
display adapter is shown correctly;
2. Nowhere in FBALOG.TXT does the PnP ID of the display adapter appear; it only appears in setupapi.log, which I think is odd
but may not matter;
3. All required PnP components are included in the build: PnP kernel mode, PnP User mode and FBA: PnP;
4. I'm using the Default Monitor component;
5. If I run the desktop control panel at runtime I can manually change the settings to 800, 600, 32, 60 with no trouble.
Unfortunately, in my application there is no access to the control panel, and I really don't want to provide a hack and require
that my production personnel manually change the settings on each box.

I'm stuck. Do you have any other wisdom or suggestions?

I appreciate your help.

Thanks,
Dean


Dean,

With the same setupapi.log you can find out if your video driver was installed properly. If it didn't, window backed up to
standard VGA driver that might not support the display settings you set up in TD.

Also, check if you got "PNP (User-mode)" component in your image config. (this component often is left out an XPe image)
Monitor component is also a thing to check in your image.

These and other relevant tips you can find on this page: http://msdn2.microsoft.com/en-us/embedded/aa731224.aspx

--
=========
Regards,
KM


KM,

Thanks for the setupapi.log tip: in it I found that the driver was not installing because the inf was trying to copy help
files. Modifying it not to do so solved that problem.

But the effective problem still remains: the component allows me to set default screen settings, and FBA (in the log) declares
that these settings cannot be found.

How does the component communicate those settings? Would you expect registry keys? What does FBA mean when it declares that
the settings "cannot be found"?

Regards,
Dean

Dean,

How did you run TAP? Was it on XP Pro install on the device or under WinPE?
If the first, the device might have been discovered and set up there manually or by dedicated installer.

It is still weird though that the PnP device doesn't get at least discovered by FBA PnP. Did you check SetupAPI.log on the
device after FBA completes?
Also, what happens if you, after FBA, manually at run time launch command like "devcon rescan"? (grab devcon from MS Support
website first). Does it discover new devices? Check SetupAPI.log here as well.

There was also a nice tool in NT/XP Resource Kit - PnpEnum. I can't seem to find where to download it from now. It would help
you to analyze PnP registry data.

--
=========
Regards,
KM


I've got an interesting problem: MB with VIA Northbridge, S3G IGP. TAP finds it's PNP ID as "PCI\VEN_1106&amp;DEV_3230", and
that's what's in the inf file. So I imported the inf and added the component. But when FBA runs, I never see the above PNP
ID listed in the log.

Why would TAP find it and FBA not?

Any help gratefully received!

Thanks,
Dean