I've found out something which should help resolving the problem. If networks are manually refreshed in Windows Wireless Configuration Tool, the graphs in inSSIDer are also refreshed - obviously Windows forces network card to refresh data. Current workaround is that you press F5 repeatedly in WZC and observe graphs, but what we need is that devs include this function in inSSIDer so it's going to be refreshed automatically.
I've also tried to use vendor's software instead of WZC, but it's the same for me.
inSSIDer uses WZC to display the SSIDs, so this makes sense. But you are right inSSIDer should be capable of adjusting the scan rate. Different vendors scan at different intervals, and they report different RSSI values. None of it has been standardized. One fix may not work for all wireless cards.
Thinkpad T43, Windows XP, latest inSSIDer -- I have the same problem.
However, it is probably worth noting that Network Stumbler has a somewhat similar issue. It works ok when signals are relatively high, but when signals are low, it continues to report them at a constant level, even if the are no longer there. This can persist for a long time.
I have used InSSIDer for the first time yesterday, because of problem with other
Network, but it is difficult to find the location of the Jamming router when
there is long time between update of the Graf. InSSIDer can become a unique fine
program if this can bee fixed.
I just installed version 1.2.2 and am still having problems on my 32bit XP SP3 HP 8510p.
When I click "Start Scanning", inSSIDer scans multiple networks once, then displays an error message stating "'Inssider' encountered a problem.". If I uncheck "Restart 'Inssider'" and click either "Send Error Report" or "Don't send", inSSIDer will update all of the networks once, and then repeat the error message.