When a driver package is installed , PC is supposed to create directories in \system32\driverstore to contain the drivers files by calling DIFx-APIs potentially .
With further observation on names of these directories , I notice that it always consists of 2 parts : infName_GUID . For example : if A.inf is installed (assume its guid is GUIDA) , then a name is produced : A_GUIDA.
Can someone please confirm what I see ? Is it a rule that DIFX follows to name directory in driver store.
My another question will be based on this suppose.
Daniel Xie wrote:
Can someone please confirm what I see ? Is it a rule that DIFX follows to
name directory in driver store.
Much like the composition of the substrings in a device interface, I expect this “rule” is supposed to be opaque to everyone but MS and you should not assume as such. Why do you care?
Thanks to Chris firstly .
I am involved in the development of a Driver installer tool.
This tool is designed to clean , update and reinstall drivers by calling DIFx-related API.
At beginning , I thought the directory name were composed in accordance with the rule drawn from what I see.
I start to realize that’s incorrect when running across a case :
I install two infs (supporting USB device) respectively by calling DIFx APIs and As a result , driver files are potentially copied to the same sub directory in the driver store . These 2 inf files are very similar except that one supports more devices ( that’s , more PID are defined ) than the other .
So , I have to investigate the naming rule of newly-installed driver.
Thanks .
xiedong_sl@126.com wrote:
When a driver package is installed , PC is supposed to create directories in \system32\driverstore to contain the drivers files by calling DIFx-APIs potentially .
With further observation on names of these directories , I notice that it always consists of 2 parts : infName_GUID . For example : if A.inf is installed (assume its guid is GUIDA) , then a name is produced : A_GUIDA.
Can someone please confirm what I see ? Is it a rule that DIFX follows to name directory in driver store.
The naming here is an undocumented implementation detail. The driver
store is a system internal structure.
The implementation varies significantly between XP and Vista.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
xiedong_sl@126.com wrote:
I am involved in the development of a Driver installer tool.
This tool is designed to clean , update and reinstall drivers by calling DIFx-related API.
If you’re trying to do this for ARBITRARY drivers, then your task is
hopeless. The driver store structure is not documented. You can
certainly do this for your own drivers, but anything else is just
reverse engineering that is doomed to fail.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.