• 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.

"160gig" = ???

Homerboy

Homerboy

Lifer
yeah I know I shouldnt get "160gig" in windows
but what SHOULD I see?

I ask becuase I have 2 160gig drives installed

windows sees one as 157gig and the other as 128gig?
 
look on the drive sometimes it will give the conversion generaly 1 gig = one billion bytes for hdd manufacturers. in reality there are 1024 megabytes not 1000 megabytes in a gigabyte so a true 160 gig drive would be 163840 megabytes not 100000 bytes as the manufacturer claims there is kind of a rip off but if you do the math you can get what you want and drives are cheap i just got a wd 160 gig 8 meg cache for 100.
sometimes xp setup does strange things with new hdds i got a new seagate 160 gig drive installed xp on it got into explorer and it showed as 131 gigs went to disk managment and there were 2 partitions on it a 131 gig and a 24 gig. who knows try that and see
have fun with all of the new space you got
 
I believe that you may be mistaken, it is not on the megabyte level that the mistake is made, but on the kilobyte level. 156 gigs should be about the amount. 160 * 1,000,000 (convert into kilobytes), 160,000,000KB/1,024KB=156,250 MB or 156.250 Gigs.
 
Look at the packaging and advertising for your HDD. All of them state "1 GB = 1,000,000,000 bytes". And that definition of GB is just as correct as 1 GB = 2^30 bytes. Why do you think there's been an initiative to use the giga-binary notation when referring to memory? "Kilo" is "one thousand" not "one thousand twenty-four". The units are ambiguous.

1 KB = 1,000 bytes: "Kilobyte"
1 KiB = 2^10 bytes = 1,024 bytes: "Kilo-binary-byte" or "Kibibyte"
1 MB = 1,000,000 bytes
1 MiB = 2^20 bytes = 1,048,576 bytes
1 GB = 1,000,000,000 byes
1 GiB = 2^30 bytes = 1,073,741,824 bytes.
 
long sotry short is that it should be more like ~155gig and NOT 128 correct?
thats what has me worried

the one that IS registering ~155 has corrupted my data 2 times now and is going to be sent back for RMA.

but I dont get why this other one is registering so small
 
Originally posted by: Homerboy
yeah I know I shouldnt get "160gig" in windows
but what SHOULD I see?

I ask becuase I have 2 160gig drives installed

windows sees one as 157gig and the other as 128gig?
Click to expand...

Clearly, if both drives are supposed to be "160GB", then there is a problem. What kind of drives are they, and more importantly, how are they connected? What OS are you running (and what service pack level)?
If you are loading any IDE controller drivers other than the ones built-in by default into Windows, then what version are they?

At first glance, it appears that one of the drives is being recognized fully, and using 48-bit LBA support, and one is not. That doesn't make sense though, unless they are plugged into different controllers.

Even if they are, answers to those questions above should help unravel this mystery. 🙂
 
Yep, the only time I'veen a large HDD come up as 127-128 GB is when 48-bit LBA is off. Are the drives on different controllers?
 
one is plugged into IDE1 and the other IDE2 (MB's IDE controllers)
Win2k with all the latest bazaillion patches and service packs.

Fully detected: Maxtor (I dont know model off top of my head).
"Partially" detected: Samsung SP1604N

No 3rd aprty IDE controllers loaded
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top