<?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: FireWire HD Problems</title>
	<atom:link href="http://alexking.org/blog/2004/12/05/firewire-hd-problems/feed" rel="self" type="application/rss+xml" />
	<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems</link>
	<description>Alex King, Denver Web Developer</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:02:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3506</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Fri, 31 Dec 2004 17:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3506</guid>
		<description>Thanks. I was able to return these enclosures - check the post linked above for more info.</description>
		<content:encoded><![CDATA[<p>Thanks. I was able to return these enclosures &#8211; check the post linked above for more info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3505</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 31 Dec 2004 09:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3505</guid>
		<description>For what it&#039;s worth, check what model of the FW chip you use (System Profiler will tell if it&#039;s Prolific, Oxford or Ingenio).  If it&#039;s Prolific PL3507, early revisions of the firmware will basically not set fw id to anything else then 0, and thus you can&#039;t have two together as you get an ID clash.   

Solution for Prolific might be a firmware flash over USB from Windows box - http://member.newsguy.com/~siccos/PL3507%20Firmware.htm

If it&#039;s Oxford, you *might* have a very early firmware version (although my experience is only with OXFW911, not OXFW922) and might need to flash it.  
http://www.fwdepot.com/firewiredepot/firmware/firmware.html  should have a link to flasher.

Initio chips so far are the best in day to day usage (I have two Macally PHC-100AC enclosures), although required flashing of the firmware too to the new revision. 

Any way, just guessing here.</description>
		<content:encoded><![CDATA[<p>For what it&#8217;s worth, check what model of the FW chip you use (System Profiler will tell if it&#8217;s Prolific, Oxford or Ingenio).  If it&#8217;s Prolific PL3507, early revisions of the firmware will basically not set fw id to anything else then 0, and thus you can&#8217;t have two together as you get an ID clash.   </p>
<p>Solution for Prolific might be a firmware flash over USB from Windows box &#8211; <a href="http://member.newsguy.com/~siccos/PL3507%20Firmware.htm" rel="nofollow">http://member.newsgu[...]Firmware.htm</a></p>
<p>If it&#8217;s Oxford, you *might* have a very early firmware version (although my experience is only with OXFW911, not OXFW922) and might need to flash it.<br />
<a href="http://www.fwdepot.com/firewiredepot/firmware/firmware.html" rel="nofollow">http://www.fwdepot.c[...]irmware.html</a>  should have a link to flasher.</p>
<p>Initio chips so far are the best in day to day usage (I have two Macally PHC-100AC enclosures), although required flashing of the firmware too to the new revision. </p>
<p>Any way, just guessing here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexking.org: Blog</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3370</link>
		<dc:creator>alexking.org: Blog</dc:creator>
		<pubDate>Sat, 11 Dec 2004 00:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3370</guid>
		<description>&lt;strong&gt;Rsync Backup System&lt;/strong&gt;
Last February I started looking at using my old PowerMac G4 (dual 500mhz, gigabit ethernet model) as a live backup server since I&#039;d moved to the PowerBook full time for development. Nine months later, I&#039;ve finally done it! I know several people t...</description>
		<content:encoded><![CDATA[<p><strong>Rsync Backup System</strong><br />
Last February I started looking at using my old PowerMac G4 (dual 500mhz, gigabit ethernet model) as a live backup server since I&#8217;d moved to the PowerBook full time for development. Nine months later, I&#8217;ve finally done it! I know several people t&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3347</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 09 Dec 2004 13:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3347</guid>
		<description>Just found this - http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/

I have 3 of these drives running under mac os x.3.4 and each drive mounts and works flawlessly individually, but as soon as i daisy chain them together, Only the first drive mounts and the other 2 just spin. thanks zen

...then...

Averagezen, you&#8217;re seeing those problems because each chip is supposed to have a unique identifier&#8230; but the PL3507 sets them to 000 for each one</description>
		<content:encoded><![CDATA[<p>Just found this &#8211; <a href="http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/" rel="nofollow">http://missig.org/ju[...]wire-device/</a></p>
<p>I have 3 of these drives running under mac os x.3.4 and each drive mounts and works flawlessly individually, but as soon as i daisy chain them together, Only the first drive mounts and the other 2 just spin. thanks zen</p>
<p>&#8230;then&#8230;</p>
<p>Averagezen, you&#8217;re seeing those problems because each chip is supposed to have a unique identifier&#8230; but the PL3507 sets them to 000 for each one</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3298</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 06 Dec 2004 11:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3298</guid>
		<description>Thanks for the info, I&#039;ll try that.</description>
		<content:encoded><![CDATA[<p>Thanks for the info, I&#8217;ll try that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isaack Rasmussen</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3294</link>
		<dc:creator>Isaack Rasmussen</dc:creator>
		<pubDate>Mon, 06 Dec 2004 05:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3294</guid>
		<description>If you have a Prolific chipset, you might want to look into upgrading the firmware. Daisy chaining with this chipset was fixed/enabled with the most recent firmware version, that most people do not have.

And if you are running it on Windows with data corruption problems, this might help you.
http://www.isaack.info/archives/2004/01/13/winxp-service-pack-2/</description>
		<content:encoded><![CDATA[<p>If you have a Prolific chipset, you might want to look into upgrading the firmware. Daisy chaining with this chipset was fixed/enabled with the most recent firmware version, that most people do not have.</p>
<p>And if you are running it on Windows with data corruption problems, this might help you.<br />
<a href="http://www.isaack.info/archives/2004/01/13/winxp-service-pack-2/" rel="nofollow">http://www.isaack.in[...]vice-pack-2/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3293</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 06 Dec 2004 00:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3293</guid>
		<description>I&#039;ve ordered a pair of &lt;a href=&quot;http://www.coolerexpress.com/byal3hadrexe1.html&quot;&gt;these&lt;/a&gt; on recommendation from some friends. I&#039;ll post a follow-up when I get them.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve ordered a pair of <a href="http://www.coolerexpress.com/byal3hadrexe1.html">these</a> on recommendation from some friends. I&#8217;ll post a follow-up when I get them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3292</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 06 Dec 2004 00:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3292</guid>
		<description>I bought two of these: http://www.argosy.com.tw/product/hd360c.htm

Combo USB2 and FireWire 400, $38 ea. plus tax and shipping.  They work great, both at the same time to different ports.  Didn&#039;t try daisy.  Each comes with USB2 &amp; FireWire cables, and the adapter for the small-sized FireWire port.

I got them here: http://www.pcmicrostore.com (undergoing maintenance right now)</description>
		<content:encoded><![CDATA[<p>I bought two of these: <a href="http://www.argosy.com.tw/product/hd360c.htm" rel="nofollow">http://www.argosy.co[...]t/hd360c.htm</a></p>
<p>Combo USB2 and FireWire 400, $38 ea. plus tax and shipping.  They work great, both at the same time to different ports.  Didn&#8217;t try daisy.  Each comes with USB2 &#38; FireWire cables, and the adapter for the small-sized FireWire port.</p>
<p>I got them here: <a href="http://www.pcmicrostore.com" rel="nofollow">http://www.pcmicrostore.com</a> (undergoing maintenance right now)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3291</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 05 Dec 2004 23:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3291</guid>
		<description>I agree, one works great, but I need them both to work. I can connect the iPod to the enclosure, but I can&#039;t connect the other enclosed drive to the enclosure. These are for backups so I haven&#039;t tried to make either of them bootable.</description>
		<content:encoded><![CDATA[<p>I agree, one works great, but I need them both to work. I can connect the iPod to the enclosure, but I can&#8217;t connect the other enclosed drive to the enclosure. These are for backups so I haven&#8217;t tried to make either of them bootable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3290</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sun, 05 Dec 2004 23:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3290</guid>
		<description>I work at CompUSA, and as such got those same enclosures for close to $30 a piece (best deal I could find that didn&#039;t require shipping).

It works perfectly (though I only have one), and I can run my iPod through it should i need to and it all works fine (all this on my 12&quot; iBook G4).

The only problem I have is that I can&#039;t get OS X to install on the drive, or after CCC&#039;ing my main drive to the one in the enclosure, I can&#039;t boot from it.

Can you boot from your enclosure (either one)?</description>
		<content:encoded><![CDATA[<p>I work at CompUSA, and as such got those same enclosures for close to $30 a piece (best deal I could find that didn&#8217;t require shipping).</p>
<p>It works perfectly (though I only have one), and I can run my iPod through it should i need to and it all works fine (all this on my 12&#8243; iBook G4).</p>
<p>The only problem I have is that I can&#8217;t get OS X to install on the drive, or after CCC&#8217;ing my main drive to the one in the enclosure, I can&#8217;t boot from it.</p>
<p>Can you boot from your enclosure (either one)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3289</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 05 Dec 2004 22:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3289</guid>
		<description>The drives are &lt;a href=&quot;http://www.compusa.com/products/product_info.asp?product_code=309209&amp;pfp=BROWSE&quot; rel=&quot;external&quot;&gt;200GB Seagate Barraccudas&lt;/a&gt;. I got generic CompUSA &lt;a href=&quot;http://www.compusa.com/products/product_info.asp?product_code=306103&amp;pfp=SEARCH&quot; rel=&quot;external&quot;&gt;FireWire enclosures&lt;/a&gt; which now seems like a mistake.</description>
		<content:encoded><![CDATA[<p>The drives are <a href="http://www.compusa.com/products/product_info.asp?product_code=309209&#38;pfp=BROWSE" rel="external">200GB Seagate Barraccudas</a>. I got generic CompUSA <a href="http://www.compusa.com/products/product_info.asp?product_code=306103&#38;pfp=SEARCH" rel="external">FireWire enclosures</a> which now seems like a mistake.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3288</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sun, 05 Dec 2004 22:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3288</guid>
		<description>Just curious, what make/model were the drives and drive enclosures?</description>
		<content:encoded><![CDATA[<p>Just curious, what make/model were the drives and drive enclosures?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3287</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 05 Dec 2004 21:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3287</guid>
		<description>I put them both on &quot;cable select&quot;, and I have the exact same behavior (testing on the PowerBook). Either will mount perfectly but when I chain them, they basically cause the system to freeze.</description>
		<content:encoded><![CDATA[<p>I put them both on &#8220;cable select&#8221;, and I have the exact same behavior (testing on the PowerBook). Either will mount perfectly but when I chain them, they basically cause the system to freeze.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3286</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sun, 05 Dec 2004 20:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3286</guid>
		<description>Can you try setting them to cable select, or set one to master and the other to slave? You know, just to spite the instruction manuals.</description>
		<content:encoded><![CDATA[<p>Can you try setting them to cable select, or set one to master and the other to slave? You know, just to spite the instruction manuals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://alexking.org/blog/2004/12/05/firewire-hd-problems#comment-3285</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 05 Dec 2004 20:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.alexking.org/blog/2004/12/05/firewire-hd-problems/#comment-3285</guid>
		<description>The are both master, per the instructions included with the FireWire case.</description>
		<content:encoded><![CDATA[<p>The are both master, per the instructions included with the FireWire case.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

