WPP on Win2K clarification request

NTDEV
1

Doron,

Does

> … that didn’t account for every scenario, this has since been fixed.

Change the (apparent) restriction that an NDIS Miniport Driver could not use
WPP on Win2K because both NDIS and the WPP generated code want to handle WMI
IRPs?

As far as I can tell (reading .tmh output) the dispatch of
IRP_MJ_DEVICE_CONTROL is still going to either be handled by NDIS or by
WPPSystemControlDispatch() - neither neither seem to be in a position to
cooperate with the other. If WPP is initialized first, then NDIS
overwrites the dispatch entry when the miniport is registered. If WPP is
initialized after miniport registration, I suspect (have not tried) that
NDIS WMI support will break.

Is there a way to get NDIS (WMI) and WPP cooperating on Win2K?

Thanks,
Dave Cattley
Consulting Engineer
Systems Software Development

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@Microsoft.com
Sent: Thursday, February 15, 2007 12:20 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] New line in WPP trace

To clarify, the only time WPP gets in the path of WMI is on win2k where WPP
registration occcured via IRPs. The WPP headers originally provided some
dispatching code that didn’t account for every scenario, this has since been
fixed. On XP and later, WPP registration is a direct call interface that
does not perturb the driver’s WMI IRP processing 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

2

YES,

Take a look at the WDK Vista release Toaster Sample
toaster\func\featured2.

This one shows how to do it, and the sample works Vista to W2K.

Thanks,
Jose Sua
Microsoft Corporation
This posting is provided “AS IS” with no warranties and confers no
rights.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Thursday, February 15, 2007 11:46 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WPP on Win2K clarification request

Doron,

Does

> … that didn’t account for every scenario, this has since been
fixed.

Change the (apparent) restriction that an NDIS Miniport Driver could not
use
WPP on Win2K because both NDIS and the WPP generated code want to handle
WMI
IRPs?

As far as I can tell (reading .tmh output) the dispatch of
IRP_MJ_DEVICE_CONTROL is still going to either be handled by NDIS or by
WPPSystemControlDispatch() - neither neither seem to be in a position to
cooperate with the other. If WPP is initialized first, then NDIS
overwrites the dispatch entry when the miniport is registered. If WPP
is
initialized after miniport registration, I suspect (have not tried) that
NDIS WMI support will break.

Is there a way to get NDIS (WMI) and WPP cooperating on Win2K?

Thanks,
Dave Cattley
Consulting Engineer
Systems Software Development

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@Microsoft.com
Sent: Thursday, February 15, 2007 12:20 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] New line in WPP trace

To clarify, the only time WPP gets in the path of WMI is on win2k where
WPP
registration occcured via IRPs. The WPP headers originally provided
some
dispatching code that didn’t account for every scenario, this has since
been
fixed. On XP and later, WPP registration is a direct call interface
that
does not perturb the driver’s WMI IRP processing 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

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

3

I am familiar with that sample and how it demonstrates getting both WMI and
ETW working in a Win2K driver. My question is specific to miniport model
drivers (NDIS) in which the ‘port’ driver takes over all responbility for
dispatching IRPs as well as hides the FDO from view. Now of course NDIS WDM
does allow us to get at the FDO but the issue remains, is there a rational
way to get involved with the IRP_MJ_SYSTEM_CONTROL dispatching without
causing problems for NDIS WMI support. I am hesitant to grab back the
IRP_MJ_SYSTEM_CONTROL dispatch after the miniport is initialized and process
it ‘ahead of’ NDIS but perhaps this is exactly how to make this work.

Thanks,
Dave Cattley
Consulting Engineer
Systems Software Development

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jose Sua
Sent: Thursday, February 15, 2007 3:16 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WPP on Win2K clarification request

YES,

Take a look at the WDK Vista release Toaster Sample toaster\func\featured2.

This one shows how to do it, and the sample works Vista to W2K.

Thanks,
Jose Sua
Microsoft Corporation
This posting is provided “AS IS” with no warranties and confers no rights.