I have a device which I am managing using WINUSB and an application.
I would like that the INF which install WINUSB over my device will include
my own custom co-installer (including the standard KMDF and WINUSB
co-installer)
I have done all the changes and write my own coinstaller.
It seems that my coinstaller has been copied to windows\system directory
but I do not see DLLMAIN or my Coinstaller exported function called at all.
I am starting to wonder if that is possible at all. if it does, what I am
doing wrong ?
I am using the standard WINUSB inf from visual studio 2012.
I add the following lines in the inf :
under : [CoInstallers_AddReg]
HKR,CoInstallers32,0x00010000,“MyCoinstaller.dll,MyCoInstaller”
under : [SourceDisksFiles]
MyCoinstaller.dll=1
under : [CoInstallers_CopyFiles]
MyCoinstaller.dll
it was relates to two different issues, one is that I used an addition
HKR,CoInstaller32 instead of unite them with the Kmdf and Winusb. The
other is … mmm, I placed a 32bit dll on my 64 bit driver
Anyway, I have an additional issue now. My coinstaller is working but I
would like when uninstall or upgrade to be able to remove the
coinstaller.dll file , if I am not doing it, it cause the system to ask for
a reboot before the device is working.
How can I do it ?
On Tue, Feb 4, 2014 at 11:38 AM, Jim wrote:
> I have a device which I am managing using WINUSB and an application. > > I would like that the INF which install WINUSB over my device will include > my own custom co-installer (including the standard KMDF and WINUSB > co-installer) > > I have done all the changes and write my own coinstaller. > > It seems that my coinstaller has been copied to windows\system directory > but I do not see DLLMAIN or my Coinstaller exported function called at all. > > I am starting to wonder if that is possible at all. if it does, what I am > doing wrong ? > > I am using the standard WINUSB inf from visual studio 2012. > > I add the following lines in the inf : > under : [CoInstallers_AddReg] > HKR,CoInstallers32,0x00010000,“MyCoinstaller.dll,MyCoInstaller” > > under : [SourceDisksFiles] > MyCoinstaller.dll=1 > > under : [CoInstallers_CopyFiles] > MyCoinstaller.dll > > Any idea ? >
