Quote (DCSS @ Nov 14 2017 06:04pm)
No, you got the correct amount, it''s just that what windows sees as 1tb differs from what 1tb actually is
like 1000gb vs 1024gb type of difference
That's not quite correct.
What they do is downright nasty. They compound the rounding. This would be like selling a house as having 3000 sq ft, but it turns out that it's only 2600 sq ft, because they rounded each room up to the nearest 100, but never rounded down.
I have a 256GB hard drive. It's not (1000/1024) * 256 = 250GB. It's actually 238GB after formatting. Tack on the space taken up by the OS, and it is understandable why people were upset about 8GB capacity iPhones, or 128GB capacity hard drives that OS's were installed on. The amount of space lost ends up being quite a bit on both ends: The actual maximum capacity, and the space used by default in order to have an operating system.
As you can see from the following, the rounding goes all the way down to the KB. They obviously don't round bit-byte from 8 to 10 though, as that wouldn't favor them.
Code
Actual Rounded favourably
1 Byte = 8 bits 8 bits
1 KB = 1024 bytes 1000 bytes
1 MB = 1024KB 1000 KB
1 GB = 1024MB 1000 MB
Working backwards:
Actual Rounded
GB to MB 256 GB = 262144 256000
MB to KB 256 GB = 268435456 256000000
KB to Byte 256 GB = 2.74878E+11 2.56E+11
Byte to bit 256 GB = 2.19902E+12 2.048E+12
Convert back to actual GB read-out: 256 238.4185791
This post was edited by Canadian_Man on Nov 22 2017 09:00pm