Componentizing your own display driver?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A note to all those who are trying to make an XPe component out of their XP display adapter driver.

Don't forget to add dependencies to the "Class installers - Display adapters" and "Device: Display" components. Otherwise your componentized driver (or parts of it) will fail to load properly. How can you tell? FBA adds an [FBAInstallNullDriver] entry to fbalog.txt for each driver module it fails to load.

Happy hunting,
idan
 
Properly formed 3rd party infs converted to SLD format by Component Designer
will result in a component that has the correct device class prototype
dependency. In other words, having to manually add the CI or Device
component means you're having to hack around a bug in our import
process -OR- there is a problem with the INF to begin with or the component
was being created manually.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


idan said:
A note to all those who are trying to make an XPe component out of their XP display adapter driver.

Don't forget to add dependencies to the "Class installers - Display
Click to expand...
adapters" and "Device: Display" components. Otherwise your componentized
driver (or parts of it) will fail to load properly. How can you tell? FBA
adds an [FBAInstallNullDriver] entry to fbalog.txt for each driver module it
fails to load.
 
Back
Top