Since the upgrade I have received several errors when replying to a thread.
Its the one where IE says...
Printable View
Since the upgrade I have received several errors when replying to a thread.
Its the one where IE says...
When was the last time you rebooted? I ask because of the unique problems you are having.Quote:
Originally Posted by RobDog888
On this system I boot up every day and shut down every night. So between
Saturday and Sunday I got the error several times Sat. and Sun I got it
once. I'm running XP Pro SP1.
I'll stick with IE since FireFox can't even display the Ads correctly. :D
Tsk tsk, even my parents changed to Firefox after trying it out a while! If you don't give it a try, you don't know if it is worth using or not ;)
Seems like FireFox has its issues too.
Ad errors like in this FireFox Error thread.
:D
Yes? Its one of the very few issues I've seen and it is related to bad javascript coding, as far as I understand ;) And if it is an issue, why still not try it? A very minor issue is only an excuse not to try :)
Edit And now that I checked it, it is VBScript, not JavaScript. No wonder it isn't working ;)
I am on my system at work and no errors with IE on Win2k SP4.
Just allot slower system. :(
Maybe its IE on XP then?
Nope, that's what I have.Quote:
Originally Posted by RobDog888
Well, it only happened once Sunday, but I wasn't on the site too much that day though.
I will keep track of what I am doing and what is running along with IE and see
what happens.
Thanks.
No errors today at home! :D
Maybe just the upgrade finally settling down
If you get an error and can get any additional details, let us know.
Thanks,
Brad!
Quote:
Originally Posted by Merri
Merri -
You are now at the point of advertising FireFox. Please stop as it is a violation of the usage policy.
Brad!
Thanks Brad. I didnt get any errors last night at home. Im thinking it may
have something to do with the forums settling down from the upgrade?
Other than that I do remember that I had two or three instances of VS.NET open,
SourceOfSite, one Explorer, and three instances of IE.
If it happens again maybe I should save the debug info that the error
message asks you to send to MS?