>>Al;
>>
>>It is nice to have know where to look for answers. Now the value of the answer is another story all together!
>>
>>I presume answers like this solve problems for some people. Somehow I would expect a definition of what caused the error and how to resolve and prevent it. Do people devote his/her professional skills to develop such answers or do they "get paid by the pound". One pound of soultions equals $$$. Oh well, we all have to survive somehow! :)
>>
>>
>>
>>A search on "Delayed Write Failed" provided the following for the first "answer".
>>
>>
>>Error Message:
>>(Lost Delayed-Write Data) The system was attempting to transfer file data from buffers to filename. The write operation failed, and only some of the data may have been written to the file.
>>User Action:
>>There may have been a loss of data. Decide if the missing data is important enough to restore the file from backup and redo the file operations that led up to the message.
>>
>>
>>
>>
>>I would imagine that the person who wrote this if confronted with such a problem would stay up for days attempting to make a decision. “Now should I restore from backup or redo the file? Is the data important”? Decisions, decisions! Decisions can be so complex especially when you have an Error Message and failed operation.
>
>It's easy to denigrate or poke fun at KB support from MS. OTOH it's a good place to start, it represents a lot of real-world experience, it's aimed at a range of end users (not all are developers or support pros) and the price is right. I don't know if the originator of this thread was aware of this resource but if not, it's the first place to go to help solve problems of this nature.

Al;

I understand that we all get what we pay for in life. I do not think that the answer I referenced was done in a professional manner and has no real value. Such utterings are a waste of time and should not be available to the community. If there is an editor in charge of what is posted they failed to do a creditable job.

Tom