<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for T.J. Schmitz.com</title>
	<atom:link href="http://tjschmitz.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://tjschmitz.com/blog</link>
	<description>It&#039;s all about me, right?</description>
	<lastBuildDate>Sat, 24 Dec 2011 21:52:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Fixing the PHP Allowed Memory Size Exchausted Fatal Error in WordPress by Matthew Name</title>
		<link>http://tjschmitz.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/comment-page-1/#comment-430</link>
		<dc:creator>Matthew Name</dc:creator>
		<pubDate>Sat, 24 Dec 2011 21:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://cstarsys.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/#comment-430</guid>
		<description>Make sure this line is in your wp-config.php file after the 
define utf 
define(&#039;WP_MEMORY_LIMIT&#039;, &#039;64M&#039;);

That&#039;s how I fixed mine. When wordpress moved up to 3.0 that specification in wp-config.php became important and if you had the permission set to 444 on that file it never got the added code. Opps!</description>
		<content:encoded><![CDATA[<p>Make sure this line is in your wp-config.php file after the<br />
define utf<br />
define(&#8216;WP_MEMORY_LIMIT&#8217;, &#8217;64M&#8217;);</p>
<p>That&#8217;s how I fixed mine. When wordpress moved up to 3.0 that specification in wp-config.php became important and if you had the permission set to 444 on that file it never got the added code. Opps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CPAP Hacking by Anonymous</title>
		<link>http://tjschmitz.com/blog/2010/08/01/cpap-hacking/comment-page-1/#comment-428</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 18 Dec 2011 03:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://tjschmitz.com/blog/?p=624#comment-428</guid>
		<description>I did one better. I built a home made CPAP machine. It turns out that I have the obstructive aleep apnea but I discovered it by lying on my back and noticed it before falling asleep. This not only gave ne a self diagnosis but I also get to titrate the needed pressure and it worked out. The first time (last century) I rigged the little but good blower to a gas mask and fell asleep as I &quot;test piloted&quot; the device. My modern version has the same centrifugal blower but hooked to what looks like a fighter pilot&#039;s mask. Sooner or later, I&#039;ll have a dream where I&#039;m flying a Grumman F-14 Tomcat! 

This is a classic &quot;do not try at home&quot; thing!</description>
		<content:encoded><![CDATA[<p>I did one better. I built a home made CPAP machine. It turns out that I have the obstructive aleep apnea but I discovered it by lying on my back and noticed it before falling asleep. This not only gave ne a self diagnosis but I also get to titrate the needed pressure and it worked out. The first time (last century) I rigged the little but good blower to a gas mask and fell asleep as I &#8220;test piloted&#8221; the device. My modern version has the same centrifugal blower but hooked to what looks like a fighter pilot&#8217;s mask. Sooner or later, I&#8217;ll have a dream where I&#8217;m flying a Grumman F-14 Tomcat! </p>
<p>This is a classic &#8220;do not try at home&#8221; thing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Windows Update Stuck on &#8220;Checking for the latest updates for your computer&#8230;&#8221; by Rob</title>
		<link>http://tjschmitz.com/blog/2010/07/01/windows-update-stuck-on-checking-for-the-latest-updates-for-your-computer/comment-page-1/#comment-423</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 28 Jun 2011 12:03:35 +0000</pubDate>
		<guid isPermaLink="false">http://tjschmitz.com/blog/?p=520#comment-423</guid>
		<description>Thank you so much.  I have been fighting this problem for 8 hrs and everything was just slow and ended up failing.  I went thru all the steps and the updates took off like a rocket.

Thanks,</description>
		<content:encoded><![CDATA[<p>Thank you so much.  I have been fighting this problem for 8 hrs and everything was just slow and ended up failing.  I went thru all the steps and the updates took off like a rocket.</p>
<p>Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DIY Virus removal by Keep getting redirected to random sites...</title>
		<link>http://tjschmitz.com/blog/2010/09/01/diy-virus-removal/comment-page-1/#comment-420</link>
		<dc:creator>Keep getting redirected to random sites...</dc:creator>
		<pubDate>Sun, 13 Mar 2011 15:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://tjschmitz.com/blog/?p=652#comment-420</guid>
		<description>[...] Corrine, I come across to this article, DIY Virus removal from T.J. Schmitz.com and I wanted to know your ideas about that.  About step two, what are your [...]</description>
		<content:encoded><![CDATA[<p>[...] Corrine, I come across to this article, DIY Virus removal from T.J. Schmitz.com and I wanted to know your ideas about that.  About step two, what are your [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing &#8220;The RD Licensing Manager encountered an internal error from the license server. Message Number: 0xc0110011&#8243; Errors by José C</title>
		<link>http://tjschmitz.com/blog/2010/07/29/fixing-the-rd-licensing-manager-encountered-an-internal-error-from-the-license-server-message-number-0xc0110011-errors/comment-page-1/#comment-419</link>
		<dc:creator>José C</dc:creator>
		<pubDate>Wed, 29 Dec 2010 20:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://tjschmitz.com/blog/?p=607#comment-419</guid>
		<description>worked, 2008, 2008 R2

ty</description>
		<content:encoded><![CDATA[<p>worked, 2008, 2008 R2</p>
<p>ty</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing &#8220;The RD Licensing Manager encountered an internal error from the license server. Message Number: 0xc0110011&#8243; Errors by Jake V.</title>
		<link>http://tjschmitz.com/blog/2010/07/29/fixing-the-rd-licensing-manager-encountered-an-internal-error-from-the-license-server-message-number-0xc0110011-errors/comment-page-1/#comment-417</link>
		<dc:creator>Jake V.</dc:creator>
		<pubDate>Fri, 01 Oct 2010 19:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://tjschmitz.com/blog/?p=607#comment-417</guid>
		<description>This worked for me, great post, thank you!!

-Jake
voipcitadel.com</description>
		<content:encoded><![CDATA[<p>This worked for me, great post, thank you!!</p>
<p>-Jake<br />
voipcitadel.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing the PHP Allowed Memory Size Exchausted Fatal Error in WordPress by Montxo</title>
		<link>http://tjschmitz.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/comment-page-1/#comment-349</link>
		<dc:creator>Montxo</dc:creator>
		<pubDate>Tue, 25 Aug 2009 09:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://cstarsys.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/#comment-349</guid>
		<description>Thanks for your fix, it worked quickly for me.</description>
		<content:encoded><![CDATA[<p>Thanks for your fix, it worked quickly for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing the PHP Allowed Memory Size Exchausted Fatal Error in WordPress by Chris Howell</title>
		<link>http://tjschmitz.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/comment-page-1/#comment-348</link>
		<dc:creator>Chris Howell</dc:creator>
		<pubDate>Wed, 05 Nov 2008 18:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://cstarsys.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/#comment-348</guid>
		<description>This fix worked for me. Thanks very much for this post. You saved my neck!</description>
		<content:encoded><![CDATA[<p>This fix worked for me. Thanks very much for this post. You saved my neck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing the PHP Allowed Memory Size Exchausted Fatal Error in WordPress by T.J.</title>
		<link>http://tjschmitz.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/comment-page-1/#comment-347</link>
		<dc:creator>T.J.</dc:creator>
		<pubDate>Tue, 05 Aug 2008 13:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://cstarsys.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/#comment-347</guid>
		<description>Brett - the .htaccess file should be in the root directory of your Wordpress installation.  There usually is also on in the root directory of your web server as well.</description>
		<content:encoded><![CDATA[<p>Brett &#8211; the .htaccess file should be in the root directory of your WordPress installation.  There usually is also on in the root directory of your web server as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing the PHP Allowed Memory Size Exchausted Fatal Error in WordPress by Brett Conway</title>
		<link>http://tjschmitz.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/comment-page-1/#comment-346</link>
		<dc:creator>Brett Conway</dc:creator>
		<pubDate>Sun, 03 Aug 2008 23:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://cstarsys.com/blog/2007/12/12/fixing-the-php-allowed-memory-size-exchausted-fatal-error-in-wordpress/#comment-346</guid>
		<description>stupid questionn... I cannot find my .htaccess file ?

Where should it be?</description>
		<content:encoded><![CDATA[<p>stupid questionn&#8230; I cannot find my .htaccess file ?</p>
<p>Where should it be?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

