Problem with windows xp service pack 2

Description:
Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file [name_of_the_file_you_want_to_save].
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.
Cause:
This problem occurs when the data redirector of a System flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access.
When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file.
More Information:
The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle.
Remediation:
Warning: Serious problems might occur if you configure the registry incorrectly by using the Registry Editor. Microsoft recommends that you create a backup of your current registry before making changes.
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then press ENTER.
3. In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
4. In the right pane, click EnableOplocks, and then press ENTER.
5. In the Value data box, type 0, and then press ENTER.
6. Quit Registry Editor.

This problem occurs when the redirector flushes the contents of the file, and writes to a file handle with read-only access instead of to a file handle with write access. When the redirector received an opportunistic lock break to none, it purged the cache for the file, but did not uninitialize the cache for the file. The redirector also needed to purge and uninitialize when the set end of file occurs because the opportunistic lock break is asynchronous. Because it did not uninitialize the cache for the file, it wrote to the incorrect file handle.Back to the top RESOLUTION Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack Back to the top Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Windows XP SP1, Windows XP Tablet PC Edition

Date Time Version Size File name
--------------------------------------------------------------
30-Jan-2003 21:41 5.1.2600.1164 400,896 Mrxsmb.sys
30-Jan-2003 21:41 5.1.2600.1164 154,880 Rdbss.sys

Windows XP 64-Bit Edition

Date Time Version Size File name
-------------------------------------------------------------
30-Jan-2003 21:41 5.1.2600.1164 1,259,392 Mrxsmb.sys
30-Jan-2003 21:41 5.1.2600.1164 489,216 Rdbss.sys


Back to the top
WORKAROUND
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To work around this problem, disable opportunistic locking on the file server:

Click Start, and then click Run.
In the Open box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters
In the right pane, click EnableOplocks, and then press ENTER.
In the Value data box, type 0, and then press ENTER.
Quit Registry Editor.

Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows XP Service Pack 2.
Back to the top
MORE INFORMATION
For additional information about opportunistic locking, click the following article number to view the article in the Microsoft Knowledge Base:
296264 Configuring Opportunistic Locking in Windows 2000
A trace of this problem shows that the file is opened at least two times, and shows the system improperly writing to the read-only file handle. A trace that shows this problem is similar to the following:

96 CLIENT SMB: C NT create & X, File = \newshare.xls
SMB: Desired Access = 0x00020089
(Read Data,Read EA,Read Attributes)
97 SERVER SMB: R NT create & X, FID = 0x5
SMB: Oplock Level = Batch

<content removed that displays the client program reading and locking the file, but the file is not closed>

450 CLIENT SMB: C NT create &amp; X, File = \newshare.xls
SMB: Desired Access = 0x0002019F
(Read/Write Data, Read/Write EA, Read/Write Attributes)

451 SERVER SMB: R NT create &amp; X, FID = 0xc007
SMB: Oplock Level = NONE

<content removed that displays the client program reading, locking, writing and flushing data on this file handle>

585 CLIENT SMB: C write &amp; X, FID = 0x5, Write 0xc00 at 0x00005000
PID = 0xFEFF TID = 0x1002 MID = 0x4400 UID = 0x0801
586 SERVER SMB: R write &amp; X - NT error, System, Error, Code = (34) STATUS_ACCESS_DENIED

Note The process identifier (PID) of 0xFEFF in frame 585 represents the client system process that is using the read-only file handle. It does not show the client program writing the data to disk.
Back to the top

You've got a "hardware" problem with the disk-drive. Windows cannot write an updated 'MFT' ("Master File Table") to reflect files that you have added/deleted/updated on the Maxtor.

Copy all the files from the Maxtor, e.g., onto another external drive, or "burning" to DVD disks, and then replace the Maxtor disk-drive.

Either the disk-drive is "full", or the disk-drive has become defective.

If the former, then delete some files.

If the latter, buy another external drive, and copy all the files from the "old" drive to the "new" drive, before the drive COMPLETELY "fails".

If the warranty for the Seagate still is active, then exercise the warranty to get a free replacement.

Hi when you buy a hard disk you do not get instructions on how to change from FATS to NTFS. Your hard drive is set to FATS by default,which limits you tranferring files up to 4GB.If you changing to NTFS does 2 things. 1.you can transfer bigger files.
2. You will lose all data on the drive so you have to save any files to another drive ect
To change to NTFS, go to Start then Right-click on My Computer and select Manage. Under Storage click on Disk Management. Now find your hard drive in the list and Right-click on it and select Format. Under File System change the Answer to NTFS and leave the Allocation Unit to default.Click on Perform Quick Format if you want. click OK and confirm your OK with losing all data on the drive,and your done.
Regards Bill

try to format the drive

windows - delayed write failed
Windows was unable to save all the data for the file I:\$mft.
The data has been lost. This errors may be caused by failure of
your computer hardware or network connection. Plese try to save elseware.

(sited from http://www.winxptutor.com/randomfolders.htm)

When you install Windows XP SP1, SP1a or SP2, this temporary folder is created on the volume that has the most free space. The folder name contains random characters, and is not always created on the same volume as the Windows folder. For example, this temporary folder may have the following random names:
9470bb12e8a4f3447657236478e41c5
or similar.
352b81d1c4bf3810e28482d9979

This folder is automatically deleted by Windows XP after you install the service pack. However, if the folder is not automatically deleted by Windows XP, you can safely delete this folder.

Please Note:
In most cases, you will receive an Access denied message while accessing or deleting this folder. First, you'll need to Take Ownership of the folder and then delete it safely.

delayed write failed is a symptom of failure of the drive where the error comes, if the error includes drive c: that would mean that your c drive is having problems and might need to be replaced.

this needs to be looked at by a professional, I can't see the problem over the internet and I suggest you take the computer to be checked out.

hi there my friend,

we have the hard way and then we have the easy way...

the hard way is to bootup with your bootable xp cd .follow the installation guide ..then.put in your key when you get the chance to ..and finish the installation. then apply service pack 2 to your installation .. and you're done...

the easy way would be to make a Slipstream Windows XP Service Pack 2 CD....which you can use each time you need to fix your system.

1 - Download the (full) "Network Install" of the Service Pack (English version [266 MB]), and save it to a directory (folder) on your hard drive (in my case D:\XP-SP2). Other languages can be downloaded from the Microsoft Download Web site.

Note: do not use spaces in the folder name!

2 - copy your Windows XP CD to your hard drive. Just create a folder (I used \XP-CD), and copy all the contents of your Windows XP CD in that folder.

3 - , open a Command Prompt (Start > Run > cmd), and go to the folder where you downloaded SP2 (cd \foldername). Type the command: servicepack filename /integrate:drive/path. In my example the command is WindowsXP-KB835935-SP2-ENU /integrate:D:\XP-CD.

Extract SP2 files

If you get the error:

This service pack can't be integrated error

This is caused by the fact that your Windows XP CD contains updates that will be automatically installed when you run setup. This type of CD's will usually be from larger OEM suppliers (like Dell, HP, or others).

You cannot use this type of CD to create a slipstreamed SP2 install.

First, the files will be extracted, and next they will be integrated in your Windows XP files:

Updating Windows Share

When ready, you should get a confirmation. Windows XP Service Pack 2 has now been Slipstreamed into your original Windows XP files.

Slipstream Completed


Creating a Bootable CD

For this part I used IsoBuster and Nero Burning ROM 6

After you install IsoBuster, you can choose to use only the product's free functionality for what we want to do, IsoBuster will look like the image below (you need to have your original Windows XP CD in the CD-ROM drive).

Start to extract the boot loader from the original Windows XP CD. Using IsoBuster, select the "folder" Bootable CD, and right-click Microsoft Corporation.img. From the menu choose Extract Microsoft Corporation.img, and extract it to the folder on your hard drive where you have your Windows XP files (D:\XP-CD in my case).

Extract Boot Image

Next, start Nero Burning ROM, and choose CD-ROM (Boot) in the New Compilation window. On the Boot tab, select Image file under Source of boot image data, and browse to the location of the Microsoft Corporation.img file. Also enable Expert Settings, choosing No Emulation, and changing the Number of loaded sectors to 4 (otherwise it won't boot!)

Nero Boot Settings

The ISO tab should be configured correctly as shown below:

Nero ISO Settings

If you have an older version of Nero you won't have the option Do Not Add ";1" ISO file version extention under Relax ISO Restrictions. You won't be able to boot your new CD, so update Nero!
You can configure the Label tab to your liking, I would however recommend that you keep the Volume Label the same as on your original Windows XP CD. Here are some (English) Labels:

* Windows XP Professional: WXPCCP_EN
* Windows XP Home: WXHCCP_EN
* Windows XP Professional OEM: WXPOEM_EN
* Windows XP Home OEM: WXHOEM_EN

Nero Label Settings

Next press New, and from the File Browser window, select the files and folders from your slipstreamed location (in my case D:\XP-CD). Now drag & drop the selected files in the ISO1 window.

Copy Files

Next, burn your new CD.

Burn

You now have a Bootable, Slipstreamed Windows XP Service Pack 2 CD!

The harddrive itself has gone bad, only solution would be to replace the HDD inside the enclosure :-( sorry.