home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.comp.os.windows-xp      Actually wasn't too bad for a M$-OS      17,273 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 16,869 of 17,273   
   JJ to R.Wieser   
   Re: USB "delayed write failed" Anyone kn   
   28 Apr 24 14:06:12   
   
   XPost: alt.windows7.general   
   From: jj4public@outlook.com   
      
   On Sat, 27 Apr 2024 17:04:57 +0200, R.Wieser wrote:   
   > Hello all,   
   >   
   > On a machine runnung XPsp3 :   
   >   
   > A while ago  tried to copy a couple of 1...4 GB files to an USB stick, and   
   > it threw the "delayed write failed" error (after a couple of hundred MByte),   
   > after which the machine froze and I had to power-cycle it to get it to   
   > respond again (not even the task-manager wanted to come up).   
   >   
   > A bit of googeling gave me the answer : unticking "Enable write caching on   
   > the disk" - even though that was in a section that was grayed out because   
   > its parent, "Optimize for performance", wasn't selected ("Optimize for quick   
   > removal" was).   
   >   
   > No, the question is not why I had to untick something in a grayed-out   
   > section, don't worry. :-)   
   >   
   > My question is even worse than that :   
   >   
   > Does anyone know (or have a link to an MS article to) why that the "delayed   
   > writing" (which I assume was still doing its job) causes such a big problem   
   > ?   
   >   
   > And don't worry, its just curiosity.  There is nothing hanging on the   
   > answer.   
   >   
   > Regards,   
   > Rudy Wieser   
      
   From MSDN:   
      
   ERROR_LOST_WRITEBEHIND_DATA   
   596   
      
   {Delayed Write Failed} Windows was unable to save all the data for the file   
   %hs. 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.   
      
   ...   
      
   My hunch tells me its due to hardware/firmware level I/O handling bug/glitch   
   or limitation on the storage device side. If the device was plugged to the   
   front panel port, try plugging it directly to the back panel port without   
   using any extension cable to avoid any interference.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca