What steps will reproduce the problem?
1. Install inSSIDer from http://www.metageek.net
2. Make sure all browsers which are running (and that maybe using the
'location' funtion) are switched off. You may need to reboot the machine if
a browser has already been run as this seems to be a "modal" issue. I have
discovered that disabling and re-enabling the network card in device
manager fixes the issue.
3. Start inSSIDer and start scanning using the wireless network card. Leave
inSSIDer scanning.
4. Start Chrome and access a webpage which uses the 'location' function
(Google Latitude via iGoogle).
5. inSSIDer should error and crash.
What is the expected result?
Application Error
Unable to continue scanning with selected interface: Unable to open device
\\.\{FFB5AE4A-197E-45C0-B7FB-3AE1486539F5}. Win32Error = 2
This issue occurs with certain other software as well (PTC Pro/ENGINEER CAD
software) however the example below is easier to reproduce. The network
cards are not "crashed" completely but the way in which the 'location'
function is accessing them causes the software which is accessing them at
the time to fail. Pro/ENGINEER uses the MAC address of the network card for
licensing and inSSIDer uses the wireless network card for scanning (obviously).
Original issue reported on code.google.com by samdicki...@gmail.com on 29 Apr 2010 at 3:39
Original issue reported on code.google.com by
samdicki...@gmail.comon 29 Apr 2010 at 3:39