Since a few days some of you aren't able to see new replies in threads for some reason. I've received a few emails about it already and I've also seen a few topics started about the subject.

Nothing has changed on my end so I suspect some ISP has changed its proxy settings.

If you can't see new replies, please answer the following questions:

• Which ISP are you using? (AOL, Rogers, etc.)
  
• Which browser are you using? (Netscape 4.x, IE 6.x, etc)
  
• Does clicking the Refresh/Reload button solve your problem?
  
• If you are using Internet Explorer, does hitting CTRL-F5 solve your problem?
  

Im one of those people, it actually happens from both home and the university... and for the last 3-4 weeks, but there was a week in the middle of that that was OK.

Also i changed IE to check for newer versions of the page from automatically to every time the page is visited.

questions answered
ISP provider - home is shaw or school, the university has their own.

Browser IE ver5.5

Refresh or F-5 does solve it (actually thats usually the first thing I do when i open a new thread)

I haven't experienced the problem you describe, but I have had a refresh-related problem.
If I go back to the forum selection screen after mucking around in TD&Q, and hit refresh to see if I have any PM's, the page frequently only loads halfway and I get an error saying "download of specified resource failed". It usually takes 3-4 tries before the page successfully downloads.

I'm using earthlink and IE 5

I think it has to do with temporay internet files.

provider: mts dsl
ie 6.0
ctrl+f5 works

I've had that problem on and off for a little while now. There can be a topic as far as halfway down the list, it can say that there are (ex.) 14 replies, but when I click there are only a few. It only happens from time to time, but I have noticed it.
IP - AOL 7.0
IE - ? 5 I think
Refresh doesnt seem to work for it...
havnt tried the control f5 thing yet.

[This message has been edited by My7Fieros (edited 04-08-2002).]

On the Imac laptops at school I get this problem, and at home I did, but I just hit the refresh button and it worked.. Now I don't even have to hit refresh.

Cory