How to deal with the two checks in NIC's Device Manager properties page ?

Hi,
I read the following paragraph from
http://www.microsoft.com/hwdev/tech/network/netpm.asp:
£½£½£½£½£½£½>
Wake-on-LAN can be enabled by the end user in the Device Manager
properties page for the network adapter, or programmatically using
the WMI calls. The following two globally unique identifiers (GUIDs)
that can be used for this purpose correspond to settings in the
Device Manager property page:
GUID_POWER_DEVICE_WAKE_ENABLE (corresponds to the first check box
in figure 1) turns wake-up capabilities on the device on or off
GUID_POWER_DEVICE_ENABLE (corresponds to the second check box in
figure 1) can be used to enable and disable power management for
the device
The buffer of WMI request will contain TRUE or FALSE to turn
these features on or off. Every time these values are changed,
they will be recorded in the registry, so that they are
preserved from session to session. More granular settings can
be enabled by implementing vendor-specific property pages
for the device.
<===============
In my miniport driver, I implement a Custom OID mapped from
“GUID_POWER_DEVICE_WAKE_ENABLE” .
The driver has no .mof file.
The Custom OID is not called when I change the selection in
NIC Device Manager property page for Power Management.
I was puzzled with this problem for several days. Can somebody
give me a way ?

Thanks for your help,

Yee


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

See
http://www.microsoft.com/hwdev/tech/network/netpm.asp
or

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen/html/netpm.asp

Stephan

On Sat, 23 Feb 2002 7:58:32, “Yee” wrote:

>
>Hi,
>I read the following paragraph from
>http://www.microsoft.com/hwdev/tech/network/netpm.asp:
>£½£½£½£½£½£½>
> Wake-on-LAN can be enabled by the end user in the Device Manager
>properties page for the network adapter, or programmatically using
>the WMI calls. The following two globally unique identifiers (GUIDs)
>that can be used for this purpose correspond to settings in the
>Device Manager property page:
>GUID_POWER_DEVICE_WAKE_ENABLE (corresponds to the first check box
>in figure 1) turns wake-up capabilities on the device on or off
>GUID_POWER_DEVICE_ENABLE (corresponds to the second check box in
>figure 1) can be used to enable and disable power management for
>the device
>The buffer of WMI request will contain TRUE or FALSE to turn
>these features on or off. Every time these values are changed,
>they will be recorded in the registry, so that they are
>preserved from session to session. More granular settings can
>be enabled by implementing vendor-specific property pages
>for the device.
><===============
> In my miniport driver, I implement a Custom OID mapped from
>“GUID_POWER_DEVICE_WAKE_ENABLE” .
>The driver has no .mof file.
>The Custom OID is not called when I change the selection in
>NIC Device Manager property page for Power Management.
> I was puzzled with this problem for several days. Can somebody
>give me a way ?
>
>Thanks for your help,
>
>Yee


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I have read both them, and I cann’t find any solution.
My code about Custom OID is copied from e100 sample.
but it is not called when i change the selection in
NIC Device Manager property page for Power Management.

Any Suggestion will be appreciated.

Yee

See
http://www.microsoft.com/hwdev/tech/network/netpm.asp
or

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen/html/netpm.asp

Stephan

On Sat, 23 Feb 2002 7:58:32, “Yee” wrote:
>
> >
> >Hi,
> >I read the following paragraph from
> >http://www.microsoft.com/hwdev/tech/network/netpm.asp:
> >£½£½£½£½£½£½>
> > Wake-on-LAN can be enabled by the end user in the Device Manager
> >properties page for the network adapter, or programmatically using
> >the WMI calls. The following two globally unique identifiers (GUIDs)
> >that can be used for this purpose correspond to settings in the
> >Device Manager property page:
> >GUID_POWER_DEVICE_WAKE_ENABLE (corresponds to the first check box
> >in figure 1) turns wake-up capabilities on the device on or off
> >GUID_POWER_DEVICE_ENABLE (corresponds to the second check box in
> >figure 1) can be used to enable and disable power management for
> >the device
> >The buffer of WMI request will contain TRUE or FALSE to turn
> >these features on or off. Every time these values are changed,
> >they will be recorded in the registry, so that they are
> >preserved from session to session. More granular settings can
> >be enabled by implementing vendor-specific property pages
> >for the device.
> ><===============
> > In my miniport driver, I implement a Custom OID mapped from
> >“GUID_POWER_DEVICE_WAKE_ENABLE” .
> >The driver has no .mof file.
> >The Custom OID is not called when I change the selection in
> >NIC Device Manager property page for Power Management.
> > I was puzzled with this problem for several days. Can somebody
> >give me a way ?
> >
> >Thanks for your help,
> >
> >Yee
>
> —
> You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

My code looks like this:

===========>
// PowerDeviceEnableGuid and PowerDeviceWakeEnableGuid
// equal to the value in “wdmguid.h”
#define PowerDeviceEnableGuid \
{0x827c0a6f,0xfeb0,0x11d0,{ 0xbd,0x26,0x00,0xaa,0x00,0xb7,0xb3,0x2a }}
#define PowerDeviceWakeEnableGuid \
{0xa9546a82,0xfeb0,0x11d0,{ 0xbd,0x26,0x00,0xaa,0x00,0xb7,0xb3,0x2a }}

NDIS_STATUS QueryInformation(…)
{
static NDIS_OID SupportedOids =
{ …,
/* custom oid WMI support */
OID_CUSTOM_POWER_DEVICE_ENABLE,
OID_CUSTOM_POWER_DEVICE_WAKE_ENABLE
};
static const NDIS_GUID GuidList[2] =
{{
PowerDeviceEnableGuid,
OID_CUSTOM_POWER_DEVICE_ENABLE,
sizeof(BOOLEAN),
(fNDIS_GUID_TO_OID)
},
{
PowerDeviceWakeEnableGuid,
OID_CUSTOM_POWER_DEVICE_WAKE_ENABLE,
sizeof(BOOLEAN),
(fNDIS_GUID_TO_OID)
}};

}
NDIS_STATUS SetInformation(…)
{

switch(Oid)
{

case OID_CUSTOM_POWER_DEVICE_ENABLE:
fucA(…);
break;
case OID_CUSTOM_POWER_DEVICE_WAKE_ENABLE:
fucB(…);
break;
}
}
<=========
and there isn’t .mof file.
When I change the states of the check boxes in the Device
Manager properties page for the Network Adapter,neither of
these Custom OID above are called.
So, i was puzzled.
Can Anyone give me a useful suggestion ?
Thanks for your Help !

Yee.

==========================================================

Hi,
I read the following paragraph from
http://www.microsoft.com/hwdev/tech/network/netpm.asp:
=======>
Wake-on-LAN can be enabled by the end user in the Device Manager
properties page for the network adapter, or programmatically using
the WMI calls. The following two globally unique identifiers (GUIDs)
that can be used for this purpose correspond to settings in the
Device Manager property page:
GUID_POWER_DEVICE_WAKE_ENABLE (corresponds to the first check box
in figure 1) turns wake-up capabilities on the device on or off
GUID_POWER_DEVICE_ENABLE (corresponds to the second check box in
figure 1) can be used to enable and disable power management for
the device
The buffer of WMI request will contain TRUE or FALSE to turn
these features on or off. Every time these values are changed,
they will be recorded in the registry, so that they are
preserved from session to session. More granular settings can
be enabled by implementing vendor-specific property pages
for the device.
<===============
In my miniport driver, I implement a Custom OID mapped from
“GUID_POWER_DEVICE_WAKE_ENABLE” .
The driver has no .mof file.
The Custom OID is not called when I change the selection in
NIC Device Manager property page for Power Management.
I was puzzled with this problem for several days. Can somebody
give me a way ?

Thanks for your help,

Yee


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I don’t think you have to support *any* GUIDs in your NDIS Miniport in
order for your Miniport to support Wake-on-LAN. Instead, you need to
support the appropriate OIDs, see “Required and Optional OIDs for
Power Management” in the DDK docs:

http://www.osr.com/ddk/206pm_8dbb.htm

Stephan

On Sat, 23 Feb 2002 19:32:12 -0500, “Yee” wrote:

>I have read both them, and I cann’t find any solution.
>My code about Custom OID is copied from e100 sample.
>but it is not called when i change the selection in
>NIC Device Manager property page for Power Management.
>
>Any Suggestion will be appreciated.
>
>Yee
>
>
>> See
>> http://www.microsoft.com/hwdev/tech/network/netpm.asp
>> or
>>
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwbgen/html/netpm.asp
>>
>> Stephan
>> —
>> On Sat, 23 Feb 2002 7:58:32, “Yee” wrote:
>>
>> >
>> >Hi,
>> >I read the following paragraph from
>> >http://www.microsoft.com/hwdev/tech/network/netpm.asp:
>> >£½£½£½£½£½£½>
>> > Wake-on-LAN can be enabled by the end user in the Device Manager
>> >properties page for the network adapter, or programmatically using
>> >the WMI calls. The following two globally unique identifiers (GUIDs)
>> >that can be used for this purpose correspond to settings in the
>> >Device Manager property page:
>> >GUID_POWER_DEVICE_WAKE_ENABLE (corresponds to the first check box
>> >in figure 1) turns wake-up capabilities on the device on or off
>> >GUID_POWER_DEVICE_ENABLE (corresponds to the second check box in
>> >figure 1) can be used to enable and disable power management for
>> >the device
>> >The buffer of WMI request will contain TRUE or FALSE to turn
>> >these features on or off. Every time these values are changed,
>> >they will be recorded in the registry, so that they are
>> >preserved from session to session. More granular settings can
>> >be enabled by implementing vendor-specific property pages
>> >for the device.
>> ><===============
>> > In my miniport driver, I implement a Custom OID mapped from
>> >“GUID_POWER_DEVICE_WAKE_ENABLE” .
>> >The driver has no .mof file.
>> >The Custom OID is not called when I change the selection in
>> >NIC Device Manager property page for Power Management.
>> > I was puzzled with this problem for several days. Can somebody
>> >give me a way ?
>> >
>> >Thanks for your help,
>> >
>> >Yee