A number of user were switched to dia, and so disabled our proxies in
whatever browsers we're using (typically firefox). Since then one of the
popular proxies has gone off-line. Coincident with that, it became impossible
for some folks to get bugster to start up.

 The workaround, it turns out is to clear the _disabled_ proxy information
form the browser dialog.

 Issues: - Should javaws even be looking at browser config files? Are they considered
           stable interfaces that can be consumed by other apps?

         - If yes, then at least the proxy enabled / disabled state needs to be
           taken into account as well.

 To reproduce:

  enter a non-proxy'ing host as the firefox proxy
select direct connection to "internet" to disable the use of the proxy
        attempt to use javaws to download and run any app.