http://blogs.msdn.com/greggm/archive/2004/08/23/218958.aspxMonica wrote a very nice document for this feature. A few quick highlights: Internet explorer defaults to having script debugging disabled. IE also likes to disable script debugging when you install a new version of IE (example: XP SP2). In IE, go toen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/greggm/archive/2004/08/23/218958.aspx#218959Mon, 23 Aug 2004 20:31:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:218959greggm's WebLoghttp://blogs.msdn.com/greggm/archive/2004/08/23/218958.aspx#218967Mon, 23 Aug 2004 20:38:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:218967greggm's WebLoghttp://blogs.msdn.com/greggm/archive/2004/08/23/218958.aspx#230874Fri, 17 Sep 2004 15:44:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:230874pkgerhart@aol.comWhen tring to log onto AOL, I get many screens that state a script error and Just-In-Time notices. <br> <br>In browsing,disable script debugging is checked but the notices still appear. <br> <br>What else can I do? <br> <br>Perry Gerharthttp://blogs.msdn.com/greggm/archive/2004/08/23/218958.aspx#230950Fri, 17 Sep 2004 17:56:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:230950Gregg MiskellyWhat kind of exception are you getting?http://blogs.msdn.com/greggm/archive/2004/08/23/218958.aspx#231747Mon, 20 Sep 2004 14:17:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:231747SmellyThe only thing I've found that works fairly consistently is the 'debugger;' statement. If you've got a lot of script in different blocks and files sometimes this is the only way to get the debugger to stop where you want, especially if your script is in a .htc! Even then, you're not always guaranteed the debugger will be pointing at actual code when it stops. <br> <br>I recently finished a lengthy complicated web application project and the script debugger was probably the one thing that caused me the most grief, hair pulling and cursing throughout the life of that project.