driver componentizer?

  • Thread starter Thread starter Henry Markov
  • Start date Start date
H

Henry Markov

I'm wondering who else has throught how useful a "driver componentizer" tool
would be. The idea is that it is often best to install XP Desktop on a
target so that a good tap.exe enumeration can be obtained. With XP Desktop
running it would be great if there were a tool that could pick out
everything needed from the running system and create a driver component. I
don't know nearly enough about XPe to know whether this is a good or
terrrible idea but I'm wondering how much work creating such a tool might be
and whether MS would consider providing it.

HM
 
After gaining a significant amount of scar tissue on my forehead (find a
wall and bang your head against it repeatedly) from the Sigmatel Driver
componentization attempt I made - I wish they would hurry up <grin>.
 
Henry said:
I'm wondering who else has throught how useful a "driver
componentizer" tool would be. The idea is that it is often best to
install XP Desktop on a target so that a good tap.exe enumeration can
be obtained. With XP Desktop running it would be great if there were
a tool that could pick out everything needed from the running system
and create a driver component. I don't know nearly enough about XPe
to know whether this is a good or terrrible idea but I'm wondering
how much work creating such a tool might be and whether MS would
consider providing it.

I'd be willing to put the time into writing one but don't have anywhere
near enough knowledge of XP/XPe to do it.

If a couple of experts were willing to answer the dozens of silly
questions that would arise I would still be willing to give it a go.
 
hmm, I'm missed out on some of the earlier conversations or I'm losing my
recollection in my old age because I honestly don't recall that subject for
this tool before. When I read Henry's request I laughed out loud because
it's a really good idea and surprised we or someone else haven't done this
before.

If I'm interpreting this correctly the tool would walk the Enum key,
identify all drivers and software enumerated devices, locate the inf that
installed the driver, identify the files, regkeys and service registration
information then populate all this to a component with repository of infs
and driver files?

For a lot of drivers this might work, some of the newer more complex drivers
from nvidia/ati for instance are doing some of the work through their
installers sometimes, as opposed to letting setupapi do the work (which
means the INF would have all needed information).

So for the detectable installation activities for a driver, yes I think a
tool like this would be possible.
 
Back
Top