P
philthym
Hi
I have an older firewire external HDD and was unable to use it under
XP Service Pack 1 although it was fine under 2K. Under XP I'd get a
Delayed Write Failed message with the text
"{Delayed Write Failed} Windows was unable to save all the data for
the file xxx. 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."
Then the HDD would disappear fom view until I restarted. The event
viewer shows mutiple occurrences of Event ID 50 with a status code of
c00000c0. While there's plenty of Microsoft KB articles regarding
write failure, I was unable to find any mention of c0000c0, nor
anything relating to firewire drives.
I gave up and bought a USB 2.0 enclosure. Incredibly I get almost the
same problem - fine under Win2K but fails under XPSP1. The only
difference is I now get a status code of c00000e. Again, I can find no
direct reference to this status code on the Microsoft site.
What's really odd is that the drive is set for no caching anyway, if
I'm looking in the right place. Under Policies for the drive the
option for "Optimize for quick removal" is set. It clearly states that
write caching is disabled when set, so that makes no sense at all
(unless I'm missing something of course!).
I should mention that both enclosures work fine with various drives on
my 2K server and my Mac PowerBook, yet consistently fail on the XPSP1
machine. Any hints gratefully received.
Thanks
Phil
I have an older firewire external HDD and was unable to use it under
XP Service Pack 1 although it was fine under 2K. Under XP I'd get a
Delayed Write Failed message with the text
"{Delayed Write Failed} Windows was unable to save all the data for
the file xxx. 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."
Then the HDD would disappear fom view until I restarted. The event
viewer shows mutiple occurrences of Event ID 50 with a status code of
c00000c0. While there's plenty of Microsoft KB articles regarding
write failure, I was unable to find any mention of c0000c0, nor
anything relating to firewire drives.
I gave up and bought a USB 2.0 enclosure. Incredibly I get almost the
same problem - fine under Win2K but fails under XPSP1. The only
difference is I now get a status code of c00000e. Again, I can find no
direct reference to this status code on the Microsoft site.
What's really odd is that the drive is set for no caching anyway, if
I'm looking in the right place. Under Policies for the drive the
option for "Optimize for quick removal" is set. It clearly states that
write caching is disabled when set, so that makes no sense at all
(unless I'm missing something of course!).
I should mention that both enclosures work fine with various drives on
my 2K server and my Mac PowerBook, yet consistently fail on the XPSP1
machine. Any hints gratefully received.
Thanks
Phil