Quote:
|
Originally Posted by Green Spit
Try running Fdisk. Fdisk talks directly to the hard drive and bypasses all else, if fdisk fails to work in anyway then it is definately the drive (very small possiblility its the cable so if you have two try it with each).
|
Which Fdisk do you talk about? The Microsoft FDISK uses standard int13 calls (im not even sure if a version supporting extended int13 is available yet). Int13 doesnt mean that it talks "directly to the hard drive" - it just means it uses the BIOS routines instead of windows drivers. Talking "directly" would mean to do ATA(PI) communication with the controller on the drive.
(no time to read the rest of the thread currently - i just spotted this posting)