Originally posted by: TwiceOver
Is this another formatted vs. unformatted capacity suit? If so it is not really Seagate's fault that formatting chews up space.
It doesn't. Not that much anyway.
Originally posted by: TwiceOver
Is this another formatted vs. unformatted capacity suit? If so it is not really Seagate's fault that formatting chews up space.
God bless America.Originally posted by: Exterous
How can they sue if the size assumptions are listed on the box?
Originally posted by: DivideBYZero
Originally posted by: AkumaX
wtf i just got this too
if theyre doing the Gb != gb crap, shouldn't all the hdd manufacturers get sued?
Well that is ~2%, and this claims 7%. I can only assume that they are being dicks and moaning about formatted space. Seagate can just argue that they have no direct impact on the way the OS of your choice formats the space and boom, no case.
You can use a drive raw, if you wish, for example...just not in windows, AFAIK.
Dumb lawsuit anyhow.
Originally posted by: Zenmervolt
Originally posted by: DivideBYZero
Originally posted by: AkumaX
wtf i just got this too
if theyre doing the Gb != gb crap, shouldn't all the hdd manufacturers get sued?
Well that is ~2%, and this claims 7%. I can only assume that they are being dicks and moaning about formatted space. Seagate can just argue that they have no direct impact on the way the OS of your choice formats the space and boom, no case.
You can use a drive raw, if you wish, for example...just not in windows, AFAIK.
Dumb lawsuit anyhow.
That 2.4% only applies if they are measuring the space in kilobytes. Otherwise it compounds. (2.4% difference on the kilobytes, then a 2.4% difference additionally when they compute the megabytes, then another 2.4% difference when they compute the gigabytes.) That means 97.6%^3 or 92.97% is what is actually available for use on a drive. That gives us a difference of a little over 7%. This suit is going nowhere.
ZV
Originally posted by: TwiceOver
Heh, just got the notice also. Seagate has always done right by me, I have no complaints. Not going to waste my time with this.
Here's a better analogy. If a container of milk was 128 ounces by volume, and clearly disclosed as such on the container, you are saying that retarded consumers who don't know the difference between ounces by weight and volume would have a legitimate reason to sue because their container of milk doesn't weigh eight pounds (128 / 16)?Originally posted by: seemingly random
I would like to see disk drive manufacturers held accountable for accuracy in the definition of KB, MB, GB, etc. The term KB refers to KiloByte which equals 1024. One thousand equals 1000. This has nothing to with formatted capacity.
I think there would be complaints if a 'gallon' of milk contained just 60oz.
Originally posted by: Pugnax
These things only make the lawyers more money. The ones who really "suffered" (if that is even the case) usually end up with 5 bucks and about 10 wasted hours.
Originally posted by: tcsenter
Here's a better analogy. If a container of milk was 128 ounces by volume, and clearly disclosed as such on the container, you are saying that retarded consumers who don't know the difference between ounces by weight and volume would have a legitimate reason to sue because their container of milk doesn't weigh eight pounds (128 / 16)?Originally posted by: seemingly random
I would like to see disk drive manufacturers held accountable for accuracy in the definition of KB, MB, GB, etc. The term KB refers to KiloByte which equals 1024. One thousand equals 1000. This has nothing to with formatted capacity.
I think there would be complaints if a 'gallon' of milk contained just 60oz.
The prefix kilo does not mean 1024.
A kilometer is not 1024 meters
A kilogram is not 1024 grams
A kilowatt is not 1024 watts
Hard drive and computer storage manufacturers have been using the 'accurate definition' of KB, MB, and GB since the 1950s.
Originally posted by: mugs
And when I actually hear someone say their computer has 2 gibs of RAM, then they can get indignant when I call my gibs gigs.
But weights and measures are defined by international convention, treaty, or government chartered organizations, such as IEEE, IEC, ISO, ANSI, and BIPM. And those authorities say kilo, mega, and giga are always 10-base in any context, without exception.Language is not defined by a dictionary...
On the contrary, consider networking, telecom, and computer bus clock and transmission frequencies, data transfer and signaling rates, all of which use SI prefix correctly:the dictionary reflects the way people actually use the language. In the context of computer storage, pretty much everyone other than storage manufacturers use the SI prefixes to represent their binary approximations.
The presentation of hard disk drive capacity by an operating system using MB in a binary sense appears no earlier than Macintosh Finder after 1984. Prior to that, on the systems that had a hard disk drive, capacity was presented in decimal digits with no prefix of any sort (e.g., MS/PC DOS CHKDSK command).
Originally posted by: tcsenter
But weights and measures are defined by international convention, treaty, or government chartered organizations, such as IEEE, IEC, ISO, ANSI, and BIPM. And those authorities say kilo, mega, and giga are always 10-base in any context, without exception.Language is not defined by a dictionary...
On the contrary, consider networking, telecom, and computer bus clock and transmission frequencies, data transfer and signaling rates, all of which use SI prefix correctly:the dictionary reflects the way people actually use the language. In the context of computer storage, pretty much everyone other than storage manufacturers use the SI prefixes to represent their binary approximations.
1kbit = 1,000 bits
10Mbit = 10 million bits
100Mbit = 100 million bits
1Gbit = one billion bits
10KHz = 10,000 Hz
100MHz = 100 million Hz
1.0GHz = one billion Hz
So within the entire realm of information technology, the only real-world application for the inaccurate binary approximation is uniquely and singularly digital storage, and only as it applies to the actual presence of formatted data.
What you are saying is that everyone in the world is supposed to define these prefixes as 10-base, except for digital storage manufacturers? Now that is a lawsuit that would have merit. IOW, manufacturers would be sued for using a definition of these prefixes that is at odds with long-established and universally accepted meanings adopted internationally and in common use among the general public without controversy.
That is kinda the definition of misleading or false advertising. As it stands now, these lawsuits have no merit whatsoever, but they would if manufacturers were to define the SI prefixes as 2-base.
From Wikipedia on the relatively recent origins of the binary v. decimal controversy:
The presentation of hard disk drive capacity by an operating system using MB in a binary sense appears no earlier than Macintosh Finder after 1984. Prior to that, on the systems that had a hard disk drive, capacity was presented in decimal digits with no prefix of any sort (e.g., MS/PC DOS CHKDSK command).