imported_navboy
Junior Member
I'm not positive, but i think this started a week ago when i upgraded my Norton A/V 2006 to Norton A/V 2008.
IE7 in Windows XP Home SP2 ... was fine, then suddenly frequent errors when loading pages, and hitting Ctrl-F or choosing to Find from the Edit menu causes a looping script error dialog - no matter how many times you hit escape or click to Not run anymore scripts on this page, it constantly throws a new script error box up. This is on a secondary account that has Admin status - on the original Owner account there is no problem.
I saw something very similar on a forum - lots of IE7 script errors in secondary admin accounts but not on admin or owner account, but it related to Flash objects and not being able to install Flash and so i ran the reg permissions fix supplied by Adobe just in case, but it didn't work, and scanning the batch file it looks like it only affected Shockwave related reg keys, so i'm not surprised.
I also saw references to people having this problem under Norton 2005 and Norton 2006 when IE7 came out, but that it was resolved by Norton 2007.
IE7 in Windows XP Home SP2 ... was fine, then suddenly frequent errors when loading pages, and hitting Ctrl-F or choosing to Find from the Edit menu causes a looping script error dialog - no matter how many times you hit escape or click to Not run anymore scripts on this page, it constantly throws a new script error box up. This is on a secondary account that has Admin status - on the original Owner account there is no problem.
I saw something very similar on a forum - lots of IE7 script errors in secondary admin accounts but not on admin or owner account, but it related to Flash objects and not being able to install Flash and so i ran the reg permissions fix supplied by Adobe just in case, but it didn't work, and scanning the batch file it looks like it only affected Shockwave related reg keys, so i'm not surprised.
I also saw references to people having this problem under Norton 2005 and Norton 2006 when IE7 came out, but that it was resolved by Norton 2007.
