<?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"
	>
<channel>
	<title>Comments on: iMac Core Duo, the First Afternoon</title>
	<atom:link href="http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/feed/" rel="self" type="application/rss+xml" />
	<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 22:31:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11471</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 23 Jan 2006 19:17:41 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11471</guid>
		<description>Rob: I tried running that video full-screen, and it didn't seem to have any effect.</description>
		<content:encoded><![CDATA[<p>Rob: I tried running that video full-screen, and it didn't seem to have any effect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11470</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 23 Jan 2006 18:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11470</guid>
		<description>Many thanks to Eric Albert for tracking down the OS bug that causes the -4942 error--over the weekend.</description>
		<content:encoded><![CDATA[<p>Many thanks to Eric Albert for tracking down the OS bug that causes the -4942 error--over the weekend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11468</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 23 Jan 2006 14:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11468</guid>
		<description>Thanks for the info, kapowaz. I don't really follow graphics cards, so my expectation based on passed experience was that the iMac video card might actually be slower than the one in an older tower. I bet Apple is happy to let us think it's the Intel chip causing that speedup.</description>
		<content:encoded><![CDATA[<p>Thanks for the info, kapowaz. I don't really follow graphics cards, so my expectation based on passed experience was that the iMac video card might actually be slower than the one in an older tower. I bet Apple is happy to let us think it's the Intel chip causing that speedup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kapowaz</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11467</link>
		<dc:creator>kapowaz</dc:creator>
		<pubDate>Mon, 23 Jan 2006 09:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11467</guid>
		<description>&lt;blockquote&gt;Is a 128 MB Radeon 9600 XT that much slower than a 256 MB Radeon X1600?&lt;/blockquote&gt;

Yes. Significantly so. This is one of the things a lot of people seem to have forgotten when looking at the new-found speed of World of Warcraft (for instance) on the Intel Macs; the X1600 is two generations later than the 9600XT and significantly faster in 2D and mid-end 3D operations (being a cut-down version of the X1800 GPU). It's one of the more quietly impressive aspects of the new iMac and MacBook Pro (to me) that they thought to use this graphics chip as opposed to one of the many previously lacklustre GPUs they've used (GeForce FX 5200? Er, wow.)</description>
		<content:encoded><![CDATA[<blockquote><p>Is a 128 MB Radeon 9600 XT that much slower than a 256 MB Radeon X1600?</p></blockquote>
<p>Yes. Significantly so. This is one of the things a lot of people seem to have forgotten when looking at the new-found speed of World of Warcraft (for instance) on the Intel Macs; the X1600 is two generations later than the 9600XT and significantly faster in 2D and mid-end 3D operations (being a cut-down version of the X1800 GPU). It's one of the more quietly impressive aspects of the new iMac and MacBook Pro (to me) that they thought to use this graphics chip as opposed to one of the many previously lacklustre GPUs they've used (GeForce FX 5200? Er, wow.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11463</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Sun, 22 Jan 2006 02:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11463</guid>
		<description>Congradulations on your purchase Michael. I am about to order one myself, especially now that I tried one out at my local Apple Store.</description>
		<content:encoded><![CDATA[<p>Congradulations on your purchase Michael. I am about to order one myself, especially now that I tried one out at my local Apple Store.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11454</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 20 Jan 2006 21:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11454</guid>
		<description>Stephen: No, because the value is correct for when it's used in line 3.</description>
		<content:encoded><![CDATA[<p>Stephen: No, because the value is correct for when it's used in line 3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Deken</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11451</link>
		<dc:creator>Stephen Deken</dc:creator>
		<pubDate>Fri, 20 Jan 2006 15:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11451</guid>
		<description>Not to be pedantic, but isn't the error really on line 1?  Line 5 is just calling a function with the value calculated in line 1.</description>
		<content:encoded><![CDATA[<p>Not to be pedantic, but isn't the error really on line 1?  Line 5 is just calling a function with the value calculated in line 1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ejalbert</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11447</link>
		<dc:creator>ejalbert</dc:creator>
		<pubDate>Fri, 20 Jan 2006 04:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11447</guid>
		<description>Can you send me the sound set file that triggered the error or tell me which file it is in an Entourage install?  Thanks!</description>
		<content:encoded><![CDATA[<p>Can you send me the sound set file that triggered the error or tell me which file it is in an Entourage install?  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11445</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 19 Jan 2006 23:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11445</guid>
		<description>Michael,

Try fixing your "dead" pixels first... they may just be temporarily stuck.  I bought a 24" Dell widescreen LCD, and it arrived with 2 stuck pixels.  I was depressed about possibly needing to send it back (or having to live with spots on a brand new screen) and went looking for answers... I found a little video (http://www.psp-vault.com/Article168.psp) that un-stuck the pixels, and I haven't had another one stick.

I ran the video (in the region of the dead pixel) on loop for half an hour, and it didn't fix it... the trick is to run it full-screen... fixed it in a few seconds!

Cheers,

Rob</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>Try fixing your "dead" pixels first... they may just be temporarily stuck.  I bought a 24" Dell widescreen LCD, and it arrived with 2 stuck pixels.  I was depressed about possibly needing to send it back (or having to live with spots on a brand new screen) and went looking for answers... I found a little video (http://www.psp-vault.com/Article168.psp) that un-stuck the pixels, and I haven't had another one stick.</p>
<p>I ran the video (in the region of the dead pixel) on loop for half an hour, and it didn't fix it... the trick is to run it full-screen... fixed it in a few seconds!</p>
<p>Cheers,</p>
<p>Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bigbang</title>
		<link>http://mjtsai.com/blog/2006/01/19/imac-core-duo-the-first-afternoon/#comment-11444</link>
		<dc:creator>bigbang</dc:creator>
		<pubDate>Thu, 19 Jan 2006 22:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1188#comment-11444</guid>
		<description>With four dead pixels I'd be sending it back.</description>
		<content:encoded><![CDATA[<p>With four dead pixels I'd be sending it back.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
