Re: NIC Power Management features Issues
- From: "asdf" <adsf@xxxxxxxx>
- Date: Sun, 25 Mar 2007 01:48:35 -0500
You are over estimating your answer.
There is no answer in this group, that has even in the slightest,
a torrent of answers trackable to the matter..
-----------------------
My opinion :
If you let 'your' hardware decide what goes,
you will become subservient to your (new) hardware, or become so.
----------------------
In short, not a good answer.
Not a bright manner in the first place to have a $5 device
decide your future time and memory...
"Charles Blair" <charles_blair@xxxxxxxxxxx> wrote in message news:OIF52c2KHHA.2632@xxxxxxxxxxxxxxxxxxxxxxx
There is not a standard WMI provider for these GUIDs.
It would be up to the NIC manufacturer to develop its own specific WMI provider and then it would need to be installed on the client computers.
If your lucky, the NIC manufacturer will include their WMI provider with their driver installation package, such as the Intel Proset utility:
http://www.intel.com/support/network/adapter/wmi/index.htm
The PowerManagementCapabilities and PowerManagementSupported syntax in the Win32_NetworkAdapter class are Read-Only as noted in the following article:
http://msdn2.microsoft.com/en-us/library/aa394216.aspx
Good luck.
Charles
"nalin chakoo" <nalinchakoo@xxxxxxxxx> wrote in message news:1166777366.114720.97250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThanks for the reply.
Yes , ofcourse we need to wake it from a standby position i.e the
network adapter wakes up the machine from its standby state to active
state.
The idea which was suggested needs to explored and discussed and
accordingly suggested upon.
Please suggest how shall we be able to do that programatically i.e
change the values of the two GUIDs that were suggested or is there an
alternative method.
Cheers Nalin
Charles Blair wrote:
Just to let you know that the "Wake-up" ability specified in this article is
in regards to waking up a workstation where the Windows OS has gone into
standby, not for waking up a workstation that is off.
True "Wake-on-LAN" is controlled by the workstation BIOS, which usually
requires vendor specific controls to change from the OS level.
For instance with Dell workstations, to change BIOS settings from the OS you
would need to install Dell's OpenManage Client Instrumentation.
This Dell application then allows you to make BIOS changes, including
enabling "Wake-on-LAN".
Charles
"nalin chakoo" <nalinchakoo@xxxxxxxxx> wrote in message
news:1166671375.590587.233200@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I need to enable the NIC Power Management features on Windows Xp...and
> later may be Windows Vista workstations so that I can use Wake On Lan
> functionality. I considered using a simple registry hack to do this,
> but before and after registry snapshots reveals the values are buried
> in a GUID which appears unique to each workstation/adapter.
>
>
> I found a MSDN article that describes how to enable WOL in general and
> pointed me in the direction of WMI:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnde...
>
>
>
> This article basically states: "Wake-on-LAN can be enabled by the end
> user in the Device Manager property 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."
> So I have been checking out the WMI Scripting Tutorials that use
> VBScript and using the WMI CIM studio utility I think what I need to
> modify is the Win32_NetworkAdapter object but it looks like the 2 > Power
> Management entries are not writeable! So I'm confused, is the above
> GUID's only relating to Driver Developement, or am I taking the wrong
> tack with using the WSH and VBScript and need to use C++ or something?
> Or do I need to write a filter/miniport driver to communicate with the
> device to get the two GUIDs???
>
.
- Prev by Date: Re: thanks for the clarification...
- Next by Date: Re: Persmission Denied
- Previous by thread: Map Printer based on Computer Group Membership
- Next by thread: Re: Persmission Denied
- Index(es):
Relevant Pages
|
