I'm sorry to be the ******* man but you're extremely ignorant. You need to learn how to form a sentence without lulz and bruh.![]()
okay bruh.. lulz
I'm sorry to be the ******* man but you're extremely ignorant. You need to learn how to form a sentence without lulz and bruh.![]()
I'm still a bit confused on how this storage **** works. Sorry but can you please explain it again.See the attached. This is my main 120GB SSD in my desktop. You will see it was 119,000,000 bytes, which is where the manufacturer gets the size 120GB, but the OS only sees it as 110GB, due to binary addressing.
Question
Why is my drive displaying a slightly less than expected capacity in Windows or Mac?
Answer
Determining drive capacity can be confusing at times because of the different measurement standards that are often used. When dealing with Windows and Mac based systems, you will commonly see both decimal measurements and binary measurements of a drive's capacity. In either case, a drive's capacity is measured by using the total number of bytes available on the drive. As long as the drive displays the correct number of bytes (approximate), you are getting the drive's full capacity.
Decimal vs. Binary:
For simplicity and consistency, hard drive manufacturers define a megabyte as 1,000,000 bytes and a gigabyte as 1,000,000,000 bytes. This is a decimal (base 10) measurement and is the industry standard. However, certain system BIOSs, FDISK and Windows define a megabyte as 1,048,576 bytes and a gigabyte as 1,073,741,824 bytes. Mac systems also use these values. These are binary (base 2) measurements.
Various Drive Sizes and their Binary and Decimal Capacities
Drive Size--------Approximate--------Decimal Capacity--------Approx Binary Capacity
in GB--------------Total Bytes------(bytes/1,000,000,000)-----(bytes/1,073,724,841)
10 GB-------------10,000,000,000------------10 GB------------------------9.31 GB
20 GB-------------20,000,000,000------------20 GB------------------------18.63 GB
30 GB-------------30,000,000,000------------30 GB------------------------27.94 GB
40 GB-------------40,000,000,000------------40 GB------------------------37.25 GB
60 GB-------------60,000,000,000------------60 GB------------------------55.88 GB
80 GB-------------80,000,000,000------------80 GB------------------------74.51 GB
100 GB-----------100,000,000,000-----------100 GB------------------------93.13 GB
120 GB-----------120,000,000,000-----------120 GB-----------------------111.76 GB
160 GB-----------160,000,000,000-----------160 GB-----------------------149.01 GB
180 GB-----------180,000,000,000-----------180 GB-----------------------167.64 GB
200 GB-----------200,000,000,000-----------200 GB-----------------------186.26 GB
250 GB-----------250,000,000,000-----------250 GB-----------------------232.83 GB
I honestly can't belive this has gotten to 4 pages long. The question was asked and answered and answered and answered and yet it still goes on.
Thanks for the enlightening responses lulz
From your username to your comments, I'm thinking you are an internet time traveler from the year 2005.
I can't believe how much this gets asked given that it's not unique to iPhones. Hard drives, SSDs, and all storage devices are all marketed in gigabytes (GB) where 1 GB byte = 1,000,000,000 bytes. The virtual capacity reported by the OS is actually expressed in gibabytes (GiB) where 1Gib = 1,073,741,824 bytes.
That's the difference plus some for that used by formatting, OS, etc.
I am tired of seeing this response to this question. I understand how the conversion works. iTunes shows drive size and capacity in GB (same unit of measure), not GiB or gb (lower case ). In my case, what is blocking 13.66 GB (10.67%) of capacity? That seems high for partition / os overhead. Any ways, just tired of seeing the GB to GiB conversion reasoning when it doesn't apply to the intent of the question. See screen shot. View attachment 576492
It does apply, its the conversion and it needs to be accounted for. You have what appears to you as 14gb used but if that was actually the case then 16gb iPhones would only have 2gb of usable space available......?
I am tired of seeing this response to this question. I understand how the conversion works. iTunes shows drive size and capacity in GB (same unit of measure), not GiB or gb (lower case ). In my case, what is blocking 13.66 GB (10.67%) of capacity? That seems high for partition / os overhead. Any ways, just tired of seeing the GB to GiB conversion reasoning when it doesn't apply to the intent of the question. See screen shot. View attachment 576492
I am tired of people responding to 10 month old threads.
While I, in principle, agree, would you rather someone start more and more threads on the same topic that's already been discussed? Damned if you do; damned if you don't.
While I, in principle, agree, would you rather someone start more and more threads on the same topic that's already been discussed? Damned if you do; damned if you don't.
I completely understand if the user who bumped has a question that relates to the thread, but it is pointless if the bumping user is regurgitating information already present in the thread. Your response indicates you didn't notice that.
I am tired of seeing this response to this question. I understand how the conversion works. iTunes shows drive size and capacity in GB (same unit of measure), not GiB or gb (lower case ). In my case, what is blocking 13.66 GB (10.67%) of capacity? That seems high for partition / os overhead. Any ways, just tired of seeing the GB to GiB conversion reasoning when it doesn't apply to the intent of the question. See screen shot. View attachment 576492
I thought this was settled near a year ago.
Apologies, I didn't realize this thread was resurrected.