i am trying to create a xp component for a driver

[jeff]

the driver is created by us in house.
it is a pnp driver (usb device) which consists of a *.inf file and a
*.sys file.

i try to import the inf file in the component designer.
i get the following error message.

"INF Importer could not find any recognizable installation to convert
in the file"

i have tried to use inctrl5 to see what registry changes occur when our
driver is installed.
the list of registry entries is very large. i would rather not manually
create a component
for our driver using this information.

is there a better way to create the xpe component for our driver?

thanks

 

[Stuart Langley]

If you driver simply consists of an *.inf & *.sys file, then in most cases
it is suitable to just copy these to the windows\inf and
windows\system32\drivers folders respectively. PNP should enumerate the
device ID's and select the correct driver based on you inf file.

Also, if the driver is an in house driver, then do you not have the registry
requirements at hand?

Of course you will need to include the correct USB core components in your
build.

Regards,

Stuart

 

[jeff]

thanks stuart,

you are right. i created a component that put the *.inf file in the
windows/inf directory and
the *.sys file in the windows/system32/drivers directory on the target.
i built the target image.
the first time it ran, it recognized the usb device and installed the
driver automatically. Im
not sure when this happened. im pretty sure the fba was responsible for
it. but anyway,
the end result was that a whole bunch of keys were put into the
registry for the driver to work properly. only 4 or 5 were actually
used by our pnp driver directly in the code. i quess once the
driver is installed the inf file is no longer necessary.

this was a whole lot easier than recreating all the many registry keys
in a xpe component.
and then putting only the .sys file in the windows/system32/drivers
directory.

thanks again,
jeff

 

[Sean Liming \(eMVP\)]

A possible problem with the INF import was the need to parse special
sections within the INF instead of automatic parsing.

It is good that it worked the other way.

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit