try STL::Stack class for same! "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture cheers, Alok Gupta VC Forum Q&A :- I/IV Support CRY- Child Relief and You

Hi Fibers, here are my understandings about this issue: 1. The fastest promised "response time" for updated information that you can get using NDIS API will be around 6 seconds. 2. If you need faster response time then this - you need to work wuth wireless NIC's drivers. 3. In order to check yourself, you may do some tests and from time to time switch the power of the transmitting AP on/off. when you switch it off - you will know exactly when the reading of the relevant AP should vanish from the list. according to my tests, I could not make them disappear fast, i.e. the reading of the AP that is no longer on air, kept reporting as if it was on air, sometimes for about 1-2 minutes (!!!) after the AP was turned off. the rx database was not flushed and held old information. This, of course, is not what I wanted. The scan command, which should have flush the RXed AP's database, surely did not work. I think that this problem is due to incompatibility of the Wireless card's vendors with NDIS requirements. If you find any wireless card (NIC) that the NDIS SCAN command actually cleans the old data from the database, using NDIS interface, please inform me with the exact model of the wireless NIC. If you find any wireless NIC that you can access it's Firmware and control it using your code (bypass the NDIS level), and that can do it with no cost (no need to pay for information on how to do this), please update me as well with the wireless card's model and brand, and with relevant sample code. As a matter of fact, I think that in order to achieve fast response, this is that direction that you should focus on. Any help will be very much appreciated ! In second thought, please update us anyway :-) Thanks a lot and good luck. -- Amit.

NDIS_802_11_BSSID_LIST* m_pBSSIDList; m_pBSSIDList = (NDIS_802_11_BSSID_LIST *) VirtualAlloc (NULL, sizeof (NDIS_802_11_BSSID_LIST) * NUMBEROF_BSSIDS, MEM_RESERVE | MEM_COMMIT, PAGE_READWRITE) ; memset (m_pBSSIDList, 0, sizeof (NDIS_802_11_BSSID_LIST) * NUMBEROF_BSSIDS); oidcode = OID_802_11_BSSID_LIST_SCAN; DeviceIoControl (m_handle, IOCTL_NDIS_QUERY_GLOBAL_STATS, &oidcode, sizeof(oidcode), (ULONG *) NULL, 0, &bytesreturned, NULL); Sleep (6100); // According to the documentation the result of the scan should be valid after 6 seconds. // The original line was delay of 2000 mSec. find out why... //Sleep (2000); memset (m_pBSSIDList, 0, sizeof (NDIS_802_11_BSSID_LIST) * NUMBEROF_BSSIDS); // @@@ why is this required ??? oidcode = OID_802_11_BSSID_LIST; if (DeviceIoControl( m_handle, IOCTL_NDIS_QUERY_GLOBAL_STATS, &oidcode, sizeof( oidcode), ( ULONG *) m_pBSSIDList, sizeof( NDIS_802_11_BSSID_LIST) * NUMBEROF_BSSIDS, &bytesreturned, NULL) == 0) { // List failed return NULL; } else { return m_pBSSIDList; }

Hi, Can anyone help me here ? I would really appreciate getting ideas for my problem. -- Amit.