On Nov 12, 2:03 pm, Benoit Renard
Yet RC2 and the final version are identical, so it doesn't sound like it
came from a change in SeaMonkey (as there was none).
Yes that makes sense.
If you want to check out what is going on on the McAfee side, go to
Site Advisor Service conflicts with
On Nov 11, 3:53 am, Martin Freitag prof_nosp...@quantentunnel.de
wrote:
psuatocobra schrieb:
I'm new to Google Groups mozilla.support.seamonkey . How does this get
investigated? I'm not taking sides. I'd just like a definitive answer.
If there's a bugreport on bugzilla chances are high
On Nov 9, 12:28 pm, S. Beaulieu seree...@netscape.net wrote:
William Morrison wrote:
They found that McAfee site adviser is causing a conflict, in msconfig
under services uncheck the McAfee site adviser, reboot and copy/cut
paste should work fine.
I also discovered that the Site Advisor
SP3 and want to give SM 2.0 a try. But, the prospect of
being able to run both SM 1.1.x SM 2.0 for at least a while is
desirable.
Thanks,
---psuatocobra
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org
4 matches
Mail list logo
