The WDF team needs your help in ensuring compatibility

NTDEV
1

You might know that the Windows Driver Framework team is working on the next version of WDF, version 1.9, and planning to release it with Windows 7.

Windows 7 will have this new version of framework built in. However, we will also provide a redistributable coinstaller so that you can install this framework on downlevel operating system with latest service packs. We have added several new features to:
a) Further simplify driver development.
b) Make it easier to debug & diagnose failures during development and also in the field after deployment.
c) Reduce CPU utilization and memory footprint.
d) Enable the use of the framework in certain new technologies.
e) Fixed numerous bugs to harden the framework to handle edge conditions - in particular run down scenarios.

So we have put in lot of effort to make driver and driver writing experience better. The presentation “What’s new in WDF 1.9” that we gave in WinHEC 2008 (http://download.microsoft.com/download/5/E/6/5E66B27B-988B-4F50-AF3A-C2FF1E62180F/COR-T546_WH08.pptx) has more details on the work we did.

How can you help us?

Based on our telemetry, we know there are large number (over 1000) of framework drivers of all versions (1.1, 1.5, 1.7) written and released to
public. In order to make sure that these drivers continue to work on Windows 7, and even on downlevel OSes - if a new device brings in the latest
framework - we request you to test your drivers with 1.9 version of framework and make sure it’s fully functional. We have put an extra ordinary
effort to maintain compatibility but when you have such a large eco-system, we will not be able to cover every possible scenario.

We made a very successful transition from 1.5 to 1.7 with absolutely no compatibility issues and we would like to ensure that we repeat that success and keep you all happy.

So please take some time and try out the new version. You can get the 1.9 version from Windows 7 beta WDK. Information on how to get the WDK is given on this page http://www.microsoft.com/whdc/DevTools/WDK/WDKbeta.mspx.

We are also putting together a small lab with some devices to do compatibility testing on our own. We are in need of more devices that use
framework drivers. So if you have released a device that we can buy from a store and use it in our lab, please send me the description.

You can post your feedback here or email to (xxxxx@discussion.microsoft.commailto:xxxxx). Remove ‘discussion’ word from the email
address.

Thank you,
On behalf of the WDF team - Microsoft</mailto:xxxxx>

2

Ilias Tsigkogiannis wrote:

We made a very successful transition from 1.5 to 1.7 with absolutely
no compatibility issues

Uh … hahahahahaha.

3

What are you referring to? Is there a 1.5, 1.1, or 1.0 driver that does not work with KMDF 1.7?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Thursday, February 12, 2009 11:53 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] The WDF team needs your help in ensuring compatibility

Ilias Tsigkogiannis wrote:

We made a very successful transition from 1.5 to 1.7 with absolutely
no compatibility issues

Uh … hahahahahaha.

4

Skip that- I take it this is in reference to “very successful transition” and the original 1.7 coinstaller issues vis-a-vis the hotfixes that broke them. Point understood. No further reply necessary.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Bob Kjelgaard
Sent: Thursday, February 12, 2009 1:18 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] The WDF team needs your help in ensuring compatibility

What are you referring to? Is there a 1.5, 1.1, or 1.0 driver that does not work with KMDF 1.7?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Thursday, February 12, 2009 11:53 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] The WDF team needs your help in ensuring compatibility

Ilias Tsigkogiannis wrote:

We made a very successful transition from 1.5 to 1.7 with absolutely
no compatibility issues

Uh … hahahahahaha.

5

Hi,

I’m posting here because I can’t see the full email address for the feedback.

We are in the process of preparing our IR Port Driver, which was released as a product using WDK 6000, for Windows 7.
When building in the WDK 7000 environment (x86, either Vista or Windows 7, either free or checked) installation fails with code 39.
So I attempted to build and install the consumer IR receiver sample driver (I modified the PnP ID in the sample INF to that of my device), and the same error occurs. If I build the sample driver in WDK 6000, installation works in the same Vista system.

I tried to change KmdfLibraryVersion from “1.5” to “1.9” in the sample’s INF, but that didn’t help.
I also copied the 1.9 co-installer to system32, and to the same directory of the driver .sys file, but still error.

Is it expected that the KMDF driver built in WDK 7000.0 cannot be installed in Vista ? If it should succeed, can you please suggest what can be done ?
I can attach setupapi logs in the next post.

Thanks,
Galit

6

Our original concern in this thread is that we want “yes” [or even more urgently “no”] answers to these questions [the intent here was not breaking compatibility]:

Does your existing driver work in Windows 7?

If you change to the coinstaller in your package (KMDF or UMDF) to the 1.9 coinstaller [without rebuilding your driver], does your device still install and work [yes, there will be signing-related issues in some cases, but should that level of detail be necessary in every communication]?

…

So your problem is a bit different, in that it appears you are rebuilding the driver. That doesn’t make things any better or worse, I just wanted to make sure our original request is understood.

So, on to your problems:

We’d like to see these logs to begin with (WDK 7000 beta should be functional for KMDF to best of my knowledge- of course, after a few months my knowledge ain’t so good):

%windir%\inf\setupapi.dev.log
%windir%\setupact.log

As for not being able to read our email alias…

The web interface for this mailing list will scramble email aliases for most folks’ protection. Our support alias is spattered all across the net, but this should avoid the scrambler…

Wdfinfo at Microsoft.com…

Bob Kjelgaard
Senior SDET
Windows Driver Frameworks QA

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@nuvoton.com
Sent: Monday, February 23, 2009 5:32 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] The WDF team needs your help in ensuring compatibility

Hi,

I’m posting here because I can’t see the full email address for the feedback.

We are in the process of preparing our IR Port Driver, which was released as a product using WDK 6000, for Windows 7.
When building in the WDK 7000 environment (x86, either Vista or Windows 7, either free or checked) installation fails with code 39.
So I attempted to build and install the consumer IR receiver sample driver (I modified the PnP ID in the sample INF to that of my device), and the same error occurs. If I build the sample driver in WDK 6000, installation works in the same Vista system.

I tried to change KmdfLibraryVersion from “1.5” to “1.9” in the sample’s INF, but that didn’t help.
I also copied the 1.9 co-installer to system32, and to the same directory of the driver .sys file, but still error.

Is it expected that the KMDF driver built in WDK 7000.0 cannot be installed in Vista ? If it should succeed, can you please suggest what can be done ?
I can attach setupapi logs in the next post.

Thanks,
Galit

7

xxxxx@nuvoton.com wrote:

We are in the process of preparing our IR Port Driver, which was released as a product using WDK 6000, for Windows 7.
When building in the WDK 7000 environment (x86, either Vista or Windows 7, either free or checked) installation fails with code 39.
So I attempted to build and install the consumer IR receiver sample driver (I modified the PnP ID in the sample INF to that of my device), and the same error occurs. If I build the sample driver in WDK 6000, installation works in the same Vista system.
…
I tried to change KmdfLibraryVersion from “1.5” to “1.9” in the sample’s INF, but that didn’t help.
I also copied the 1.9 co-installer to system32, and to the same directory of the driver .sys file, but still error.

Is it expected that the KMDF driver built in WDK 7000.0 cannot be installed in Vista ? If it should succeed, can you please suggest what can be done ?

I know that KMDF 1.9 from the 6800 WDK would not work in anything
earlier than Windows 7, but I thought I saw something saying that would
be relaxed in the 7000 release.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

8

>>
I know that KMDF 1.9 from the 6800 WDK would not work in anything
earlier than Windows 7, but I thought I saw something saying that would
be relaxed in the 7000 release.
<<

Yes, the 7000 release is supposed to have fully functional coinstallers- that’s why I asked for logs…