Paul B. Gallagher wrote: > > If I got cleared in 12 hours and it took you a week, maybe you should > switch to my method. Have someone with a Norton product install it, then > report the snag as an end user. >
Fwiw, *I* have the product as well, because it came with my laptop purchase, I hate it but chose not to fight the uninstall-get-a-better-product dance yet. I tested this method in the past, before I found their whitelist page, the problem is that doing this method, only clears it for *me* not *you* it takes a "significant" number of reports for them to clear it for others, how many they never say. And it is ONLY that install, e.g. * Installed SM <x.y> * Ran SM <x.y> * Norton flagged and quaranteed for this issue * Submitted false positive, un-quaranteened file * Exited SM * Uninstalled SM * re-installed SM <x.y> [same ver] * Ran SM <x.y> * Norton *again* flagged and quaranteed despite my marking it to ignore that file. * -- This is part of why I noticed that Norton modifies the file slightly when it restores it, presumably to add an internal signature of some sort that doesn't really change how the file behaves, but does modify the sha-sum and causes the hotpatching used by our update system to break Also since each LOCALE/VERSION is different it adds up in terms of human effort to even do that. -- ~Justin Wood (Callek) _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
