6 total posts
(NT) Marty, Grey just means the site is not yet rated.
Very true but this happens...
at sites that have displayed a specific color. Example: cNet Forums display green and cNet Downloads displays amber. When SA stops responding it shows gray for all sites even the two above.
Could it be server problems?
From what I have inspected, SA works by sending information about the website you are viewing now to the SA website/server and acquire the safety information from there. I have tried this by changing between tabs quickly and sometimes the SA indicator couldn't follow up and it remained grey or stayed in the previous color state of the previous tab. Also, when I had a slow connection, sometimes the SA indicator isn't responding and giving any feedback.
Could it be related to a SA server problem? Maybe the bandwidth usage is too high so it can't reply to many queries from multiple users quickly.
I believe the problem was with my PC...
the way the DUN was functioning....basically incorrectly.
SA seem to be very efficient at bandwidth usage. Even with DUN it turns whatever color the particular site will be even before the site is maybe 25% loaded. It doesn't slow down the progress either if you can imagine that. DUN is basically a snails-pace type of networking. As though it were trying to squeeze an ocean through an orifice the size of a pea compared to everything else. There is an incredibly small amount of bandwidth to work with and you'd think any amount of peripheral usage would slow it down but SA doesn't. Of course, Mozilla/Firefox is an efficient browser.
I think the problem with SA could have been a loading problem Mozilla/Firefox had due to a modem dial up problem. I had been having an issue at first PC startup after all the startup programs have settled in and I click on M/F. The automatic dial-up command is initialized where the homepage initializes and the modem dials. Well, the dial-up seemed to pause for about 10 to 15 seconds then I would hear the dial tone and dialing.
By this time M/F would display a "Try again" screen. I think clicking the "try again" button rather than X-ing out of M/F and reloading caused some kind of screw up.
So far I haven't seen SA malfunction and I haven't been having the dial-up problems. Don't know why "but that's my story and I'm stickin' to it".