i've never captured this oid query in mpqueryinformation handler. i
confirmed it's in the supported list and ndismedium_802_3 is returned
if queried. the weird thing is, when i used oidscope and macaddrII to
query this oid, the breakpoint for case oid = OID_GEN_MEDIA_IN_USE is
never hit. it's almost like the query was serviced and completed before
it even reached this mpqueryinformation handler. oidscope shows medium
unknown while macaddrII correctly shows 802_3. I was able to confirm
breakpoints set for the media connect status oid and other oids (even
custom ones) were hit ran correctly. stepping throu macaddrII where
it's sending the deviceiocontrol for OID_GEN_MEDIA_IN_USE didn't reveal
why my breakpoint in mpqueryinformation wasn't hit while the correct
medium was returned to the caller.

what gives? thanks.

"tcpoob" wrote:
There are several OIDs that are handled internally by NDIS,
or cached, so your driver won't see them.
This is normal.

--PA

I currently don't remember if this is actually the case but there is a
chance that the NDIS Wrapper answers the OID_GEN_MEDIA_IN_USE request
on behalf of your miniport.

If you want to verify your miniport, use the official NDISTest tool,
see e.g.

"Testing Network Drivers with NDIS the Test Tool"
http://www.wd-3.com/archive/NDISTest.htm

"Using NDISTest During Driver Development"
http://www.microsoft.com/whdc/DevToo.../NDIStest.mspx

Stephan
---
tcpoob wrote:

Correct. NDIS handles this on behalf of the driver.

-ali
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Stephan Wolf [MVP]" <stewo68@hotmail.com> wrote in message
news:1162565759.836266.76620@b28g2000cwb.googlegro ups.com...