Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[Cookie]

I have recently installed my new IDE hard drive (ST380215A). BIOS detects it ok. But during the Windows XP installation I receive "Setup cannot copy the file" errors. It happens to significant number of files. I've tried installing it several times and what I don't like is that it happens to the same files. Does it mean that some sectors on HD are corrupted?(I know that the CDROM and the CD are ok). I've run the Basic and Long tests using SeaTools and no errors were found.

[JanJanssen]

Maybe try the Seatools for DOS full zero-fill and then try the XP install again.

Also, are you sure the jumper is set correctly on the drive?

Have you ever  used that XP install CD before?  Like on another drive?

Is it a proper CD or is it a burn? 

[Cookie]

The jumper is set to Cable select.

I don't think the problem is with CD. I've tried 2 different CDs on two CDROMS and it gave me the same mistakes.

I have some other bad news . I have tried using SeaTools again and now it doesn't detect the hard drive! I'm also unable to create partitions.

I can't figure out is it the problem with the drive or some other hardware???

[JanJanssen]

Sounds like a bad drive probably.

Try connecting this drive to the master position on the secondary IDE cable (make sure that cable is an UltraATA cable) and make sure the BIOS detection mode for that drive is set to AUTO.  If it still doesn't detect, take the drive back to the store.

[Cookie]

I've tried this hd on another computer and windows installed ok there. So it's probably the problem with some other hardware. I wonder could it be the memory?

[Dawg]

Hi Cookie, just posted on this very problem then noticed your thread, probably get shot now!

Anyway, sounds like these drives have compatability issuses to me, I have 2 st380815a, I am guessing there sata vers of your drive, dont spose you are using asus board or something with an ICH9 chipset? Prob not if your installing an IDE. Strange we both have same fault from same manufacture but diff model and prob diff hardware?

Alan