john - 08/13/07 09:06 AM The ideal resolution would be something like: Scenario A 1. Spark set to auto-launch and auto-login with username/password saved 2. Computer boots up on home network 3. Spark launches, but cannot connect because VPN is not running 4. Spark does some sort of 5second balloon/toast notification that it cannot connect and will keep trying 5. Once VPN is running, Spark connects just fine 6. Some sort of 6 second balloon/toast says it reconnected Scenario B 1. Spark set to auto-launch and auto-login with username/password saved 2. Computer boots up on wired network 3. Spark launches, and connects to server. 4. Wired network is unplugged, temporarily disconnecting spark 5. Spark does some sort of 5 second balloon/toast notification that it lost a connection and will keep trying 6. Wireless network is activated, and Spark reconnects 7. Some sort of 5 second balloon/toast says it reconnected Bonus points if you can turn off the balloon/toast notifications and have it silently keep trying to connect. Goal here is that no matter what network interface it's using, Spark will always try to keep reconnecting in the background.

wroot - 08/13/07 10:22 AM john, i think this issue isnt about "silent" reconnect, though it was demanded a lot and would be great to have.

LG - 08/21/07 04:34 PM I'd also give one some pea nuts if the "balloon/toast notification" would be completely missing. Changing the TNA icon to b/w or adding a red x to is the way I and many other uses except an reconnect to work.