It would appear that WMI no longer functions in KMDF 1.5 for W2000. In the WDK release notes, it states that ETW tracing won’t work for miniport drivers, but my driver is not a miniport and all WMI functionality appears to be lost, not just tracing.
There was no problem with KMDF 1.1 with the DDK builds - but the older framework won’t function with WDK-built drivers. Now I’m faced with either 1) building a separate binary for W2000 with the 3790 DDK or 2) rebuilding the 32-bit driver with the old DDK & then going thru the entire test cycle on Vista, XP, and Server 2003.
Is this a known issue or am I missing something?
David Bradsher
This shouldn’t be happening to you. But I don’t think I’m the best person to help get you through this one. I’ll see if I can get the WMI QA or dev owner to assist. It’s still pretty early in the workday here, so there will probably be a delay…
WMI should work on win2k, there is nothing in the code that has a win2k dependency. In fact, the WMI code is the same for all OS’s. Tracing is a bit different though, but that does not go through the std WMi path.
d
It isn’t just tracing - the top of the driver stack allows only a single open handle so our diagnostic & monitoring app uses WMI to access the driver while another application has the device open.
Also, I know we tested WMI at least weekly on Win2K, all through the 1.5 test cycles. Same tests we used on all the OS’s. Perhaps I should have said so earlier… I’ve just not worked on it as heavily as some of the other members of the team.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@Microsoft.com
Sent: Friday, January 19, 2007 9:11 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] WMI problem in W2000 with KMDF 1.5?
WMI should work on win2k, there is nothing in the code that has a win2k dependency. In fact, the WMI code is the same for all OS’s. Tracing is a bit different though, but that does not go through the std WMi path.
d
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
You mentioned ETW, are you by chance doing something special for ETW on
2000 the way developers had to do for WDM drivers, with 3790? The WDK
changed the handling of this at least in WDM, such that I found I could not
use the old WPP tracing code with the WDK. I had filed a bug in the beta,
and the last I knew it was still listed as outstanding.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
wrote in message news:xxxxx@ntdev…
> It would appear that WMI no longer functions in KMDF 1.5 for W2000. In
> the WDK release notes, it states that ETW tracing won’t work for miniport
> drivers, but my driver is not a miniport and all WMI functionality
> appears to be lost, not just tracing.
>
> There was no problem with KMDF 1.1 with the DDK builds - but the older
> framework won’t function with WDK-built drivers. Now I’m faced with
> either 1) building a separate binary for W2000 with the 3790 DDK or 2)
> rebuilding the 32-bit driver with the old DDK & then going thru the
> entire test cycle on Vista, XP, and Server 2003.
>
> Is this a known issue or am I missing something?
>
> David Bradsher
>
Nothing special - tracing was done pretty much textbook (using the tracedrv sample for a template) as was WMI. In any event, both functions worked in 2000 with the older build and 1.1 framework; none of the supporting code has changed since that version of the driver.
I sent an email directly to David to get more information about the problem
he is facing with WMI.
FYI, WDK contains a KMDF sample “wmisamp” that illustrates how to use WMI
(and this was tested on Win2K for KMDF 1.5 release).
-kumar
wrote in message news:xxxxx@ntdev…
> Nothing special - tracing was done pretty much textbook (using the
> tracedrv sample for a template) as was WMI. In any event, both functions
> worked in 2000 with the older build and 1.1 framework; none of the
> supporting code has changed since that version of the driver.
>
Repairing WMI database may help. It seems to be somewhat bristle
on win2k.
–PA
“Kumar Rajeev” wrote in message news:xxxxx@ntdev…
>I sent an email directly to David to get more information about the problem he is facing with WMI.
> FYI, WDK contains a KMDF sample “wmisamp” that illustrates how to use WMI (and this was tested on Win2K for KMDF 1.5 release).
>
> -kumar
>
> wrote in message news:xxxxx@ntdev…
>> Nothing special - tracing was done pretty much textbook (using the tracedrv sample for a template) as was WMI. In any event,
>> both functions worked in 2000 with the older build and 1.1 framework; none of the supporting code has changed since that
>> version of the driver.
>>
>
>
Regarding the KMDF WMI samples: I built it in the KMDF 1.1/ 3790 DDK environment as well as in the WDK (KMDF 1.5). Installed each one separately on systems with a fresh W2000 image. The 1.1 version works while the 1.5 version does NOT!