The Firmware Page

sorry, I must have confused everyone here. I didn't mean for you to install the max128k filter driver I wrote. I wanted to know if, WITHOUT the filter driver installed, whether you get a "Delayed Write Failure" error when you run the 1394Test.exe program from the BusTrace website(http://www.bustrace.com/downloads/1394Test.exe). That program they wrote simulates writing to the disk in progressively higher IO sizes, which if your firmware won't support it(the firmware on my PL-3507 doesn't), will cause an error. What I'm interested in is if your updated firmware will support it or not, WITHOUT my filter driver in the way.

The Max128k filter driver I wrote fixes the issue, if your firmware doesn't already. So if your firmware already supports it, you probably don't want to run my filter driver, because that just adds an extra layer of complexity for no benefit.

So yeah, if you could, just uninstall the filter driver by deleting it from the LowerFilters registry value(you can always put it back in there later, if you want to/need to). Restart the computer(so the filter driver isn't loaded), run the 1394Test.exe app on the external hd and see whether it errors.

And back to off topic:
Ghost doesn't(well my ghost doesn't anyway) actually need to have a drive letter assigned for it to work. All I do is I whack my Ghost floppy into the drive, boot off it with my external drive connected and turned on. It boots in DOS, runs the config.sys/autoexec.bat and scans the firewire bus, finds my external drive. It then comes up with some sort of message which says "No drive letters assigned" or whatever, which makes sense because DOS doesn't recognise NTFS. It then runs Ghost. I can then just backup my partition to the drive(or restore from it) just by choosing the drive from the target disk dropdown. I can't remember off the top of my head what exactly it appears as in the dropdown, but as long as it appears in the dropdown I can select it as a target disk to put the image on. It doesn't appear grayed out or anything as far as I can see, I can just choose it as the target, and it works. Have you tried that(just selecting it as the target disk)?

I must be the lucky one for sure. The 1394 test ran twice with no errors reported without the max128 driver. I have about 16gb of data on the drive and that also remained unharmed. It would appear I have no need for the driver although I have NEVER seen a delayed write error with this drive at any time.

sounds good to me...must mean that the new firmware might actually fix the 128k error...hard to tell now because we don't know whether or not with your old firmware, the 1394Test.exe would have indicated an error or not in the first place. But hey, if everything's good and working with your stuff, I'm happy for ya.

If anyone else out there who had old firmware(or still does) AND has a B or C revision chip, can you run the 1394Test app before you flash and run it again after you flash, and just report the results? Info like what you version you flashed from and to would be good as well


Did you ever get Ghost to work with NTFS on the external enclosure like I described?


For those who might be willing to flash "ghetto" style, this might be of interest:

http://www.sandeen.net/fwfix/index.html

Lack of NF7 2.0 (also nf7 1.0 , and so on abit nforce boards) Compatiblity
And USB 2.0 transfer rate of NF7 is worse than other boards.

There are some good news for NF7

Orange USB driver will be overcome this problems

Why don't you update your usb 2.0 driver ?

you can find driver www.parkoz.com (this site is mode of FLASH)

find top right side "PARKOZ Community then POWER Download tab)

(You don't need read Korean most of this site related to English)

just search for USB , NF7 then some usb 2.0 articles then download

most recent usb 2.0 drivers .. and try it~~

Have fun

Hello ghostdunks

Keep watching this thread for a response from me regarding the ntfs issue with ghost. I haven't forgotten about it to be sure. I had some other unrelated issues come up around here and my experimenting has come to a screeching halt. I should be ready for ntfs testing some time towards the end of this week hopefully.

Last night I tried a small hard drive partitioned as NTFS in the external box with Ghost 2003 and it worked fine.

I ran across an issue with a Maxtor one touch external drive having problems with ghost 2003 on the web through google. Symantec put together an apparent fix for those issues. The fix involved using live update on ghost to be sure the program was updated etc. Then the fix required replacement of the aspi**.sys drivers for the IEEE1394 and USB on the boot disk as well as replacing them in the "common" section of the ghost directory structure.

Try a search at symantec for "maxtor one touch" or if the link I tried to paste in here is alive, try that for more information.

Here's the link

that's a good point that I might have neglected to mention... I had problems with ghosting to external firewire until I had got the latest patches for Ghost(ie. LiveUpdate), since then it's been working fine.

Sorry, I totally forgot I had to get the newest version of Ghost for it to work..just assumed that most people always got the latest patches anyway. It's been so long since I patched it that I didn't even think about it.

Hi,
I've got this Prolific PL3507 bridge with a 160GB Samsung HD. My problem with it are quite strange, since they occur only in both Windows 2000/XP on my Laptop, but on another computer the HD works fine with Windows. With Linux I have no problems on my laptop since I upgraded the firmware.

I have the chip revision C and updated to the latest firmware. However, in Windows apparently randomly the partition crashes. This means, while a partition from the external HD is mounted something happens and then all the directories have scrambled names. After reconnecting, the partition is lost completely and the partition type is 'RAW' -- nothing left of the file table. This happens about every second day (have been trying to find the reason, so I keep using the HD).

Now if I have file caching enabled, I get the 'delayed write' error message, too. If it is disabled, I get no error message and it simply happens in the background. I think I can reproduce the error by writing a CD on my external USB1.0 CD burner. Even if the burned data does not come from the external HD partition, it seems to happen in this very circumstance. Reading data from the external CD drive does not seem to create problems. However, it happens randomly without burning CDs, too.

I tried the max128k driver that ghostdunks wrote. Thanks a lot for your effort! However, it didn't change anything in my case.

I also have an ipod, which works just fine with Windows, I've never had a problem.

My PC is a Toshiba Portege 3480, the PCMCIA Firewire card is made by IBM, recognized by Windows as Texas Instruments Chipset.


I just hope any of you guys has an idea what else I could try, I just don't wanna keep loosing data. This is the most annoying thing I can imagine on a PC...

Thanx, Cluso.

I seem to have a rather vague recollection of reading about corruption issues on external drives and laptops. The part I remember is about hibernation mode or some such. Like not waking up nicely. Take a look in the power options in control panel. Also look at the drive itself and the controller it's on in device mangler for options of letting the drive go to sleep. Disable all that if you haven't already and see if it behaves any better.

I don't think it's a standby problem. I have it switched off anyway that my hds spin down, just in case...

I am sure now how to reproduce the problem. It seems to be something different from what was described in this thread.

When the HD is connected via firewire, the mounted partition is completely lost as soon as I write something onto a CD. Even erasing a CD-RW is enough. My burner is connected via USB1.0. If the hd is connected via USB, too, I have no problems.

I have just tried another firmware update for the PL3507 (v2004.07.07.129). However, it did not help. It just seems that it has nothing to do with acutally transferring data to the hard disk, since when erasing a CD-RW, nothing should be written at all other than on the CD. I just don't understand what's going on...

Any ideas? Cluso.

very strange indeed....can't say I've ever heard of this happening before...based on your symptoms, I would have been very surpised if the filter driver fixed that problem

Weird that something on the USB bus can interfere with something on the firewire bus...weird also that this error happens even if you don't use the cd burner(if this is a wrong assumption let me know).. if I had this problem I would...hmm...this is a toughie...could be anything, maybe a conflict between IRQs between the PCMCIA card and the USB controller???(now I'm really scratching the bottom of the barrel)....see if you can manually assign the PCMCIA card it's own IRQ in device manager

Actually the first thing I would do is use some kind of partitioning program to clear 2 gigs of space, setup a 2 gig partition, do a fresh install of 2000 or XP(or whatever you run), don't do any performance-enhancing things(ie. enlarge virtual mem, disable kernel paging, etc..), and straightaway try and reproduce the error. at least that way you can tell if your windows is just FUBARed...

Hm, good point with the IRQs. In fact, both the IEEE1393 and the USB bus are on IRQ 11. Just that I cannot change the ressources for some reason. What can I do to change the IRQs?

I tried a clean installation of Windows XP. However, I had the problem initially in Windows 2000, there in combination with the 'delayed write error' message. In XP I don't get this message anymore, just lose the data without an error message.

Strange is that, as soon as I write on CD, always the whole partition gets lost. I have a very reliable chance of losing data on the partition if I use Aconis True Image to write an image from my internal HD on the external partition. So it definitely happens without the CD drive being involved.


Cluso.

For those of u interested, I put the latest firmware for the Prolific PL3507 on this link:

http://cluso.net/files/fw3507-707.rar.zip

Upgrade on your own risk... It's a rar archive, the zip ending is just for some browsers to give you a download dialog.

Cluso.

Changes since the 22.04. version, copied from the readme:

PL-3507 Firmware Update (for DoTop Release ONLY)

Release Date: 07/07/2004

Note: Some information are for Chip B and C versions only.

Note: You must use ICP AP v2.0.4 if you are updating from an older date firmware before 4/10/03.
Note: You must use ICP AP v2.0.4 if you are updating from PMC flash chips with firmware date 10/17/2003 and earlier.
==========================

Changes on this update:

1. Fixed Sony Showtime Issue. [1394]

==========================

Revision History:

06/28/2004 -

1. Fixed LiteOn CPRM disc issue. [USB]
2. Fixed LiteOn WinRRT system error. [USB]

--------------------------------
05/21/2004 -

1. Supports LG Firmware Update Tool. [USB]

--------------------------------
05/19/2004 -

1. Supports LG Firmware Update Tool. [1394]

--------------------------------
05/04/2004 -

1. Support 1394 Descriptor - for adding Chip ID Hi value. [1394]

Note: Must use PL3507 EEPROM Writer v10051.

In XP, does any error message show up at all in the Event Viewer(Administrative Tools)?

Give it some time...for me I know that when I used to get the Delayed Write error, it would take about 30-60 seconds before the error actually appeared as a bubble prompt on the system tray, when it had errored out ages before.

Oha, there are a lot of error messages, including the dalayed write error:

Here is the event log of the CD burning issue I had described above:

---------------------------------------------------------------------------
00:27:53: Service Control Manager: The IMAPI CD-Burning COM Service service entered the running state.

00:28:15: sbp2port: The device, , did not respond within the timeout period.

00:28:17: Disk: An error was detected on device \Device\Harddisk1\D during a paging operation.

00:28:52: same again

00:28:52: Ftdisk: The system failed to flush data to the transaction log. Corruption may occur.

00:28:52: Ntfs: {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

00:28:52: Application Popup & Ntfs: Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file E:\. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Note: I did not get a popup window with this message, however.

00:28:52: App. Popup: Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file E:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Note: This is when the MFT dies, I guess...

00:28:52 Ftdisk: The system failed to flush data to the transaction log. Corruption may occur.

Note: this one: several times.
---------------------------------------------------------------------------

Independent there is sometimes another error (from the ACPI), but I don't know if it is related:

AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0x4d0), which lies in the 0x4d0 - 0x4d1 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

Cluso.

I'm beginning to get the delayed errors now I've ran that IEEE test, all test OK..this is from the event log..

"The system failed to flush data to the transaction log. Corruption may occur"

"An error was detected on device \Device\Harddisk1\D during a paging operation."


Any ideas?

Hi Everyone,

Can someone help me to recover my firmware? After I flash it half way it said fail. I trun it off and on. Now window Xp Pro cannot detect it anymore. I got it for 2days from newegg, they state it have a oxford 911 chip(Bytecc ME-740U2F). They lie, I have problem on small file transfer as little as 5mb to 1GB. I search the web and find this page, so I give it a try to see it can fix the transfer fail. I download the firmware from this link http://member.newsguy.com/~siccos/ . I have 4153C Chip, it read as follow before I flash it.

Code Size: 3179(b)
Rom Size : 32(KB)
FW Ver: 2003.10.17.010
Vendor ID: pmc
Chip ID: PM39LV512

The box said New Version
Now support 300Gb hard Drive
Since it new Version, why it have old old firmware???
I call Bytecc foe 2 days now no body answer.
Please Help, I don't want to RMA it.
Thank You Very Much

This thread has been pretty much regarding the Prolific PL3507 series programmable chip.

Your model (although it does start with a P) is not the same as what we are discussing.

Your specs:

Vendor ID: pmc
Chip ID: PM39LV512

I think you may have seriously made an error in flashing that chip with the firmware for the PL3507.

RMA the thing and don't do it again to the replacement.

I'm getting delayed write failed frequently with my PL-3507 03033A over USB 2.0. I know that the thread is primarily about firewire problems but I thought I would throw that in. Perhaps I will try flashing firmware even though it is thought to be impossible.

Does anyone have firmware for revision PL3507 03541C, it is a FreeData (HDD350UF) external drive?

http://www.freedata.com.cn/english/main ... 7&classs=A

It has a 2003 firmware on it and refuses all attempts at using ones floating around It seems not to support PIO data mode transfers and doesnt work with 3/4 (old-ish) hard drives I have tried in it with this firmware.

Thanks if anyone can help

Hi,

In case it may be of interest to any of the people with the same Firewire problem, you'll find hereafter a summary of my personal experience with Firewire external enclosure equipped with a Prolific PL-3507 chip :

VAIO FX502 laptop
WinXP Home SP1

Bytecc ME-320U2F external enclosure
Prolific PL-3507 03473C
PMC Flash Pm39LV512
Original firmware version : 2003.10.17.010

equipped with Seagate Barracuda 2700.7 8Mo 200GB ATA HDD

Summary of the trials :

With the original firmware, the system doesn't even recognize HDD multi-partitioning.

With ghostdunks's firmware version fw_pl3507B_d042204, no problem to prepare and multi-partition HDD.

No heavy use of the HDD, but no "Delayed Write Failure" error seen, however one system freezing, which usually never happens. I can't be sure if it is related with Firewire or not.

But still, with ghostdunks's firmware version fw_pl3507B_d042204, busTrace utility 1394Test systematically hangs at 257 (if I remember correctly).

Then I installed ghostdunks's max128k driver and tried 1394Test again :

IT WORKED PERFECTLY, NO DELAY WRITING ERROR.

Afterwards, I wanted to try the firmware realase posted by cluZo at http://cluso.net/files/fw3507-707.rar.zip. It seems that this firmware is coming from Sony some way or other.

Outcome : the enclosure works, but max128k driver doesn't even load. I tried 1394Test and it obviously hangs again.

Conclusion :

the unique option I had to make the Bytecc ME-320U2F enclosure work properly is :

-load again the PMC-Flash with ghostdunks's firmware update
-install and use ghostdunks's max128k driver together with the firmware update

Ghostdunks, thank you very much for your contribution to solve this Firewire problem.

Cheers.

E.

I have 2 sanmax external drive enclosures with the Prolific PL-04144C chip and PMC Flash (MH030 0337 Pm37LV512-70JC)

I can't get the firmware to load on it. I get the error message and i have a feeling it has to do witht he PMC flash chip. In the readme for the firmware update, it says ver.2.1.1 has the added capability for PMC flash chips but I'm not sure. Any ideas?


Also, I wanted to have 2 of these enclosures plugged in at the same time. I have a 6 port Firewire hub, and when i plug the first one in it works fine, but plug the second one in, can hear the hard drives spin down, and the second drive is never detected. After a few minutes, i get the delayed write error. Anybody have any ideas about this? Can I even have 2 of these plugged in at the same time?

Thanks to everyone for their help with this thread so far!

Has anyone who successfully flashed theirs had the same PMC EEPROM chip with the pl-3507?

PL-3507
03541C

with

PMC Flash
MH1FJ
0342
Pm37LV512-70JC

?

It refuses to work (

What do you mean "it refuses to work" ?

A minimum of details would certainly help.

Are you using the USB link ?

What Writer do you use ?

What firmware ?

Is the device recognized ?

Can you read ?

What happens ?

Etc...

E.

The precise firmware on it at the moment is dated
2003/06/19.241

Using all of the 4 available hex codes that have been posted here,
(PL3507-0422.hex)
(PL3507-0422B.hex)
(PL3507-0428B.hex)
(PL3507-0707B-sepower-SONY.hex)

and connected via USB (tried on pc with A7N8X nforce2 using USB2 and BX6V2 using USB1) inside WinXP. Device
detects and works with USB and firewire.

Flash programmer AP v2.1.4 says "Cant't access the chip.(Be rejected!)"
Flash Programmer AP v2.0.4 says "ROM code verification error" (it says ok with verify off but firmware doesnt change)

I can save my existing firmware to drive (as a .bin) and reload it back and it verifies ok.

Is there someone with the latest firmware that could save it out as a .bin and post it here?

Cheers