The AutoIt stuff seemed to be based on this C/C++ code into the Native WiFi API

Hm... I'll have to explore that this evening as it just may be a better angle of attack than the one I'm currently using.

Below is the current build with working save to .ini, or registry options. The default action is to save nothing anywhere in the interest of portability.
(see attachment in previous post)

this version works well on my netbook (WinXP SP3), nice work!

Quote from: superboyac on January 31, 2011, 03:30 PM

I tried it at home on a Windows 7 pc with no wifi adapters, and it gave some kind of GUID error dialog.

Really? Weird, I just ran it here (Win7 desktop/no WiFi) and it just quietly exited. Might that have been an earlier build? I gotta remember to put build numbers in these things (bad habbit...).

If you let me know which GUID error (there's several...) it threw, I'll see if I can figure out how it got there. I still gotta work out a dead adapter check too.

I'll make sure to do that once I get home.

Quote from: Stoic Joker on January 31, 2011, 05:50 PM

Quote from: superboyac on January 31, 2011, 03:30 PM

I tried it at home on a Windows 7 pc with no wifi adapters, and it gave some kind of GUID error dialog.

Really? Weird, I just ran it here (Win7 desktop/no WiFi) and it just quietly exited. Might that have been an earlier build? I gotta remember to put build numbers in these things (bad habbit...).

Quietly exited here on my x64 W7 PC when I selected an unplugged WiFi adapter.  Selecting the LAN connection does the same as clicking on the tray icon.

Yeah, that's gonna need some polish.

Selecting the WiFi adpater when it's plugged in resulted in the same as clicking on the tray icon, (the popup window that shows what you're currently connected to - same result as LAN connection).

Am I miss-reading that? ...Or are you saying you got a connections window for a LAN adapter?

Am I miss-reading that? ...Or are you saying you got a connections window for a LAN adapter?

I get the popup window you get when clicking on the Network SysTray icon that shows what you're currently connected to.

This is when I select the LAN connection (no WiFi plugged in):


This is when I select the WiFi adapter (when it's plugged in):


If I select the LAN connection when the WiFi is plugged in then I will get the same result as attachment 2.

If I select the WiFi connection when it's not plugged in I get nothing - exits quietly.

Hope that's clearer

Ahh, I see what happened - not your mis-reading but rather my mis-writing 

The C# Native WiFi API thing didn't pan out as it's Vista/7 only (I'm not ready to give-up on XP just yet), so I'm polking around looking for options.

That's strange because they implemented it from XP SP2 onwards, well according to Microsoft....but then, what would they know

And it seems to work OK on XP-SP3 via my LANToggle program, (ie. it lists the interfaces and lets me (dis|en)able them), AutoIt of course so maybe there is a little more trickery going on.

However, I don't think it will work if the you don't use the Wireless Zero Config in Windows, (ie. the adapter uses whatever the manufacturer supplied by way of connection software).

That error message is (should only be) displayed when you hit the cancel button.

Quote from: Stoic Joker on February 01, 2011, 03:15 AM

That error message is (should only be) displayed when you hit the cancel button.

yes, that's what i did. was just testing on a PC with non-wifi component to see what happens.

Okay, my intention was to give the user feedback regarding the programs intentions. So they weren't waiting for it to do something else, and/or were not sure it had completely closed. If it is actually causing more confusion I can pull it out of the next build.

Okay, nothing real exciting at this point. But I did figure out how to get the adapter status so we can weed out the inactive ones.

I started with some MSDN example code, and beat on it until it started doing what I wanted. Now I just gotta figure out how to combine it with the rest of the project.

While I plan on releasing the code with the finished program, here's is the adapter bit I've been working for the last few days (Which is a bit embarrassing when I thing about it); everything needed to compile & run is below:

 // GetIfEntry.cpp : Defines the entry point for the console application.
//=============== Created by Stoic Joker: Tuesday, 02/01/2011 @ 6:23:11pm
#include "stdafx.h" //--------------------------------------------+++-->

 //================================================================================================
//-------------+++--> Strip \DEVICE\TCPIP_ Off of wszName to Get the Adapter's GUID For Comparison:
void StripOutGUID(WCHAR *szGUID, WCHAR *wszName) { //---------------------------------------+++-->
	WCHAR *p; // Walk the string to find the GUID opening '{' character. Sure There
	int i=0; // Are Easier Ways to do This ... But This Way I Avoid Language Issues.

  p = wszName;
  while(*p != '{') {
	  *p++; i++;
  }

  wsprintf(szGUID, L"%s", p); 
}
 //================================================================================================
//------------------------+++--> Get Lst of Network Interfaces Available on Machine for Comparison:
BOOL GetAdapters(WCHAR *szTarg) { //-----------( Much of This is From the MSDN )------------+++-->
	PMIB_IFTABLE ifTable; // Declare and initialize variables.
	PMIB_IFROW pMibIfRow;
	DWORD dwSize = 0;
	DWORD dwRetVal = 0;

  // Allocate memory for our pointers.
  ifTable = (MIB_IFTABLE*) malloc(sizeof(MIB_IFTABLE));
  pMibIfRow = (MIB_IFROW*) malloc(sizeof(MIB_IFROW));

   // Before calling GetIfEntry, we call GetIfTable to make sure there are entries to get.
  // So... First, make an initial call to GetIfTable to get the necessary size into dwSize
  if(GetIfTable(ifTable, &dwSize, 0) == ERROR_INSUFFICIENT_BUFFER) {
	  GlobalFree(ifTable);
	  ifTable = (MIB_IFTABLE *) malloc (dwSize);
  }
  // Then make a second call to GetIfTable to get the actual data we want.
  if((dwRetVal = GetIfTable(ifTable, &dwSize, 0)) == NO_ERROR) {
	  if(ifTable->dwNumEntries > 0) {
		  for(UINT i=1; i<= ifTable->dwNumEntries; i++) {
				pMibIfRow->dwIndex = i;
			  if((dwRetVal = GetIfEntry(pMibIfRow)) == NO_ERROR) {
				  if(pMibIfRow->dwType == MIB_IF_TYPE_ETHERNET &&
					  pMibIfRow->dwAdminStatus == MIB_IF_ADMIN_STATUS_UP) {
						  WCHAR szGUID[GEN_BUFF] = {0};
					  printf("\tDescription: %s\n", pMibIfRow->bDescr);
					  printf("\twszName: %S\n", pMibIfRow->wszName);
					  StripOutGUID(szGUID, pMibIfRow->wszName);
					  if(wcscmp(szGUID, szTarg) == MATCH) {
						  printf("\tGUID: %S <--+++--> MATCHES REQUESTED ACTIVE TARGET ADAPTER!!!\n", szGUID);
					  }else{
						  printf("\tGUID: %S <-+-> Is Active, But Not the One We're After.\n", szGUID);
					  }
					  printf("\tReceived %d, Sent %d\n", pMibIfRow->dwInOctets, pMibIfRow->dwOutOctets);
					  printf("\t\tNext...\n\n");
				  }
			  }
		  }
	  }
	  GlobalFree(ifTable);
	  return TRUE;
  }
 return FALSE;
}
 //================================================================================================
//--------------------------------------//---------------------------+++--> Console Program Main():
int _tmain(int argc, _TCHAR* argv[]) { //---------------------------------------------------+++-->
  if(argc < 2) {
	  printf("\n\n\tERROR: No GUID Specified, Exiting!\n\n");
	  return 0;
  }else{
	  printf("\n\n\tSearching for GUID: %S\n\n", argv[1]);
  }
  if(!GetAdapters(argv[1])) printf("\tGetIfTable failed.\n");
 return 0;
}

 // ============================================= STDAFX.H <-> Header File Below This Line!
// stdafx.h : include file for standard system include files,
// or project specific include files that are used frequently, but
// are changed infrequently
//

#pragma once

#ifndef _WIN32_WINNT		// Allow use of features specific to Windows XP or later.                   
#define _WIN32_WINNT 0x0501	// Change this to the appropriate value to target other versions of Windows.
#endif

#define GEN_BUFF   128
#define MATCH		 0

#include <stdio.h>
#include <tchar.h>

// TODO: reference additional headers your program requires here
#include <Windows.h>   //--+++--> Also Required by GetIfEntry():
#include <Iphlpapi.h> //---+++--> Required by GetIfEntry():
#pragma comment(lib, "Iphlpapi.lib") //-++-> ^See Above^:

...Crap, I just realized that int i doesn't actually do a damn thing... *Sigh*

It's really just different levels of the same thing. The original code used a registry key to enumerate the physical adapters on the machine (and was right on the edge of Quick-N-Dirty). On my dev machine it found 1 Physical Adapter.

The code above is the much more detailed Network Interface list, which is where the more detailed state & status info is kept. On my dev machine it found (roughly) 20 Network Interfaces.

The nested if's around the for(...) loop are narrowing the list down to less than a dozen items that can/will then be compared (GUID-to-GUID) to the Physical Adapters list to eliminate the disabled adapters from the Drop-Down menu.

From a (Windows) programming standpoint, these kind of shenanigans are normal...

Note: Granted using the WiFi API 4wd mentioned above would have been a more elegant solution (simpler code & faster to pound out), however it also doesn't run on (isn't available in) Windows XP ... Which is (after all) or target platform.

Note: Granted using the WiFi API 4wd mentioned above would have been a more elegant solution (simpler code & faster to pound out), however it also doesn't run on (isn't available in) Windows XP ... Which is (after all) or target platform.

Sorry if I seem to be pushing a dead donkey but I'm still not clear here, everything I've read on the Native WiFi API says it's available from XP SP2, (SP2 via patch, incorporated into SP3), onwards, (when Wireless Zero Config was introduced - I would have thought most people would be running SP3 by now), the only function not available to XP seems to be WlanGetInterfaceCapability according to MSDN.

So I would have thought that their example code for WlanEnumInterfaces would be just what's needed, (bearing in mind their note about GUIDs at the bottom which seems to make any program more convoluted than it needs to be).

I'm just trying to understand why it wouldn't run for you on XP but feel free to call me an idiot - I've been called worse  

Aahh...I see.....

But, (you knew that was coming didn't you), prior to XP SP2 doesn't that mean that Wireless Connection Manager, (or the window you get after hitting View Wireless Networks, whatever it's called), wasn't available?

ie. Prior to XP SP2, didn't you have to use whatever software the manufacturer provided with the adapter and as such won't what you're trying to do not work anyway?

Sorry, it's been a while since I saw anything but XP SP3 around.

Thanks for clarifying - I'll leave you to you nutz and futz now