inSSIDER 3 for Home Crashes
Hi Joel,
I've got the problem where inSSIDer 3 for Home will not run under Win 7 64-bit (Pro, all updates current) on a Lenovo X220T Tablet. Symptoms: Installed normally, per your instructions for using msiexec. Started and displayed initial screen OK. When I switched to networks, it ran for about 2 seconds, show current WiFi environment and then I got a Win 7 exception screen. I tried your suggestion of removing the cached setup folders, found 1 folder and removed it. Tried again, got same experience. I have uploaded the exception log to you, hoping that would help.
Looking for a fix as this is a very useful program and I've used prior versions to good effect in my pro-bono work for seniors in Eugene, OR.
Thanks, DVHirst
Updated 14 Jan 2014:
I've checked the WiFi card driver; it is current. I've re-installed .net from ground up and that hasn't made a difference. Following some info here, I have removed inSSider3 and reinstalled inSSider2 -- it works very nicely, thank you!
Here are the Win 7 64 SP1 event log entries re the errors I'm seeing for inSSider3:
Application:
Faulting application name: inSSIDer.exe, version: 3.0.7.48, time stamp: 0x51ba1938
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x1c18
Faulting application start time: 0x01cf10f928763e12
Faulting application path: C:\Program Files (x86)\MetaGeek\inSSIDer 3\inSSIDer.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 6b17139d-7cec-11e3-83f4-005056c00008
.net Runtime Error: (same timestamp as above error)
Application: inSSIDer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeIm pl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(System.Ob ject)
at System.Windows.Application.RunInternal(System.Wind ows.Window)
at System.Windows.Application.Run(System.Windows.Wind ow)
at StartupApplication.App.Main()
I hope this helps, meantime, I'm continuing to use inSSider2. Thanks.
Bookmarks