Delayed write failed?

Rev

I got myself a 2.5" external drive to back up my hard drives onto and store away from the PC, few of my friends do this and it seemed like a good idea. Beats backing up onto 10 DVD's

I remember reading a while back that motherboards with VIA chipsets have a 'delayed write faliure' problem with external drives on USB 2.0 but I had totally forgotten about this until I tried to back up my hard drives and a few files in I get 'delayed write failed'

I have this Asus motherboard with a VIA chipset.

I've searched the net all day for fixes but I can't find anything that worked so I thought I'd ask here and see if anyone has any idea's on how I might be able to stop this before I give up and take the drive back.

Any advice is greatly appreciated.

Thanks

IvanOpinion

I have no idea but if it is a problem with the motherboard USB sockets you could maybe try adding a PCI USB2 card (cost about £5, so it might be worth a try).

Ivan

espresso

I have copied 45GB in one go from a Gigabyte motherboard with a VIA chipset, to a USB2 external hard drive with no problems. If you search the M$ knowledge base you will find various articles about 'delayed write failure'.

Rev

IvanOpinion wrote:

I have no idea but if it is a problem with the motherboard USB sockets you could maybe try adding a PCI USB2 card (cost about £5, so it might be worth a try).

Ivan

I already have one and it's still not working.

Rev

espresso wrote:

I have copied 45GB in one go from a Gigabyte motherboard with a VIA chipset, to a USB2 external hard drive with no problems. If you search the M$ knowledge base you will find various articles about 'delayed write failure'.

Yeah, I searched through them all yesterday, to no avail. It's still happening.

Take a look at this site Via Arena you'll see it's quite a common problem.

Chippy_Minton

Try trawling these threads at HardwareAnalysis.com. Some people said that tweaking the registry with the UltimateBootCD fixed the problem, but beware as in one case data was lost.

Rev

Chippy_Minton wrote:

Try trawling these threads at HardwareAnalysis.com. Some people said that tweaking the registry with the UltimateBootCD fixed the problem, but beware as in one case data was lost.

Thanks. I'll go have a look now.