<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mercurythread &#187; google chrome</title>
	<atom:link href="http://www.mercurythread.co.uk/blog/category/search-engines/google-search-engines/google-chrome-google-search-engines-search-engines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mercurythread.co.uk</link>
	<description>The personal website of Michael Briggs : Professional SEO and Internet Geek</description>
	<lastBuildDate>Tue, 08 Nov 2011 22:31:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Google Chrome &#8211; Crashing with Symantec (Part 2)</title>
		<link>http://www.mercurythread.co.uk/blog/google-chrome-crashing-with-symantec-part-2/2008/09/</link>
		<comments>http://www.mercurythread.co.uk/blog/google-chrome-crashing-with-symantec-part-2/2008/09/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 15:39:29 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[google]]></category>
		<category><![CDATA[google chrome]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[google broser]]></category>

		<guid isPermaLink="false">http://www.mercurythread.co.uk/blog/?p=78</guid>
		<description><![CDATA[As mentioned in previous post you can turn off the sandboxing in Google Chrome to stop it conflicting with Symantec Endpoint Protection. However this is really a bit of a hack and as the sandbox is one of the cool things in Google Chrome turning it off isn&#8217;t really a great solution. As sandboxing means [...]]]></description>
			<content:encoded><![CDATA[<p>As mentioned in previous post you can <a href="http://www.mercurythread.co.uk/blog/google-chrome-crashing-with-symantec/2008/09/03/trackback/" target="_blank">turn off the sandboxing in Google Chrome</a> to stop it conflicting with Symantec Endpoint Protection. However this is really a bit of a hack and as the sandbox is one of the cool things in Google Chrome turning it off isn&#8217;t really a great solution. As sandboxing means if the page running in one browser tab crashed the whole browser doesn&#8217;t crash. By using the previous hack you&#8217;re simply going to experience FirFox style crashes with your nice new Google browser.</p>
<h2>The Elegant Solution to fix Google Chrome</h2>
<p>The best solution would be to get rid of Symantec altogether and get a better anti-virus system &#8211; I don&#8217;t like it in the first place. But this isn&#8217;t going to be appropriate for everyone so instead&#8230;</p>
<p><span id="more-78"></span></p>
<p>1) Back up the registry on an affected system.<br />
2) Open the registry on the Agent system by entering regedit from a run prompt.<br />
3) Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSysPlant.<br />
4) Open the Start DWORD.<br />
5) Change the value to 4 to disable the drivers.<br />
6) Reboot the system to commit the changes.</p>
<p>Have fun getting your Google browser working with Symantec. Let us know how you get on.</p>
<p>TY to <a href="http://foofu.wordpress.com/2008/09/03/chrome-2/trackback/" target="_blank">The Art of Foo</a> for the heads up</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mercurythread.co.uk/blog/google-chrome-crashing-with-symantec-part-2/2008/09/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

