<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Short list of MacBook Pro/Leopard issues</title>
	<atom:link href="http://mccammon.org/keith/2008/02/27/a-list-of-macbook-proleopard-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://mccammon.org/keith/2008/02/27/a-list-of-macbook-proleopard-issues/</link>
	<description>What I'm doing when I'm not doing anything else...</description>
	<lastBuildDate>Sun, 16 May 2010 19:01:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Keith</title>
		<link>http://mccammon.org/keith/2008/02/27/a-list-of-macbook-proleopard-issues/comment-page-1/#comment-4001</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Thu, 28 Feb 2008 14:24:45 +0000</pubDate>
		<guid isPermaLink="false">http://mccammon.org/keith/2008/02/27/a-list-of-macbook-proleopard-issues/#comment-4001</guid>
		<description>I have not.  And not because I don&#039;t think that a tech might know how to fix these problems.

When purchasing my MacBook Pro (which I had for a few days, and spent an entire month attempting to get replaced), I had what can only be described as the single worst customer service and support experience of my entire life.  The prospect of turning my beloved notebook over to those donkeys is terrifying.

Also, based on what I&#039;ve read--mainly on Apple&#039;s support site--these are intermittent problems that they claim can be or have been fixed by some combination of software updates or PRAM/SMC resets.  

Even more terrifying than turning over my notebook for hardware repair is the prospect of turning it over for &quot;repair,&quot; only to find out that it sat on a shelf for three days awaiting yet another PRAM reset, and was then returned to me as &quot;fixed.&quot;

Can you tell that, despite my love for this machine, I&#039;m somewhat disenfranchised by Apple&#039;s &quot;award-winning&quot; support?</description>
		<content:encoded><![CDATA[<p>I have not.  And not because I don&#8217;t think that a tech might know how to fix these problems.</p>
<p>When purchasing my MacBook Pro (which I had for a few days, and spent an entire month attempting to get replaced), I had what can only be described as the single worst customer service and support experience of my entire life.  The prospect of turning my beloved notebook over to those donkeys is terrifying.</p>
<p>Also, based on what I&#8217;ve read&#8211;mainly on Apple&#8217;s support site&#8211;these are intermittent problems that they claim can be or have been fixed by some combination of software updates or PRAM/SMC resets.  </p>
<p>Even more terrifying than turning over my notebook for hardware repair is the prospect of turning it over for &#8220;repair,&#8221; only to find out that it sat on a shelf for three days awaiting yet another PRAM reset, and was then returned to me as &#8220;fixed.&#8221;</p>
<p>Can you tell that, despite my love for this machine, I&#8217;m somewhat disenfranchised by Apple&#8217;s &#8220;award-winning&#8221; support?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raoul</title>
		<link>http://mccammon.org/keith/2008/02/27/a-list-of-macbook-proleopard-issues/comment-page-1/#comment-4000</link>
		<dc:creator>Raoul</dc:creator>
		<pubDate>Thu, 28 Feb 2008 14:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://mccammon.org/keith/2008/02/27/a-list-of-macbook-proleopard-issues/#comment-4000</guid>
		<description>Have you taken it to the Apple Store for repairs? I&#039;m curious to see what they say.</description>
		<content:encoded><![CDATA[<p>Have you taken it to the Apple Store for repairs? I&#8217;m curious to see what they say.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

