Hope you all can find this usefull (not Vista compatible). Zip only contains source, no compiled .EXE.
No error handling as yet.
Need to be connected to a wireless network for stats (as there is no error handling yet).
All stats are retreived from WMI.
Stats received include:
Wireless Adapter name,
Signal Strength in DB,
Signal Strength as a bar (Excellent, Good, Poor, etc),
Signal Strength as a percentage (to use a progress bar),
Current connected SSID,
MAC of AP,
Frequency of AP,
Channel of AP,
Connection Status,
Speed (in Mbps),
Network type.
(Still in the process of adding listbox at bottom showing available wireless networks, noticed that MsNdis_80211_BssiList does not work because that uses old structures where the SSID was fixed length, now there are new structs where the SSID is variable length, that is why the first AP info shows but all others are garbage when using BssiList call). See here regarding getting list of available networks,
Mars base one Username: Jim Davis Password: yCrm33
Posts
1,284
Re: Wireless Stats (for connected AP)
Oh yes, ok it really works!
The only problem is that you didnt use Option Explicit, so you cant see that you just use temporary and undefined variables and objects. You also create a new object for each WMI calling, that im not sure you have to.
It may be better to create only one WMI object at startup, but you can execute the queries, by using this primary (and only) wmi object.
You may also want to set the refresh rate to 500 or 1000. Thats fairly enough for refreshing the informations. Now it ruin up things on me, it causes around a 30% cpu usage, on my Intel E6750.
Its still work in progress, definately not the final result.
I am a firm believer in declaring my variables, I just wanted to knock something together quickly.
I will post a new updated version soon (in the mean time I think I am actually going to solve the available networks issue, I am making calls directly to the driver using NDIS.... so its exciting times). The new version will probably not use WMI at all, and totally be based on NDIS, which I am sure will help many folks on VB6.
I have just used Ndis driver call, through VB6 and received my first successful results (thus communicating directly with the driver and totally avoiding WMI). So far its only RSSI (signal Strength), but its a start.
I am getting my way around "deviceiocontrol" and Ndis queries.
Reply With Quote
I am ecstatic.... 