I bought a 250 gig HD a while back and it has been giving me problems.
I think it is because you are suppsed to have a bios that supports 48-bit lba, mine is 32 bit
but the bios could "see" the whole drive so I figured everything was fine until the other day all the files on the 250gb was corrupted well even though my bios can unexplainably detect the whole drive, I realied that it was actually a windows problem my atapi.sys driver file wasn't ver. 5.1.2600.1135 or newer i tried to get the hotfix, but wouldn't let me install because I already had sp1 which was SUPPOSED to have it the problem is that I often hibernate my computer, and without the new version of atapi.sys when it does the memory dump it only sees 137 gb of the drive so then I got sp2 and it fixed my problem with atapi.sys I think, but I'm worried about files getting corrupted.
What should I do? Do you think the files will be alright now?
edit: Found this guess it was sp2 ** Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
I think it is because you are suppsed to have a bios that supports 48-bit lba, mine is 32 bit
but the bios could "see" the whole drive so I figured everything was fine until the other day all the files on the 250gb was corrupted well even though my bios can unexplainably detect the whole drive, I realied that it was actually a windows problem my atapi.sys driver file wasn't ver. 5.1.2600.1135 or newer i tried to get the hotfix, but wouldn't let me install because I already had sp1 which was SUPPOSED to have it the problem is that I often hibernate my computer, and without the new version of atapi.sys when it does the memory dump it only sees 137 gb of the drive so then I got sp2 and it fixed my problem with atapi.sys I think, but I'm worried about files getting corrupted.
What should I do? Do you think the files will be alright now?
edit: Found this guess it was sp2 ** Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.