Using: Windows 11.
I thought all filesizes and the hard drive were measured in Gigabytes, but despite Windows claiming this is the case, they are all measured in Gibibytes. Since that's the case, why Windows omits the "i" in the middle of these units?
For example, I selected 9 files with 6 GB (in fact, GiB, not GB!) each, and Windows says:
54,0 GB (57.982.059.738 bytes)
Using a calculator (to convert bytes to Gibibytes) the end result is:
54.000001156703 GiB
Now, if we do this to GIGABYTES (pay attention to this word), this is what we end up with:
57.982059738 GB
******************
My 1 TB SSD is reported this way by Windows (never mind the rest reserved for partition):
*************
999.409.315.840 bytes = 930 GB
*************
Which the converter says: 930.7724571228 GiB
Or:
999.40931584 GB (meaning 1 TB, we aren't seeing a precise number because the rest of it it's being reserved in terms of partition).
So, 1000 GIGABYTES = 1 TB
or =
931.32 GiB
*******
Did you notice Google Drive free accounts offer 15 GB of disk space and when we create a file with almost 15 GB, it is actually 15 GiB?
Meaning when GOOGLE advertises their accounts offer 15 GB, this is in fact 16.1 GIGABYTES and 15 Gibibytes.
In the end we have plenty of examples of that term, however almost no one calls it for what it is.
A 18 TB hard drive will be reported this way by Windows:
***********
16763 GiB
***********
Not like this:
****************
18000 GB
****************
The only software that was doing things correctly is JDownloader (JDW), which allows us to replace TiB with TB and the same for GiB or GB.
However, I reversed that decision because based on the previous explanations, knowing how many Gigabytes there is in a file is irrelevant, because all we are seeing has the "i' letter in the middle measuring everywhere.
My question is: why such confusion? I don't think this is even similar to the imperial vs. metric system, because the names aren't different.
I thought all filesizes and the hard drive were measured in Gigabytes, but despite Windows claiming this is the case, they are all measured in Gibibytes. Since that's the case, why Windows omits the "i" in the middle of these units?
For example, I selected 9 files with 6 GB (in fact, GiB, not GB!) each, and Windows says:
54,0 GB (57.982.059.738 bytes)
Using a calculator (to convert bytes to Gibibytes) the end result is:
54.000001156703 GiB
Now, if we do this to GIGABYTES (pay attention to this word), this is what we end up with:
57.982059738 GB
******************
My 1 TB SSD is reported this way by Windows (never mind the rest reserved for partition):
*************
999.409.315.840 bytes = 930 GB
*************
Which the converter says: 930.7724571228 GiB
Or:
999.40931584 GB (meaning 1 TB, we aren't seeing a precise number because the rest of it it's being reserved in terms of partition).
So, 1000 GIGABYTES = 1 TB
or =
931.32 GiB
*******
Did you notice Google Drive free accounts offer 15 GB of disk space and when we create a file with almost 15 GB, it is actually 15 GiB?
Meaning when GOOGLE advertises their accounts offer 15 GB, this is in fact 16.1 GIGABYTES and 15 Gibibytes.
In the end we have plenty of examples of that term, however almost no one calls it for what it is.
A 18 TB hard drive will be reported this way by Windows:
***********
16763 GiB
***********
Not like this:
****************
18000 GB
****************
The only software that was doing things correctly is JDownloader (JDW), which allows us to replace TiB with TB and the same for GiB or GB.
However, I reversed that decision because based on the previous explanations, knowing how many Gigabytes there is in a file is irrelevant, because all we are seeing has the "i' letter in the middle measuring everywhere.
My question is: why such confusion? I don't think this is even similar to the imperial vs. metric system, because the names aren't different.