WDF Coinstaller and my coinstaller

NTDEV
1

I’ve updated an existing WDM driver (for a PCI card) to KMDF 1.5, and
everything is working fine, except for one thing: the existing driver
also installed a coinstaller (to provide an extra property page). I
modified the INF file to add the WDF-related stuff, and now I don’t get
the property page. It appears to me that WDF is listed as “the”
coinstaller in the registry. So, how does one arrange things in the INF
to include both the WDF coinstaller and the driver’s coinstaller?

I didn’t want to post the INF (before and/or after converting to KMDF)
to reduce the noise level, but I can do that if it will help.

Cheers,

– mkj

//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

2

You can include multiple coinstallers for a device. We do this in the UMDF USB samples since the device requires WdfCoinstaller0100x.dll, WudfUpdate_0100x.dll and WinUsbCoinstaller.dll. I’d look at one of the UMDF USB samples and see how they put more than one coinstaller on the device and then make sure you’re doing the same.

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Michael Jones
Sent: Thursday, October 04, 2007 1:29 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF Coinstaller and my coinstaller

I’ve updated an existing WDM driver (for a PCI card) to KMDF 1.5, and
everything is working fine, except for one thing: the existing driver
also installed a coinstaller (to provide an extra property page). I
modified the INF file to add the WDF-related stuff, and now I don’t get
the property page. It appears to me that WDF is listed as “the”
coinstaller in the registry. So, how does one arrange things in the INF
to include both the WDF coinstaller and the driver’s coinstaller?

I didn’t want to post the INF (before and/or after converting to KMDF)
to reduce the noise level, but I can do that if it will help.

Cheers,

– mkj

//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

Ahh-I see; the CoInstallers32 value is a MULTI_SZ. Helps if you
actually decode the magic value. Thanks!

–mkj

Peter Wieland wrote:

You can include multiple coinstallers for a device. We do this in the UMDF USB samples since the device requires WdfCoinstaller0100x.dll, WudfUpdate_0100x.dll and WinUsbCoinstaller.dll. I’d look at one of the UMDF USB samples and see how they put more than one coinstaller on the device and then make sure you’re doing the same.

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr…com] On Behalf Of Michael Jones
Sent: Thursday, October 04, 2007 1:29 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF Coinstaller and my coinstaller

I’ve updated an existing WDM driver (for a PCI card) to KMDF 1.5, and
everything is working fine, except for one thing: the existing driver
also installed a coinstaller (to provide an extra property page). I
modified the INF file to add the WDF-related stuff, and now I don’t get
the property page. It appears to me that WDF is listed as “the”
coinstaller in the registry. So, how does one arrange things in the INF
to include both the WDF coinstaller and the driver’s coinstaller?

I didn’t want to post the INF (before and/or after converting to KMDF)
to reduce the noise level, but I can do that if it will help.

Cheers,

– mkj

//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

–

//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________