NDIS IM power and Unbind question

ganesan.nagrajan_at_gmail.com
Date: 01/23/05 

Date: 23 Jan 2005 13:13:21 -0800

Hi

THANKS VERY MUCH ANY HELP.

The NDIS IM driver is meant for WINDOWS CE. I guess question number 1)
could be common. The driver is based on Passthru sample.

1) When a built-in wireless medium is switched off(using software
options), The NdisIMDeInitializeDeviceInstance() system call HANGS. in
the ProtocolUnbind() function.

How to solve this problem?.

Is it ture, when NdisIMDeInitializeDeviceInstance() is called, NDIS
will look for some state before issuing unbind to all the bound
protocols?
If Yes, since the underlying adapter has gone to D3 state,
What else could be done, other than return Failures to any sends
and queries?

2) How to get Power Down and/or Power Up notification.
The IM driver registers stream functions XXX_* for the GUI
interaction. It also includes XXX_Power and XXX_PowerDown. But the
driver doesn't get these notifications.

The problem:

When a medium is alive (like Ether card), if the user presses power
button and then up, the device is DEAD.

I am unable to distinguish between power button and other
on/offs(software). Both send me same kind of messages and same states.
a) PnpHandler (D3 state)
b) MiniportSet (D3 state).

So the drive can't tear down the bindings or do anything, when power
comes up or goes down.

I believe there was some discussion about this topic some time back. I
tried to search, but couldn't find.

Thanks much
Ganesan