Despite the recent hamster supercharging, I still experience the following problems (on all forums):
A large percentage of the time, if I try to click on a newly created thread (example of a new thread (at the time I post this)), I get a “Web Site Not Responding” or “Gateway Timeout” error. After two or three attempts, I am able to read the thread. Also, some of the time (1 in 4, maybe) after posting a new thread myself, I get the “Web site Not Responding” error. When I reload the page, the thread is there.
I am running WinME, AOL 7.0 (whose browser I usually use to acces the boards), and IE 5.5 (which I also use).
Time of day or day of week do not seem to be factors.
That’s weird. I’ve got WinMe, IE 5.5 and AOL 7.0, too, and after the hamsters’ high colonic last week, things have been running slicker than…well, pretty slick.
Don’t you just hate it when people post, “Gee, I’m not having any problems…”
Mr. Blue Sky, I don’t get that error either. It must be an issue with your client PC. Unfortunately the staff does not have the necessary resources to troubleshoot your problem.
I post at different locations, some of which have:
[ul]
[li]Dialup 56k - home computer usually evenings[/li][li]Dialup 9.6k (yes 9.6k - work computer daytime pacific[/li][li]Broadband (TW RoadRunner) - when I babysit my daughters kids usually evening[/li][li]Broadband (AOL) when we visit another daughter usually weekends.[/li][/ul]
I have the best response on TW Roadrunner; the AOL broadband sucks as does the 9.6k*; 56k is ok, but not great. Actually, I think it’s when you post, i.e., if the board activity is high you’ll get the hourglass/whatever wait signal, otherwise you shouldn’t have any trouble. Amazingly, The * means I have great success with searching on the 9.6 at work; as to why I have no idea.
Of course, as always, YMMV.
Actually, I get the same problem at work, 3.30 to midnight EST, so maybe this is a peak hours thing. I’m pretty sure it’s not just me, because we’ve got a t1 line here.
Not a huge deal, but refreshing a million times does get annoying.
With a search, you’re not waiting for the data to be transferred; you’re waiting for the server to actually do the search. OK, there’s the information transfer, too, but it’s not significant. So you get about the same search performance on any sort of connection.
If it’s actually better on the 9.6, that might be a reflection of the time of day when you’re using that line.
