Maybe i misunderstand but that sounds like a security issue just hooking up to first available wifi network.
Is it to much to ask for that if you change network the user have to acknowledge it, by actively doing so.
Could you not just run the wifi tool when you want to connect to a new network it will then update the wifi.db to reflect that.
Unless you know what you are doing dont edit the wifi.db your self leave it up for wifi tool.
anyway i dont know if we are talking past each other but maybe simplified functionality description is needed for a better surgestion.
[/quote]
I think we are somewhat getting sidetracked and talking past each other.
By first available network, I meant first network which I've at some point indicated a willingness to use, although admittedly I would want to be informed whether I'm being connected to a secure or open network and there should be a preference for secured networks if/when they are available.
But my current problem has nothing at all with wishing to change networks. When I sit in the Starbucks there are maybe 15 networks which get listed. All but two (sometimes three) are properly secured. One which isn't secured also can't be connected to as there is no DHCP server and/or they require a specific MAC address to connect. The other two are both run by Starbucks and have identical SSID names "BTOpenNetwork" (or something like that -- which perhaps may be a problem as I though SSID names had to be unique... but it doesn't seem to completely cripple their network) and both operate on channel 11. When I am in Starbucks, this is the only one I can connect to and I'm willing to accept the risk that this is an open network.
However, when I am using Tinycore to connect to BTOpenNetwork, the connection while valid and even useful is very unstable. I am silently disconnected every few minutes and must manually reconnect. With other operating systems (e.g. Puppy Linux), the network manager (Frisbee) quickly realizes and reconnects me without my ever needing to take any action (and I know it is the network manager because I see occasional pop-ups telling me it is doing this).
This is the only problem I am presently looking to solve.
(For whatever it is worth, I have verified that using wifi somewhere else, where I can get on a less trafficed private server, Tiny Core does not have any problem maintaining the connection, so I think that rules out driver problems.)