<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Prolific PL3507 Firewire Device</title>
	<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/</link>
	<description>Former Open Source programmer with experience at companies like IBM and Apple. Now a UI Designer with an education in Cognitive Science and Human-Computer Interaction.</description>
	<pubDate>Fri, 04 Jul 2008 00:06:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Pete</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-99544</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Thu, 06 Mar 2008 09:35:01 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-99544</guid>
		<description>Looks like the cause was bad sectors on the Seagate drive, either naturally occurring or caused by the external case. After repair with SeaTools, I reformatted it anyway.</description>
		<content:encoded><![CDATA[<p>Looks like the cause was bad sectors on the Seagate drive, either naturally occurring or caused by the external case. After repair with SeaTools, I reformatted it anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-98944</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 29 Feb 2008 16:57:41 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-98944</guid>
		<description>I've had a history of pain with two enclosures with the Prolific PL-3507 chipset:

Two years ago, it was delayed write errors using Firewire. They would corrupt my drive and I always had to use partition recovery software to restore it. Luckily, you usually only need to restore the partition data to get everything back. I always flashed with all the latest firmware and while the most recent one (2006-04) makes the drive a lot more stable, I'd still get a delayed write error once in a while, without the corruption. Since those days, I've switched to USB2 and just settled with it. Not to mention, I never bought an external case with a Prolific chipset again.

Two months ago, I put in a Seagate 230GB drive in the Prolific enclosure and have been having problems copying large files from it over the LAN. It fills the System event log with "error during page operation" and "system failed to flush data." It reminds me of the good 'ole days.

Since I don't feel like buying yet another enclosure, I will backup my data and partition the drive into 30+100+100 instead of the current 20+200. I'm following Monster's suggestion above. Will report back soon.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had a history of pain with two enclosures with the Prolific PL-3507 chipset:</p>
<p>Two years ago, it was delayed write errors using Firewire. They would corrupt my drive and I always had to use partition recovery software to restore it. Luckily, you usually only need to restore the partition data to get everything back. I always flashed with all the latest firmware and while the most recent one (2006-04) makes the drive a lot more stable, I&#8217;d still get a delayed write error once in a while, without the corruption. Since those days, I&#8217;ve switched to USB2 and just settled with it. Not to mention, I never bought an external case with a Prolific chipset again.</p>
<p>Two months ago, I put in a Seagate 230GB drive in the Prolific enclosure and have been having problems copying large files from it over the LAN. It fills the System event log with &#8220;error during page operation&#8221; and &#8220;system failed to flush data.&#8221; It reminds me of the good &#8216;ole days.</p>
<p>Since I don&#8217;t feel like buying yet another enclosure, I will backup my data and partition the drive into 30+100+100 instead of the current 20+200. I&#8217;m following Monster&#8217;s suggestion above. Will report back soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shippley</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-77353</link>
		<dc:creator>Shippley</dc:creator>
		<pubDate>Tue, 22 May 2007 22:56:17 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-77353</guid>
		<description>Problem with [url=http://www.prolific.com.tw/eng/Products.asp?ID=9]Prolific PL3507 Combo Device[/url]

Running Mac OS X 10.4.9
Probably no one cares.. but the Chipset issue with this drive has caused me many hours of pain and heart ache.
The drive works fine in every thing except the one thing I bought it for.. to record audio..

Just the fact they they aren't using the Oxford 911 standard is reason enough for no one to buy this product.. ever..

I wish I would have known before I spent the money..

Anyone wanna buy a somewhat used, but still in great condition Prolific PL3507 Combo Device?!?!?</description>
		<content:encoded><![CDATA[<p>Problem with [url=http://www.prolific.com.tw/eng/Products.asp?ID=9]Prolific PL3507 Combo Device[/url]</p>
<p>Running Mac OS X 10.4.9<br />
Probably no one cares.. but the Chipset issue with this drive has caused me many hours of pain and heart ache.<br />
The drive works fine in every thing except the one thing I bought it for.. to record audio..</p>
<p>Just the fact they they aren&#8217;t using the Oxford 911 standard is reason enough for no one to buy this product.. ever..</p>
<p>I wish I would have known before I spent the money..</p>
<p>Anyone wanna buy a somewhat used, but still in great condition Prolific PL3507 Combo Device?!?!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Monster</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-69242</link>
		<dc:creator>Monster</dc:creator>
		<pubDate>Tue, 03 Apr 2007 01:46:01 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-69242</guid>
		<description>Running Mac OSX 10.3.9
Maxtor 300G (279G in reality)
Had it partitioned to 190G and 80G (or something like that)
I had my harddrive stall on transfers @ 107MB mark.
Repartioned the drive into 3 smaller drives and presto! the problem stopped.

Used VolumeWorks to do the job without having to lose any of the data. Worked great.
http://www.subrosasoft.com/OSXSoftware/index.php?main_page=product_info&#38;cPath=200&#38;products_id=6

I'm guessing the problem had something to do with the mac "big drive" issues.

hope this helps.</description>
		<content:encoded><![CDATA[<p>Running Mac OSX 10.3.9<br />
Maxtor 300G (279G in reality)<br />
Had it partitioned to 190G and 80G (or something like that)<br />
I had my harddrive stall on transfers @ 107MB mark.<br />
Repartioned the drive into 3 smaller drives and presto! the problem stopped.</p>
<p>Used VolumeWorks to do the job without having to lose any of the data. Worked great.<br />
<a href="http://www.subrosasoft.com/OSXSoftware/index.php?main_page=product_info&amp;cPath=200&amp;products_id=6" rel="nofollow"></a><a href='http://www.subrosasoft.com/OSXSoftware/index.php?main_page=product_info&amp;cPath=200&amp;products_id=6'>http://www.subrosasoft.com/OSXSoftware/index.php?main_page=product_info&amp;cPath=200&amp;products_id=6</a></p>
<p>I&#8217;m guessing the problem had something to do with the mac &#8220;big drive&#8221; issues.</p>
<p>hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: podo</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-68747</link>
		<dc:creator>podo</dc:creator>
		<pubDate>Fri, 30 Mar 2007 21:18:17 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-68747</guid>
		<description>NICE!!! A++++</description>
		<content:encoded><![CDATA[<p>NICE!!! A++++</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donate car</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-68702</link>
		<dc:creator>donate car</dc:creator>
		<pubDate>Fri, 30 Mar 2007 11:37:04 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-68702</guid>
		<description>does 1394 stand for Firewire ?</description>
		<content:encoded><![CDATA[<p>does 1394 stand for Firewire ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-67118</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 19 Mar 2007 18:13:28 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-67118</guid>
		<description>I left out the web address of the above comment: http://www.prolific.com.tw/eng/downloads.asp?ID=44</description>
		<content:encoded><![CDATA[<p>I left out the web address of the above comment: <a href="http://www.prolific.com.tw/eng/downloads.asp?ID=44" rel="nofollow"></a><a href='http://www.prolific.com.tw/eng/downloads.asp?ID=44'>http://www.prolific.com.tw/eng/downloads.asp?ID=44</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-67117</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 19 Mar 2007 18:11:05 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-67117</guid>
		<description>i have a PL3507 USB/FIREWIRE 230GB drive.  i had problems, also, when copying large files to this drive.  The access light on the drive would stay on and the OS wouldn't be able to access the drive.  What was worse: The drive wouldn't work at all after that, without a "write zeroes format" (2-hour chore).  I had it on the Firewire interface.  I researched some, found this address and updated the firmware (the instruccions said you had to use the USB port).  And...
now it works just fine.  Was it the update? or the change to USB?  Don't know, but it works pretty ok now!</description>
		<content:encoded><![CDATA[<p>i have a PL3507 USB/FIREWIRE 230GB drive.  i had problems, also, when copying large files to this drive.  The access light on the drive would stay on and the OS wouldn&#8217;t be able to access the drive.  What was worse: The drive wouldn&#8217;t work at all after that, without a &#8220;write zeroes format&#8221; (2-hour chore).  I had it on the Firewire interface.  I researched some, found this address and updated the firmware (the instruccions said you had to use the USB port).  And&#8230;<br />
now it works just fine.  Was it the update? or the change to USB?  Don&#8217;t know, but it works pretty ok now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ankh</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-65821</link>
		<dc:creator>ankh</dc:creator>
		<pubDate>Fri, 09 Mar 2007 01:06:13 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-65821</guid>
		<description>No you cannot update the firmware over FIREWIRE even on a PC.
You cannot even think about doing it on a MACINTOSH since there is no Firmware updater program for the MACINTOSH.
</description>
		<content:encoded><![CDATA[<p>No you cannot update the firmware over FIREWIRE even on a PC.<br />
You cannot even think about doing it on a MACINTOSH since there is no Firmware updater program for the MACINTOSH.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: osg</title>
		<link>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-63898</link>
		<dc:creator>osg</dc:creator>
		<pubDate>Mon, 26 Feb 2007 22:09:56 +0000</pubDate>
		<guid>http://missig.org/julian/blog/2004/06/10/prolific-pl3507-firewire-device/#comment-63898</guid>
		<description>Hi,
The external box cause several problems.
First the 137Go limit on windows versions before xp SP1.
Second the prolific 3507 chipset with firewire connection.
In most of case, change the controller card, is the easier and best way to fix the problem.
How to test if your configuration could be affected: http://www.bustrace.com/downloads/free_utilities.htm (1394 Delayed Write Stress Tester).
A soft way to deal with: http://member.newsguy.com/~siccos/Max128k.htm.
A good link in french: http://forum.hardware.fr/hfr/Hardware/HDD/firmware-icy-box-sujet_662233_1.htm.

Anyway be careful if you are using your external case, with another computer, you may lost all your data !!!
All the details on https://www.osgpcq.net/osg/Documentations/A_disquedurexterne.html (In french sorry).
Best regards.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
The external box cause several problems.<br />
First the 137Go limit on windows versions before xp SP1.<br />
Second the prolific 3507 chipset with firewire connection.<br />
In most of case, change the controller card, is the easier and best way to fix the problem.<br />
How to test if your configuration could be affected: <a href="http://www.bustrace.com/downloads/free_utilities.htm" rel="nofollow"></a><a href='http://www.bustrace.com/downloads/free_utilities.htm'>http://www.bustrace.com/downloads/free_utilities.htm</a> (1394 Delayed Write Stress Tester).<br />
A soft way to deal with: <a href="http://member.newsguy.com/~siccos/Max128k.htm." rel="nofollow"></a><a href='http://member.newsguy.com/~siccos/Max128k.htm'>http://member.newsguy.com/~siccos/Max128k.htm</a>.<br />
A good link in french: <a href="http://forum.hardware.fr/hfr/Hardware/HDD/firmware-icy-box-sujet_662233_1.htm." rel="nofollow"></a><a href='http://forum.hardware.fr/hfr/Hardware/HDD/firmware-icy-box-sujet_662233_1.htm'>http://forum.hardware.fr/hfr/Hardware/HDD/firmware-icy-box-sujet_662233_1.htm</a>.</p>
<p>Anyway be careful if you are using your external case, with another computer, you may lost all your data !!!<br />
All the details on <a href="https://www.osgpcq.net/osg/Documentations/A_disquedurexterne.html" rel="nofollow"></a><a href='https://www.osgpcq.net/osg/Documentations/A_disquedurexterne.html'>https://www.osgpcq.net/osg/Documentations/A_disquedurexterne.html</a> (In french sorry).<br />
Best regards.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
