NetStumbler.org Forums

Hi!

I used the autosave feature of the ministumbler and now all of my files seem to be corrupt. I do not know if the auto save feature is the reason but it might be. Anyway, I tried the NS1 file recovery program (http://www.frontiernet.net/~beakmyn/ns1kfrac.htm) but it crashes when I try to fix the files.

Anyone that could help me fix my files?

I uploaded the files here: http://www.magnusottosson.se/downloads/files.zip

Please help!

kaksi wrote:Hi!

I used the autosave feature of the ministumbler and now all of my files seem to be corrupt. I do not know if the auto save feature is the reason but it might be. Anyway, I tried the NS1 file recovery program (http://www.frontiernet.net/~beakmyn/ns1kfrac.htm) but it crashes when I try to fix the files.

Anyone that could help me fix my files?

I uploaded the files here: http://www.magnusottosson.se/downloads/files.zip

Please help!

From what I can tell so far, is that some how your system is inserting null characters into the SSID which is inconsistent with what the field size value is reporting.

Example in your gbg4.ns1 file the first SSID is "belkin54g" which is 9 characters long and is reported as 9 characters. However in your case the SSID is being saved as "b.e.l.k.i.n.5.4.g." the periods between characters represent nulls your system is adding, which is increasing the physical length of the SSID from 9 to 18 characters.
Because NS1 files use variable length fields its very important that the field length value be consistent with the actual field data or the NS parser or any other parser will fail when attempting to read the file.

I should be able to fix, but you need to figure out why the null are being inserted into the SSID.

Here's your files back.

I broke them down to one AP/network per ns1 file and repaired the SSIDs.

Merge them back together using NS's merge function found in the "File" menu. You can select more than one at a time, but I don't recommend more than 3 at a time or you'll get NS format errors. However if you do get a format error, try loading the AP file by itself. If the error persist, then its a bad file which can't be used.

You still need to find out what is causing your file corruption, you might try this link as a starter.

Ministumbler isn't the problem. It's Activesync. Turn off file conversion (in Activesync) when transferring the files from your device to your computer. I thought there was an option in my program NS1kfrac to fix this (or that it did it automagically). but I'll see if I need to modify for Activesync transmorgified files.



Edit:

Yep I reported on this a while back
http://netstumbler.org/showthread.php?t=15361&highlight=ministumbler+null

beakmyn wrote:

http://netstumbler.org/showthread.php?t=15361&highlight=ministumbler+null

That's the link I meant.

Move the ns1 from PPC to PC, Open ns1 file with netstumbler then save as (same name) Fixes the problem.
Just to say EXCELLENT PROGRAM!