Re: windows 2k and msndis_80211_bssilist
From: steve (a_at_b.com)
Date: 09/20/04
- Next message: Simon Hempsall: "Asynchronous ManagementObjectSearcher.Get"
- Previous message: Ivan Brugiolo [MSFT]: "Re: NIC does not "update" IP Settings after changing them"
- In reply to: Ivan Brugiolo [MSFT]: "Re: windows 2k and msndis_80211_bssilist"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 19 Sep 2004 21:56:45 -0500
man! that's great info! thanks a ton for that response. i'll see where i can
get w/ ndisuio.
thanks again!
"Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
news:OiEQeJbnEHA.3868@TK2MSFTNGP11.phx.gbl...
| The architecture works more-or-less this way.
|
| A driver, during initialization, calls ntoskrnl!IoWmiRegistration
| passing the resource ID of a binary MOF resource.
| The binary MOF resource is essentially a compressed representation
| of a MOF schema that describes what that driver exposes through
| a CIM-based instrumentation model:
| the kind of instances and the operation supported.
|
| Now, this works great for monolithic drivers.
| I think you can google this forum for an example
| of a driver exposing an object with a method that I posed some time ago.
|
| For NDIS drivers, it does not work that great, given the Miniport
| architecture.
| From the point of view of the instrumentation, NDSI.sys optimisitcally
| exposes
| the "standard" instrumentation information
| (that's why you have all of these MSNDIS_XXX_YYY classes in root\wmi),
| and then it does what it can, relaying on miniportsto
| imlement the lower bottom of the functionality.
|
| Certain classes in MSNDIS relay completely on existing Miniport codes.
| For example, you can get a network-cable-disconnect event,
| because this is a mandatory notification for NDIS 5.0 miniports.
|
| For the 5.1 Miniports, it's recomended to have the WMI-WDM
| support, but, if you write a NDIS 5.0 miniport, it's not event required.
|
| In Win2000, you are at NDIS 5.0, and, ndis.sys does not
| expose the 5.1 clases.
|
| You need to eitehr write a protocol driver a-la NDISUIO,
| sneakly use the existing NDISUIO, or google for NDISUIO
| and try to see what others have done in this area.
|
| --
| This posting is provided "AS IS" with no warranties, and confers no
rights.
| Use of any included script samples are subject to the terms specified at
| http://www.microsoft.com/info/cpyright.htm
|
|
| "steve" <a@b.com> wrote in message
| news:10kls45ld6kdh27@corp.supernews.com...
| > being new to wmi, i'm at a loss as to how to properly ask this question.
| is
| > the class "msndis_80211_bssilist" part of wmi that ships with windows
os's
| > or does a driver provider, in this instance a wireless network card,
| create
| > the class when the driver is installed. if the case is the former, is
| there
| > a wmi sdk that i can download for windows 2k that includes the class?
i'm
| > developing on windows xp pro but deployment is on a windows 2k pro
| > laptops...which don't have that class.
| >
| > i'd love to use wmi to scan for available waps and their signal
strengths
| > especially given the amount of api knowledge i'd have to acquire should
i
| > attempt to use ndis via unmanged code.
| >
| > any input is appreciated.
| >
| > tia,
| >
| > steve
| >
| >
|
|
- Next message: Simon Hempsall: "Asynchronous ManagementObjectSearcher.Get"
- Previous message: Ivan Brugiolo [MSFT]: "Re: NIC does not "update" IP Settings after changing them"
- In reply to: Ivan Brugiolo [MSFT]: "Re: windows 2k and msndis_80211_bssilist"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
