Enabling PNP virtual device driver after install
Hello,
I have a virtual device PNP driver. The problem is that dpinst installs it to driver cache and after that waits for an event when the "device" will be plugged in (this will never happen, as there is no physical device, it is a virtual drive emulation software :>).
The best results I got from google for now is that there is a function that forces this kind of drivers to be loaded up - InstallRootEnumeratedDriver
I have not done all the reading there is and this topic is a quick question if anyone has already been struggling with the same situation and would like to share a solution.
Thanks.
I have a virtual device PNP driver. The problem is that dpinst installs it to driver cache and after that waits for an event when the "device" will be plugged in (this will never happen, as there is no physical device, it is a virtual drive emulation software :>).
The best results I got from google for now is that there is a function that forces this kind of drivers to be loaded up - InstallRootEnumeratedDriver
I have not done all the reading there is and this topic is a quick question if anyone has already been struggling with the same situation and would like to share a solution.
Thanks.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
AngelD
12 years ago
Answer by Google ;)
Since it is a virtual device, you'll need to programmatically create a devnode for it before you attempt to install the driver using the DIFx tools. Guessing the same for DPinst.
The source code for the devcon tool ships in the DDK and has an example of how to create a devnode programmatically. Look for the implementation of the "devcon install" command and you'll find it there.
Once you've created the devnode you can use the DIFx tools to install the driver on it. Or you may want to simply use devcon if that suits you better.
As far as I know, the DIFx tools will not automatically create this devnode for you.
Since it is a virtual device, you'll need to programmatically create a devnode for it before you attempt to install the driver using the DIFx tools. Guessing the same for DPinst.
The source code for the devcon tool ships in the DDK and has an example of how to create a devnode programmatically. Look for the implementation of the "devcon install" command and you'll find it there.
Once you've created the devnode you can use the DIFx tools to install the driver on it. Or you may want to simply use devcon if that suits you better.
As far as I know, the DIFx tools will not automatically create this devnode for you.
Posted by:
GrGrGr
12 years ago
Thank you for taking your time to look into it.
Post temporary edited.
Post temporary edited.
ORIGINAL: AngelD
Answer by Google ;)
Since it is a virtual device, you'll need to programmatically create a devnode for it before you attempt to install the driver using the DIFx tools. Guessing the same for DPinst.
The source code for the devcon tool ships in the DDK and has an example of how to create a devnode programmatically. Look for the implementation of the "devcon install" command and you'll find it there.
Once you've created the devnode you can use the DIFx tools to install the driver on it. Or you may want to simply use devcon if that suits you better.
As far as I know, the DIFx tools will not automatically create this devnode for you.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.