Delayed Write Error

bbq wiz wrote on 3/7/2006, 3:42 AM

I am trying to save mpg files to a firewire drive. Have not had issues in the past saving files to this drive, but I get the error "Delayed Write Error" when I save a large mpg file. Smaller mpg files (appears to around less than 1 MB) save just fine. What ideas/suggestions do folks have to get around this?

BBQ Wiz

Comments

farss wrote on 3/7/2006, 4:34 AM

Hm,
seen that one. Drive has gone off line. Save the file to a different drive and restart everything and you should be OK.

I have a funny feeling (unconfirmed) that the problem went away for me once I sorted out the 'Enable LBA' bit but just what way around I changed things to fix the problem I know not.

My drives (200GB mostly) get swapped between Win2K and WinXP systems and between 1394 enclosures and direct IDE connections.

Bob.

DCV wrote on 3/7/2006, 8:03 AM

Check out this thread I started a while back:

http://www.sonymediasoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=378797

Hope this helps fix your problem!
John

farss wrote on 3/7/2006, 2:00 PM

So have uSoft made this patch more widely available?

Bob.

R0cky wrote on 3/7/2006, 3:11 PM

I have a collection of non-working patches from Microsoft for this issue. I finally gave up and started using USB2 which has been OK. I need to check to see if this is a new and improved one that might actually fix it on my system.

To get it is relatively easy in the US, you call microsoft Customer Service, NOT tech support and ask for hotfix for KB article #885464 and they email you a link to download it. Doesn't cost anything, no hassle with s/n's etc. The phone number is kind of difficult to find on their website and of course the location changes all of the time as they try to make getting support as difficult as possible.

DavidMcKnight wrote on 3/7/2006, 3:28 PM

I don't mean to reopen the old thread, but I occasionally get this not with firewire, but with an IDE connected drive. And the drive tests fine in all vendor tests (I think it's a maxtor)

Harold Brown wrote on 3/7/2006, 3:43 PM

I get these errors with aftermarket enclosures but never with MY WD external drives. For internal I have only gotten this once and it was because an older driver replaced a newer one (promise control card)..

GlennChan wrote on 3/7/2006, 4:21 PM

Drives with the Prolific chipset can have this problem. To check for these chipsets:
go to remove device safely
hit stop
read off the name of the device.

Flashing these chipsets will fix things. However, the drive may not play well with other devices on the same bus.

Steve Mann wrote on 3/8/2006, 1:00 AM

This is one of the most bewildering problems with Windows. Google it and you will find thousands of incidents and an equal number of "fixes". It is caused when the drive does not acknowledge a data transfer before the driver times out. There is no single cause or repair.

In my case, simply switching the USB ports that my external drive was plugged into solved it. With some people, using a IDE USB card fixed theirs.

MarkWWWW wrote on 3/8/2006, 5:25 AM

If you haven't already found it, have a look at this page which deals with dozens of possible solutions to the problem, depending on exactly what chipset, etc, you are using. If you're lucky one of the solutions there will solve your problem, but there is a lot of information to wade through.

Mark