[krohnjw]

If anyone is curious regarding what they are actually effecting they appear fairly straightforward.

Navigate to: HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0

From MSDN:
http://msdn2.microsoft.com/en-us/library/ms890616.aspx
The NDISWAN implementation in Windows CE includes a HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms registry key. This key contains a set of subkeys that allow you to configure values that are specific to the WAN miniport driver.

So, this enables power management for the WAN Miniport driver.
If you want more info as to exactly what the WAN miniport driver is/controls: http://msdn2.microsoft.com/en-us/library/ms890616.aspx

They appear to only apply to RAS and connectivity utilizing the PPP protocol (do I need protocol twice?).

Navigate to: HKEY_LOCAL_MACHINE\Comm\Irsir1\Parms
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0

From MSDN:
http://msdn2.microsoft.com/en-us/library/ms900374.aspx

This controls the IrDA components – this will enable power management for the IR COMM.

Navigate to: HKEY_LOCAL_MACHINE\Comm\PPTP1\Parms
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0


Navigate to: HKEY_LOCAL_MACHINE\Comm\L2TP1\Parms
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0

The last 2 will enable power management for the PPTP and L2TP transport protocols – these only apply to VPN tunneling AFAIK.

They seem safe to implement assuming you aren't relying on an active VPN tunnel. It may slow down the initialization of a Beam transfer (don't use it - so I don't know) but it shouldn't cause any real issues.