Hi,
I have a coinstaller for my device that runs correctly if I install my driver in a running OS. However if the same driver is injected in an offline OS image then the coinstaller is not run when the driver is loaded for the first time!
Is this an expected behavior, or am I missing something?
Regards,
Suresh
xxxxx@yahoo.com wrote:
I have a coinstaller for my device that runs correctly if I install my driver in a running OS. However if the same driver is injected in an offline OS image then the coinstaller is not run when the driver is loaded for the first time!
Is this an expected behavior, or am I missing something?
It may seem like a silly question, but what exactly do you mean by
“injected” here? Did you just include the driver package in the Driver
Store? Or did you actually copy things into place? The co-installer
runs when the driver is INSTALLED (meaning when the INF is first
executed), not when the driver is LOADED.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
> what exactly do you mean by “injected” here?
I injected the driver in to offline OS image using “dism”.
If my understanding is right then as a result my vendor.inf file became oem1.inf
Now when OS boots from that image, it doesn’t load the coinstaller because it finds the oem1.inf and deduce that the driver is ‘preinstalled’ and so being ‘loaded’.
However the fact remains that the driver’s inf never went through the ‘install’ phase where the coinstaller got a chance to run.
Is there any way the OS can differentiate that the driver is being loaded after offline injection and so it should run the coinstaller?
If OS can’t, then do I have any other way? Thanks.