i've done web development for quite some time, and in testing, i've been used to the "errors on page, do you wish to keep running scripts on this page" error, and clicking yes, after installing visual studio or other development application that wonderful box changes, and you get stuck with cancel or debug in MS interdev ( yay *gag* ) if anyone would like to know HOW to return your spiffy browser page error to it's prior state ( and not the ruddy debugger ). The main reason why i researched, and pestered MS about this is when accidentally clicking the OK that sends the script to debug, if you "oops" the click and then close the debugger/interdev it will in turn close the window that contained the script, and that becomes very annoying.
Took a little arm twisting from the experts @ MS. On installation of any MS dev program you get a copy of the MS debugger and interdev"lite", the files responsible for the new error handling on IE's side.
Find all instances of comcat.dll v5.x+ (typically shared folder in program files and system32 in windows) and roll it back to the pre v5.x version you can find in your search results, typically v4.71 ... side note, be SURE to also rollback the one located in the $NTuninstall<Blah> folders in system32 these are the files windows immediately will use to restore the new comcat.dll file as soon as the prior version is pasted to rollback. (don't forget to rename the v5.x version and archive it somewhere, just in case.)
After that you're back to your standard Yes/No on "continue running scripts" vs debug and close window
documentation just incase anyone feels this is a farce :
ps took em a month(nearly daily communication) to chase this solution down
( S for $ for $piders )
Took a little arm twisting from the experts @ MS. On installation of any MS dev program you get a copy of the MS debugger and interdev"lite", the files responsible for the new error handling on IE's side.
Find all instances of comcat.dll v5.x+ (typically shared folder in program files and system32 in windows) and roll it back to the pre v5.x version you can find in your search results, typically v4.71 ... side note, be SURE to also rollback the one located in the $NTuninstall<Blah> folders in system32 these are the files windows immediately will use to restore the new comcat.dll file as soon as the prior version is pasted to rollback. (don't forget to rename the v5.x version and archive it somewhere, just in case.)
After that you're back to your standard Yes/No on "continue running scripts" vs debug and close window
documentation just incase anyone feels this is a farce :
ps took em a month(nearly daily communication) to chase this solution down
( S for $ for $piders )![[thumbsup2]](/data/assets/smilies/thumbsup2.gif "[thumbsup2] [thumbsup2]")
DreX