• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Another weird hard drive issue

W

wraith3k

Senior member
So I installed Win2k SP4 to a 200GB SATA drive, only to see that it already is using the drive to the maximum capacity. Correct me if I'm wrong, but I thought win2k did not already have large LBA support enabled. I was sure win2k would have made me make a 137gb partition first during the setup, but it recognized the entire drive. I did go ahead and make the correct registry change anyway though once in windows (to enable lba), but I'm just afraid I might run into data corruption down the road if it tries to write to an area above the 137 gb barrier. I was going to use partition magic to resize the whole thing to 200, but with the way it is now it appears I don't need to. Anyone have some guidance?
 
So basically you're saying I don't need to do anything else, I can just go ahead and use the drive like normal? Any way to confirm the actual size?
 
As I understand it, officially, W2K SP3 and later support 48-bit LBA, but like you, I'm slightly unsure about whether the "EnableBigLBA" registry key needs to be manually set as well. I'm pretty sure that it did in SP3, perhaps it doesn't have to be in SP4, I don't know. I know that using a seperate controller card like a Promise Ultra100 PCI IDE, that looks like a SCSI card to the OS, can bypass the entire issue, because it relies on the SCSI miniport to provide 48-bit LBA, rather than the IDE port driver.
 
Originally posted by: VirtualLarry
As I understand it, officially, W2K SP3 and later support 48-bit LBA, but like you, I'm slightly unsure about whether the "EnableBigLBA" registry key needs to be manually set as well. I'm pretty sure that it did in SP3, perhaps it doesn't have to be in SP4, I don't know. I know that using a seperate controller card like a Promise Ultra100 PCI IDE, that looks like a SCSI card to the OS, can bypass the entire issue, because it relies on the SCSI miniport to provide 48-bit LBA, rather than the IDE port driver.
Click to expand...

I went ahead and set it anyway even though it appears windows was seeing the entire drive. I just don't want to run into that problem where after filling up 137gb, it starts writing over at the start of the drive (this has happened to people who haven't fully prepped their drive for this type of thing)
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top