Search:

Huh, I wrote that error message more than a year ago and never noticed it was misspelled. :D

On startup, inSSIDer tries to save a dummy setting value to check if it can save user settings later....

Strange, because I just installed inSSIDer on my Windows 8 Pro (32-bit) and it works perfectly.

Give this version a try and see if it fixes your problem. :)

If you wouldn't mind uploading your GPX file somewhere, I'll take a look at it and see if I can determine the problem.

Hi,

I've attached a tool I just wrote that will convert inSSIDer's GPX logs into NetStumbler NS1 files.
You can drag your gpx files onto the exe and it will convert them for you.

Max Rate is the maximum data rate that is supported by the access point.

@Stephen:

.NET 3.5 uses a different runtime version than .NET 4. v3.5 uses the v2.0 CLR, while .NET 4.0 uses the v4.0 CLR.
If a program is compiled for v3.5, it requires .NET 3.5 to be installed....

inSSIDer requires a WiFi adapter to be present on the local machine. Using a netbook should work well.

I would recommend adding information about starting the wlan services. See here: http://www.metageek.net/forums/showthread.php?4832-ERROR-inSSIDer-requires-the-WLAN-AutoConfig-service

Yes, inSSIDer requires a wireless adapter to show access points. It cannot use a wired Ethernet connection to show access points.

The Lat and Lon values are the location at which inSSIDer received the strongest signal from an access point. The only way to determine where the access points are is to walk around and find the...

You are correct. inSSIDer only displays the information that it gets from your WiFi adapter.

P.S. I love the thread title :)

On Windows XP, inSSIDer communicates with the NDIS driver using DeviceIOControl. All code relating to that should be in the MetaGeek.IoctlNdis project.

Yeah, I may just answer ;)

Gene,

The InterfaceManager.LastInterface is saved in the ScanController.Interface property setter. The LastInterface property takes the last saved interface ID and...

Hello,

Would you please download and install the .NET framework 3.5 SP1 to see if it resolves your issue?
You can find it here: http://www.microsoft.com/download/en/details.aspx?id=22

I think the linux version was broken a while back with an update to some network manager component in most linux distros.

Have you tried changing the WaitAny(WaitHandle[], Int32) to WaitAny(WaitHandle[], Int32, boolean) and set the last parameter to false?

I think what they mean is that Windows be in charge of managing your WiFi connections, not meaning that you have to a Microsoft driver.

I could see using it to find a particular client to see show much air time it's using/how many packets/etc.

Trust me, it wasn't easy. :D

Oh, sorry, I didn't build a binary for the last fix. I only committed the source code to my repo.
Fixed! There should be a binary for version 2.A.8.0314 up in the downloads section of my repo.

That would be because...I forgot to push it to my github repo :o
I just resolved that after reading your post. :)

Here you go: https://github.com/downloads/TylerAdkisson/inSSIDer-2/inSSIDerGPXStats_3-6-12.zip
The program is written in C#, FYI.

I'd like to be able to drag pcap files onto EyePA and have it open them.

Ok, well, the problem was that the NMEA sentence parser was assuming that the longitude value from the GPGGA and GPRMC sentences were going to have a whole-number part that was 5 characters long....