randyrives opened this issue on Nov 28, 2003 ยท 7 posts
randyrives posted Fri, 28 November 2003 at 7:02 AM
I installed Netscape and Mozilla on my systems months ago. I have been using Mozilla so I have not noticed this problem before. Now when I try and access this site with IE the pages will not load, just sits there loading forever. I noticed also this is true at work. I am running XP Home, on a Dell 1.0ghz with 512 mb Ram. At work it is Win 98. Any clues why I can't get to Rendersoity with IE now. This is the only site that I am having that trouble with.
tim posted Fri, 28 November 2003 at 7:22 AM Site Admin
Most of the folks who visit the site use IE. If you have a version greater than 4.x installed, it shouldn't be a problem. Might be you internet settings for IE/windows. Bad proxy settings under Tools|Internet Options|Connections|LAN settings might cause this problem. Can you use IE for other sites without problems? TC
randyrives posted Fri, 28 November 2003 at 2:21 PM
Yes IE works fine every where else. No problems with any other sites. No proxy settings to worry about. Just dosen't make sense.
Penguinisto posted Fri, 28 November 2003 at 4:24 PM
I've used Mozilla for quite awhile (even in Windows), and no problems (except when the site itself goes down.) IE takes a while to complete the connection to R'osity, but it does eventually connect. Using Mozilla 5.0 and stuck with IE 6 in WinXP. /P
elizabyte posted Sat, 29 November 2003 at 1:10 AM
I use NS7.1 (Mozilla based, of course) and I don't have too mnay troubles. I also have NS4.7, Opera something or other, and IE whatever is the latest installed. I do sometimes get timeouts still on Renderosity, but that's about it. bonni
"When a man gives his opinion, he's a man. When a woman gives her opinion, she's a bitch." - Bette Davis
randyrives posted Sun, 30 November 2003 at 11:45 AM
I have tried everything I can think of, but IE will not load Renderosity. I have to open Mozilla to get here.
tim posted Sun, 30 November 2003 at 5:59 PM Site Admin
Weird - did you clear your cache - sometimes cache corruption can cause this type of behavior. Tc