![]() ![]() ![]() |
|
tonyhughes: And pick up chicks too I'd say.
ubergeeknz:tonyhughes: And pick up chicks too I'd say.
And then she said "Your hard drive is just not as big as you say it is!"
I'm not a complete idiot, I still have some parts missing.
sidefx:
Which is correct and illustrates where the standardised binary prefixes are less confusing in distinguishing between the two:
1TB = 1000GB = 1 000 000 MB = 1000 000 000 KB = 1000 000 000 000 Bytes = 976 562 500 KiB = 953 674 MiB = 931 GiB
But given they've barely been adopted at all in the hardware\software industry the confusion is just something we live with.
Kyanar: 1TB=1024GB. That is all.
Kyanar:
They haven't been adopted because they're stupid. Noone wants to randomly change the measurement system that's been happily in use by everyone except hard drive manufacturers for the last 30 years simply because someone got their panties in a bunch about misuse of SI prefixes. And they certainly don't want to change to a system where every unit sounds like something their cat vomits up on the floor.
1TB=1024GB. That is all.
"I was born not knowing and have had only a little time to change that here and there." | Electric Kiwi | Sharesies
- Richard Feynman
*Insert big spe*dtest result here*
sidefx:Kyanar:
They haven't been adopted because they're stupid. Noone wants to randomly change the measurement system that's been happily in use by everyone except hard drive manufacturers for the last 30 years simply because someone got their panties in a bunch about misuse of SI prefixes. And they certainly don't want to change to a system where every unit sounds like something their cat vomits up on the floor.
1TB=1024GB. That is all.
Except it hasn't been "happily in use by everyone except hard drive manufacturers" in computing. There are plenty of other examples. GigE is 1,000,000,000 bits per second. CD-ROM speeds (1x, 4x, etc) are based on metric. DVD capacities are generally quoted in metric. A 1 GHz processor run at... well you can probably guess.
It's just created in a weird mix in the computing world where while most people in the industry know where each is used, there are still plenty of gotchas.
Please support Geekzone by subscribing, or using one of our referral links: Dosh referral: 00001283 | Sharesies | Goodsync | Mighty Ape | Backblaze
freitasm on Keybase | My technology disclosure
freitasm:
No, not... Where bits and bytes are used - binary quantities, M, G, T are well established as a 1024 multiplier. The "GHz processor" example is wrong because the Hz measurement is not binary.
As per this 1000 is to be used for powers of 10 and 1024 for powers of 2.
"I was born not knowing and have had only a little time to change that here and there." | Electric Kiwi | Sharesies
- Richard Feynman
hamish225: the least they could all do is if they indeed are using metric they should use the appropriate unit name. so just to clarify, GIB is metric and gb is the other one?
hahahahaha thanks for the replies and the laugh :P
1 GB = 1024 MB
Ray Taylor
There is no place like localhost
Spreadsheet for Comparing Electricity Plans Here
raytaylor:hamish225: the least they could all do is if they indeed are using metric they should use the appropriate unit name. so just to clarify, GIB is metric and gb is the other one?
hahahahaha thanks for the replies and the laugh :P
Problem is
GB = gigaByte
Gb = gigabit
The upper case B = Byte, or 8 bits
The lower case b = bit, or 1/8th of a byte
So if your hard drive had 1024 GB of storage, it would have 8192 Gb of storage
Historically Bytes were used to measure the capacity of a storage medium such as a hard drive, and bits were used to measure a network speed between computers (bits per second)
Older networking systems such as serial cables etc. didnt necessarily use protocols that had 8 bits to one Byte. So the standard form of measurement was to measure speed in bits.
At this time you would use a cassette tape to store your data and you didnt buy it in storage capacity because different systems read and write to the cassette at different speeds - so you just had the 60 or 90 min tapes. However at this time it was common for you to dial up to a BBS system or use a serial cable to link computers and because of the different formats, bits per second was used to measure the speed of your modem or cable.
Later when digital consumer storage mediums entered the retail market - such as floppy disks and hard disks, the format of 8 bits to a Byte was common and so capacity in bytes became the standard.
Correct me if i am wrong
GIB and gib would be good if only the G was used to tell the difference, but because there is already too much confusion between bits and Bytes, it would just add to the difficulty.
1 GB = 1024 MB
+1
I dont like mac computers artifically rounding numbers like suggested above. One of the many reasons i dont use them. They dumb things down and when you do that, you get consumers ringing up saying things like the op's original question. HDD manufacturers should go back to using the proper 1024x system.
Or advertise a Terrabyte hard drive capable of 1,073,741,824 bytes. But that wont stop the problem of a hard drive file system such as EXT, FAT, FAT32 or NTFS having its own overhead and removing part of that capacity - still causing a mismatch in numbers between raw capacity and what is shown on the end user's screen.
The hard drive manufacturer cannot control what operating system, file format or how the files are organised and managed on the hard drive, and therefore cannot guarantee that you will get a certain amount of USABLE capacity - they can only guarantee an amount of RAW capacity.
I had this conversation with a lame customer who bought a computer from a retail company i worked for a few years ago. Basically he was trying to come up with a reason to get out of his hire purchase contract after 3 months of signing it because he wanted to buy dragon ball z cards off trademe instead.
Anyhow the argument of computer manufactures such as Dell, Acer, HP and Asus using the hard drive manufacturers specifications is also moot - because the pc maker may sell it with windows, that had its file managment overheads, but the customer is free to install linux or anything else that may use less space for file managment. Therefore they too can only tell you the raw data capacity, and it comes back to the end user to decide how they want to use it. If the end user decides to use an operating system that reserves 10% for file managment then thats up to them.
*Insert big spe*dtest result here*
|
![]() ![]() ![]() |