Intermittent Problem Starting Wirelessmon

[dozment]

I tried yesterday while near an AP, and the new version worked flawlessly. It also closed properly when I shut it down. On the earlier version I was getting a similar error every time I shut down. I tried today outside the presence of an AP, and it failed. The contents of the log file follows:

0.000s - DEBUG: Starting...
0.000s - DEBUG: WirelessMon V1.0 Build: 1004-1
0.000s - Debug: OS 5.1.2600.2 (2.0)
0.010s - DEBUG: New Instance of WLAN802_11 class initialized successfully
0.010s - DEBUG: Service control manager opened
0.010s - DEBUG: Network Driver Interface service opened
0.010s - DEBUG: Network Driver Interface started
0.010s - DEBUG: Network Card Service has been started successfully
0.030s - DEBUG: Tab Control has been created successfully
0.030s - DEBUG: Windows major version: 5 windows minor version:1
0.040s - DEBUG PERF: Found perf functions in DLL
0.040s - DEBUG: Graphic has been Initiailized successfully
0.060s - DEBUG: InitCounter entry
0.070s - DEBUG: All strings Wireless-G Notebook Adapter v.2.0 - Packet Scheduler Miniport
0.080s - DEBUG: Wireless-G Notebook Adapter v.2.0 - Packet Scheduler Miniport
0.080s - DEBUG: Intel[R] PRO_100 VE Network Connection - Packet Scheduler Miniport
0.080s - DEBUG: MS TCP Loopback interface
0.080s - DEBUG: InitCounter exit
0.080s - DEBUG: Begin to Enumerate Devices
1.222s - Debug: Network card 1: VMware Virtual Ethernet Adapter for VMnet2 \DEVICE\{6CABF863-460E-434D-9267-4DE7657D8CB3}
1.222s - Debug: Network card 2: VMware Virtual Ethernet Adapter for VMnet8 \DEVICE\{DC1E41EC-1A2D-4194-88F9-1C9DA726869F}
1.222s - Debug: Network card 3: VMware Virtual Ethernet Adapter for VMnet1 \DEVICE\{AC0DF2F8-2B1A-417B-9157-08F37F53BBE4}
1.222s - Debug: Network card 4: Wireless-G Notebook Adapter v.2.0 - Packet Scheduler Miniport \DEVICE\{745A26FB-1C10-42E7-8923-C69D2AAA965C}
1.232s - Debug: Network card 5: Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport \DEVICE\{452B3809-E8BD-4B1F-B2AE-535CF5583009}
1.232s - DEBUG: Network card 4 has been selected by string parse
1.232s - Debug: successfully opened this device: \DEVICE\{745A26FB-1C10-42E7-8923-C69D2AAA965C}
1.232s - DEBUG: GetSSID function return OK
1.232s - DEBUG: return ssid length: 1
1.242s - DEBUG: MAC Address read OK
1.242s - DEBUG: Signal strength read OK
1.242s - DEBUG: txpower, antenna, auth mode read OK, Begin to find access point nearby
1.242s - DEBUG: SetAccessPoint entry
1.242s - DEBUG: Get AP list information
1.252s - DEBUG: GetAPList entry
1.252s - DEBUG: sent m_dwIOCTL_NDISUIO_SET_OID_VALUE
1.252s - DEBUG: sent m_dwIOCTL_NDISUIO_QUERY_OID_VALUE

I tried again near an AP, and it worked once again. I can't help but wonder if it is failing to start when it can't detect a single AP.

I hope this helps. Today is the end of my trial. Unless there is a way to extend the trial I will not be able to test further. If this can be resolved I do plan to purchase a licensed version. If you would like for me to test further you can contact me at dan@ozment.net to help me extend the trial period.

Regards,
Dan

[Tim (PassMark)]

There is a new build of WirelessMon that has had a few changes made and some extra debugging output added, http://www.passmark.com/ftp/wirelessmon1.1004-1.exe.

Could you please try this version out with the DEBUGMODE parameter and if it crashes please send us the WirelessMonTestLog.txt file.

Thanks.

[dozment]

Ok, it finally happened again. I thought it heard us talking, and decided it was going to act properly!

The error signature section of the message says:
AppName:wirelessmon.exe
AppVer 1.0.1004.0
ModName: ntdll.dll
ModVer:5.1.2600.2180
Offset: 00011639

From the technical information link, the Exception Information:
Code 0xc0000005
Flags 0
Record 0
Address 0x000000007c911639

It also refers to an xml file that it created in a temp directory. The contents of that file follow...

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="WirelessMon.exe" FILTER="GRABMI_FILTER_PRIVACY">
</DATABASE>
.....

Let me know if you need more info.

Thanks!

[David (PassMark)]

Yes, you're right, the log terminates abruptly. We'll investigate it.

Those "Generic" errors are in fact almost never generic.

There is usually a message like, "To see what data this error contains, _Click_here_"

It is the information that appears after you click which is interesting. In particular there might be an address like, 0x00451234 which is important.

----
David

[dozment]

The log file was from a failed attempt. It worked when I was at home last night within range of my access point. Today, in the area where I am working it initially worked, failed yesterday and again today. I am connected to an access point right now. I brought the app up again to try to generate the error, and it worked.

The error was a generic Windows XP "the application is not working properly, click here to send info to us" kind of message. I couldn't find details of a dll that died or anything useful in the message. I will capture it next time I see the error, and post the exact message here.

Thanks!

The trace you include in your post just shows that everything worked as expected on that attempt.

It would be good if you could post the same log file from a attempt that had the error.

Also if you could give us the exact text of the error message. That might help.

----
David

[dozment]

I'm using wirelessmon in trial mode, and would like to register it. However, I am having intermittent problems getting it to start. I'm using Windows XP Pro and the current published version of wirelessmon. When I start it and tell it to run in trial mode I get a "wirelessmon.exe has encountered a problem" error. I used it successfully yesterday. In fact, I'm using my wireless card at a free hotspot that wirelessmon helped me find yesterday.

I was able to start it in debug mode based on another post here. Following is the contents of the debut file:

0.000s - DEBUG: Starting...
0.010s - DEBUG: WirelessMon V1.0 Build: 1004
0.010s - Debug: OS 5.1.2600.2 (2.0)
0.010s - DEBUG: New Instance of WLAN802_11 class initialized successfully
0.010s - DEBUG: Service control manager opened
0.010s - DEBUG: Network Driver Interface service opened
0.010s - DEBUG: Network Driver Interface started
0.010s - DEBUG: Network Card Service has been started successfully
0.030s - DEBUG: Tab Control has been created successfully
0.040s - DEBUG: Windows major version: 5 windows minor version:1
0.040s - DEBUG PERF: Found perf functions in DLL
0.040s - DEBUG: Graphic has been Initiailized successfully
0.120s - DEBUG: Begin to Enumerate Devices
1.512s - Debug: Network card 1: VMware Virtual Ethernet Adapter for VMnet2 \DEVICE\{6CABF863-460E-434D-9267-4DE7657D8CB3}
1.512s - Debug: Network card 2: VMware Virtual Ethernet Adapter for VMnet8 \DEVICE\{DC1E41EC-1A2D-4194-88F9-1C9DA726869F}
1.512s - Debug: Network card 3: VMware Virtual Ethernet Adapter for VMnet1 \DEVICE\{AC0DF2F8-2B1A-417B-9157-08F37F53BBE4}
1.512s - Debug: Network card 4: Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport \DEVICE\{452B3809-E8BD-4B1F-B2AE-535CF5583009}
1.522s - Debug: Network card 5: Wireless-G Notebook Adapter v.2.0 - Packet Scheduler Miniport \DEVICE\{745A26FB-1C10-42E7-8923-C69D2AAA965C}
1.522s - DEBUG: Network card 5 has been selected by string parse
1.522s - Debug: successfully opened this device: \DEVICE\{745A26FB-1C10-42E7-8923-C69D2AAA965C}
1.522s - DEBUG: GetSSID function return OK
1.522s - DEBUG: return ssid length: 15
1.522s - DEBUG: MAC Address read OK
1.532s - DEBUG: Signal strength read OK
1.532s - DEBUG: txpower, antenna, auth mode read OK, Begin to find access point nearby