<?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 on: OS X&#8217;s Weak Spot &#8211; The Finder</title>
	<atom:link href="http://marcusvorwaller.com/blog/archives/2004/11/18/os-xs-weak-spot-the-finder/feed/" rel="self" type="application/rss+xml" />
	<link>http://marcusvorwaller.com/blog/archives/2004/11/18/os-xs-weak-spot-the-finder/</link>
	<description>Software, Mac and other Goodness</description>
	<lastBuildDate>Sun, 05 Feb 2012 11:33:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: anon</title>
		<link>http://marcusvorwaller.com/blog/archives/2004/11/18/os-xs-weak-spot-the-finder/comment-page-1/#comment-175</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://marcusvorwaller.com/blog/index.php/os-xs-weak-spot-the-finder/#comment-175</guid>
		<description>datamem.com - good Mac-friendly RAM cheap. Those in the know go there...</description>
		<content:encoded><![CDATA[<p>datamem.com &#8211; good Mac-friendly RAM cheap. Those in the know go there&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Williams</title>
		<link>http://marcusvorwaller.com/blog/archives/2004/11/18/os-xs-weak-spot-the-finder/comment-page-1/#comment-176</link>
		<dc:creator>Brandon Williams</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://marcusvorwaller.com/blog/index.php/os-xs-weak-spot-the-finder/#comment-176</guid>
		<description>Hey Marcus,

For recovery, I&#039;ve found a good thing to have is a spare firewire drive - just boot off the drive with cmd+opt+shift+del and back up your hard drive.  Another indespensible tool is Alsoft&#039;s DiskWarrior.  I maintain about 400 Macs, and I use both on a regular basis for troubleshooting and maintenance.

For large copying actions, I&#039;ve found just about the only thing you can do with a broken OS X install is copy things in very small batches.  An OS X install that&#039;s in good working shape should be able to copy a large amount of data without a hitch - I regularly back up users&#039; entire hard disks to my firewire drive prior to re-imaging their computers.  Typical backup size is ~70k+ files and 30-50GB of data, and I very rarely see any hiccups while copying.

As far as downloading files goes, I keep a folder on my desktop as my system-wide target download directory - that way, I don&#039;t have junk constantly littering my work space.  I&#039;ve also titled the folder &#039;To Be Sorted,&#039; so seeing it prompts me to take care of the files that are accumulating in it.

In your case, I&#039;d say DiskWarrior probably would have saved you some grief - it sounds like a damaged volume wrapper or other filesystem error.

RAM - Spot on, especially since Macs switched to DDR.  It wasn&#039;t as big an issue when they still used SDRAM; now, I really see a marked increase in crash rates with non-Apple RAM installed in newer machines.

In any case, while I agree the Finder does occasionally leave something to be desired, a well-tuned OS X system shouldn&#039;t crash nearly as often as it has for you - I&#039;ve seen perhaps two kernel panics in the past year, and both were caused by faulty hardware.  You might want to run the Hardware Test disc that came with  your Mac and make sure everything is peachy.

Best,

Brandon
</description>
		<content:encoded><![CDATA[<p>Hey Marcus,</p>
<p>For recovery, I&#8217;ve found a good thing to have is a spare firewire drive &#8211; just boot off the drive with cmd+opt+shift+del and back up your hard drive.  Another indespensible tool is Alsoft&#8217;s DiskWarrior.  I maintain about 400 Macs, and I use both on a regular basis for troubleshooting and maintenance.</p>
<p>For large copying actions, I&#8217;ve found just about the only thing you can do with a broken OS X install is copy things in very small batches.  An OS X install that&#8217;s in good working shape should be able to copy a large amount of data without a hitch &#8211; I regularly back up users&#8217; entire hard disks to my firewire drive prior to re-imaging their computers.  Typical backup size is ~70k+ files and 30-50GB of data, and I very rarely see any hiccups while copying.</p>
<p>As far as downloading files goes, I keep a folder on my desktop as my system-wide target download directory &#8211; that way, I don&#8217;t have junk constantly littering my work space.  I&#8217;ve also titled the folder &#8216;To Be Sorted,&#8217; so seeing it prompts me to take care of the files that are accumulating in it.</p>
<p>In your case, I&#8217;d say DiskWarrior probably would have saved you some grief &#8211; it sounds like a damaged volume wrapper or other filesystem error.</p>
<p>RAM &#8211; Spot on, especially since Macs switched to DDR.  It wasn&#8217;t as big an issue when they still used SDRAM; now, I really see a marked increase in crash rates with non-Apple RAM installed in newer machines.</p>
<p>In any case, while I agree the Finder does occasionally leave something to be desired, a well-tuned OS X system shouldn&#8217;t crash nearly as often as it has for you &#8211; I&#8217;ve seen perhaps two kernel panics in the past year, and both were caused by faulty hardware.  You might want to run the Hardware Test disc that came with  your Mac and make sure everything is peachy.</p>
<p>Best,</p>
<p>Brandon</p>
]]></content:encoded>
	</item>
</channel>
</rss>

