Delayed Write Error :-(

[#66]

I know that this is not the place for this type of problem, but maybe someone has had the same problem and has a fix. Or help from doing the same as me!

Problem. Original XP doesn't support disks over 137GB. In service pack 1 this is fixed. I have done everything possible to fix this, registry fix etc etc but to no avail. Anyone ? Yes my mobo does suppot 48bit etc. I have SP2

Think I'm looking at a reformat of the drive.

This shows that one should install the second (larger than 137GB) drive AFTER one had installed sp 1 or 2.

[HtV]

I guess the drive is formatted 137 GB, you can probably "enlarge" the drive with a program like partition manager or acronis, without losing the data.

[mikelu]

I got such an error writing to a Firewire drive. I believe it's because XP, over time, tries to write in larger and larger buffers, until finally there's an error. I ended up using an ATA drive instead, but turning off write-cacheing may fix it for you.

[Lindsay]

Your post is confusing. I presumed your problem was the "Delayed write error" but you then go on about disk sizes and SP versions.

There are several possibilities for the delayed write error. Do a google search on these words and see if anything matches your system.

[pBS]

that error is usually a sign of drive failure on one or more sectors..
[which also is caused by the addressing error if system doesn't have 48bit on]
Presizer is a free re-sizer that allows you to keep all data and resize..but you have to be sure fix the 48bit problem first.. there's a 48bit.inf out there that you can right click on and hit 'install' and that should fix it up...[turn it on]
[search for 48bit.inf i think it's called]
i remember as long as you had the newest service packs even win2k would support it..[all that's required is having the newer ntfs version,and win2ksp4 does]
i'm pretty sure even xpsp1 only needs the inf installed...it should be correct ntfs..
then do a surface scan of the drive, it may have developed bad sectors from power surges etc..[not fatal but needs to be remapped]
sometimes it won't give you any errors till you defrag or copy long files..by then it's too late..whole fat table will be toast...but if it's just a bad sector, just have chkdsk mark it bad and all is well..
makes no differnece when you set it up as long as you don't try to access data past 137g marker before applying fix...
[which is easy, so do it soon as possible]
is yours working now?

[pBS]

i usually don't have to deal with this issue cuz i slipstreamed sp2 into my xp install cd...
[it's fairly simple,instructions are on the web]
plus it's a cleaner install with less work afterwards..

[drain]

I had this problem with my SATA drives. Though it was a drive fault, so I replaced the drive, but still had there error. Also tried the drives in other machines, and finally replaced my Gigabyte motherboard with a Foxconn, and all is sweet now (and I have a total of 450GB storage)! I reckon it's a incompatibility problem.

[Jeff]

I had a problem like this with an external USB drive. It turns out the drive was fine but that the controller board for the drive was bad. I bough a new external USB drive box and moved the disk from the old box to the new one. All is now fine.

Jeff

[#66]

thanks pBs, good informative post. I'll give it a wirl and let you know how it went.

BTW I have seached and read at least a hundred different forum posts on the subject. Just wasn't getting anyware! Everything on my systems says all is ok. Just have to work on it. Also save up for a new drive, can see I'm going to need one as thee wife has found out how to record everything!

[Rexel99]

My 200G was doing this early on, std IDE drive gave this error while recording just occasionally. I basically tweaked and confirmed bios drive settings, rebooted a few times and it got working again. aside from an occasional recurrance (like 3 times) it's been good for over a year. Confirm you have no windows power saving features set either.