Slashdot Mirror


Seagate Offers Refunds on 6.2 Million Hard Drives

An anonymous reader writes "Seagate has agreed to settle a lawsuit that alleges that the company mislead customers by selling them hard disk drives with less capacity than the company advertised. The suit states that Seagate's use of the decimal definition of the storage capacity term "gigabyte" was misleading and inaccurate: whereby 1GB = 1 billion bytes. In actuality, 1GB = 1,073,741,824 bytes — a difference of approximately 7% from Seagate's figures. Seagate is saying it will offer a cash refund or free backup and recovery software."

780 comments

  1. wow by Anonymous Coward · · Score: 0, Insightful

    free backup and recovery software... yea, that'll help alot.

    1. Re:wow by mrbcs · · Score: 1

      I'd gladly take that, but this is only for US purchases. I really don't care that much about a rebate though. I like their stuff cause it works. I switched to Seagate about 4 years ago when Maxtor went really bad, really fast. Actually still using the first 80 gig Seagate I bought.

      --
      I'm not anti-social, I'm anti-idiot.
  2. Think this will set precedent? by Adradis · · Score: 4, Insightful

    Wow, I'm surprised that actually went through, if only because the court systems seem so broken. Hopefully, other manufacturers will get the hint and start changing their plans. I could just see this going after other manufacturers too, who insist on using smaller sizes for their measurements to seem bigger.

    1. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      insist on using smaller sizes for their measurements to seem bigger

      and this is new how?

    2. Re:Think this will set precedent? by DiSKiLLeR · · Score: 2, Insightful

      Wow, I'm surprised that actually went through, if only because the court systems seem so broken. Hopefully, other manufacturers will get the hint and start changing their plans. I could just see this going after other manufacturers too, who insist on using smaller sizes for their measurements to seem bigger. I bloody well hope so.
      --
      You can tell how powerful someone is by the magnitude of the crime they can commit and be able to get away with.
    3. Re:Think this will set precedent? by Harmonious+Botch · · Score: 5, Interesting

      There is a precedent of sorts...back in the 80's at Kaypro, we had a customer threaten to sue us because some fool in marketing said that we had 65K of memory, and there was only 64K, of course. Management told him to take a hike. And that was the last we heard of him.

    4. Re:Think this will set precedent? by LodCrappo · · Score: 1

      gee thanks for setting the purely crappiest standard in customer service.

      --
      -Lod
    5. Re:Think this will set precedent? by hedwards · · Score: 1, Insightful

      I bloody well hope so. Why? What they advertised was correct, the hard disks do have the number of gigabytes that they claim to, 8,000,000,000 bits, or 1,000,000,000 bytes. The fact that the OS uses base 2 as the numbering system doesn't negate the fact that there are 8,000,000,000 bits on the hard disk per gigabyte. It isn't the responsibility of the manufacturer to know in all cases how much of that is going to be usable or how it is going to be notated.

      It is just a nominal difference, anybody ignorant enough not to understand that, shouldn't be purchasing hard disks separately from a computer. Better yet, keep them from having a computer, I get enough spam and virus exposure as it is.

      It doesn't really matter what the units are called, as long as they are standard amongst the industry. In this case, they have been standard since before I began using computers 20 years ago.
    6. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      Western Digital settled in the same way for a similar suit a couple years ago...I got some backup software (Retrospect) out of the deal.

    7. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      Uhhh, as soon as they found out they canned the guy. Did you expect them to hire Carmac to predict who would screw up before it happened? Minority report hadn't even been written yet!

    8. Re:Think this will set precedent? by darthflo · · Score: 4, Informative

      Since your post is written with about as much intelligence as one'd expect from a tree stump, I doubt you are going to grasp anything at all, but to try and help you anyway: Read what the U.S. gov't has to say about it. If that's too dry for you, this wikipedia article might be interesting, too.

    9. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      I'm hoping this puts an end to the constant arguing on slashdot every time we have a story about hard drives. It still surprises (and annoys) me that on a tech site like slashdot, we have people that actually believe 1 kilobyte should equal 1000 bytes.

    10. Re:Think this will set precedent? by AndyChrist · · Score: 1

      Who did they tell to take a hike, the customer or the marketroid? Both, I hope.

    11. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      Now i will sue my ISP, i've got 2 Meg connection but i'am not getting 2 Mo downloads, and i've got an IE screenshot to prove it!

      Damned, they sold me 2 * 10^6 bit/sec !!!

    12. Re:Think this will set precedent? by teg · · Score: 1

      Given that "k" is _defined_ to be 1000, "M" 1E6, "G" 1E9 and so on and are generic prefixes, I don't think it should go through even if the courts weren't broken. The prefixes are used properly in computing when it comes to speed, weight, dimensions etc, memory is the bastard exception.

    13. Re:Think this will set precedent? by Eivind · · Score: 4, Insightful

      The difference does however grow as capacity grows.

      The difference between 2^10 bytes and 10^3 bytes is 2.4%. (kilobyte)

      The difference between 2^20 bytes and 10^6 bytes is 4.9% (megabytes)

      The difference between 2^30 bytes and 10^9 bytes is 7.4% (gigabytes)

      The difference between 2^40 bytes and 10^12 bytes is 10% (terabytes)

      In other words, treating 10^(3n) as equivalent to 2^(10n) makes less and less sense as the capacities go up.

    14. Re:Think this will set precedent? by pairo · · Score: 1

      Actually, it should. Since as many people pointed out, k = 10^3. Not 2^10. Instead of defining kX as 10^3 X, you define it as "10^3 X, except if X is bytes, or bits. But not even then always, because we can never make up our minds" (see 1.44 floppies)

    15. Re:Think this will set precedent? by nlogax · · Score: 1

      What? 64K ought to be enough for anyone!

    16. Re:Think this will set precedent? by cripkd · · Score: 2, Interesting

      Must have been, Philip K. Dick, that wrote the original story, died in 82.

      --
      Curiously yours, crip.
    17. Re:Think this will set precedent? by Kickasso · · Score: 1

      No, "K" is not defined to be 1000. "k" is.

    18. Re:Think this will set precedent? by eldepeche · · Score: 0, Flamebait

      I can't convert from 1Gb to a kilometre Yeah, and I can't convert from a hogshead to a fathom. Shut the fuck up.

    19. Re:Think this will set precedent? by eldepeche · · Score: 1

      Uh, I don't think the prefix M means 1 e6.

    20. Re:Think this will set precedent? by dotgain · · Score: 1

      PROTIP: The AC's are actually trolls that believe, like you, that 1kB = 1000B. They're (or "he is", most probably) merely taking a contrary position in order to provoke you.

    21. Re:Think this will set precedent? by cheater512 · · Score: 0, Troll

      Its deliberately misleading. Simple as that.

      Plus I want my 120gig (base 2 measurement) which they are stealing from me.
      It adds up very quickly.

    22. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      There are many points of view on what should be right. The real problem is that the Operating Systems and the Hard Drive manufacturers are not using the same terminology. Windows XP uses 1024, while the hard drive manufacturers use 1000. My HD is 40GB, but Windows says its 37.2GB (as does df -ah in Linux). While everyone argues about which it should be, most people only care that the numbers don't match. I think that if they did match, there would not be as much noise about this, if any. The issue is getting one side or the other to make a change, the average person really doesn't care which side does, just make the numbers match. Being a computer geek, my vote is 1024. My 14 year old brother asked me about this exact issue 2 weeks ago, wanting to know why the HD said one thing, and Windows said another.

    23. Re:Think this will set precedent? by db32 · · Score: 3, Funny

      I take offense to that. I have a very kind and polite tree stump in my front yard that is arguably much more intelligent than "vaginal_flatulance" has demonstrated themselves to be.

      --
      The only change I can believe in is what I find in my couch cushions.
    24. Re:Think this will set precedent? by neoform · · Score: 1

      I just bought a "1TB External Hard Drive", formatted it and was delighted to find I had 920GB available.

      I love being sold products with accurate packaging.

      Imagine cars were sold like this? "Gas tank capacity: 50L", then you find out you can only put 42L in the tank..

      --
      MABASPLOOM!
    25. Re:Think this will set precedent? by Firehed · · Score: 1

      Technically, you're completely right with this one - in fact, I've defended the same position (except for the elitist view, seeing that external hard drives suffer the same problem as internal drives and they're becoming increasingly common). Technically, the 'difference' in space is the fault of the operating system as well.

      In order to make this difference go away, it becomes a matter of logistics:
      1) Change the packaging of hard drives in order to reflect the "actual" capacity (ie, GiB units)
      2) Change every operating system in such a way that all software recognizes the new measurement unit

      Number one is not only trivially easy, but can be used for new marketing if they're smart about it (Seagate's new TrueSize 1TB drive would actually show up as 1TB in the OS, by actually having a capacity of at least 1,099,511,627,776 bytes, for example). Other manufacturers would soon follow suit. Number two, on the other hand, would take quite a bit of effort, and would likely only ever show up in the latest and greatest software if it even ever happens.

      --
      How are sites slashdotted when nobody reads TFAs?
    26. Re:Think this will set precedent? by tchuladdiass · · Score: 5, Funny

      I was more upset when I ordered a case of hard drives -- the shipping container said "Quantity: 1K", and I only got 1000 hard drives, not the 1024 I was expecting.

    27. Re:Think this will set precedent? by camperdave · · Score: 1

      ... formatted it...

      Why are you surprised? You must think that the partition table, used cluster maps, index tables, and all the other format related data somehow magically doesn't take up any room. I suppose you think that the drive manufacturer is somehow supposed to guess which file system you're going to put on the drive, and put the formatted capacity on the box? News flash! Not everyone uses the same formatting system. Fat32, NTFS. Ext2/3, ReiserFS, etc will all format the same drive to different capacities.

      --
      When our name is on the back of your car, we're behind you all the way!
    28. Re:Think this will set precedent? by OwnedByTwoCats · · Score: 1

      It's more like being sold a car with a 40 US Quart gas tank, and then discovering that it only holds 37.8 Liters.

    29. Re:Think this will set precedent? by reezle · · Score: 2, Interesting


      just bought a "1TB External Hard Drive", formatted it and was delighted to find I had 920GB available.
      I love being sold products with accurate packaging.
      Imagine cars were sold like this? "Gas tank capacity: 50L", then you find out you can only put 42L in the tank..


      I just bought a new ladder to clean my gutters.
      The big colorful bold-face signs all over it say "20' Ladder", which should be plenty long.
      After quite a bit of searching the sides of the ladder, I found the 2"x3" B&W sticker on the side that had product weight and dimensions including real height of a little less than 17'
      The ladder assumes a 5'10 person on the highest safe rung with an additional 12" reach when calculating it's 20' length.

      So, yeah... lots of this going around. Difference with hard drives is that it's been going on since day one, and most anyone with enough of a clue to install their own hard drive should reasonably know this...

      Perhaps I can start a lawsuit because the last batch of 2x4's I bought at the lumber store was actually NOT 2x4 ?

    30. Re:Think this will set precedent? by darthflo · · Score: 2, Funny

      That's great for you! I hope you, for one, welcome your kind and polite tree stump overlords.

    31. Re:Think this will set precedent? by hedwards · · Score: 1

      Technically, you're completely right with this one - in fact, I've defended the same position (except for the elitist view, seeing that external hard drives suffer the same problem as internal drives and they're becoming increasingly common). Technically, the 'difference' in space is the fault of the operating system as well. I don't think that it is as elitist as it might seem, the ability to comprehend that point is something which at least 90% of the population could do if they chose to do so. Security software is far more complex to understand, or even to just install properly than this is, if people can't be bothered to read up on the technology that they are using, that is a good reason for them not to be using it. I don't expect people to understand malloc, the ins and outs of disk compression or the significance of inodes.

      But, if we're really going to sue people for drive capacity, the first ones that ought to be sued are companies that sell snake skin oil like drivespace, I briefly messed with that one, and it did little more than inlfate the numbers and slow access times. The numbers there were far more misleading than these ones are, in practice both the total space and the used space were both greatly inflated, making it difficult to tell what if any advantage was coming from the software. That's misleading, this is just a bit confusing.

      If it were just 1 company doing this, I'd say that they had a point, but it has been an industry standard to use SI units for longer than I can personally recall.

      The industries in general have come a long way, but it is still a technical thing to do, and it does still require no how in order to make a computer, if we're going to start allowing lawsuits because things are complicated, there are at least 3 dozen other frivolous suits that can be made.
    32. Re:Think this will set precedent? by Selivanow · · Score: 2, Insightful

      It might not be "new" but it wasn't always this way. I do remember drives that were labeled in the "correct" binary values. Of course it has been a while, the last drive I can absolutely remember is my WD 525MB drive (being 525.7MB or something). Manufacturers are just trying to get something (our money) for nothing (missing drive capacity) and to make themselves look better and more productive. Consumers also have something to do with this. We are never happy with the latest and greatest. We will always demand more capacity, speed, etc.

      --
      -- ...trying to make digital files uncopyable is like trying to make water not wet. -Bruce Schneier
    33. Re:Think this will set precedent? by WNight · · Score: 1

      Anyone that ignorant of how every major operating system measures space shouldn't be manufacturing computer products.

      Or, admit that they're lying trying to make it sound better. Yes, everyone is. Doesn't excuse it though. They know what consumers mean by 1GB, enough to put wording on the box explaining they're not using the standard meaning. Too bad this is only Seagate, the whole industry needs this.

      Ditto CRT sizes. I'm glad we're all moving the LCDs because they aren't allowed to lie about the visible size like with monitors. (oh, not lie, just print one entirely misleading thing and the least noticable * mark to indicate that it doesn't really mean what it says. But no, not lie...)

    34. Re:Think this will set precedent? by WNight · · Score: 1

      Sigh. Yes, we know. Thank your for basic OSes refresher material. But you know as well as we do that the drive lost very little capacity to being formatted and most of it due to labeling lies.

    35. Re:Think this will set precedent? by tiny1877 · · Score: 2, Insightful

      Regardless of what FS you use, you will NOT lose 80GB just by formatting it. If I'm buying a 1TB drive (1024GB!!), it should not report in ANY OS any less than 1023GB allowing for all FS data, and that's being generous. On the flip side, food products are allowed a 20% margin in weights. Those granola bars you buy that say they're 2oz? They can range from 1.6oz to 2.4oz and it's perfectly allowable. Where's the outrage there?

    36. Re:Think this will set precedent? by BillyBlaze · · Score: 1

      I just bought 2 gigs of RAM, but when Vista booted, I ended up with only like 1.7. The nerve!

    37. Re:Think this will set precedent? by Anonymous Coward · · Score: 2, Funny

      That was pretty funny. Not a troll!

    38. Re:Think this will set precedent? by COMON$ · · Score: 1
      Someone can correct me if I am wrong here, but who taught you that hard drives calculate in base 10? The HD manufacturers use Base 10 because it is easier to understand by the user. However, it is misleading for Joe 6 pack who, upon installing their hard drive only sees the "Real computable number". Standards are not base 10 in the industry, Go out and buy some RAM see if you can find 1000MB sticks, they are always labeled correctly even though the MOBO may steal some for video and the OS will report less than is there.

      I wouldnt call the base ten method a standard, it is more of a widely spread misconception.

      --
      CS: It is all sink or swim...oh and did I mention there are sharks in that water?
    39. Re:Think this will set precedent? by while1noop · · Score: 1

      The notation that I'd seen in one of my texts was along the lines of:

      kb = 1000 bits
      kB = 1000 bytes
      Kb = 1024 bits
      KB = 1024 bytes
      m = 1000^2
      M = 1024^2

      and so on, where a lowercase prefix denotes base-10, an uppercase prefix denotes base-2, a lowercase b denotes bits, and an uppercase B denotes bytes. Has anybody else heard of this?

    40. Re:Think this will set precedent? by BillyBlaze · · Score: 1

      Just because you can't convert between different units doesn't mean we should use a different base for different units. Especially if we use the same prefixes. That's stupid. I like powers of two as much as the next guy, but you can't deny they really ought to have different prefixes. If only kibi- and mebi didn't sound so stupid.

    41. Re:Think this will set precedent? by Yartrebo · · Score: 1

      I'm outraged now that I know about it. I always assumed that the error margin was set by the number of significant digits. If a product said 1 lb (454g), I expected it to fall between 453.5g and 454.5g. Not having a balance to measure with, I have just taken this on faith.

      A 20% error is outrageous. Even food packed by hand can be within 1% error with a little care.

      If I can get my hands on a decent balance, I certainly intend to do some measuring.

    42. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      Yes, that is the naming convention used by everyone. What drive manufacturers are doing is saying their 500gB drive holds 500GB. I expect the only permanent outcome of these lawsuits will be a labeling change on the boxes to say 'gB' instead of 'GB'.

    43. Re:Think this will set precedent? by camperdave · · Score: 1

      But you know as well as we do that the drive lost very little capacity to being formatted and most of it due to labeling lies.

      Not knowing the drive make/model, the format used, whether or not there are hidden partitions, and the contents of the labelling, and even which labels were looked at, I can't tell you anything. Mind you, losing 80G to formatting overhead does seem excessive.

      --
      When our name is on the back of your car, we're behind you all the way!
    44. Re:Think this will set precedent? by megabyte405 · · Score: 1

      Actually, that might be a BIOS issue. The PCI address space has to go somewhere, as does PCI-E: At least in WinXP, if you don't choose the "Remap PCI above 4gb" and something to do with a PCI-E address space, Windows will not have access to very much of large amounts of memory (like over 2gb)

      --
      I recognize people by their sigs. Is that a bad thing?
    45. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      Yeah, who's got the 26.67 cm?

    46. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      jack ass.

    47. Re:Think this will set precedent? by Blkdeath · · Score: 1

      and so on, where a lowercase prefix denotes base-10, an uppercase prefix denotes base-2, a lowercase b denotes bits, and an uppercase B denotes bytes. Has anybody else heard of this?

      {SIGH!} And people wonder why geeks are ostracized. Think back to physics class. Think reeeal hard. Remember when standard units of measurement were covered? Ok, that in mind, remember this;

      • Lower case (eg; 'm') equates to less-than such as "mm = millimetres", or one millionth of a metre.
      • Upper case (eg; 'K') equates to greater-than such as "Km = Kilometres", or one thousand metres.

      This is how it works in the scientific community, the grocery store, the gas station, all products/services sold by weight and/or capacity EXCEPT computer hard drives? Come on people. Get over the stigma and just accept that sometimes conforming to the way the rest of the world does things is actually a very good thing.

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    48. Re:Think this will set precedent? by jagdish · · Score: 1

      Yeah, well I got a 1000 bricks.

    49. Re:Think this will set precedent? by Anonymous Coward · · Score: 0

      Wow, I'm surprised that actually went through, if only because the court systems seem so broken.

      It went through *because* the court system is broken. Seagate wouldn't offer to settle if it wasn't.

    50. Re:Think this will set precedent? by Anonymous Coward · · Score: 0
      Except in SI, the kilo prefix is a lower case "k", not an upper case "K".

      "milli" means one thousandth, not one millionth (which would be "micro", represented by the lowercase greek letter mu ( )).

      So perhaps you need a refresher course in SI...

    51. Re:Think this will set precedent? by Workaphobia · · Score: 1

      Where I come from, "k" is an acceptable abbreviation of "kilo", and wikipedia seems to agree: http://en.wikipedia.org/wiki/Si_prefix#List_of_SI_prefixes

      Since it does not make an ounce of sense to talk about fractions of a bit unless we're describing averages, entropy, etc., I don't see why we can't reuse the lowercase half of the alphabet for the purpose the parent described. And yes, I believe I've seen it before.

      > "{SIGH!} And people wonder why geeks are ostracized."

      That statement is strange on several levels.

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    52. Re:Think this will set precedent? by Blkdeath · · Score: 1

      Where I come from, "k" is an acceptable abbreviation of "kilo"

      Ok, so I messed up the numerical equivalent of milli and the case of the 'k', however as usual around here the point was completely missed in favour of pointing out minor errors.

      I don't see why we can't reuse the lowercase half of the alphabet for the purpose the parent described. And yes, I believe I've seen it before.

      Have you ever been the only English speaker in a room full of, say, Cantonese? Really difficult to communicate, no? Try explaining your theory to a room full of NON geeks and see what their reactions are. Hint: Usually it's a combination of confusion, bewilderment and bemusement. "Sure, whatever, a small k means a thousand and like twenty eight or something. Whatever you say."

      "{SIGH!} And people wonder why geeks are ostracized."

      That statement is strange on several levels.

      The point, and the underlying point to my posting, was that geeks like to re-invent things as convenient to them but that are completely outside the level of understanding of the rest of the civilized world. It's apparent that a contingent of geeks (and, apparently, lawyers) would like hard drive storage re-defined but refuse to accept any of the standard notations that have been proposed which would do exactly that.

      Mega, kilo, giga, etc. have existed for quite some time both in and out of the computer industry as base-10 notations - even with the measure of network bandwidth, CPU Hz and other forms of measurement but when it comes to disk drive storage capacity suddenly the rules change and an exception is formed?!? Nonsense. Pure nonsense.

      BTW - please feel free to come up with more trite references to Wikipedia. It shows beyond a shadow of a doubt that you, too, can use a search engine.

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    53. Re:Think this will set precedent? by Thing+1 · · Score: 1

      Difference with hard drives is that it's been going on since day one [...]

      It most certainly has not; I am that old.

      Can't find a reference, but I remember purchasing the first hard drive that did not conform to binary rules (it conformed to SI decimal rules), sometime in the early 90s. It was Maxtor who did it first, IIRC.

      Glad to see them getting their comeuppance.

      --
      I feel fantastic, and I'm still alive.
    54. Re:Think this will set precedent? by StrongAxe · · Score: 1

      They know what consumers mean by 1GB, enough to put wording on the box explaining they're not using the standard meaning. Too bad this is only Seagate, the whole industry needs this.

      Precisely. Because there is some discrepancy as to what the word "Megabyte" actually means, they make it perfectly clear by stating what they mean by it on the outside of the box, to make sure the customer is no confused. It's a pity that most people can't be bothered to read the words, they just look at the HUGE NUMBERS on the front of the box and then ignore the rest, and then sue when it means what it says instead of what they think it ought to have said.

    55. Re:Think this will set precedent? by Workaphobia · · Score: 1

      > "Ok, so I messed up the numerical equivalent of milli and the case of the 'k', however as usual around here the point was completely missed in favour of pointing out minor errors."

      You specifically quoted those examples and asserted that the "rest of the world", which "geeks" are apparently not part of, uses those terms and definitions. In this case, details are moderately relevant, as you blasted the parent over his deviation from perfect adherence to the standard while demonstrating variations of your own.

      > "Have you ever been the only English speaker in a room full of, say, Cantonese? Really difficult to communicate, no? Try explaining your theory to a room full of NON geeks and see what their reactions are. Hint: Usually it's a combination of confusion, bewilderment and bemusement. "Sure, whatever, a small k means a thousand and like twenty eight or something. Whatever you say.""

      I'm a bit bewildered by how much importance you attach to this matter. You imply that it is extremely difficult for an average person to comprehend even the *existence* of a technical fact or definition that does not exactly coincide with daily usage, and make it sound as though this would have disastrous consequences. I seriously doubt it would be that hard to explain to most people what a binary kilobyte is. If you wanted to try to be confusing to prove me wrong, you could start off yammering about representing numbers in different bases and quoting various powers of two, and in that case I can imagine their eyes glazing over. If on the other hand you wanted to tell someone that the prefix "kilo" doesn't necessarily mean "thousand" when people talk about disk storage, you could just *say* that and be done with it.

      > "The point, and the underlying point to my posting, was that geeks like to re-invent things as convenient to them "

      !! Of course, as does anyone with "technical" knowledge in any subject. I fail to see how this is the grievous sin you're making it out to be.

      What, you didn't think all words in the English language were used in the same way by all professionals, did you? (By the way, did you know that engineers use the symbol "j" to represent the imaginary unit? Or that a "trusted" party in a security model is one that is capable of breaking your security policy?)

      > "but that are completely outside the level of understanding of the rest of the civilized world."

      Exaggerate much?

      > "It's apparent that a contingent of geeks (and, apparently, lawyers) would like hard drive storage re-defined but refuse to accept any of the standard notations that have been proposed which would do exactly that."

      Re-defined? How long have mega, giga, etc., been understood as binary prefixes when applied to hard drive storage? Was there ever a time when this was not the case? It's certainly not a recent development on the part of renegade geeks who aim to destroy society by attacking its language. Perhaps the proposed alternative notations have not been adopted by many because they *suck*. By your logic, we should all suddenly start using the prefixes "kibi", "mebi", and "gibi" in all conversations when we wish to indicate multiples of 1024. You can't possibly expect that to not raise some eyebrows among a crowd of non-geeks; they'll think you have a speech impediment.

      > "Mega, kilo, giga, etc. have existed for quite some time both in and out of the computer industry as base-10 notations - even with the measure of network bandwidth, CPU Hz and other forms of measurement but when it comes to disk drive storage capacity suddenly the rules change and an exception is formed?!? Nonsense. Pure nonsense."

      Prefixes, like all forms of vocabulary, mean what the speaker and listener agree upon. The English language has loads of exceptions that one could claim are pure nonsense under your logic, but that doesn't make it so. A significant portion of people use those words as binary prefixes, and while you can argue that it's suboptimal, the mere fact that it's a

      --
      Evidently, the key to understanding recursion is to begin by understanding recursion. The rest is easy.
    56. Re:Think this will set precedent? by sasdrtx · · Score: 1

      Your surprise is surprising. The courts remain broken, because this lawsuit was stupider than SCO vs. IBM. Seagate, along with all other disk drive manufacturers, have always used the standard decimal power notation for disk drive capacity. Because that's what the Greek prefixes mean, and has been since they were invented many centuries ago.

      Then along came RAM, which can only be reasonably be made in quantities of powers of two, and the inaccurate usage of the greek prefixes began. Windows, in one of the 8k ways it is a piece of shit, reports disk drive capacities inaccurately, by dividing the capacity by powers of two.

      And because so many people are greedy morons, this idiotic lawsuit progressed to the point where Seagate decided it was sensible to just accept the fact that a large portion of their customers are greedy morons, and cave.

      If I was a disk manufacturer, from now on I would state drive capacity as e.g. 400,000,000,000 bytes. Whine about that, bitches.

      --
      Most people don't even think inside the box.
    57. Re:Think this will set precedent? by msromike · · Score: 1

      Wouldn't that be more like "...find out you could only put 46L in the tank."? In the big scheme of things not being able to do math is a much bigger problem than losing $32 worth of advertised disk space (assuming a TB drive costs $400 that is.) I find this all quite ridiculous. The reason that the drives are advertised this way in the first place is that the VAST majority of people either can't do the math or don't have enough of a computer background to know the difference. The drive manufactures did it to make it simple for these people to understand it all in the first place. Evey one knows a billion has only 1s and 0s in it for goodness sakes. Maybe we should get some legislation going that makes them advertise what the consumer is really getting. Then we all could tell are friends, "hey I just got a new 2.14748 × 10^9 bit hard drive for my laptop."

    58. Re:Think this will set precedent? by PastaLover · · Score: 1

      what I don't get is how 1GB (10^9 bytes?) then suddenly is 1,073,741,824 bytes (as in the summary). So it's more bytes than they're saying it is?

  3. "or?" by scottrocket · · Score: 1

    What is this "or"? Give both.

    1. Re:"or?" by Anonymous Coward · · Score: 0

      Probably "xor" is to be read here.

  4. Direct Link to claims by micksam7 · · Score: 5, Informative

    File online [no cash, just software]

    Mail-in [cash or software, cash claim only if bought before 2006 & you have proof-of-purchase. 5% of what you paid]

    1. Re:Direct Link to claims by houstonbofh · · Score: 5, Informative

      cash or software, cash claim only if bought before 2006 & you have proof-of-purchase. 5% of what you paid

      The mail in form also allows you to use your drive serial number as proof if you do not have proper documentation.

    2. Re:Direct Link to claims by Erpo · · Score: 1

      In actuality, 1GB = 1,073,741,824 bytes -- a difference of approximately 7% from Seagate's figures. Seagate is saying it will offer a cash refund or free backup and recovery software."

      cash or software, cash claim only if bought before 2006 & you have proof-of-purchase. 5% of what you paid


      Shouldn't that be 7% of what I paid? They're fudging the numbers again!

      Ok, seriously, the best solution to this problem is for software authors to start using powers of 10 for sizes when giving information to the user. In the mean time, just print on the side of the box how many bytes there are. You can't screw that up.

      "750,000,000,000 byte hard drive for sale" - is that so terribly hard? I thought the computer industry liked to print big numbers on the outside of boxes anyway.
    3. Re:Direct Link to claims by Anonymous Coward · · Score: 1, Funny

      I already have a script that logins to all our production boxes and queries the 3ware controllers for seagate serial numbers. 5% of 500+ drives of various sizes .... lots of money here.

    4. Re:Direct Link to claims by Anonymous Coward · · Score: 0

      The wording on the form makes me suspect that "no proper documentation" = "no money, just the software".

    5. Re:Direct Link to claims by Anonymous Coward · · Score: 0

      5% of what you paid

      They sold the customer 7% short, and are refunding 5%. To me it looks they still are on top of it with 2% ...

      And thats outside of the fact that I do not see any kind of punishmentment for the trickster in this, just a "return what you let the customer overpay you". A funny kind of justice if you ask me.
    6. Re:Direct Link to claims by mpe · · Score: 1

      [cash or software, cash claim only if bought before 2006 & you have proof-of-purchase. 5% of what you paid]

      The software most likely isn't as cross platform as a HDD either. So in quite a few cases the offer will be worthless...

    7. Re:Direct Link to claims by John+Straffin · · Score: 1

      ... lots of money here. Not likely. From TFA (emphasis mine):

      The Seagate drives must have been purchased in the U.S. from an authorized Seagate retailer or distributor, separately as a Seagate product that was not preinstalled into and bundled with a PC or any other type of electronic device.
      --
      My contempt for the behavior and beliefs of the two major political parties cannot be adequately expressed in 120 chara
    8. Re:Direct Link to claims by Kuvter · · Score: 1

      I'm not loosing any sleep over it. Many companies seemed to have done this, as another post stated, and I was aware of it when I acquired the hard drives. I've enjoyed my 2 SATA Segate hard drive that I bought pre '06, from Newegg so I could acquire a receipt. I don't plan to get the compensation. That would just take from their development budget and slightly hinder hard drive competition. I like the competition that's what gives us better products for cheaper.

      --
      "To be is to do." --Socrates
      "To do is to be." -- Aristotle
      "Do-Be-Do-Be-Do..." --Sinatra
    9. Re:Direct Link to claims by tepples · · Score: 2, Insightful

      "750,000,000,000 byte hard drive for sale" - is that so terribly hard? That or "750 GB (698 GiB) hard drive for sale".
    10. Re:Direct Link to claims by FunkyELF · · Score: 1

      The other 2% probably goes to the lawyer which doesn't seem bad. I have heard of class action lawsuits where the lawyers get more than half.

    11. Re:Direct Link to claims by justthisdude · · Score: 2, Funny
      Interestingly, the fine print indecates they will actually reimburse you 7% less than you were expecting...

      --

      "There are 10 kinds of people in the world, those who think in binary, and those who don't"

      --
      "I love his boyish charm, but I hate his childishness" - Leela
    12. Re:Direct Link to claims by Erpo · · Score: 1

      As I recall, this whole mess got started because someone got the bright idea to "redefine" 1MB as 1,000,000B to sell less product for the same amount of money. This conferred a financial advantage over other manufacturers (who then followed suit). I doubt manufacturers would be willing to go back, and I don't especially want them to either.

  5. SI units by Anonymous Coward · · Score: 5, Informative

    1 GB (gigabyte) = 10^9 B
    1 GiB (gibibyte) = 2^30 B

    1. Re:SI units by bh_doc · · Score: 3, Insightful

      Exactly. The information technology sector is and has always been wrong to suggest that k is 2^10. It is not, and it will never be. k=10^3, M=10^6, G=10^9, etc.

    2. Re:SI units by DRobson · · Score: 5, Insightful

      Regardless of whether the IT sector is _technically_ in the wrong it's commonly accepted that in this area we work with powers of two. The fact that people have to explicitly explain this fact shows that everyone expects it to be that way. The HDD manufacturers damn well know this and fairly blantantly use measurements which would commonly be interpreted more favourably.

    3. Re:SI units by DiSKiLLeR · · Score: 5, Insightful

      Regardless of whether the IT sector is _technically_ in the wrong it's commonly accepted that in this area we work with powers of two. The fact that people have to explicitly explain this fact shows that everyone expects it to be that way. The HDD manufacturers damn well know this and fairly blantantly use measurements which would commonly be interpreted more favourably. Exactly.

      This says it perfectly.

      RAM manufacturers do it correctly, and Application Vendors and Operating System Vendors have been doing it this way for DECADES. SI units be damned, this is the way it has always been and there is no reason for it to be changed.
      --
      You can tell how powerful someone is by the magnitude of the crime they can commit and be able to get away with.
    4. Re:SI units by bh_doc · · Score: 1

      Regardless of whether the IT sector is _technically_ in the wrong it's commonly accepted that in this area we work with powers of two.
      ...Just so long as we're talking about filesize, or RAM capacity. HD capacity and bandwidth are commonly accepted to be powers of ten. Consistency, anyone?

      The fact that people have to explicitly explain this fact shows that everyone expects it to be that way.
      What? Please read what you just wrote, because it sure doesn't make any sense to me.
    5. Re:SI units by Anonymous Coward · · Score: 0

      Well butt-head, the transistors in my computer go on and off. There are no 10 states for them to go, only 2. You can't apply SI to computers. They don't count to 10. They count to 2. To a computer, 10 means 2 (in your base 10 SI world). Computers can't be made to be SI compliant. They are base 2 beasts. Its always (for 50+ years) to use these prefixes as 2^10(x). Computers are not SI. They aren't. SI is base 10. Computers are base 2. Its quite bizarre that a country that so dearly holds onto the imperial system of measurement, gets to wired up about metric SI prefixes when it comes to a system that cannot be made SI. The way it is, is the way it will remain, and that is, a gigabyte (as spelled) is 2^30 bytes. Its different than a gigameter which is 10^9 meters. The hint for you is the suffix. Meters are SI units with SI definitions. Bytes are use in computers. Computers are not (and cannot be made to work internally) base 10.

    6. Re:SI units by bh_doc · · Score: 1

      I'm sure you're smart enough to think of examples of things people have done for decades that are or were wrong and should be or were changed, so I won't bother, just to point it out.

      People are being confused by two incompatible definitions. Is that not a reason to change?

      Inconsistency of IT be damned, SI units were defined and consistent long before IT usurped and mangled its prefixes.

    7. Re:SI units by Anonymous Coward · · Score: 0

      I've been saying that a spider is an insect for DECADES. Taxonomy be damned, this is the way it has always been and there is no reason for it to be changed.

    8. Re:SI units by IWannaBeAnAC · · Score: 5, Insightful

      While I can see the technical merit in using the Ki/Mi/Gi prefix instead of K/M/G, I object to it for the simple reason that kibibyte, mibibyte and gibibyte are stupid sounding words and I refuse to use them for that reason alone.

      It might be, for a newcomer, initially confusing that a kilobyte is 1024 bytes instead of 1000 bytes, but the original scheme is a consistent exception. The powers of 2 apply to bytes and only bytes, nothing else. 1Km = 1000 meters. 1KW = 1000 Watts. 1KB = 1024 bytes. 1 KN = 1000 Newtons. Not completely uniform, but there is no ambiguity.

      On the other hand, if someone came up with a set of power of 2 prefixes that didn't suck, I'd happily switch.

    9. Re:SI units by dgatwood · · Score: 4, Insightful

      The problem is that a 2^k organization of bytes is fundamental to the way computers operate. It can't be changed to a power-of-ten unit just because it is "more convenient to work with" as the SI folks want. You can't realistically design a RAM chip with 1000 bytes of memory. You could do it, but you'd end up building one with 1024 bytes of memory and just burning out the last 24 cells. Ditto for all other forms of electronic storage, including the caches on hard drives. Only magnetic and optical storage have the luxury of defining units in non-power-of-2 ways, and yet they generally do not, choosing to standardize on 512-byte blocks primarily because if they didn't, the VM system's paging path would be heinously inefficient.

      So we have a choice: we can either standardize on one unit---the base-2 definition of a gigabyte---or we can standardize on two units---one for RAM and one for hard drives---or we can foolishly standardize on the base-10 definition and have RAM chips described as 1.074 GB. I, for one, can't imagine that last choice being too popular, and the second choice (the status quo) is sufficiently confusing to an average layman that it really doesn't work, either. Thus, the only -reasonable- choice is to standardize on base-2 definitions of these units. There's a reason the standards were bent a bit fifty years ago. The SI units just don't work. They can't work. They will never work. And the sooner we stop trying to force a base-10 unit of measurement into a base-2 world---the sooner we can dispose of this fundamentally flawed view that everything must be in base 10---the sooner we can resume actually getting things done instead of quibbling over crap like this that was set in stone before most folks on Slashdot were even born.

      Put another way, it's 9 years later, and the term kibibyte is still almost universally guaranteed to get you modded "troll" in any computing forum. Maybe it's type for the SI folks to realize that perhaps the reason their standard has been near-universally rejected in computing circles for almost a decayear is that it is fundamentally brain damaged from a practical use perspective.... It makes about as much sense if the SI had standardized base-10 units of time other than the second. Kiloweeks, anyone? Decidays? The SI folks wisely realized that moving time to a base 10 unit was not practical because the natural division of days into years could never be forced into base-10 units comfortably. Instead, they acknowledge the usefulness of these non-SI units as acceptable for use in spite of their non-base-10 nature. The same is true for computing, and they would be wise to acknowledge that the same fundamental problems hold true in this area.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    10. Re:SI units by Anonymous Coward · · Score: 0

      He didn't say you shouldn't measure in powers of two, but that you should use other names for those. The mega/mebi notation allows the two systems to co-exist. For example I have two feet so I think a kilometer --when I walk it-- should be 1024 meters. With kibi I can start measuring in kibimeters without introducing ambiguity, but people like you ruin it for me.

    11. Re:SI units by dgatwood · · Score: 1

      P.S. The term "byte" predates the SI units by four years. The term Megabyte was only coined a single digit number of years after the SI units (circa 1970). Therefore, by interpolation, we can assume that kilobyte was coined at about the same time as the SI units. The SI units most certainly were NOT "defined and consistent long before IT usurped and mangled its prefixes" as you claim.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    12. Re:SI units by khellendros1984 · · Score: 1

      Computers can be (and historically have been) designed to work in base 10. It's just inefficient. It makes far more sense to construct them to function in base 2. Also, I'd say that the number's just a base. you're arguing about the base-representation of the same number...you say drive sizes "can't" be represented in base 10. They most certainly can, and it's clear from the prefix that they actually are. The only question is, is it too confusing for the average consumer? That's the only reason to switch to the base 2 system (with the appropriate changes in prefix, of course).

      --
      It is pitch black. You are likely to be eaten by a grue.
    13. Re:SI units by Anonymous Coward · · Score: 0

      Like what, "kilogram" or "kilometer" was not used before the 70s ? Damn

    14. Re:SI units by Dachannien · · Score: 1

      The second units you mention are not SI units. They were adopted by the IEC, but have met with great difficulty achieving worldwide usage due to the inertia of the pre-existing terms, such as "megabyte" referring to 1024^2 bytes.

    15. Re:SI units by bh_doc · · Score: 2, Insightful
      While much of what you say is insightful...

      Put another way, it's 9 years later, and the term kibibyte is still almost universally guaranteed to get you modded "troll" in any computing forum.
      ...I must say I find the attitude exhibited by the profession against simply using a slightly different moniker to avoid any ambiguity with an already established metric disturbingly egoistic.

      Go ahead. Don't use base 10 for measuring RAM sizes, use base 2, I really don't care. Just don't go calling it a Gigabyte, because it isn't. I would have no problem picking up a 2 GiB stick of RAM. If you'd prefer not to call it a Gibibyte, either, fine, call it something else. Just please stop calling it what it isn't. For an industry that regularly has to deal with and resolve ambiguities, it's surprising to me how inert it seems to have been on this one.
    16. Re:SI units by amorsen · · Score: 3, Insightful

      It makes about as much sense if the SI had standardized base-10 units of time other than the second.

      No, the comparison is if everyone decided to call weeks dekadays, but keep their length as 7 days. It's simply wrong. If you want to use the SI units, use the SI definition. Otherwise come up with your own terms.

      --
      Finally! A year of moderation! Ready for 2019?
    17. Re:SI units by Anonymous Coward · · Score: 0

      Yep, consistency is cool. A kilogram is 1000 grams, a kilometer is 1000 meters, but a kilobyte is ... a blurb ? Let's take a look at what a kilobyte can be. For HDD manufacturers, it's 1000 bytes, sensible. For RAM manufacturers, it's 1024 bytes, practical for them, but while the difference with 1000 didn't matter much up to megabytes, it starts to matter for gigabytes. But what is a megabyte, actually ? That should be a kilokilobyte, right ? For HDD manufacturers, it's 1000 kilobytes, that makes it 1000000 bytes For RAM manufacturers, it's 1024 kilobytes, that makes it 1048576 bytes For FD manufacturers, it's 1000 kilobytes, that makes it 1024000 bytes. Yes, your good old 1.44MB 3.5" floppy disk is 1474560 bytes, which is 1440 kilobytes... consistency... And, while OSes may choose to display file sizes with power of 2 based system (be it labelled wrongly MB or correctly MiB), when file sizes are displayed in bytes, people do use power of 10 based system: who would say a 50000000 bytes big file is 47.68MB ?

    18. Re:SI units by drsmithy · · Score: 1

      People are being confused by two incompatible definitions. Is that not a reason to change?

      People are only being confused because hard disk manufacturers changed how their drives were labelled in the late 80s/early 90s. Everyone else except them uses KB/MB/TB/etc in a consistent - if not SI-compliant - fashion.

      Exactly the same thing happened - around the same time, interestingly enough - when monitor manufacturers started to market their monitors according to the tube size rather than the visible area.

      From this, one might be inclined to draw the conclusion that a market's maturity is inversely related to the honesty of those selling to it.

    19. Re:SI units by bh_doc · · Score: 1

      The metric system was renamed SI and properly standardised in the 1960s. The metric system, with prefixes in the form as they are now, have existed since before the 1800s.

    20. Re:SI units by Dahan · · Score: 0

      It might be, for a newcomer, initially confusing that a kilobyte is 1024 bytes instead of 1000 bytes, but the original scheme is a consistent exception. The powers of 2 apply to bytes and only bytes, nothing else. 1Km = 1000 meters. 1KW = 1000 Watts. 1KB = 1024 bytes. 1 KN = 1000 Newtons. Not completely uniform, but there is no ambiguity.

      So... the burst transfer rate of a Ultra DMA/66 hard drive is 66.666...MB/s, right? Is that 66,666,667 bytes/second or 69,905,067 bytes/second?

      The answer is the former. According to the specs, UDMA66 transfers 4 bytes every 60ns. 1MB = 1000000 bytes.

    21. Re:SI units by amorsen · · Score: 3, Insightful

      The powers of 2 apply to bytes and only bytes, nothing else

      They apply to bytes, when you happen to talk about RAM. Anything else, even flash, is in powers of 10. Sometimes, but rarely, they apply to bits as well -- 2Mbps E1 is 2048kbps. ADSL can go either way. In short, "consistent" is certainly not a good description of this mess.

      --
      Finally! A year of moderation! Ready for 2019?
    22. Re:SI units by Anonymous Coward · · Score: 0

      While I can see the technical merit in using the Ki/Mi/Gi prefix instead of K/M/G, I object to it for the simple reason that kibibyte, mibibyte and gibibyte are stupid sounding words and I refuse to use them for that reason alone.

      Man, if you check out my twitter, you'll see that I was just blogging and podcasting the same thing! Yeah, when I'm surfing my wifi, I don't want to use any stupid-sounding words like "kibibyte".

    23. Re:SI units by Anonymous Coward · · Score: 0

      Well, it's k not K anyway (unless you're talking about temperature). Your consistent, unambiguous scheme is already breaking apart. KiB and friends are more accurate. If you don't like the way they sound (which is an idiotic excuse) then say something else, like "kibb" and "gibb" or whatever suits your fancy.

    24. Re:SI units by Myopic · · Score: 4, Funny

      The SI folks wisely realized that moving time to a base 10 unit was not practical because the natural division of days into years could never be forced into base-10 units comfortably. Instead, they acknowledge the usefulness of these non-SI units as acceptable for use in spite of their non-base-10 nature.

      I totally agree! Now when can we please have reasonable measures of small quantities of volume, based on a unit approximately the size of two cupped hands? That's a human-understandable unit. Since it's based on cupped hands, we'll call it a "cup".

    25. Re:SI units by bh_doc · · Score: 1

      Your insinuation (within your unnecessarily aggressive diatribe) that I am American amuses me. I'm not. FYI, I do happen to reside in a country that standardised on the metric system, ooh, a few decades ago now.

    26. Re:SI units by IWannaBeAnAC · · Score: 2, Interesting

      No, the word 'Kilobyte' had established a consistent meaning of 1024 bytes long before Flash existed. All you are saying is that the Flash manufactures have succumbed to the same deceptive marketing tricks of the hard disk manufacturers. It is an abuse of language for marketing purposes, nothing else. So is using 'bits' in network speeds, it is purely so they can market a number that is 8 times bigger. If you are going to download files, then you want to know what the transfer speed is in units of the file size, which is bytes. But 2Mb/s looks way faster than 244KB/s, [*] so lets print that number on the box!

      ISO tried to sort out the mess by defining new terms for the power of 2 prefixes, and it would have worked if they had chosen names that don't suck.

      [*] I was debating exactly what number to put in there. I was tempted to put in 200KB/s, since that is probably a realistic peak transfer speed on a 2Mbit connection. But that is a silly suggestion - who would come up with the idea of actually putting a number on the box that is immediately useful to a consumer? Better to put in some technical nonsense that depends on using some weird definition of the units to get a bigger looking number!

    27. Re:SI units by IWannaBeAnAC · · Score: 0, Troll

      LOL, your troll-fu is weak. Quibbling over k vs K is silly. Kelvins is a base unit, not a prefix. I don't recall ever seeing the 'kilo' prefix in a unit that also had a Kelvin in it, and conversely I've never seen a k or K written where it wasn't immediately obvious from the context whether kilo or Kelvin was intended. Try again!

    28. Re:SI units by RzUpAnmsCwrds · · Score: 1

      The problem is that a 2^k organization of bytes is fundamental to the way computers operate.


      It's fundamental to the way that memory is addressed, but there's NO REASON why you need to butcher SI prefixes. We just need binary prefixes.

      Oh wait, we already have binary prefixes. NIST, the IEC, and IEEE highly encourage their use.

      You can't realistically design a RAM chip with 1000 bytes of memory.


      You don't know what the hell you're talking about. Yes, if you have byte addressing, your addressable space will be a power of two. No, you don't need to use the whole addressable space.

      Nor do you have to use byte addressing. NAND flash is addressed by sectors, and it is often specified in SI units.

    29. Re:SI units by Mycroft_VIII · · Score: 1

      Accepted, expected, and causes BAD problems when ignored use in IT and related fields:
      kilobyte = 2^20 bytes
      megabyte = 2^10 bytes
      Gigabyte = 2^20 bytes

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    30. Re:SI units by HappyEngineer · · Score: 1

      This whole fight is ridiculous. On one side you have people who are just trying to maintain the purity of the standard definition of the word giga. On the other side you have anarchists who believe that they can use any word they want to mean anything they want. Sure, the SI prefixes were here first but who cares about that?

      In that spirit I am now going to start calling the dustballs under my computer "slashdots". I'm also going to use "slashdot" as the name for my monitors, my telephone, the dots at the ends of sentences, a dead badger that I found (which used to be called Ralph), and my toilet plunger. Oh, you mean that name was already taken and refers to something else? Good god, don't be such a stuck up prick. If I want to live in a smurfy... sorry, I mean a slashdotty world then that's what I'm damn well going to do!

      *sticks-tongue-out-in-manly-defiance*.

    31. Re:SI units by rgravina · · Score: 1

      I object to it for the simple reason that kibibyte, mibibyte and gibibyte are stupid sounding words and I refuse to use them for that reason alone.

      Interestingly enough, they sound perfectly fine in Japanese - kibibaito, mibibaito and gibibaito. So maybe those terms will be big in Japan!
    32. Re:SI units by darthflo · · Score: 4, Funny

      We had that kind of units. They went by the names of ell, foot, inch. After scientists realized that those units were pure idiocy for any kind of scientific work (and missed any kind of logic), they were replaced by the international system of units (abbr. SI). Units like the meters and grams have started replacing "old" units internationally starting in the 19th century and as for today, no civilized nation would ever have the idiotic idea to use something as arbitrary as a foot anymore, now would it?

    33. Re:SI units by devman · · Score: 1

      Bytes (Nor bits) are not and have never been SI units and are not bound to use the same base system for prefixes. Since computers operate in base 2 it only makes sense that a KB is 1024 bytes, and kibi and all that other nonsense has never been an accepted standard in the tech industry. I've yet to see it ever be used in anything other than discussion. A gigabyte is 2^30 bytes, not 3 billion bytes.

    34. Re:SI units by Anonymous Coward · · Score: 0

      Whenever I see kibibytes I think Kibbles'n bits.

    35. Re:SI units by darthflo · · Score: 4, Informative

      Everyone else except them uses KB/MB/TB/etc in a consistent - if not SI-compliant - fashion.
      Bullshit. Remember 4.8 kbps modems which managed to transfer 4800 bps? What's the throughput of what's commonly referred to as Gigabit Ethernet, while we're on it? 1024 Mibps or more like 1'000'000'000 bps? What about an 1.5 Gbps SATA link? How many Pixels in a Megapixel? How many lomaniacs in a Megalomaniac?
    36. Re:SI units by weapon · · Score: 1

      I understand people complain because everywhere else in the SI system is base 10, except with computers who like to count in base 2. So therefore people think to be compatible with the SI system bytes need to be counted in base 10 instead of base 2. The obvious problem is that computers count in base 2, but what I find interesting is that bytes are not SI units nor could they be derived from the SI base units. Furthermore SI units are not always that consistent, for example, there are seconds and micro seconds, but never kilo or mega seconds. Also the base unit for mass is the Kilogram, not the gram, yet we don't have a milikilogram or a kilokilogram, maybe we should fix these up first before we look at bytes and bits.

      It does not make sense for people to demand that bytes be scaled as a SI unit when they cannot even be related to the SI base units, and are not expressible in the SI system.

    37. Re:SI units by Dahamma · · Score: 1

      WHOOSH! Right over your head it goes...

    38. Re:SI units by Dahamma · · Score: 1

      He said "realistically", and I would imagine that means "financially and otherwise optimal". Routing address lines is much more expensive than a few more 1-transistor DRAM cells (no one was talking about NAND flash - these days manufacturers lie about that as much as they do magnetic storage). So if they can get 24 more bits per 10 bits of address space with just 24 more transistors, why the hell not?

      Who cares about how it's addressed? We are talking about efficiency of DATA storage, not addressing.

    39. Re:SI units by arkhan_jg · · Score: 1

      Transmission speeds are done in base 10, Mb/s etc. Screen sizes and resolutions are done in base 10. Physical dimensions are done in base 10. The ONLY thing done in base 2 are computer storage sizes. We have units for those; the kibibyte etc. It's clear that one is base 2, and one is base 10. Using a base 10 unit to designate base 2 numbers just because 'it didn't really matter back at the beginning' is frankly bloody stupid. It matters now, and base 2 units should be described properly. We just need to get it done. Keep storage in base 2, as you say it's the only practical choice. But since you're using a base 2 number, you have to use a base 2 unit not a base 10 unit.

      You're setting up a straw man by the way with deciweeks. SI units are not about redefining existing concepts; they're about having a consistent name scheme. kilo is times one thousand; mega is times one million. Everywhere but here. Week is not an SI unit, but if it were it'd be seven days as that's how everyone uses it. The ONLY place K- M- and G- are used incorrectly is computer storage. It's time we got over it, and use the proper prefixes.

      How about if we redefined the week to have 8 days on computer clocks, to make it easier to store and work with on computers? That's what you're saying we should be doing. Hmm, now I think of it, we already had one time where computer guys took a shortcut with dates, which caused a few problems later on...

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    40. Re:SI units by RzUpAnmsCwrds · · Score: 1

      While I can see the technical merit in using the Ki/Mi/Gi prefix instead of K/M/G, I object to it for the simple reason that kibibyte, mibibyte and gibibyte are stupid sounding words and I refuse to use them for that reason alone.


      I think that the Henry, and Coulomb are odd sounding units. It doesn't matter, they're the standard units.

      Seriously, could you have picked a worse reason why to use SI prefixes in a nonstandard way?

      the original scheme is a consistent exception


      No, it's not. With some exceptions, such as RAM and ROM, there has never been consistency. "1.44MB" floppies are neither 1.44MiB nor 1.44MB. DVDs use SI units. Earlier flash cards, based on NOR (which is byte-addressable) is measured in binary units. Newer flash cards almost always use SI prefixes. Data transmission rates have always used SI units.

      On the other hand, if someone came up with a set of power of 2 prefixes that didn't suck, I'd happily switch.


      The current prefixes are ideal. Not only are they similar to the old prefixes for ease of transition, they are also short.

      What's your problem with "meh be byte"?
    41. Re:SI units by Atario · · Score: 1

      You forgot the fourth option: redesign all digital circuitry to use ten levels of voltage to represent the numerals 0 to 9, instead of two levels for 0 and 1.

      Time to get a Computer Engineering degree for some sweet lucrative redesign money!

      --
      "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    42. Re:SI units by Anonymous Coward · · Score: 0
    43. Re:SI units by Atario · · Score: 2, Funny

      What's your problem with "meh be byte"?
      Meh be byte, meh be bit, who knows? Meh be we should just forget it and go have a beer.
      --
      "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    44. Re:SI units by jimicus · · Score: 2, Insightful

      For an industry that regularly has to deal with and resolve ambiguities, it's surprising to me how inert it seems to have been on this one.

      There wasn't an ambiguity before hard disk manufacturers decided to invent one.

    45. Re:SI units by Anonymous Coward · · Score: 0

      I agree that the SI terms do not apply to everything. Taking time as an example: we have a week = 7 days, but we do not call a day a centiweek because it is not. Thus (and I know we cannot change the past) you should not call 1024 bytes a kilobyte because it is not. The term "kilo" already means 1000, not 1024... no matter how useful it would be if it DID mean 1024.

      The SI system is not useful for time, so we don't use it. The SI system is not useful for computing so we... do use it? But change the meaning to add to the confusion? Wouldn't it be great if a dozen meant 12 for everything except potatoes for which it in fact meant 15 because it was more convenient for potato farmers? That's the situation we have here. Kilo means 1000. 1024 is a hugely useful unit... we just need a different name for it.

    46. Re:SI units by prockcore · · Score: 1

      The problem is that a 2^k organization of bytes is fundamental to the way computers operate


      Only for RAM.

      Your cpu speed is GHZ or 1 billion hertz. Your network speed is in mbps or 1 million bits per second.

      RAM is the ONLY thing that is measured by powers of two... so why should filesize be?
    47. Re:SI units by The+Clockwork+Troll · · Score: 3, Insightful

      In chemistry, it's very common to see heat capacity expressed in terms of kilojoules per Kelvin (kJ / K).

      I'd agree with your latter statement, but as long as I'm trolling, I'll point out that it was not technically the logical converse of your former statement but rather a wholly different proposition (1: "I have never seen 'k' and 'K' together in a single unit." vs. 2: "I have never seen an ambiguous 'k' or 'K'").

      In Soviet Russia, it fails you!

      --

      There are no karma whores, only moderation johns
    48. Re:SI units by Znork · · Score: 1

      "Regardless of whether the IT sector is _technically_ in the wrong it's commonly accepted that in this area we work with powers of two."

      No it isnt. It may be commonly accepted among some semi computer literate, but most knowledgable techs will know both the debate and understand that the original usage is too far off the rounding errors to be incorrect for some situations by now (not to mention that anyone the least interested in science or history will understand the idiocy of perpetrating the same kind of errors our less educated ancestors did that left half the world on inconsistent measurements that still occasionally result in blown spacecraft).

      KB never, ever, meant 1024 bytes. It meant 'close enough to 1024 bytes that you'll get the drift'. Anyone thinking otherwise obviously missed the classes explaining SI prefixes.

      I'm sure the HDD manufacturers used the most favourable measurement, but the fact is that they're correct. And even more, for most people it simply doesnt matter, because as long as they all use the same labelling, even the 10% difference they can get if they're misinformed today will not change the decision to buy the particular disk.

    49. Re:SI units by h4rm0ny · · Score: 1

      On one side you have people who are just trying to maintain the purity of the standard definition of the word giga. On the other side you have anarchists who believe that they can use any word they want to mean anything they want. Sure, the SI prefixes were here first but who cares about that?


      The SI prefixes weren't here first in this context. KB, MB, GB have an established meaning that goes way back and was never originally tied to the SI prefixes. You can say that using 1KB = 1024B is changing the SI meaning in this specific context, but saying 1KB - 1000B is changing the meaning of widely established words and that matters more. Neither you nor anyone else has a chance of suddenly stopping people using the actual terms GB, KB, MB, etc. They are the standard terminology. If the meaning of those terms were to change, then you would have a unit that is less useful than the existing one. For a number of reasons, power of 2 numbers are more appropriate in this context. I certainly don't want to be buying a 1.073741824GB stick of of RAM, but that's what the nature of computer addressing leads us to. I also want to be able to convert to and from network speeds (bits) easily. There are other issues. The point is that to be a useful and concise unit, it needs to be a power of 2, and that we have established terms that aren't going to go away.

      If somebody needs a decimal version, then it is the decimal version that requires a newly invented term, because whether it fits with another system or not, the GBs et al, are already there and their meaning was chosen for solid, practical reasons.

      The majority of computer purchasers don't particularly care what the standard is, so long as they know it is a standard. Those fewer computer users that do care, are certainly capable of understanding that a kilobyte means 1024 bytes and are sometimes greatly inconvenienced when someone fucks with the definitions as Seagate just has.

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    50. Re:SI units by Petersson · · Score: 1

      Inconsistency of IT be damned, SI units were defined and consistent long before IT usurped and mangled its prefixes.

      Please do not mix physics and IT. IT counts in discreet units (bytes, bits) and has its own definitions. The mess we have is caused by "smart" marketroids, trying to trick customers.

      RAM/Flash memory manufacturers cannot afford to make marketing tricks with volume of memory because of one obvious technical reason: the number of addressing lines. This very essentials of digital computing created the definition of kB, MB, GB, TB etc. Therefore claiming that kB could also be 10^3 of bytes is showing a)ignorance, b)gimmick.

      --
      I'm not insane. My mother had me tested.
    51. Re:SI units by HappyEngineer · · Score: 1

      The only units that you can claim that about are KB (meaning KiB) and possibly MB (meaning MiB). Storage didn't come in giga sizes until recent decades.

      I find it interesting that you claim it's widespread. When I see a hard drive advertised as 200GB I assume that it has 200*10^9 bytes. It never would have crossed my mind that it was 200*2^30 bytes. Can you point to any hard drive that is advertised with a size which is actually the GiB size?

      Those who know about binary would also know enough about hard drives that they know it's advertised in base 10 numbers. Anyone who doesn't know binary would never even guess that the size wasn't in base 10.

      You claim that using the SI prefix to mean what the SI prefix means in this context would be changing a widely established word. That's not true. The words are already polluted. If you see an SI prefix used in computing you ALWAYS need to look deeper to find out if it's a base 2 or base 10 number. What we've got here is a mushed up word. Thank goodness the values are close enough together that it usually doesn't matter much. The difference between 1GB and 1 GiB is only 73MB.

      How many flops are in a gigaflop? The answer is that it's 10^9 flops. Google the term and you'll find that it's widely used in that way. Would you have assumed that it was 2^30 flops? If so then that goes to prove the point that the prefix has been mushed up when used in the context of computing.

    52. Re:SI units by bm_luethke · · Score: 2, Insightful

      You are not going to win this argument - the sides have been drawn and you bring no new information to the table. All of us have already made up our minds.

      You have the two sides that care and then the rest of us that do not. It's not that I do no understand it - I've been an academic weenie for quite some time and find these things highly entertaining, yet I just don't care when it comes to my money. If I had to choose I prefer the base 2 definition as it makes the most sense, yet as long as I can compare two devices I do not care of they use "miblywinks" to rate their storage size - I just want something I know what they mean and standard across devices.

      In the end what file table I decide to use has more impact as to the usable size of my hard drive than if they use base 2 or base 10. That is WAY more confusing and "dishonest" than the esoteric idea of which standard you use. I find that I spend more time explaining why their 105gb (converted to base 2) device shows much less than that (also in base 2) when they click on it to non technical people. But then, do we then standardize on NTFS, FAT16, FAT32, EXT3, REISERFS, or ExoMibFS? Again, as long as I can compare apples to apples I could care less, just lets standardize on one.

      It's not a big deal to anyone who has half an idea what is being discussed, but most people do not know it. That isn't making fun of anyone - that is what those of us in IT are payed for. Lets face it, how many of us know what the building set backs for Residential One zones are - that is what Land Surveyors are for and there are going to be more of us worried if our house meets zoning laws than if our hard drives capacity is based on base 2 or base 10. Yet how many that feel that average people should know this know their local zoning laws (or land laws) to the extent we expect people to know computer technology (and there is WAY more money involved with land)? Unfortunately to many do no trust their IT professionals like they do the professionals they hire in other areas - but that is a different complaint.

      --
      ------- Sorry about the spelling, I suffer from two problems. Dyslexia makes it difficult to spell well, lazy makes it
    53. Re:SI units by Anonymous Coward · · Score: 0

      I don't recall ever seeing the 'kilo' prefix in a unit that also had a Kelvin in it I suppose you haven't ever seen a millimetre either.
    54. Re:SI units by HappyEngineer · · Score: 3, Interesting

      Not that it's particularly relevant, but in the book "A Deepness in the Sky" by Vernor Vinge, the characters used a timekeeping system where they talked about things like: "It'll take at least 10 Msec to get this done!" or "we've been travelling in hibernation for over 1Gsec! That's a long time!"

      The reason was that everyone had been out in space for thousands of years. Only a tiny percentage of the human race still lived on a planet where 24 hours was a day or 365 days was a year. So instead they have a calender which starts at Jan 1, 1970 and is measured in seconds from that point on. (obviously a reference to the internal clock of computers which measure times from the epoch)

      The book even included a chart at the beginning showing how megasecond, gigsecond, and terasecond values related to hours, days, and years. I actually think it's a wonderfully simple system which makes sense once you're off the earth.

    55. Re:SI units by Anonymous Coward · · Score: 0

      And 1KB per second = how many bytes per second? Since it's usually 1,000, I wouldn't call 1KB unambiguous.

    56. Re:SI units by trentblase · · Score: 2, Insightful

      But the base 2 units have been used for decades. Calling that use anarchy is similar to saying that we shouldn't use "bug" to describe a software malfunction simply because it has another meaning. Context will always tell you the answer. In the computer context, kilo is 1024.

    57. Re:SI units by jez9999 · · Score: 1

      or we can foolishly standardize on the base-10 definition and have RAM chips described as 1.074 GB

      No, we can 'foolishly' standardize on the base-10 definition and have RAM chips described as 1GiB.

    58. Re:SI units by aquaepulse · · Score: 1

      If I had mod points, you'd have them. He definitely failed hard.

    59. Re:SI units by jez9999 · · Score: 1, Informative

      It's not a prefix, it's a suffix. £1000 involves a prefix, 1000MB involves a suffix.

    60. Re:SI units by DrBoumBoum · · Score: 1

      No. 1Km = one Kelvin meter. 1KW = 1 Kelvin Watt. 1 KB = whatever you want. 1 KN = 1 Kelvin Newton. Please explain me what do exactly those units measure.

    61. Re:SI units by roguetrick · · Score: 1

      I agree with the spirit of the argument, the average user won't assume something is in base 2. However the average user will also not assume their OS is base 2. So when they go out to buy more hard drive space they base how much they want to buy on how much they use already, without much care on how the unit is measured. This ignorance causes a major screwup that wouldn't be helped by labeling sizes with GiB, the user still gets home and perhaps rightly thinks hes been ripped off. In this case however, maybe its some latent feeling of elitism in my bones that lets me say "screw it, thats okay."

      --
      -The world would be a better place if everyone had a hoverboard
    62. Re:SI units by tonzack · · Score: 1

      Oh, if only I can actually write what I am thinking right about now. The SI units have defined the prefixes to support base-10 representations of units: kilo = 10^3, mega = 10^6, giga = 10^9, etc. The reason why they invented kibi = 2^10, mibi = 2^20, gibi = 2^30, etc. is because they didn't want people to use the prefixes kilo, mega, giga, etc. for representing different quantities, especially when quantities in orders of magnitude higher are very much different between the unit quantifiers. That is why SI have proposed those prefixes. Scientifically, the new rules make sense, and I am for one appreciative of these efforts.

    63. Re:SI units by Jah-Wren+Ryel · · Score: 2, Informative

      Only magnetic and optical storage have the luxury of defining units in non-power-of-2 ways, and yet they generally do not, choosing to standardize on 512-byte blocks primarily because if they didn't, the VM system's paging path would be heinously inefficient. Using an OS's handling of RAM as a rationalization for 2^10 = K is a new one.

      The fact is that NO modern hard disks have sector sizes of 512 bytes. You heard me, NONE. They commonly have payload sizes of 512 bytes, but the actual sector on a hard disk contains a lot more than just payload - there are the ECC bits and the servo field which holds track, sector and disk head field grey code bits just to name the big ones. When added up, all the bits in a complete disk sector rarely equal a power of two, much less 2^10. Then are disks with 520 byte data payloads which are almost universally used in enterprise level disk arrays from manufacturers like HP, IBM, EMC, etc.

      So, what's the point of that? Anyone who says disks naturally have power of 2 data organization as justification for saying 2^10 = 1K is just talking out of their ass.

      ...is sufficiently confusing to an average layman that it really doesn't work, either. Thus, the only -reasonable- choice is to standardize on base-2 definitions of these units. Life is complicated, especially the technical parts. Unless you also propose to redefine data transmission rates like 100mbps ethernet and 150mbps SATA all your proposal does is rearrange the deck chairs.
      --
      When information is power, privacy is freedom.
    64. Re:SI units by The_Noid · · Score: 2, Insightful

      Mega is a Prefix to Byte.
      This whole discussion is about the use of the prefixes Mega and Giga as a multiplier other then the 1000 they have been defined as.

    65. Re:SI units by Kludge · · Score: 1, Flamebait

      The fact that people have to explicitly explain this fact shows that everyone expects it to be that way.


      "Everyone"?? If you asked 98% of people how many bytes there are in a gigabyte, they would not be able to tell you. Of the 2% that could, 98% of those would say "a billion", not "1.07 billion".
      A very small fraction of computer geeks in the population would say "2^30".

      SI units be damned, this is the way it has always been and there is no reason for it to be changed.


      No! SI units have been around a lot longer than computers have, and just because a few come-lately computer nerds have started abusing and misusing SI units, is no reason to drop their real meaning. Science is exact. Giga means 10^9 period. If "computer scientists" want to consider themselves real scientists they need to get with the f---ing program.
    66. Re:SI units by Anonymous Coward · · Score: 0

      Thats still hard-drive related, and is exactly what this thread is bitching about... inconsistency.

    67. Re:SI units by Opportunist · · Score: 1

      Correct. And no scientific community would measure anything in inches anymore.

      Not even just in the US. Try to go into a computer store in Europe and buy a 53.3cm Monitor. They'll stare at you. Yes, you get monitor diagonals given in inches here.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    68. Re:SI units by jamesh · · Score: 2, Funny

      I think that the Henry, and Coulomb are odd sounding units. It doesn't matter, they're the standard units.

      On the other hand, the Fonzie is a very cool sounding unit.
    69. Re:SI units by dotgain · · Score: 1

      What's Mega? (As in MegaHertz?)

    70. Re:SI units by twistedcubic · · Score: 1


      Go ahead. Don't use base 10 for measuring RAM sizes, use base 2, I really don't care. Just don't go calling it a Gigabyte, because it isn't.

      No. You can't just wipe away decades of common usage because you don't like it. And no, NIST doesn't get to do it either, even if they think they have the authority. This "gibibyte" nonsense hasn't caught on because it isn't needed, and even worse, the name sounds pretty lame.

    71. Re:SI units by drsmithy · · Score: 1

      Bullshit. Remember 4.8 kbps modems which managed to transfer 4800 bps? What's the throughput of what's commonly referred to as Gigabit Ethernet, while we're on it? 1024 Mibps or more like 1'000'0 00'000 bps? What about an 1.5 Gbps SATA link?

      Your examples do not contradict the point. Bits are not bytes.

      I repeat, the usage of 2^X powers within the computing industry has been consistent and logical. The *only* ones who have created confusion are those with agendas.

    72. Re:SI units by darthflo · · Score: 1

      On that one you're right. Some stores have, however, started transitioning TV's screen diagonals from inches to centimeters, so a longer-term switch may be possible. Also, I personally find the screen diagonal of something to be kind of a "soft" value. If you want to make sure the device will fit in a given spot, you check that spot's measurements (in centimeters) and check those values back against the screen's dimensions (which are, all over europe, given in *meters). If you want to make sure the screen will properly display 1080p video, you'll check the screen's resolution and so on. Especially with the recent uptake of widescreen displays, those diagonal values seem more like AMD's PR (processor rating; e.g. Athlon X2 4000+) - a more or less useful, more or less arbitrary value to help you group different products at a glance.

    73. Re:SI units by TiggsPanther · · Score: 1

      But the base 2 units have been used for decades. Calling that use anarchy is similar to saying that we shouldn't use "bug" to describe a software malfunction simply because it has another meaning. Context will always tell you the answer. In the computer context, kilo is 1024.

      I'm in complete agreement. I guess the main problem is that it's a simple conflict with non-simple repercussions.

      As you say, it's all to do with context. "Kilobyte", and the like, refers to 1024 bytes. The use of the term to mean something else would be a wrong use of the word kilobyte.
      Having just said that, this doesn't change the fact that it is not the correct use of the prefix kilo-. But the complete word kilobyte still has the 1024 meaning, whether it's technically correct or not.

      A couple of other points I've seen in this discussion do raise some interesting points, though. As regardless of the techncal correctness of the terms used, the hard drive manufacturers are getting off extremely lightly.
      Changes: Changing the terms used inside software/computers/manuals/documentation/etc would take a lot of doing. And could take years to be fully realised. Changing the terms used on the packaging of drives would be a lot quicker.
      Honesty: It's quite interesting that, apparently, hard drive sizes used to use the "accepted" definitions of kilobyte, megabyte, etc. If this is the case (I accept that "read it on slashdot" is not always a ringing endorsement of accuracy), then the manufacturers were incredibly sneaky. They're technically in the right, as they're using the terms in the officially correct way. Yet they're able to sell drives that are smaller than the accepted meaning of the sizes would suggest. Very clever, as they can point at the SI-endorsed terms and claim complete compliance.

      --
      Tiggs
      "120 chars should be enough for everyone..."
    74. Re:SI units by Mythrix · · Score: 1

      So, what we need is to find better names for the computer units. Surely something like gigantobyte and megalobyte must sound better than gibibyte and mibibyte. Hmm, what about kilo... killerbyte? Kilongbyte? Can't think of anything.

    75. Re:SI units by ceeam · · Score: 0, Flamebait

      Cock. Suck it.

      Really - except in HDD marketing is there any use for 10^x measurement of bytes? And no - if you say that SI should be uniform I don't buy it - SI prefixes only measure continuos (better word?) values, not discrete things like bytes and bits. You can't have 1.3932 bytes can you? And GiBi is so gay on many levels - for once - what's that mixing greek and latin. Why Gi - just because it's _close_ to Giga of 10^9? Etc etc. Then there's the issue of history and culture.

      Now that HDD manufacturers acknowledge that their Gigabyte is not _the_ proper Gigabyte can we stop this XxBi bullshit? Pretty please?

    76. Re:SI units by EvilIdler · · Score: 1

      A gigaflop is not a unit of storage.

    77. Re:SI units by Anonymous Coward · · Score: 0

      That's ridiculously picky. This is Slashdot, not a scientific journal. Yes, technically, the "kilo-" prefix should be abbreviated in lower case, like this:

      1 km = 1 kilometer
      1 kW = 1 kilowatt
      1 kB = 1 kilobyte
      1 kN = 1 kilonewton

      But honestly, the meaning is understood, and your "precision" is unwarranted.

    78. Re:SI units by redhog · · Score: 3, Informative

      No, not RAM. Anything you _address_. You don't address the 412th cycle in the CPU frequence, you don't address the 1201st byte in transmission speed, etc. You address RAM content, and disk content and ports and hosts on the internet. All such addresses are stored as binary numbers inside the computer, and can thus address two to the power of number of bits in the address numbers of positions (bytes, hosts, bits, whatever).

      --
      --The knowledge that you are an idiot, is what distinguishes you from one.
    79. Re:SI units by webrunner · · Score: 1

      The issue here is that "byte" is not an SI unit, but "mega" "kilo" etc are SI prefixes.

      It is actually probably NEVER technically correct to say "Gigabyte", in any context.

      --
      ADVENTURERS! - ANTIHERO FOR HIRE - CARDMASTER CONFLICT
    80. Re: SI units by Diablerie · · Score: 1

      There's no reason you can't have a "kilo" prefix in a unit that also has Kelvins in it. SI prefixes can apply to just about any unit of measurement. I'm pretty sure this statement is valid:

      The Sun's surface temperature is approximately 6 kK. (6000 K)

    81. Re:SI units by Anonymous Coward · · Score: 0

      Wow, Europeans are angry about some pretty insignificant things...

    82. Re:SI units by ruinous · · Score: 0

      Your post, while rather nicely written, misses the point entirely.

      A kibibyte is NOT defined as 1000 bytes, it is defined as 1024 bytes. You argue that SI units are nonsense because they attempt to standardize at base 10; this would indeed be ridiculous, but on the contrary, they are an attempt to standardize at base 2. Essentially, a kibibyte is exactly the same as what is currently known as a kilobyte in conventional usage.

      The trouble with using prefixes like 'kilo', 'mega', 'giga' is that they are ambiguous in the computing context. By definition, these terms represent powers of 10, yet the way these terms are used in computing contradict their intended usage.

      Replacing these terms with clearer ones like kibibyte, mebibyte etc makes alot of sense to my way of thinking, especially when their abbreviations are identical (KB, MB, etc).

    83. Re:SI units by Anonymous Coward · · Score: 0

      Megan does not mean a million "N"s
      Megatron does not mean a million Bruce Boxleitners
      Million does not mean one thousandth of an On
      Millipede does not mean one thousandth of a foot
      Nanobot does not mean one billionth of a bot

      Deal with it

      BTW we do use "SI" for time smaller than a second.

    84. Re:SI units by speculatrix · · Score: 1

      actually, base 12 can be enormously useful provided you adopt the correct processes for handling the numbers.. why do we still have 360 degrees in a circle? 24 hours in a day. Where did base 12 arithmetic come from? I'll let google and wikipedia give the answers. Hint: using your thumb to point at the joints on your four fingers, you can count to 12 on one hand.

    85. Re:SI units by jabuzz · · Score: 1

      It's not remotely picky, because the standard for computers has always been to use an upper case K to differentiate it from the S.I. prefixes.

    86. Re:SI units by Anonymous Coward · · Score: 2, Insightful
      Go ahead. Don't use base 10 for measuring RAM sizes, use base 2, I really don't care. Just don't go calling it a Gigabyte, because it isn't.

      Except, it is a gigabyte.

      Gigabyte (and megabyte and kilobyte and all the other -bytes) are not SI measurements, although they share some similarities with them. The prefixes "kilo" and "mega" (and the rest) are used by SI measurements, but they aren't unique to them; their origins date back to Greek and the computer industry has as much right to co-opt them as SI did.

      The computer industry decided from its infancy that its measurements would be in powers of two. It decided to use prefixes similar to those used by SI measurements for each order of magnitude; hence kilobyte, megabyte, etc.

      Arguing that a gigabyte isn't 1,073,741,824 bytes because it sounds similar to SI measurements is like arguing a foot isn't a unit of measurement to 0.3048 meters because it also happens to refer to a human appendage. While you could argue against the logic of this sort of measurement, it is the proper term; it's just not SI.

    87. Re:SI units by Oscaro · · Score: 1

      The SI units just don't work. They can't work. They will never work. That's because people think that units are for measuring hardware. They are not. They are meant to be a measure for quantities of information which are entirely abstract and not related on the hardware you put it into. Quantities of information are something you do math with, and are best expressed in powers of ten.

      The hardware vendors can (and should) just use the correct prefix. That's already happening. I've seen the KiB and MiB prefixes used both on memory modules and disks.
    88. Re:SI units by xaxa · · Score: 1

      decilitre? = 0.42 US cups.

      Wine bottles are usually 0.75 litres = 7.5 decilitres = 75 centilitres = 750 millilitres, a serving is 15cl. A measure of spirits (in the UK) is 25ml.

      A carton of fruit juice is 1 litre, the small cartons 2dl. 1 litre of water is a kilogram.

    89. Re:SI units by Anonymous Coward · · Score: 0

      Furthermore SI units are not always that consistent, for example, there are seconds and micro seconds, but never kilo or mega seconds.
      Why not? If I say some took a kilosecond to complete, you know EXACTLY how many seconds that was...1000 seconds, or one kilosecond. How is that not consistent?

      Just because a unit isn't commonly used doesn't make it inconsistent.

      I agree thought that the base unit of mass being a kilogram seems a bit odd, but the prefixes and suffixes are consistent. You know that a mass of 1 kilogram is 1000 grams. A centimeter is 10^-2 meters.
    90. Re:SI units by someone1234 · · Score: 1

      Normally i'm fond of SI, but i don't think it is the 'SI folks' that want kB as 1000.
      It is HD manufacturers. And only because it favours them.

      --
      Patents Drive Free Software as Hurricanes Drive Construction Industry
    91. Re:SI units by Anonymous Coward · · Score: 0

      The power of ten definition has been around far longer than computers.

      It's not that ten is more convenient to work with, it's what things have
      been defined as long before computers came to be. Trying to re-define it
      to a different power makes it more CONVENIENT for computer people but it
      is wrong.

    92. Re:SI units by Anonymous Coward · · Score: 0

      But its not a consistent exception.
      As things get bigger and bigger, the two terms will diverge more and more.

      You say 1GB = 1,073,741,824 bytes.
      In actuality, 1GB = 1 billion bytes (the article has this reversed).
      Your GB is simply the closest power of two to that.
      So should a GB x GB be 1,073,741,824 x 1,073,741,824 or the
      closest power of two to 1 billion x 1 billion. Do you use the closest
      power of two (as units are currently defined in computer work) and break
      GB x GB being equated to 1,073,741,824 x 1,073,741,824 or what?

    93. Re:SI units by BoogieChile · · Score: 1

      I always thought that SI thing was due to some powerful lobbying from the hard drive industry in the first place. I know no real technical person was involved. I mean seriously...Mebibytes? Gibibytes? Bibibytes? Stupid names for a stupid idea.

    94. Re:SI units by Anonymous Coward · · Score: 0

      As my grandfather said who was stationed in england during ww2 (he hit the beach at normandy):

      "You know the british are nuts. They eat out of the same bowl as their dogs ... and at the same time...."

    95. Re:SI units by Smidge204 · · Score: 1

      Neither frequency nor transmission speed are addressable. RAM and other data storage are.

      The problem is this: To address things in even quantities of a thousand, you need 10 bits:

      11 1110 1000 (binary) = 1000 (decimal)

      From a practical computing standpoint, this is a horrible way to do it. You want to maximize your range using as few bits as possible - so if you're using 10 bit addresses you use the full [11 1111 1111 (binary) = 1023 (decimal)] for a total of 1024 addresses.

      This became known as a "kilobyte." That's just the way it happened and it made plenty of sense at the time. From that day forth, adding "byte" to the end of an SI prefix automatically implied you were talking in base-2 measurements.

      ...until the hard drive manufacturers decided to break the pattern and actually use the SI meaning of "kilo" in "kilobyte," most likely as a marketing ploy, but it could also have been a convenience thing.

      I propose, instead of trying to get everyone to use a new unit of measure (KiB/MiB/GiB) that hard drive manufacturers start labeling their drives in terms of BITS. This will remove all confusion from both ends: bits are always measured in base 10 by everybody, and it makes the drives sound more impressive (8 terabit!) while still being truthful and practical. Also, a bit will always be a bit - being the quanta of data used in binary computing, you can't break it down any further. A "word" is not always 16 bits, depending on who you talk to, so heaven help us if the definition of "byte = 8 bits" should become obsolete too (Probably won't, but no harm in future-proofing.)
      =Smidge=

    96. Re:SI units by ebcdic · · Score: 1

      Nope, we're going to use the SI units and we won't use their definition. It's our language, and we'll use it how we want.

    97. Re:SI units by tilandal · · Score: 1

      SI was set as an agreed standard in 1960. ENIAC was first run in 1946. Care to try again?

    98. Re:SI units by Blakey+Rat · · Score: 1

      The problem is that a 2^k organization of bytes is fundamental to the way computers operate.

      Not my computer! I'm writing this post on ENIAC.

    99. Re:SI units by springbox · · Score: 1

      THANK YOU. I was going to post the same thing. I wish people would stop asserting that "1GB = 1GiB." The SI units were hijacked by the computer industry and not the other way around.

    100. Re:SI units by Anonymous Coward · · Score: 0

      "Bit" usage in networking has historical and practical purposes. It's not an arbitrary marketing decision.

    101. Re:SI units by mrand · · Score: 1

      Why do you say Flash chips are in powers of 10? They have address lines just like RAM (and ROM), so at their core, it is based on powers of 2.

      E1 being 2048 kbps is a fluke and isn't really "based" on a power of 2: it's 32 channels of * 64000 bit/sec. The telecom and datacom worlds use powers of 10 for SI prefixes... sometimes they round up, sometimes they round down.

            Marc

      --
      -- PGP keyID: 0x4C95994D
    102. Re:SI units by springbox · · Score: 1

      It might be, for a newcomer, initially confusing that a kilobyte is 1024 bytes instead of 1000 bytes, but the original scheme is a consistent exception.

      Hmm.. 1000 = 1024? Yeah, I wonder how that one got past the scientific community.

    103. Re:SI units by Bee1zebub · · Score: 1

      No, you use 1GB x 1GB = 1 152 921 504 606 846 976B, which is what you get either way. If it matter, use logical binary prefixes so that GB x TB = Yottabyte, not 1.xxxxYB and so on.

      Once the storage gets big enough to care about your quibble, it might be worth worrying about it, but we aren't anywhere near there for most uses yet (for data centres etc. marketroids are the ones who choose the names, so they would use decimal prefixes)

      Floppies are a straw man, 1.44MB is a piece of nonsense and those who still use them know it.

    104. Re:SI units by springbox · · Score: 1

      It might be, for a newcomer, initially confusing that a kilobyte is 1024 bytes instead of 1000 bytes, but the original scheme is a consistent exception.

      Although SI units have had a well established meaning before they were abused for use with computer applications, what you're suggesting amounts to context sensitive units. Think about that for a moment. Something like that would be laughed at by any respectable scientist yet people keep insisting on it.

    105. Re:SI units by Skapare · · Score: 1

      No ... the IT sector has NOT been wrong ... we're just different. It's a base 2 world, not a base 10 world, for a great many things in IT. We have our own standards system for base 2 stuff that does not involve creating a whole new set of prefixes. Where a base 10 system applies, a base 10 notation system is used. But where a base 2 system is needed, that is what is used.

      That said, let's have a closer look at what this means. First, not everything in IT is handled as base 2. RAM memory certainly is. But disk space capacity does not have to be. But the point raised in the legal case is that because the software on Windows REPORTS TO THE USER the capacity in the base 2 units system, and presumably Seagate knows this, then Seagate's use of the base 10 units system for advertising purposes constituted the misrepresentation.

      --
      now we need to go OSS in diesel cars
    106. Re:SI units by Anonymous Coward · · Score: 0

      Now when can we please have reasonable measures of small quantities of volume, based on a unit approximately the size of two cupped hands? That's a human-understandable unit.
      That's dumb. SI already has a perfectly acceptable unit of volume: the amount of beer one would drink in a sitting. It's called the liter. Only an uncivilized brute would drink beer out of his hands.
    107. Re:SI units by Anonymous Coward · · Score: 0

      The problem being, it's NOT your language, you moron.

      It's everyones, 99.9% of whom disagree with your idiotic abuse of the term.

    108. Re:SI units by u-235-sentinel · · Score: 1



      Hold on a sec.... "computer scientists" are now in the process of changing binary from base 2 to base 10. No longer will it be 1's and 0's. We'll have a lot of options available in 10^9 hours ;-)

      --
      Has Comcast disconnected your Internet account? Same here. You can read about it at http://comcastissue.blogspot.com
    109. Re:SI units by binaryartist · · Score: 1

      If that was the case why would segate lose the "court case". Segate claimed that 1GB = 10^9. In the court verditct it was proved that 1GB=2^30 which is 1073741824 B ...making Segate lose the Case!

      --
      When a thief sees a saint, all he sees are his pockets!
    110. Re:SI units by Just+Some+Guy · · Score: 1

      Life is complicated, especially the technical parts. Unless you also propose to redefine data transmission rates like 100mbps ethernet and 150mbps SATA all your proposal does is rearrange the deck chairs.

      ...says the guy with a 100millibit/s NIC.

      --
      Dewey, what part of this looks like authorities should be involved?
    111. Re:SI units by Just+Some+Guy · · Score: 1

      SI units have been around a lot longer than computers have, and just because a few come-lately computer nerds have started abusing and misusing SI units, is no reason to drop their real meaning.

      Or you could accept that RAM isn't measured in SI units. Why is that so important to you? Do you anticipated converting from liters to bits some day, or words per kilonewton?

      --
      Dewey, what part of this looks like authorities should be involved?
    112. Re:SI units by Anonymous Coward · · Score: 0

      Nobody is asking computers to use SI unit, that's a straw man.

      Since you brought up time, the situation is same as if computer people had hijacked "week" to mean 8 days in some arbitrary and highly variable contexts, because, you know, it's close enough to 7 and in base-2. Fast forward few decades, the field is starting to get larger and more and more people get exposed to and confused by the ambiguity, some start to call for changing the term, and cs people throw a hissy fit instead of admitting they're simply and obviously wrong and using another word.

    113. Re:SI units by Anonymous Coward · · Score: 0

      the standard for computers has always been to use an upper case K to differentiate it from the S.I. prefixes.
      Which is exactly why this "standard" is no longer usable. M, G, and T already are uppercase. Before the ISO binary prefixes were invented, I was always careful to write "KB" or "KByte" instead of the ambiguous "kB", and say "kay-byte" instead of "kilobyte". Now that there are binary prefixes, I'll use them no matter how often I get flamed. Being precise is the right thing.
    114. Re:SI units by fwr · · Score: 1

      It's also important to note that all of the contradictory examples happen to be involving communications, with bits as you point out, not storage. Storage, whether it be how much RAM a computer can access or how much storage space on a hard drive, has always been measured in base-2 units, not base-10.

      Create a base-10 computer instead of a base-2 computer and we'll start using base-10 storage terms.

    115. Re:SI units by Anonymous Coward · · Score: 0

      The problem being, it's NOT your language, you moron.

      It's everyones, 99.9% of whom disagree with your idiotic abuse of the term. You did a poll, did you?
    116. Re:SI units by Mattintosh · · Score: 1

      kibibyte, mibibyte and gibibyte are stupid sounding words and I refuse to use them for that reason alone.

      If they'd just have named them "kbyte", "mbyte", and "gbyte", we'd be just fine with it, right? We could keep our prefixes, too, and tell the SI people to stuff it.

      Speaking of which, how did International Standard units get named "SI"? Oh, yeah. Frenchies. Not only do they want to screw up our computer jargon (Our jargon, dammit! You don't mess with a man's jargon!), they also want to rearrange words so they make sense in their backwards-ass middle-ages language. Lingua Franca is so 1100 AD. Welcome to the 21st century, where we speak English and Spanish in most of the world (with shout-outs to Chinese, our up-and-coming buddy) and SI units are actually IS units.

      Now let's keep using Kilo as 1024 when talking about bits or bytes. The Frenchies can have their "it means 1000 zomg!" the rest of the time. Let the baby have his bottle.

    117. Re:SI units by OwnedByTwoCats · · Score: 1

      Hard Disk Manufacturers are using the standard definition of kilo, mega, and giga, and their standard abbreviations k, M, and G that have been in use for over 2 centuries, and are used that way to measure many different things (kilogram, kilometer, megahertz, gigahertz).

      It is the operating systems vendors who decided to use kilo, mega, and giga in non-standard ways to mean 2^10, 2^20, and 2^30.

      If I order 10 tons of grain, can I sue after delivery if I was only given 9.07 metric tons? And add fraud charges on top? Especially if the contract (the package of the hard drive) says that GB means 10^9 bytes, and ton means US ton?

    118. Re:SI units by GiMP · · Score: 1

      ENIAC was first run in 1946.


      Bad example.. ENIAC was not a binary system like those of today, it was decimal -- thats right, it was base 10. Its memory, then, would've been calculated as powers of 10, not 2. For the ENIAC, a kilobit would really have been 1000 bits, not 1024 -- not that the original ENIAC had nearly that amount of storage, it only had 15 decimal-bit "storage" in the form of painted lightbulbs. However, being decimal, that allowed for calculations up to pow(10,15).
    119. Re:SI units by OwnedByTwoCats · · Score: 1

      This very essentials of digital computing created the definition of kB, MB, GB, TB etc
      No, essentials of digital computing created the usefulness of binary-based units. The definitions of k, M, G, and T were established long before digital computing (digital? Base 10? Really?) came on the scene.


      And the standards bodies have agreed on units for the digital computing information storage needs. Yet the lawyers in this case have convinced a company that it would be less expensive to fork over payola than it would be to maintain that they are correct the prefixes in the way they have been used for centuries.

    120. Re:SI units by amorsen · · Score: 1

      Why do you say Flash chips are in powers of 10? They have address lines just like RAM (and ROM), so at their core, it is based on powers of 2.

      So what if they're based on powers of 2? They use variable amounts of space for sectors for reallocation and various other things. Fun will be had once we get to store say 6 levels per cell -- then they'll be based on powers of a non-integer number.

      --
      Finally! A year of moderation! Ready for 2019?
    121. Re:SI units by Metaphorically · · Score: 1

      It's metric tonne, not ton, and that's a whole different discussion. The tonne is the stupidest unit ever invented and has been a source of great confusion, quite possibly causing real damage to real things.

      --
      more of the same on Twitter.
    122. Re:SI units by illegalcortex · · Score: 1

      Only magnetic and optical storage have the luxury of defining units in non-power-of-2 ways, and yet they generally do not Actually, the interesting thing is that DVDs are labeled in MB (base 10), not MiB (base 2). This is the same as hard drives. CDs, on the other hand, are labeled in MiB (base 2).

      Network speeds (Kbps, Mbps, Gbps, etc.) are also listed in base 10, not base 2. That confused me for a while, as well.

      In another post, one person claims USB memory sticks are labeled base 10, as well (can't confirm).
    123. Re:SI units by IWannaBeAnAC · · Score: 1

      I am a scientist. You obviously have no idea what you are talking about. Technical language tends to be extremely consise, why bother with extra words when the meaning can be extracted from the context, etc. In math, why bother labelling the matrix with indices when it can be inferred from the context that it is obviously a matrix, and not just an ordinary number. And so on. What is wrong with that? Other units are context sensitive. Assuming you are from the USA, how often do you use the correct unit for mass? The average american probably hasn't even heard of it!

    124. Re:SI units by steelfood · · Score: 1

      That's the difference between continuous and discrete. Bits, by nature, function in a discrete manner. Thus, functional groups must be discrete as well, e.g. based on the power of the states of a bit. However, continuous groups can be arbitrary.

      And hence, bits can be grouped using base-10 when the frame of reference is a continuous entity (space and/or time), while they cannot when referenced functionally, i.e. described by other bits.

      Oh, and by the way, as you no doubt know, bits uses the lowercase 'b' while bytes uses the uppercase 'B'.

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    125. Re:SI units by Myopic · · Score: 1

      lightweight. come stateside and we'll show you how to drink a gallon.

      PS i like liters better than gallons. gallons are too big. but kilograms aren't better than pounds, and meters are far worse than feet or inches.

    126. Re:SI units by IWannaBeAnAC · · Score: 1

      Not really. The baud has a historical usage, and as far as I can tell once baud fell out of usage, bit/sec (without much thought as to what the prefix means) took over. maybe there is a precise technical meaning, but no one knows it.

    127. Re:SI units by darthflo · · Score: 2, Insightful
      The problem with storage examples is the limitation they have - basically, there's only three kinds of storage: Hard drives, internal electronic (as in Flash, RAM etc) and removable devices. But since you pointed out that all storage is computed in base 2 by referring to the second kind, I found myself forced to check the capacities of some removable media: (Mkt. C stands for Marketed capacity, Real C for the actual Capacity)

      Product| Mkt. C | Real C .| Result
      Name
      DVD . .| 4.7 GB | 4.3 GiB | bse 10
      CD . .| 700 MB | 703 MiB | base 2
      BluRay | 50. GB | 46. GiB | bse 10
      HD-DVD | 51. GB | 47. GiB | bse 10
      DLT . .| **. GB | **. GiB | bse 10 -- see explanation below
      I couldn't confirm the DLT claim, but according to a Quantum manual, DLT seems to be based on base-10 as well. Ultrium and co will (probably) be similar.

      Four out of five samples of removable storage media seem to be using base-10 for their claims which kinda positions two of three storage types in the base-10 camp which could be interpreted as RAM being the evil, non-uniform group. So let's ask them to add the tiny little "i", eh?
    128. Re:SI units by Anonymous Coward · · Score: 0

      "What's the throughput of what's commonly referred to as Gigabit Ethernet, while we're on it?"

      8589934592 bits/sec or 1073741824 bytes/sec. Which is 1 gigabit. Bad example.

      "What about an 1.5 Gbps SATA link?"

      Again, bad example. Its actually 1.5 Gb/s just like it says.

    129. Re:SI units by Jah-Wren+Ryel · · Score: 2, Informative

      No, not RAM. Anything you _address_. You don't address the 412th cycle in the CPU frequence, you don't address the 1201st byte in transmission speed, etc. You address RAM content, and disk content and ports and hosts on the internet. All such addresses are stored as binary numbers inside the computer, and can thus address two to the power of number of bits in the address numbers of positions (bytes, hosts, bits, whatever). Correction - you do not address disk content that way, you address filesystem content. Filesystems are defined by the host computer, disk sectors are not. Disk sectors exist independently from any host system and disks frequently contain an odd number of sectors, clearly not a power of two.

      Furthermore, try finding a modern tape drive system with capacities measured in powers of two. You won't, they are all sized in base-10 units.
      --
      When information is power, privacy is freedom.
    130. Re:SI units by sharp_blue · · Score: 1

      No, the comparison is if everyone decided to call weeks dekadays, but keep their length as 7 days. It's simply wrong. If you want to use the SI units, use the SI definition. Otherwise come up with your own terms.

      Exact!

      If I tell one: meet me in one dekadays, he still would be able to univocally figure out when it would be, notwithstanding the oddness of this unit.

      And yet, if I say, please send me that 1Mbyte text file, and if he has both a 1,000,000 and a 1,048,576 text file, witch one should he send?

      This misuse the SI units leads to unnecessary ambiguity. Please come up with own terms, of one wants to abbreviate 1048576 bytes. 1M is not a valid option; it has its precise meaning already defined much before this whole issue emerged.

    131. Re:SI units by afabbro · · Score: 1

      So how much is a trilobyte then?

      --
      Advice: on VPS providers
    132. Re:SI units by xaxa · · Score: 1

      I'd rather (FSVoR) drink a gallon here (London):
      "1 Imperial gallon = 8 Imperial pints = 1.20095042 US gallons = 9.60760333 US pints = 4.54609188 litres"
      (except I drank at least 6 UK-pints of "proper" cider on Wednesday [lost count], and it was about 8%, so another day of recovery is in order. Sometimes the big-brother tracking here is useful, the next day I went to a station and used the ticket machine to find out where my RFID travel card had been...)

      I don't care for pounds, it's hard to guess weights anyway -- although a reference 1 litre carton of juice is useful when I'm trying to do so.
      I'll use metres ("it's only 100m to the station, run!"), feet only for inaccurate body height ("she was two feet shorter than me!"), but I still say inches sometimes -- again, hardly ever with any accuracy intended, just because it's the word ("missed it by inches" "just an inch away" "give me a couple of inches of that" etc).

    133. Re:SI units by Anonymous Coward · · Score: 0

      Oh, you mean like the French Revolutionary Calendar? ;-)

    134. Re:SI units by Dahan · · Score: 0

      Thats still hard-drive related, and is exactly what this thread is bitching about... inconsistency.

      The post I was responding to said that the prefixes had a "consistent exception"--that kilo always mean *1000, except when referring to bytes, in which case it meant *1024. My point is that even that exception isn't consistent. There are many cases that can't be blamed on "marketing" where a kilobyte is 1000 bytes, a megabyte is 1000000 bytes, etc...

      I agree that "kibi" sounds stupid, but that's not a very good reason to use incorrect and potentially confusing terminology instead.

    135. Re:SI units by Anonymous Coward · · Score: 0

      "Go ahead. Don't use base 10 for measuring RAM sizes, use base 2, I really don't care. Just don't go calling it a Gigabyte, because it isn't."

      Good, bug off. Byte itself is 8-bit, not 10-based, and gigabyte is 2^30 bytes - who told you gigabyte is a metric/SI unit? It ain't one just because you insist.

    136. Re:SI units by dgatwood · · Score: 1

      Exactly. And other SI orders of measurement for bytes don't make sense. Decabytes don't work, decibytes are impossible because the unit is indivisible, etc. The byte will always be different from SI units because it isn't like other SI units. It has its own fundamental order.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    137. Re:SI units by Ahuitzotl · · Score: 1

      I hate to break it to you, but flash is not rated in powers of 10. Go read a datasheet will ya? The reason the number is odd for NAND FLASH (the kind used in USB keys flash cards blah blah blah...) is because of all the spare sectors in the device. Also, NAND FLASH is almost always spec'd in BITS not BYTES (For example a 1Gb flash chip is 128MB + some extra for ecc and such). NOR FLASH on the other hand is always spec'd in even powers of 2, and is always listed by the bit and byte capacity (at least in the datasheet).

      Spec'ing FLASH (and anything else directly addressed by a CPU for that matter) in base 10 makes no sense. The hardware simply does not work that way, and its incredibly inefficient to do it. Representing the number 10 in base 10 in a computer would require 8 bits, it only requires 4 if you do it in base 2. Assuming we would be using BCD to do this base 10 representation would mean we have to use 4 bits for every digit in the number. Thats a very huge waste! I suppose someone could build an analog computer with 9v (or equivalently scaled) logic and do it, but why?

      I believe the E1, E2, E3 stuff is represented in powers of 2 because each sub channel is 32kbps. Here in the states where we have the T1 etc, each sub channel is 24kbps, so we do not use base 2 math. That seems to be the case for all of the European vs US telco stuff. The Brits got smart and used easily computer divisible clock rates where us here in the US are stuck with this crazy junk. Which brings me to another point... Using power of 2 based data rates is smart because its really a pita to divide a clock by anything but a power of 2 and get a 50/50 duty cycle clock out of the divider. This is one reason why PLL based clock multipliers/dividers were invented...

      Oh yeah, and someone else mentioned the 4800 baud modem... That was back when Baud and Bits were NOT synonymous.. Technically to anyone that knows anything about modems (I can't say I know much...) they still aren't the same today, only marketers make them the same. Baud has to do with the modulation technique, which means the bit rate can be higher or lower then the baud rate. So applying powers of 2 to baud rate would not make much sense...

    138. Re:SI units by BillyBlaze · · Score: 1

      So if I dream up some new type of unit, am I free to use powers of 3*pi for it? Or would that be stupid? Is this less stupid because it's a better approximation?

      "Computers" includes networking, where they use SI prefixes. Which means that your hard drive fills up at only 1 kB/s when you're downloading at 1.024 kB/s. How is that not retarded?

    139. Re:SI units by BillyBlaze · · Score: 1

      Yes, for example networking hardware uses 10^x prefixes for bytes. And SI prefixes are used to measure energy, which is quantized. And yes, you can have 1.3932 bits. That's about what the entropy per character of English is, for example. Finally, your argument against the pedantry of gibi- is that it mixes latin and greek? Can you not see the irony in that?

    140. Re:SI units by Firethorn · · Score: 1

      Oh wait, we already have binary prefixes. NIST, the IEC, and IEEE highly encourage their use.

      And the rest of the world continues to ignore them. I've seen some of their documents, and THEY don't even use them. How's that 'highly encouraging'?

      --
      I don't read AC A human right
    141. Re:SI units by The+-e**(i*pi) · · Score: 1

      he specifically said only bytes, so why do you start trying to apply it to bytes per second which is a totally different unit?

    142. Re:SI units by PMBjornerud · · Score: 1

      The same is true for computing, and they would be wise to acknowledge that the same fundamental problems hold true in this area. Utter nonsense.

      Reporting memory sizes to end users has nothing to do with the internal workings in base 2. It is our job to convert between this, so the end users can only relate to easy, round numbers. 512 + 512 = 1k does not make sense for anyone outside the IT sector.

      Days are very different, since everyone related to earth in a very real and intuitive way. If earth was tucked away into a black box, you would be expected to report the days in units of 1000. Because people would not care, and not want to know, why the earth inside that black box spins at 1/365.25 cycles.
      --
      I lost my sig.
    143. Re:SI units by Kopretinka · · Score: 1

      The powers of 2 apply to bytes and only bytes, nothing else.

      How about bits?

      --
      Yesterday was the time to do it right. Are we having a REVOLUTION yet?
    144. Re:SI units by amorsen · · Score: 1

      Spec'ing FLASH (and anything else directly addressed by a CPU for that matter) in base 10 makes no sense. The hardware simply does not work that way, and its incredibly inefficient to do it. Representing the number 10 in base 10 in a computer would require 8 bits, it only requires 4 if you do it in base 2. Assuming we would be using BCD to do this base 10 representation would mean we have to use 4 bits for every digit in the number. Thats a very huge waste! I suppose someone could build an analog computer with 9v (or equivalently scaled) logic and do it, but why?

      You are awfully confused. The size of the medium has nothing to do with the way we represent numbers on that particular medium. To the computer it's just a bitstring with a particular length. There is no constraint that the length should be a power of two. Each chip tends to be a power of two long, but the computer doesn't see the individual chip -- there is remapping and wear-levelling in between. NOR flash tends to be directly addressed by the computer, just like RAM would be, but NOR flash capacity is basically zero anyway, so who cares.

      --
      Finally! A year of moderation! Ready for 2019?
    145. Re:SI units by SimonBelmont · · Score: 1

      Regardless of whether the IT sector is _technically_ in the wrong it's commonly accepted that in this area we work with powers of two. The fact that people have to explicitly explain this fact shows that everyone expects it to be that way. The HDD manufacturers damn well know this and fairly blantantly use measurements which would commonly be interpreted more favourably.

      At the same time, this has been going on with hard drives for over a decade. I just always expect capacity to be 10-based and not 2-based when I buy a drive. It's a stupid system, but if everyone is doing it and competing with each other, whatever the market will pay me per 10^9 bytes is close to the actual market value of 10^9 bytes, and not 2^30 bytes. While I'm glad it's going to change back, it seems unfair that Seagate is taking a blow for this if it's not everyone, and the appropriate time for such a lawsuit would have been back when a few manufacturers started this practice and forced everyone to follow, not long after it's established, because at this point manufacturers can no longer use it as a way to inflate their prices.

      Of course, there's also the problem that the mismatch grows with the units - 1KB is only off by 2.4%, while 1GB is off by 7.4%. I suspect this is why it took so long for anyone to raise a stink about it.

    146. Re:SI units by amorsen · · Score: 1

      he specifically said only bytes, so why do you start trying to apply it to bytes per second which is a totally different unit?

      Ah, so when I have a 20GB hard drive with a 20MB/s write speed, overwriting the disk doesn't take me 1000 seconds OR 1024 seconds, but actually 1074 seconds? I admit I hadn't foreseen that particular insanity.

      --
      Finally! A year of moderation! Ready for 2019?
    147. Re:SI units by redhog · · Score: 1

      Well, the cable to the disk is still digital, and addresses sent over that cable are also still digital. That disks seldom (never, although there is a reason for LBA addressing...) use the full width of the address is another thing.

      --
      --The knowledge that you are an idiot, is what distinguishes you from one.
    148. Re:SI units by alexo · · Score: 1

      How many lomaniacs in a Megalomaniac?

      That's easy, one million, since lomainacs are not binary.

      Also remember that:

      There are 10^12 picornaviruses in a rnavirus.
      There are 10^6 microbes = in a be.
      There are 10 millipedes in a centipede (and a whole 1000 in a pede).
      There are 10 decisions = in a sion.
      A hectograph is a 100 graphs.
      A megaphone is a 1000 phones (and 10^9 microphones).
      A gigantism is 10^9 ntisms.
      A teratoma is 10^12 tomas.
      A petasos is 10^15 soses.
      And finally, an examination is 10^18 minations!

    149. Re:SI units by Ahuitzotl · · Score: 1

      The fact that it is a bit string fully implies that its stored using powers of 2! What are you talking about? Each bit has 2 states, on and off, that is a very direct and obvious proof that computers work in powers of 2! Even floating point is powers of 2 based! And I was not talking about size re whats stored on it, I was talking about size with respect to how its represented! And you obviously don't know much about NAND flash if you think the 'computer' never directly accesses it. Of course it does! The 'computer' in this case is the CPU that actually accesses the flash and does the wear leveling on it! Or in the embedded systems sense, it very much is the CPU running linux that has direct access to the NAND flash chips. Why do you think the NFTL driver exists? The fact that the length of a chip is a power of 2 long is DIRECTLY RELATED TO HOW ITS ADDRESSED. Why would you have a chip with 1000 bytes if you have 9 address lines? That would waste 24 bytes of address space.

      And as for NOR flash flash capacity being zero... I think 32MB exists quite well to me, being an embedded developer that programs CPU's with 8-512 KB of flash.

    150. Re:SI units by HappyEngineer · · Score: 1

      So you have no problems with a gigaflop being 10^9 flops while a gigabyte is 2^30 bytes (except on all packaging for all hard drives and all ram of course)?

    151. Re:SI units by Anonymous Coward · · Score: 0

      Maybe it's type for the SI folks to realize that perhaps the reason their standard [binary integers] has been near-universally rejected in computing circles for almost a decayear is that it is fundamentally brain damaged from a practical use perspective....
      It is not. A kibibyte is perfectly usable for both binary-orientated systems and for people who call 2^10B '1kB'. There is no difference except for the correct name.

      It makes about as much sense if the SI had standardized base-10 units of time other than the second.
      You're perfectly right. A centiday is a perfectly well-formed hundredth of a day. It is a valid SI unit which makes sense, although this unit is quite uncommon.

      Kiloweeks, anyone? Decidays?
      No, thanks. Kiloweeks, decidays and centidays sound too unfamiliar for common use. But they are valid SI units.

      The SI folks wisely realized that moving time to a base 10 unit was not practical because the natural division of days into years could never be forced into base-10 units comfortably.
      You got something wrong here. The SI standardizes units (such as 'seconds', 'days', 'years') and prefixes (such as 'milli-', 'centi-', 'deci-', 'deca-', 'kilo-', and so forth). You can combine them as you wish, those combinations are all valid.

      Instead, they acknowledge the usefulness of these non-SI units as acceptable for use in spite of their non-base-10 nature.
      This is not true. 'Seconds', 'minutes', 'hours' and 'days', and so forth, are valid and pretty decimal SI units. (They are binary as well: One hour is exactly 111100 minutes, in binary. SI units have nothing to do with the base of the completely unrelated numeral system you choose to use in combination with them.) Their *relationships* are (for historical reasons) not defined in bases of 10, therefore one hour is slightly more than ten minutes. Concerning your explanations of the binary system as more usable for computers: You're right, yes. We should continue to express binary contents in the binary system. As is defined by SI, the prefix 'kilo-' means 'one thousand times'. '1kB' therefore is exactly '1000B'. If you say '1kB', but mean '1024B', you're lazy (because there was no SI prefix to express 'one thousand and twenty-four times'. But now there is. Use it.)
    152. Re:SI units by similar_name · · Score: 1

      I remember when I worked for Creative Labs. We received several calls of people complaining that they couldn't load their 2 MB soundfont into the AWE32's 4 Mb of memory.

    153. Re:SI units by wizrd_nml · · Score: 1

      I frankly don't care what unit is used as long as when I check the total disk capacity of my hard drive in Windows or Linux or whatever, I get the same number as the one on the box.

    154. Re:SI units by DanQuixote · · Score: 1


      Sorry, but you won't be hired to tame the complexities of technology for human use with this approach.

      If we as computer scientists can't translate our powers-of-2 into normal numbers for the masses, then we are failing in our jobs.

      It is fine to develop, design, architect, prototype and implement with 2^n, but once it goes on screen or on sale for the masses, for hell's sake quit screwing around and use the SI standard units.

      Another blow against logic in the U.S. court system!

      --
      "We think people rightly feel that once they buy something, it stays bought," --Suw Charman, Open Rights Grp
    155. Re:SI units by porpnorber · · Score: 1

      While I can see the technical merit in using the Ki/Mi/Gi prefix instead of K/M/G, I object to it for the simple reason that kibibyte, mibibyte and gibibyte are stupid sounding words and I refuse to use them for that reason alone.

      I resolve this issue to my satisfaction by reading "KiB" as "Kibobytes."

    156. Re:SI units by Anonymous Coward · · Score: 0

      >It makes about as much sense if the SI had standardized base-10 units of time other than the second.

      Yes, but but your argument is flawed. Our units of time - days, weeks, seconds - are all BASE units. There are no SI prefixes there. And if you claimed a day was equal to a kilosecond, people would call you mad. However, that's precisely what has happened here: people call 1,073,741,824 bytes equal to a gigabyte - which it is not. "Giga" means 1,000,000,000.

      I don't argue it's hard to physically create circuits or what-not in base-10 units - but they need their own units to describe them then. Don't steal someone else's unit and then get pissed when they say "no! bad computer scientist!"

    157. Re:SI units by vidarh · · Score: 1

      KB certainly "never ever" meant 1000 bytes either, since "K" isn't a SI prefix. It thoroughly amuse me when the "SI prefixes are holy" crowd keep writing KB instead of "kB" which is what you should be writing if you wish to actually use SI prefixes.

    158. Re:SI units by Reaperducer · · Score: 1

      Hint: using your thumb to point at the joints on your four fingers, you can count to 12 on one hand.
      Great post. Seven years and I finally learn something on Slashdot that I can actually use. It's about damned time.
      --
      -- I'm old enough to have lived through six different meanings of the word "hacker."
    159. Re:SI units by Danny+Rathjens · · Score: 1

      kilo, mega, giga, tera, peta are silly, too. You are just used to them. :)

    160. Re:SI units by vidarh · · Score: 1

      Flash chips doesn't. Flash drives do. So what you are saying is really just that the the flash drive manufacturers is doing the same as the harddrive manufacturers. It has nothing to do with the capacity of the flash chips, which are typically reported in Mbits with M=1048576.

    161. Re:SI units by vidarh · · Score: 1

      If that precision isn't needed, because the meaning is understood, then what the fuck is the problem with using K=1024?

    162. Re:SI units by owlstead · · Score: 1

      "So we have a choice: we can either standardize on one unit---the base-2 definition of a gigabyte---or we can standardize on two units---one for RAM and one for hard drives---or we can foolishly standardize on the base-10 definition and have RAM chips described as 1.074 GB. I, for one, can't imagine that last choice being too popular,"

      Why the hell not, because a bunch of nerds get bragging rights about getting it right? Computers have moved out of the realm of specialists, they are now common tools. What percentage of people do you think know how many bytes go into 1 GB RAM? I've got no problem at all calling it 1.07 GB of RAM, hell, we do that for currency all the time.

      If we just use SI units, all those irritating conversions go away as well. How much time does it take to send 3 TB over a 1 Gb/s link? How many bytes in 1 GB? And in 1000 MB? Can you explain *that* to the average Joe?

    163. Re:SI units by Jah-Wren+Ryel · · Score: 1

      Well, the cable to the disk is still digital, and addresses sent over that cable are also still digital.

      WTF?
      --
      When information is power, privacy is freedom.
    164. Re:SI units by Anonymous Coward · · Score: 0

      I'm sorry, but I don't think SI units have exclusive rights to letters.

      In physics, do you know how many things are represented by "p" or other letters? You have to look at the context of the equation to know what it means in that case.

      That's how you know when to use 2^10 or 10^3; context.

      If it is too much brain power to discern things based on context, I'm amazed you can hold conversations with people in English.

      Anybody who doesn't know that "kb" means kilobyte, or 2^10 is not familiar with the field of computing. And in that case, who cares what they think?

    165. Re:SI units by Anonymous Coward · · Score: 0

      Okay, let me rephrase this for clarity:

      kilobyte = 2 XOR 20 bytes = 22 bytes = Gigabyte
      megabyte = 2 XOR 10 bytes = 8 bytes

    166. Re:SI units by Anonymous Coward · · Score: 0

      OK haha, yes I made the error late at night, "kb" is kilobit not kilobyte, make your jokes, whatever. It's late, and I spent all day researching, I have the right to make dumb errors once in a while, as long as it doesn't ruin my grant opportunities.

    167. Re:SI units by Anonymous Coward · · Score: 0

      Just plain wrong. In the context of bytes, 'kilo-', 'mega-', and 'giga-' have always meant multiples of 1024. SI simply cannot come in and tell everyone that 'kilobyte' no longer means what it has meant for over 50 years. You simply cannot dictate language, especially when you tell people to ignore decades of usage and pretend 'kilobyte' always meant 100,000 bytes. Not only is this bullheaded, but it has caused mass confusion, as evidenced by this case. This is why the retarded 'kibibyte' still has not and never will catch on. It is also why I have started to use 'gidebyte' for the misleading units on DVDs and hard drives.

      If they really wanted people to switch to decimal, which is probably a good idea from a usability aspect, they should have recommended everyone slowly move over to bits. After all, that realm has always worked in decimal (kilobit, megabit, &c.).

    168. Re:SI units by TeatimeofSoul · · Score: 1

      I hereby define one knibble (kilo-nibble) to mean exactly 183459349724 nibbles. I have a file
      stored on a harddrive which weighs about one kilo, and this definition therefore makes everything very neat and simply. So much so, that demands of consistency will just have to yield. I also define one Mword (mega-word) to mean 1 word (since 'mega' is one word).

      This might be confusing, and not completely uniform, but there is no ambiguity.

      Seriously (well...), please finish this sentence for me. "Having KB mean 1024 bytes is very practical since 1024 is precisely the number of integers you can describe with 10 bits, and this amount of bits is frequently encountered when..."

    169. Re:SI units by trentblase · · Score: 1

      Well, hertz is frequency context where SI prefixes are appropriate because hertz is an SI unit. The byte, however, is not an SI unit. You are correct to point out that I probably should have said should have said said "data context"

    170. Re:SI units by James+Youngman · · Score: 1

      While I'm not sure if it is true in this case, you still sometimes see vendors rounding sizes up, for example selling a 287 x 10^9 byte drive as 300GB.

    171. Re:SI units by The+-e**(i*pi) · · Score: 1

      Exactly, but B/s can go either way as its really based on the frequency of a clock times the data size per tick (Marketing probably adds in the protocol overhead to write a number on the box so a 1 GBit network card should not be written as a 1GBit per second ethernet card as the Ethernet overhead is wasted space ie: if I rent you a 20'long moving truck and I put the drivers seat, engine, fuel tanks in the same compartment with the storage you are really getting only 15' of space unless you want to rip out the engine, seat, and gas tank which would make the truck useless for all but the most basic of operations (think PODS))

      What they should list is the frames per second and the protocol ie 10baseT 10baseTx 100BaseTX and 1GBE over copper.

      You could theoretically have a 10/100 network card that can only handle sending 100k frames per second which would top out at 10 mbps but still able to connect as a 100mbit card by having a 10mbit internal bus to get data from the computer to the out port and it would be fine.

      You could then also have a good network card that sends about 50M frames per second shown as better than one that tops out at 1M while both can only send a peak of about 1GBit of data out, but the second one would only send about 20mbps of small frames while the first will send out the full 1gbit.

      and scrap all this for serial interfaces they are just different.

    172. Re:SI units by sasdrtx · · Score: 1

      As seems to be usual, you're confusing RAM with disk drives. RAM is restricted to powers of two by its nature; disk drives are not. Using 1GB to mean 1073741824 bytes of RAM is a convenience, not a definition.

      --
      Most people don't even think inside the box.
    173. Re:SI units by Anonymous Coward · · Score: 0

      Why would you switch from KiloByte to KibiByte? Those stupid terms were created years afterwards from marketting pressure. The computer term has always been 1 KB = 1024 bytes since the dawn of the binary computer era. It has always been that way, so there is no point in switching. Just because some marketting pricks thought they could scam the average layman with 1 KB of hard disk = 1000 bytes doesn't change the way we've been using the term of 1 Kilobyte.

      I have never heard of anyone using the term Kibibyte until I first saw it in some obscure wiki document a few years ago. Now they want it to be a new standard? That's right, dumb it down for the masses who can't use that 1 extra brain cell to realize that computers are binary systems.

      Don't let marketting dictate changes. They fuck things up.

    174. Re:SI units by dotgain · · Score: 1

      Okay then, data. How fast is a two megabit connection?

  6. Seems Silly to me by IcarusMoth · · Score: 4, Insightful

    Seriously, the blame could just as easily be laid at the feet of the OS developers. There is a long standing history of disk manufacturers using base 10 counting numbers. It would not be so horribly difficult for the OS developers to conform to the base 10 measurement. I mean what next are the consumers going to sue because the formatting and allocation tables take up room? or perhaps because it hides space for virtual memory? seriously. come on people.

    1. Re:Seems Silly to me by xiang+shui · · Score: 1

      No shit. I wish I had mod points.

    2. Re:Seems Silly to me by gadzook33 · · Score: 2, Insightful

      Yeah, other than the fact that computers suck at base-10 counting and are really really good at base-2 counting, you're absolutely right.

    3. Re:Seems Silly to me by hakr89 · · Score: 5, Insightful

      You are buying the drive to store base 2 numbers, so why shouldn't the value be rated in terms of base 2?

    4. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Just because bits have two values doesn't mean you have to count them in base 2.

      Are you going to use base 3 to count triangles?

    5. Re:Seems Silly to me by gadzook33 · · Score: 1

      Yeah, that was my point

    6. Re:Seems Silly to me by Prof.Phreak · · Score: 1

      Indeed. Wait till they go after Gigabit Ethernet... uh, oh, it's only 1000000000 bits, not 2^30 bits!

      --

      "If anything can go wrong, it will." - Murphy

    7. Re:Seems Silly to me by DiSKiLLeR · · Score: 4, Insightful

      Seriously, the blame could just as easily be laid at the feet of the OS developers. There is a long standing history of disk manufacturers using base 10 counting numbers. It would not be so horribly difficult for the OS developers to conform to the base 10 measurement. I mean what next are the consumers going to sue because the formatting and allocation tables take up room? or perhaps because it hides space for virtual memory? seriously. come on people. You're moronic.

      Every operating system, whether it be Windows NT, XP, or Vista, Linux, FreeBSD, or Solaris, states that 1Kb = 1024bytes, 1Mb = 1024Kb, and so on.

      Every application, does too.

      Why rewrite all software, and god forbid, patch all old software going back however many DECADES into the past to implement this change, when harddrive manufacturers could simply start labelling their drives correctly?

      Besides, when you buy a gigabyte of ram, are you really getting 1 billion bytes? or 1073741824 bytes? You tell me :)

      Last I checked, bios reported 1024Mb was a 1gb, and 4096mb was 4gb's of ram :)

      I don't see why hdd manufactureres are the ONE single exception to this long standing rule, and SI units be damned.
      --
      You can tell how powerful someone is by the magnitude of the crime they can commit and be able to get away with.
    8. Re:Seems Silly to me by IcarusMoth · · Score: 1

      I understand where you are coming from, but I think that a decision like this caters to the stupids among us. not to mention the fact that it is only through human interaction with computers that this "problem" was even discovered, but also consider that the average human brain, knows base-10. Not to mention the fact that the Kilo-byte itself is an approximation. (an approximation of 1000). I'm simply stating that, on the usability end, it would be minimal to do a simple conversion when the user asks to see "space remaining on disk" because that is how this gets started; user buys a 200 GB drive, it only shows 185Gb or so, user thinks "Oh my gosh, they stole my bits!" If the OS simply converted the value, for usability, this problem would have been avoided. I would agree with you if the HDD manufacturers had only recently started using base-10 to inflate their numbers after decades of using base-2, but that is not the case. HDD manufacturers have "Always" used base-10, it's nothing new, it's only recently that the capacities have gotten large enough for it to be noticeable. As for the Ram thing, you are comparing apples and oranges, which is a lot like comparing GB's with Gb's.

    9. Re:Seems Silly to me by otomo_1001 · · Score: 4, Interesting

      Lay the blame at os developers? How about you propose changing how computers fundamentally work then?

      Oh wait, that is exactly what you are proposing. Do you know why a byte is 8 bits long? Yes it is arbitrary, but we are sort of stuck with the nomenclature now. Either memory (RAM) manufacturers are labeling their stuff right or wrong, or hard drive manufacturers are labeling their stuff right or wrong.

      Most people seem to agree with the memory manufacturers however. Sure we could have all the os tools divide by 1000 for displays of size, but that only masks the issue. And as we get to larger storage will probably cause problems. Just think of when we have exabytes of storage and are approaching some limit we currently think is insanely high. This "little" difference becomes rather substantial. And with the future of storage leaning towards flash, which follows the powers of 2 a byte scheme, hard drives become even more the bastard child of computing.

      Either hard drive manufacturers step into line with the rest of the computing world, or they learn their little trick isn't appreciated anymore. As silly as it seems it may be the only way to get this little annoyance of computing to go away.

      PS: I do think people have sued about the formatting of a drive bit. Time for filesystems like zfs methinks.

    10. Re:Seems Silly to me by bh_doc · · Score: 1

      The OS wouldn't even have to do the conversion. (As a bare minimum) All that needs to be done is a little "i" inserted between the "G" and the "B".

    11. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Yes, they always have used that measurement, and I have always been offended that they did so.

      Their behavior was NEVER correct.

    12. Re:Seems Silly to me by 5pp000 · · Score: 5, Interesting

      I don't see why hdd manufactureres are the ONE single exception to this long standing rule, and SI units be damned.

      Ever hear of a "1.44MB" floppy? How many bytes do you suppose it holds? That's right... it's a double-sided version of a "720kB" floppy, so it really holds 1440KiB... which, perhaps inevitably, people started calling "1.44MB", even though that "MB" is the bastard child of the decimal and binary kilobytes, 1024000 bytes.

      Once that monstrosity caught on, I'm afraid we were doomed.

      --
      Your god may be dead, but mine aren't!
    13. Re:Seems Silly to me by nocomment · · Score: 4, Insightful

      Because computers are base2.

      It might not sound like a big deal, but as HD's get bigger so does seagates 'edge' over the competition. They get to trim 73MB (or so) off every gig. This means that a 250GB drive from seagate is missing 18,435,456,000 bytes. A 500GB drive: 36,870,912,000. In the olden days, this wouldn't have mattered (much) because you weren't talking about a lot of space. People complained back then too. Now it's getting a little silly. If you need to build a 5TB array, there will be 368GB that's just missing (and that's not even counting the FS overhead).

      Seagate isn't doing it to be a champion of change for a switch to base10 counting (if they were then it would make more sense), they are doing it to rip people off on a technicality.

      --
      /* oops I accidentally made a comment, sorry */
      /* http://allyourbasearebelongto.us */
    14. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      You haven't used fdisk lately :)

    15. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Seriously, the blame could just as easily be laid at the feet of the OS developers.

      And damn those RAM manufacturers for making those 256, 512, 1024 and 2048 megabyte sticks of memory!

      seriously. come on people.
    16. Re:Seems Silly to me by absoluteflatness · · Score: 2, Informative

      Drive manufacturers are in a position to make the much easier fix though. Changing OSes to report base-10 sizes, or to keep the existing sizes with the *iB notation requires changes from every OS manufacturer, and suddenly leaves them inconsistent with older versions of their products.

      Whereas, for storage companies, it's a simple matter of changing the labeling and packaging. A switch to only using the base-2 sizes (my personal favorite) would also probably mean that the drive companies would start subtly altering drive sizes so they wouldn't be selling "85.7 GB" drives and would instead align neatly on a round GB number (which is actually incrementally harder to do now, because drives already are organized with power-of-2 blocks). Otherwise, they could simply list both sizes on the packaging, or include something to the effect "your computer will report this drive as having a capacity of X".

      Really, the problem now with the MiB, KiB units is that people in general aren't aware that these are any different than MB and KB, and would likely only increase confusion. Another unit distinction that's still causing confusion is illustrated by your last line (comparing GB's with Gb's).

      GB is gigabtye, where Gb is gigabit. So it's very easy to compare these, take Gb's and divide by eight: ta-da, GB. Another confusion taken advantage, this time, mostly by the Internet industry. Modem companies quickly jumped on the terms "56K modem" and such, which helpfully obscure that the K is for kilobits (base-10 again), of course until your computer reports you transferring data at a maximum of something like 5 KB (not to mention physical line limits that further decreased the actual maximum).

      Really, computer-related industries seem to like to sow confusion in the market. The distinctions don't matter as much with increased capacities (even though the distinctions themselves increase in size). Take as an example, say you have a file your computer reports is exactly 1.41 MB in size. Ideally, this should fit on a 1.44 MB disk (filesystem usage of the disk aside), but that 1.44 MB is really 1440 KB, where KB is the base-2 unit, or only 1.40625 "standard" MB.

    17. Re:Seems Silly to me by Myopic · · Score: 1

      Huh? My computer doesn't have any trouble at all understanding base-10 numbers. Computers can translate between bases with trivial effort. I don't think we need to choose our human counting methods according to how easy it is for the computers. Trust me, the computers can keep up.

    18. Re:Seems Silly to me by Myopic · · Score: 1, Funny

      Dude, you just blew my mind, seriously. I never thought of that before.

    19. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      You're moronic.

      Every operating system, whether it be Windows NT, XP, or Vista, Linux, FreeBSD, or Solaris, states that 1Kb = 1024bytes, 1Mb = 1024Kb, and so on.


      Oh really? Linux too?
      The following is from Linux dmesg output I googled for:
      http://osdir.com/ml/openbsd.mac68k/2004-04/msg00010.html

      SCSI device sda: 3450902 512-byte hdwr sectors (1767 MB)
      SCSI device sda: drive cache: write back
        sda: [mac] sda1 sda2 sda3
      Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
      SCSI device sdb: 2503872 512-byte hdwr sectors (1282 MB)
      SCSI device sdb: drive cache: write back
        sdb: [mac] sdb1 sdb2 sdb3 sdb4 sdb5 sdb6
      Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
      SCSI device sdc: 625356 512-byte hdwr sectors (320 MB)
      SCSI device sdc: drive cache: write through
        sdc: [mac] sdc1 sdc2 sdc3 sdc4


      Let's see:
      625356 sectors * 512 bytes = 320182272 bytes
      320182272 / 1024^2 = 305.3496

      The next dmesg output:
      http://launchpadlibrarian.net/1687260/dmesg_out_2.6.15-18_dapper.txt

      [4294675.733000] ide1 at 0x170-0x177,0x376 on irq 15
      [4294675.748000] hda: max request size: 128KiB
      [4294675.748000] hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(100)
      [4294675.748000] hda: cache flushes not supported
      [4294675.749000] hda: hda1 hda2 hda3

      OMG, they are using those ugly KiB!

      And the next one is from Vista help:
      http://windowshelp.microsoft.com/Windows/en-US/Help/2af64e60-60aa-4d79-ab6c-3a5db5806cbe1033.mspx

      Which CD or DVD format should I use?
      DVD-R

      You can burn files to a DVD-R more than once (each time is referred to as a session), but you can't delete files from the disc. Each burn is permanent.

      4.7 GB

      You must close the session to read this disc in a different computer. Highly compatible with most computers and devices.

      DVD+R

      You can burn files to a DVD+R more than once (each time is referred to as a session), but you can't delete files from the disc. Each burn is permanent.

      4.7 GB

      You must close the session to read this disc in a different computer. Compatible with many computers and devices.


      So according to Microsoft DVD+/-R has 4.7 Gigabytes capacity.
    20. Re:Seems Silly to me by RzUpAnmsCwrds · · Score: 2, Informative
      Note: The following post uses SI prefixes (e.g. GB=10^9 bytes, etc.) correctly. Binary prefixes are used when appropriate.

      Every operating system, whether it be Windows NT, XP, or Vista, Linux, FreeBSD, or Solaris, states that 1Kb = 1024bytes, 1Mb = 1024Kb, and so on.


      WRONG. Use a modern Linux distro. You will find that many tools either use the binary prefixes or use SI-standard prefix usage.

      Why rewrite all software, and god forbid, patch all old software going back however many DECADES into the past to implement this change, when harddrive manufacturers could simply start labelling their drives correctly?


      Because HDD manufacturers ARE labeling their drives correctly. "Giga" means 10^9 in SI. It always has and always will. The computer industry usage has never been correct.

      The disparity only grows as we go up in prefixes. 1TiB = 1.099TB. 1PiB = 1.125PB. 1PiB = 1.153PB.

      Moreover, the non-SI use is ambiguous. A "1.44MB" floppy is neither 1.44MiB nor 1.44MB, it's 1 440 KiB. A "650MB" CD is 650MiB, but a 4.7GB DVD is 4.7GB.

      GiB is NEVER ambiguous. If you want to keep using the power-of-two units, use the proper prefixes. IEEE, NIST, and the IEC encourage it.

      I don't see why hdd manufactureres are the ONE single exception to this long standing rule, and SI units be damned.


      Hard drives, flash storage, DVDs, Blu-Ray/HD-DVD, transfer rates (8Mbps = 8 000 000 bps), and everything else uses the standard SI prefixes.

      Why should computer memory be the ONE EXCEPTION to the SI standard prefixes? We have binary prefixes. Use them if you want.
    21. Re:Seems Silly to me by tecmec · · Score: 1

      Yeah, but when you are dealing with bits or telecommunications (and networking) the base 10 definition is the one that is more widely accepted. This is why (usually) you can't convert directly from Kb to KB just by dividing by 8 (or Mb to MB, or whatever). Yes, B to b it's just a simple 'divide by 8', but kilo meaning 1000 for bits, and 1024 for bytes really starts to make things fun.

    22. Re:Seems Silly to me by moderatorrater · · Score: 1

      You seem to be stuck in an overly relative universe, where this one component has every right to redefine a term that every other computer part defines differently. As pointed out above, the CPU, RAM, OS and every programming language with something resembling market share define it the same way, as a power of two. The term has been defined the same way everywhere else, therefore, it's fraud to redefine it for the purposes of marketing.

    23. Re:Seems Silly to me by RzUpAnmsCwrds · · Score: 1

      You are buying the drive to store base 2 numbers, so why shouldn't the value be rated in terms of base 2?

      BECAUSE SI PREFIXES DON'T CHANGE BASED ON WHAT YOU ARE MEASURING.

      It doesn't matter whether you are measuring distance (km), mass (kg), force (kN), energy (kJ), power (kW), pressure (kPa), frequency (kHz) or resistance (k).

      Kilo always means 10^3. Mega always means 10^6. Giga always means 10^9.
    24. Re:Seems Silly to me by grahamwest · · Score: 1, Informative

      You are right that it's actually 1440KB but you're totally wrong about everything else. 720KB floppies were double sided and "double density". That means 80 tracks, 18 sectors per track, 256 bytes per sector - with the 2 sides you get 720KB. "high density" or "quad density" floppies were 36 sectors per track, doubling them up to 1440KB. This is equivalent to 1.40625MB.

      --
      Graham
    25. Re:Seems Silly to me by darthflo · · Score: 2, Insightful

      Technically, you're right. Most "advanced" systems ("advanced" as in "catering a crowd that understands the difference between GB/GiB") are actually doing just that right now. Try `df --si`. Most commonly used other tools also include a similar if not the exact same switch.
      On the other hand: If Joe sixpack buys a 200 Gigabyte hard drive, he'll expect Windows Explorer to show 200 Gigabytes of space. Vista will most probably eat about 50 of 'em, but that doesn't concern him, as long as there's 200 Gigabyte of total space. What also won't concern him is if that unit right behind the number says GB or GiB. He doesn't commonly use the mega or even giga prefix (if he's american he might even still be used to using medieval terms like feet and miles (no prefixes for those, of course)), 'cause commonly thousands of kilometers aren't expressed as megameters. He'll ignore the i and be as annoyed as before, cause they still took his bytes.

    26. Re:Seems Silly to me by darthflo · · Score: 1

      OS manufacturers are in a position to make the much easier fix though. Changing hard drives to report base-2 sizes, or to introduce sizes with the *iB notation requires changes from every hard drive manufacturer, and suddenly leaves them inconsistent with older versions of their products.

      Whereas, for OS manufacturers, it's a simple matter of changing the labeling and packaging.

      It works that way round too, you know?

    27. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      It *is* a new thing. I've got a bunch of hard drives that ARE what they claim to be. And they're not even that old either. I bought one of them two years ago. Of course, it had been sitting in a box for a few years, but still.

    28. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      I don't see why hdd manufactureres are the ONE single exception to this long standing rule, and SI units be damned.

      Didn't you forget about flash memory manufacturers?
    29. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      I don't see why hdd manufactureres are the ONE single exception to this long standing rule 'Kilo' means thousand. 'Mega' means million. Why should the computing industry be the ONE single exception to this extremely long-standing (think 'centuries') rule?
    30. Re:Seems Silly to me by Anonymous Coward · · Score: 0
      As for the Ram thing, you are comparing apples and oranges, which is a lot like comparing GB's with Gb's.


      So if I load 1GB from my hard drive into 1GB of RAM then I should have 48576 bytes free?

      It's not apples to oranges, it's more like oranges and orange crates.

    31. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Every operating system, whether it be Windows NT, XP, or Vista, Linux, FreeBSD, or Solaris, states that 1Kb = 1024bytes, 1Mb = 1024Kb, and so on.

      Every application, does too.

      Why rewrite all software, and god forbid, patch all old software going back however many DECADES into the past to implement this change, when harddrive manufacturers could simply start labelling their drives correctly?

      This is what Windows XP reports as the size of a particularly large file on my HD when I do a right-click > properties:

      823 MB (863,821,824 bytes)

      When a look at the properties of my hard drive, I get a similar answer:

      Capacity: 80,015,491,072bytes 74.5GB

      I can't vouch for Linux, Solaris, etc, but XP is just as happy as can be quoting both exact decimal and binary approximation figures. No patching is necessary. It's as easy as two clicks for any user to see the exact difference between the decimal and binary representations of hard drive space.

      If a person is technically savvy enough to look at his available disk space and see that he only has about 74.5GB of space on his 80GB hard drive, then he's probably technically savvy enough to see that those two numbers side by side don't equal each other. An intelligent person might ask why that is before going off on Seagate. In the process of looking into this, he might find out that HD manufacturers always list the decimal number. He would discover that Seagate wasn't some rouge company trying to pull a fast one on capacity, but rather it was acting in full compliance with industry norms and that every computer technician on the planet was very much aware of the discrepancy and always expects those numbers to be different.

      Not only is the grandparent not a moron, but his proposed fix works well and is already in place. Seeing as we all are aware of the situation and the math is accurate (At least in binary. Who the hell knows how many bytes there are in that "823MB"?) why don't we continue to use both numbers and specify which one we're using whenever there's a potential for ambiguity, just like my OS does.

      Drivers in London are not wrong for driving on the left side of the road. They all know what to do and they do it. You all know that you don't get 80GB(Binary) in an 80GB(Decimal) drive. You all know that all of the drive manufacturers use decimal values. They are not wrong. You are wrong for having all that knowledge, having consistent and accurate labeling, and still complaining that those "morons" are driving on the "wrong" side of the road.
    32. Re:Seems Silly to me by prockcore · · Score: 1
      The GNU tools have already switched.

      $ dd if=/dev/zero of=test bs=1MB count=1
      1+0 records in
      1+0 records out
      1000000 bytes (1.0 MB) copied, 0.00797 seconds, 125 MB/s
      you can also say 1MiB and it'll copy 1048576 bytes.
    33. Re:Seems Silly to me by thue · · Score: 1

      The base two thing is a low-level technical detail. It has no relevance to consumers.

      The fact that some operating systems choose to let that low-level detail show to the consumers is because of poor operating system design, not because of any logic reason.

    34. Re:Seems Silly to me by prockcore · · Score: 1

      Sorry, saying "1.4 MiB" to represent a file that's 1,500,000 bytes requires just as much math as saying "1.5 MB" to represent the same file.

      There's no excuse for OSes to not use base10 measurements when talking about filesizes.

    35. Re:Seems Silly to me by Emetophobe · · Score: 1

      There is a long standing history of disk manufacturers using base 10 counting numbers.

      And there is an even longer standing history that computers use the binary system. Perhaps you should read about the binary system.

      The average person only understands the decimal system from what they learned in school, so hard drive manufacturers decided to use the decimal system to market their drives. It was purely a marketing decision. Computers have always used the binary system and it's idiotic to say that OS developers are at fault for using the binary system when that's all computers understand and that's how computers have functioned for the past 50 years. If anything, blame the hard drive manufacturers for spreading misinformation and confusing the general public for over a decade.

    36. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      A network is used to transmit 1s and 0s (base 2 numbers). So why is it OK for network specs to use 100Mbit/sec = 100,000,000 bits per second?

    37. Re:Seems Silly to me by LS · · Score: 1

      Because most humans, who are users of computing devices, use base-10 for almost everything. The design of a system should be abstracted away from the customer. Should Word display binary numbers instead of characters? Should your cars speed be shown in tire revolutions per minute?

      LS

      --
      There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
    38. Re:Seems Silly to me by jez9999 · · Score: 1

      Of course, OSes could just report both figures... ie. Drive C has 200GB (185GiB)

    39. Re:Seems Silly to me by wertarbyte · · Score: 1

      Every operating system, whether it be Windows NT, XP, or Vista, Linux, FreeBSD, or Solaris, states that 1Kb = 1024bytes, 1Mb = 1024Kb, and so on.
      Nearly all linux distributions I worked with in the last few years (!!) display storage capacities with the correct binary unit (KiB, MiB etc.).
      --
      Life is just nature's way of keeping meat fresh.
    40. Re:Seems Silly to me by prockcore · · Score: 1

      Maybe we should use octal then.. since bytes are 8 bits.

      So 1 byte = 10 bits (in base 8)
      1 KiB (1024 in base10) = 2kb (2000 in base 8)
      1 MiB (1048576 in base10) = 4mb (4000000 in base 8)

      Nice round numbers.

      Computing internals shouldn't affect what is displayed to the user. It's absolutely ridiculous that a file that's 5,000,000 bytes should be displayed as "4.8mb" because that's "easier" for computers.

    41. Re:Seems Silly to me by Detritus · · Score: 1
      I know it's a losing battle, but a byte isn't always 8-bits. That's why we have the octet.

      The use of powers of 2 for RAM sizes is a side-effect of digital circuit design techniques, in particular, binary addresses and address decoders. Mass storage devices are not subject to the same constraints. They deal in streams of bits, which can be segmented in arbitrary ways by the drive's firmware.

      I'm disappointed that Seagate caved on this issue. They didn't do anything wrong. They are being punished for the illiteracy of the average computer user.

      --
      Mea navis aericumbens anguillis abundat
    42. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      dd if=/dev/zero of=test bs=1MiB count=1
      1+0 records in
      1+0 records out
      1048576 bytes (1,0 MB) copied, 0,00173071 seconds, 646 MB/s
      Inconsistent assholes !
    43. Re:Seems Silly to me by jamesh · · Score: 1

      The 720KB disks I used to buy were advertised with a "1MB unformatted capacity". Trouble is, they never worked when they weren't formatted...

    44. Re:Seems Silly to me by dfgchgfxrjtdhgh.jjhv · · Score: 1

      yeah, it'd be much easier for consumers to remember they have 1.073741824gb of ram

    45. Re:Seems Silly to me by bestinshow · · Score: 2, Insightful

      The fact that the storage of data on a floppy disc (and hard drives) is segregated into blocks that are sized in powers of two (512 bytes for most floppies) suggests that the capacity of said drives should be expressed as a number that is a multiple of said block size.

      E.g., Floppy Drive: 2 sides * 80 tracks * 9 sectors * 512 bytes = 720KB

      Any other argument is totally pointless to be totally fair. If you want a base 10 capacity for binary data that is not stored in blocks of base 2 size you use bits, e.g., 20Mbit. For example TCP/IP packets can be any size, so using bits is common for networking capacities/bandwidths.

      I appreciate that there are SI units, but they are not in common use apart from total SI/standards nerds, and their creation was misguided and based upon a core misunderstanding of the issue.

      I hope this means that hard drives, flash memory, and so on, are now sold with the true capacity on the label.

    46. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      It's easy to see that the harddrive manufacturers are doing it right. This I can claim with the same empirical evidence as which has been posted previously by other slashdaughters.

      1GB, as the harddrive manufacturers use it, is 1 billion bytes. 1 000 000 000.
      G stands for Giga and is an SI unit.
      1GB, as the memory manufacturers use it, is more (almost 1/10) than 1 billion bytes. 1 073 741 824.
      Gi stands for Gibi and is an SI unit. Gi would be the correct label.

      If you ask me, it causes more confusion when people don't follow standards. As well as the fact that we get robots which don't make it all the way to Mars in one piece.

      --
      [Non-]anonymous coward MMN-o

    47. Re:Seems Silly to me by Solra+Bizna · · Score: 1

      Sorry, saying "1.4 MiB" to represent a file that's 1,500,000 bytes requires just as much math as saying "1.5 MB" to represent the same file.

      Actually, one is a bit shift and one is a divide. The latter calculation could take as long as a dozen cycles, even on modern processors! This extra performance hit is unacceptable, especially for performance-critical applications such as displaying file sizes!

      -:sigma.SB

      DISCLAIMER: JOKE

      --
      WARN
      THERE IS ANOTHER SYSTEM
    48. Re:Seems Silly to me by jshackney · · Score: 1

      Hmm, I thought "surely you're talking about df -h."

      Tried 'em both.

      hrmfph!

    49. Re:Seems Silly to me by TiggsPanther · · Score: 1

      Of course, OSes could just report both figures... ie. Drive C has 200GB (185GiB)

      Better still, if OSs and package labelling and drives and media used both then it would be a lot easier. Additionally, if the two terms were used side-by-side then, eventually, it would become understodd (and accepted) that the two have different meanings.

      Now if only the pronunciations weren't so laughable...
      It would certianly help adoption if the terms used didn't sound/feel like a joke when spoken out loud.

      --
      Tiggs
      "120 chars should be enough for everyone..."
    50. Re:Seems Silly to me by Nazlfrag · · Score: 1
      Luckily then they are COMPUTING PREFIXES AND NOT SI UNITS OF MEASURE.

      The clash of computing engineers and scientists on slashdot makes this the best place for these discussions. Everyone gets so worked up! You can shout without getting modded troll! Everyone is right! You're inconsistent! NO YOU ARE!

      Face it, computer geeks are stubborn bastards. Kibibyte my arse, YOU should change to kidigram DAMMIT!

    51. Re:Seems Silly to me by TiggsPanther · · Score: 1

      Nearly all linux distributions I worked with in the last few years (!!) display storage capacities with the correct binary unit (KiB, MiB etc.).

      The useful thing that I do find about that notation is that I see it and automatically know which measurement they're using. I do wonder, though, how people "hear" it when they read it.

      I know I still sort of see it as "Megabyte (using binary calculation)". As I know what the older term meant, and still does to me. Yet I certainly find it a useful visual distinction, even if I'd still say the old (technically wrong) term.

      --
      Tiggs
      "120 chars should be enough for everyone..."
    52. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      If you ask me, it causes more confusion when people don't follow standards. As well as the fact that we get robots which don't make it all the way to Mars in one piece.

      they don't follow standards because for decades those standards didn't exist - and those so called 'standards' were made up by an organization outside the computer industry so go figure that they haven't adopted it

    53. Re:Seems Silly to me by alexhs · · Score: 1

      Exactly. I already posted on that.

      People are clueless and it's Windows that's lying, not the disk manufacturer. Many FLOSS applications either use KB, or mention KiB (like Nautilus, cfdisk... I will need to check about Konqueror...).

      Chipsets use power of two physically. So using *iB allow for round numbers. But hard drives, optical drives, ... are neutral. Hey, there's 2352 bytes in an audio cd and you can put 2336 bytes of data in a CD sector (Mode 2). So using standards is just good behaviour.

      <rant>Now, US still use feets and stones, so why should one be surprised about people asking for fucked up units ?</rant>

      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    54. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Where did you see floppies formatted with 256 byte sectors? All I ever got was 512 bytes/sector, and of course 9 per track for DD and 18 for HD floppies.

    55. Re:Seems Silly to me by SillyNickName · · Score: 1

      Every operating system, whether it be Windows NT, XP, or Vista, Linux, FreeBSD, or Solaris, states that 1Kb = 1024bytes, 1Mb = 1024Kb, and so on. Every application, does too.
      Simply not true. Additionally, 1Kb was often used to refer to 1024 bits, not bytes. Likewise for Mb, Gb and so on.
    56. Re:Seems Silly to me by Thaelon · · Score: 1

      The base two thing is a low-level technical detail. It has no relevance to consumers.

      It suddenly becomes very relevant when their computer tells them that the 2GB SD card they just bought and plugged in is actually only 1.87GB.

      It's deceptive advertising. HDD manufacturers and flash memory manufacturers seem to be the only ones to do this. Even system memory is measured in powers of 2. A 2GB stick of ram is 2048MB, not 1914.88MB.
      --

      Question everything

    57. Re:Seems Silly to me by Blakey+Rat · · Score: 1

      Except there's nothing that requires computers to operate in base-2. Early electronic computers (the kind used to aim nukes and such) were analog. Early programmable computers operated in base-10. A future computer based on nanotubes, or lasers going through crystals or whatever advancement is "5 years out" could do something entirely different, who knows?

      I agree that "kibibyte" sounds moronic, though.

    58. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Conveniently, the long-standing history started at the exact moment someone made a consumer hard disk drive that was just shy of an actual GB, but still over 1000 make-believe MB. "First 1 GB consumer drive" sure sounds better than "first almost 1 GB drive."

      But I'm sure that was just a coincident, it's all for standardization's sake, right?

    59. Re:Seems Silly to me by Bee1zebub · · Score: 1

      No, they are just as bad as the HDD manufacturers, it's just that since network speeds are theoretical values anyway, so no-one makes a fuss. Of course the use of bits/second is itself somewhat dishonest, but that is a fight for another day.

    60. Re:Seems Silly to me by swilver · · Score: 1

      Nice try! 1440 * 1024 bytes = 1474560 bytes = 1.47 * 10 ^ 9 bytes. Calling it a 1.44 MB floppy is wrong on both counts, so I don't see how it supports your argument.

    61. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      1Kb = 1024bytes
      Who fooled you into believing that one Kbit equals 1024 bytes? They really scammed you. You should sue them for a 87.5% refund. And about those 4096 millibits of RAM... oh, forget it.
    62. Re:Seems Silly to me by Bee1zebub · · Score: 1

      Well, I'm a physics student, and so use SI units all the time, but I have no problem remembering the difference between SI and computer units and I use Imperial units for some things as well (and on rare occasions the Fortnight/Furlong/Firkin system or the attoparsec), all depending on the suitable unit for the job. (Of course, I only use the latter two on rare occasions.)

    63. Re:Seems Silly to me by drew · · Score: 1

      It might not sound like a big deal, but as HD's get bigger so does seagates 'edge' over the competition.


      Except for the fact that every other hard drive manufacturer does the exact same thing, and has been for at least the last ten years, so they're not really edging out anybody....
      --
      If I don't put anything here, will anyone recognize me anymore?
    64. Re:Seems Silly to me by Agripa · · Score: 1

      Which Flash memory manufacturers were you thinking of?

      The Flash memory integrators who are using Flash chips for storage devices are using the same notation that the hard drive manufacturers are using. The chip manufacturers themselves however are using the notation that the semiconductor memory manufacturers are using except they do not count the area reserved for error correcting data in the actual storage capacity.

      In some respects this is a little odd because the actual number of bits stored in the array is not a power of 2 when you count the extra error correcting bits (64 bytes per 2048 byte block) but that is only at the lowest level and the pages and blocks themselves are addressed in powers of 2. It is just the page size itself which is not a power of 2.

      I guess the lesson here is that it is the interface that matters. This is especially the case for low pin count parallel interfaces (DRAM and SRAM) where initially the chip organization was driven more by the cost of the package pins then chip layout considerations. If your interface relies on powers of 2, then a kword (whatever the word size happens to be) is 1024 of something. Maybe the hard drive manufacturers should have switched to binary coded decimal.

      A typical bulk NAND Flash device is specified like this: (copied from a Micron datasheet)

      Page size x8: 2,112 bytes (2,048 + 64 bytes)
      Block size: 64 pages (128K + 4K bytes)
      Plane size: 2,048 blocks
      Device size: 4 Gb: 4096 blocks; 8 Gb: 8,192 blocks; 16 Gb: 16,384 blocks

      So for this device not counting the page level error correcting bytes:

      4 Gb = 4096 blocks x 64 pages/block x 2048 bytes/page = 4294967296 bytes

      You might also note that the block size of 128K is equal to 131072 bytes.

      I remember when the hard drive manufacturers switched to base 10 notation and I do not remember anybody who thought it was done for anything except marketing reasons. It made their own drives look larger then the drives of their competitor's who had not switched yet.

    65. Re:Seems Silly to me by Agripa · · Score: 1

      I made a small mistake:

      4 Gb = 4096 blocks x 64 pages/block x 2048 bytes/page = 4294967296 bytes

      should have been:

      4 Gb = 4096 blocks x 64 pages/block x 2048 bytes/page x 8 bits/byte = 4294967296 bits

    66. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Last I checked, bios reported 1024Mb was a 1gb, and 4096mb was 4gb's of ram :) >/quote>

      I wish people would stop pointing this out, I am a CS student and even though I study this stuff, I *always* *feel* the extra value when I see those 96mb!
    67. Re:Seems Silly to me by tilandal · · Score: 1

      HD manufactures have not "Always" used base 10. They started out using base 2 and converted to base 10 when some marketing genius figured out you could cut costs by mislabeling your merchandise.

    68. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      That's right... it's a double-sided version of a "720kB" floppy,


      No it isn't.
      It's the same 720 floppy, but you just snip-off the corner.
      =P
    69. Re:Seems Silly to me by BronsCon · · Score: 1

      Very true. However, the computer counts them in base 2.

      If I have 1GB (2^30) of RAM, I would expect a raw 100GB disk to be able to hold the contents of my RAM 100 times over. If I have a 1GB (2^30) file and the ability to write to a raw 100GB disk as though it were tape, I would expect that disk to be able to hold 100 copies of that file.

      Please, tell me what is unreasonable about that?

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    70. Re:Seems Silly to me by 5pp000 · · Score: 1

      1440 * 1024 bytes = 1474560 bytes = 1.47 * 10 ^ 9 bytes. Calling it a 1.44 MB floppy is wrong on both counts

      My point exactly. It's neither 1.44 * 10 ^ 6 nor 1.44 * 2 ^ 20.

      --
      Your god may be dead, but mine aren't!
    71. Re:Seems Silly to me by 5pp000 · · Score: 1

      You're right, the "720k" floppy was already double-sided. Sorry. Doesn't change my main point, though.

      --
      Your god may be dead, but mine aren't!
    72. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      And how fast do you think you're Internet connection or LAN connection is? Hate to break it to you, but those are also in metric.

      Some parts of the computer industry have historically used binary units, others metric. It doesn't make one more correct than the other - they're simply using that which is convenient in calculations.

    73. Re:Seems Silly to me by evilviper · · Score: 1

      GiB is NEVER ambiguous.

      You're ABSOLUTELY RIGHT.

      Hard drive manufacturers just have to start marking their packaging, and notating their products in GiBs, and this problem will go away entirely, in an instant.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    74. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      If I ever see that on my machine I'm reporting a bug because that's just plain old wrong.
      DD is for block copying. It almost never makes sense to use anything other than powers of two.

    75. Re:Seems Silly to me by BillyBlaze · · Score: 1

      Computers also use ASCII, not bitmaps. However, we convert from one to the other when outputting information for human use. Just as we now have graphics hardware that can do the conversion, we also have ALUs that can divide by 10.

    76. Re:Seems Silly to me by BillyBlaze · · Score: 1

      How is the base in which the computer counts relevant? The computer outputs in (bitmap representations of) base 10.

      Do you also expect your 1 GB/s network connection to transfer the contents of your ram in 1 second? Because it won't be able to. What it boils down to is that your initial assumption is incorrect. You have 1 GiB of RAM. You decided to make a bad approximation of how much RAM you have because you like round numbers but hate pedantry. You are now angry that your approximation has led to imprecision. That is stupid.

    77. Re:Seems Silly to me by BillyBlaze · · Score: 1

      Drawing a distinction between computing prefixes and SI prefixes, when they share the same name, violates the principle of least surprise. As software guys, we should be receptive to that.

      This is a really fun flamewar. :-)

    78. Re:Seems Silly to me by BillyBlaze · · Score: 1

      Easier still would be to remember that they have 1 GiB of RAM.

    79. Re:Seems Silly to me by BillyBlaze · · Score: 1

      Why rewrite all software, and god forbid, patch all old software going back however many DECADES into the past to implement this change, when harddrive manufacturers could simply start labelling their drives correctly?

      Because that software is INCORRECT. Should we have just decided that time was circular instead of fixing the Y2K bugs? It would have been easier!

      Besides, when you buy a gigabyte of ram, are you really getting 1 billion bytes? or 1073741824 bytes? You tell me :)

      Your premise is false. You actually bought a gibibyte of RAM. You ought to be pissed that they mislabeled the product.
    80. Re:Seems Silly to me by BillyBlaze · · Score: 1

      [citation needed]

    81. Re:Seems Silly to me by BillyBlaze · · Score: 1

      You seem to be stuck in an overly compartmentalized universe, where this one area of technology has every right to redefine a term that every other field of human endeavor defines differently. As pointed out above, grams, meters, seconds, and every other quantity with something resembling widespread use define it in the same way, as a power of 10. The term has been defined the same way everywhere else, therefore, it's stupid to redefine it for the purposes of convenience.

    82. Re:Seems Silly to me by BillyBlaze · · Score: 1

      Um, to one decimal place, 1048576 bytes = 1.0 MiB = 1.0(48576) MB.

    83. Re:Seems Silly to me by Gat0r30y · · Score: 1

      This is indeed an interesting ruling.
      I don't think seagate is going to see any measurable fallout from this as i don't see many people backing up everything on their hard drive, pulling it out, sending it in for a refund, waiting for a check, then going out to buy a replacement labled 1 GiB instead of 1GB.
      Perhaps its indicative of our society when you can litigate something like (2^3) * 10 ^9 (8000000000 bits) != (2^3)(2^30) (8589934592 bits).
      Hey, maybe they'll just start putting the specs in engineering notation. There could be little room for litigation there.

      --
      Prediction: The real iPhone killer is going to be sex robots from Japan. Think about it.
    84. Re:Seems Silly to me by BronsCon · · Score: 1

      For technical reasons, RAM is sized in powers of 2. One byte is equal to eight bits. Two bits, four bits, eight bits, that's 2^3 bits to make one byte.

      While you could, in theory, have 1000 bits in a kilobit, that would give you 125 bytes. 125 is not a power of 2, while 128 is, leaving 128 bytes as 1024 bits, which is why that is a kilobyte. It is not an approximation, it is a technical requirement. It is also the standard when dealing with binary computers because it is the one thing which can not change.

      It stands to reason that, for no other reason that simplicity, this standard would be followed universally when dealing with binary computers. Why should I have to convert from KB-of-RAM for KB-of-disk when determining whether the contents of RAM will fit on a disk? If i have 1GB of RAM and 1GB of disk and wish to write out those contents, bit-for-bit, I should know immediately that it will fit.

      As for your question about the network connection; no, I would not expect to be able to transfer one gigabyte over a one-gigabit-per-second connection in one second. Not only has networking gone down the same path as disk storage, meaning that what should be 1,073,741,824 bits-per-second is only approximately 93% of that (1,000,000,000 bits-per-second); add to that the fact that a gigabyte is eight gigabits and I would expect it to take roughly eight point six seconds. Of course, this assumes perfect line conditions, completely compatible hardware and no protocol overhead. Realistically, it would take closer to fifteen seconds.

      How do YOU like pedantry, friend?

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    85. Re:Seems Silly to me by absoluteflatness · · Score: 1

      Except for the drive manufacturers, it's actually just changing the packaging.

      You can make some strange argument that changing how sizes are reported is somehow changing the "packaging" of the OS, but that would pretty much be wrong. So it actually doesn't work both ways.

    86. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      I'm buying it to store pr0n. Base 2 could never satisfy me. I'd like to get to the third base at least. Otherwise, the money I spent on the candle light dinner is a complete waste.

    87. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Who uses more than 3 decimals in colloquial language? You might not believe it but almost everyone will think of 1 GB as about 1,000,000,000 byte and not bother about the exact value at all. It only matters in code, technical specifications, business deals. You know that's exactly why people started using 'K' and later 'KB' instead of saying 1024 bytes because most of the time rounded values or figures within the same magnitude are sufficient. There's an obvious difference though between using this valid approximation and literally claiming that 1 GB equals 1024 bytes.

    88. Re:Seems Silly to me by Anonymous Coward · · Score: 0

      Pardon? What competition? All vendors (IBM, Hitachi, Samsung, Western Digital, Maxtor etc.) use SI prefixes to specify hard disk capacity (1 MB = 1,000,000) and always have. How the heck could your comment get modded "insightful"?

    89. Re:Seems Silly to me by Rich0 · · Score: 1

      I appreciate that there are SI units, but they are not in common use apart from total SI/standards nerds, and their creation was misguided and based upon a core misunderstanding of the issue.

      Uh, the SI prefixes are used EVERYWHERE, and with the exception of IT it always referrs to a power of 10.

      The only reason that a KB of ram = 1024 bytes is because some computer designer was lazy 50 years ago. In EVERY other industry the SI terms refer to a power of 10.

      The SI didn't misunderstand anything when they suggested using a different prefix for powers-of-2. Their whole point is that having one prefix mean two different things is completely contrary to the whole point of the metric system. And they're right. And the fact that a manufacturer is being sued and everybody is arguing over what "kilo" ought to mean just proves that the SI has a point...

    90. Re:Seems Silly to me by no-karma-no-worries · · Score: 1

      "'edge' over the competition". WTF? Every other harddisk manufacturer specifies 1Gb as 1,000,000,000 bytes.

    91. Re:Seems Silly to me by prockcore · · Score: 1

      I've got news for you, when you use a number like "20 megabytes" you're using the decimal system.

      Now, if, from now on, you're going to say "10100b megabytes" you can use the binary prefixes.

    92. Re:Seems Silly to me by bestinshow · · Score: 1

      I meant in reference to the computer industry, and you knew that, but as an SI nerd you had to argue about it and alter my argument to make a point.

      In the computer industry, the SI binary prefixes aren't well known, and the misuse of the existing decimal SI prefixes is the defacto standard.

      However the end point should be that the expected number is on the hard drive, whether or not the characters after it are "GB" or "GiB". Power-of-10 capacities should not be given.

    93. Re:Seems Silly to me by Rich0 · · Score: 1

      I meant in reference to the computer industry, and you knew that, but as an SI nerd you had to argue about it and alter my argument to make a point.

      Uh, I'd hardly call myself an SI-nerd. I would call myself a chemist. Surprisingly enough, chemists tend to use SI units. Then again, so does just about every profession outside of the US, and quite a few inside the US. A noteworthy exception would be some people in the IT industry. But apparently not all - otherwise we wouldn't have various groups using the same abbreviation for two different things.

      I'll be the first to admit that Seagate benefits from using the SI abbreviations, but that hardly makes them wrong.

      However the end point should be that the expected number is on the hard drive, whether or not the characters after it are "GB" or "GiB". Power-of-10 capacities should not be given.

      I want to know what my hard drive capacity is. For some strange reason I was born with ten appendages sticking out of my hands, oddly enough I prefer to use power-of-10 arithmetic. If I need to know how that translates into base-2, LBA, or whatever, I'll ask a computer (one of the many reasons I own one). Sure, I know how to do the conversion by hand as well, but while I might know how to add it doesn't stop me from using a calculator.

      So, I'll take my hard drive capacities in GB please (and not GiB). Ditto for RAM, filesizes, and whatever else I need to know. And go ahead and round it all off - I really don't care if I have 107 GB or 107.374GB - 107GB is just fine. The inode table will probably waste more space than I'm not accounting for...

  7. Yet Again, the Courts Drop the Ball by Revotron · · Score: 0

    Anyone with a few functioning brain cells would look at Wikipedia to see what, exactly, a gigabyte is! A gigabyte is a SI unit- literally, 1,000,000,000 bytes. What the layman thinks is a gigabyte (1024MB) is a gibibyte, a giga-binary-byte.

    Seagate was being completely honest in their branding of the package. It's the operating system, still referring to a gibibyte as a gigabyte, that is "defrauding" users of that non-existent 7% that they seem to want so badly. Hell, the IEC even recommended about 8 years ago that everybody make that distinction between gibibytes and gigabytes, and refer to them properly to avoid the exact same confusion that brought this lawsuit about.

    1. Re:Yet Again, the Courts Drop the Ball by emurphy42 · · Score: 2, Funny

      The problem is that you can't say "gibibyte" without sounding like a fucking tool. :)

    2. Re:Yet Again, the Courts Drop the Ball by Rachel+Lucid · · Score: 1

      Would pronouncing it 'give-a-byte' help?

    3. Re:Yet Again, the Courts Drop the Ball by SaidinUnleashed · · Score: 5, Insightful

      Yes, but no one uses the *bi- prefixes, because they sound stupid, and make one sound stupid for trying to use them. The word "gigabyte" has meant 1,073,741,824 bytes in common usage for over thirty years. So, to steal an apparantly legitimate proof of factuality, the consensus among IT professionals is that a gigabyte is 1,073,741,824 bytes. If consensus among professionals in a field can make something a fact in any one field, it can make it a fact in every field.

      --
      Shiny. Let's be bad guys.
    4. Re:Yet Again, the Courts Drop the Ball by emurphy42 · · Score: 1

      Probably not. Sounds too much like a plastic tray you'd see next to the cash register at Fry's - "give a byte, take a byte"...

    5. Re:Yet Again, the Courts Drop the Ball by bmo · · Score: 1

      "Would pronouncing it 'give-a-byte' help?"

      SEDAGIVE!?!?

      http://www.geocities.com/Hollywood/Set/4159/sedagive.wav

      --
      BMO

    6. Re:Yet Again, the Courts Drop the Ball by zippthorne · · Score: 1

      Yeah, And we should keep it that way because 1,073,741,824 is a much easier number to remember than 1,000,000,000.

      I wanna know how many of the "giga=gibi, damnit" people are out there that are also metric superiorists.

      I understand that the ibi- prefixes are there to shoehorn a convenient convention. I also know that that convention was convenient when the error between binary k- and SI k- was only ~2%, but it was never as convenient a notation as people have creditied it.

      It hasn't saved any actual space in describing drive size, the only benefit is that it may have made a human-readable-izing converter marginally simpler back when everything was at a premium.

      It's just a little crazy to keep insisting on the 1000 ~ 1024 approximation anymore. It's a lot like using 20 as an e^pi - pi. It shouldn't have *ever* been used for anything more precise than comparing orders of magnitude.

      --
      Can you be Even More Awesome?!
    7. Re:Yet Again, the Courts Drop the Ball by Tuoqui · · Score: 1

      How many times has Wikipedia article been edited by the Hard Drive Industry though?

      --
      09F911029D74E35BD84156C5635688C0
      +2 Troll is Slashdot's way of saying groupthink is confused
    8. Re:Yet Again, the Courts Drop the Ball by IkeTo · · Score: 1

      Perhaps it's good that the courts "drop the ball"... imagine what Seagate can do now. Mark their drives as 200GB when everybody else mark it as 215GB? Makes no business sense--they will simply lose orders. Make special production lines for the US that mark it as 200GB while every other production line marks it as 200GB? Makes no operational sense--even their own staff will mix up the two. Easiest solution? Well... just stick a tiny "i" (perhaps at a smaller font) at the middle between G and B! At least they can tell their curious customers that "it is mandated by the court, you'll get just the same no worry". Other vendors will follow suit shortly for fear of litigation, there's nothing to lose anyway. People will soon find it not so awkward to utter the sound "gibibyte", and after that there is some reason for the OS to change their ways, too. And our decades long mess of units will finally be past issues. Or perhaps that's just my own wishful thinking.

    9. Re:Yet Again, the Courts Drop the Ball by Mycroft_VIII · · Score: 1

      I think you've scrambled a term, a layman is someone NOT in the field, that is not a someone who works with computers and used to standard 1024 bytes to one kilobyte, 1024 kilobytes to a megabyte, etc. The layman is the one who might mistakenly think the computer field was using the base ten meanings found elsewhere.
          Perhaps if another prefix set had been devised/picked back when digital computing was brand spanking new things would have been less confusing but, 50 years later the the whole *bi prefix thing just makes one sound like an esperanto enthusiast or other loony.
          The point of the suit however is that since most other forms of data storage are expressed in the conventional meaning, and until recently hard drives as well, the switch in meaning with BIG disclaimers is clearly a ruse to inflate the perceived size.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    10. Re:Yet Again, the Courts Drop the Ball by mungtor · · Score: 1

      And it was consensus in Kansas that Pi = 3. A lot of people that habitually mis-use a term shouldn't be allowed to redefine what the term means. It just means that a lot of people are wrong.

    11. Re:Yet Again, the Courts Drop the Ball by SaidinUnleashed · · Score: 1

      You do realize that pi to one significant digit /is/ 3, right?

      --
      Shiny. Let's be bad guys.
    12. Re:Yet Again, the Courts Drop the Ball by Just+Some+Guy · · Score: 1

      The problem is that you can't say "gibibyte" without sounding like a fucking tool. :)

      Amen! Did they get a committee together to come up with the absolutely stupidest sounding name possible? It almost seems like deliberate sabotage. If they'd given us something like "ninjabytes" or "megapirates", then "kilobytes" would be about as cool and current as "cyber" and not even the most dogged Slashdotter would be defending it.

      Gibibyte. Wow.

      --
      Dewey, what part of this looks like authorities should be involved?
    13. Re:Yet Again, the Courts Drop the Ball by Anonymous Coward · · Score: 0

      It's only a fact in one field. Nobody else cares.

    14. Re:Yet Again, the Courts Drop the Ball by aegl · · Score: 1
      The word "gigabyte" has meant 1,073,741,824 bytes in common usage for over thirty years.

      Over thirty years ago the word "gigabyte" was mostly just of theoretical interest. Almost nobody (apart from governments and major corporations) could afford even one gigabyte. I'd guess that gigabyte didn't hit common usage (outside of computer data center professionals) until the mid to late nineties.

      So the question for the court is really did the marketting types at disk drive manufacturers switch definitions on an unsuspecting public, or have they been using gigabyte = 10^9 bytes for as long as the general public have had any interest in gigabytes?

      The track record for marketting in the computer industry isn't good. "19 inch" CRT monitors (with only 17 inches of actual screen). "Full speed USB 2.0 devices" (where "full speed" means just 11 mb/s ... not the highest speed that USB 2.0 is capable of). Etc.

  8. Mark the return of 2^x sized drives? by hakr89 · · Score: 1

    Does this settlement mean that Seagate might actually start sizing their drives correctly?

  9. Cash or Backup? by calebt3 · · Score: 0, Flamebait

    Cash. You can buy backup software and a smaller HDD with it. If you are too dumb to use the OS's built-in backup feature.

    1. Re:Cash or Backup? by flyingsquid · · Score: 5, Funny

      Yes, cash seems like a good option, but the problem is that Seagate defines the dollar as having 93 cents.

    2. Re:Cash or Backup? by Satertek · · Score: 1

      It's only 5% though. Even if I didn't disagree with the ruling, I'd only get around $7 for the drive for which I paid $140.

      This isn't gonna make a dent in Seagate, fortunately. You have to mail in your claim to get cash, and giving away the recovery software costs them essentially nothing.

    3. Re:Cash or Backup? by cicatrix1 · · Score: 1

      Uh no. Seagate's branding is spot on. You're the one with the mis-conception. You must value the dollar at $1.07.

      --

      I know more than you drink.
    4. Re:Cash or Backup? by Anonymous Coward · · Score: 0

      So does Canada (BA-DUM-TISH).

    5. Re:Cash or Backup? by Anonymous Coward · · Score: 0

      1 USD = 1.05778 CAD, as of 11.02.2007 It's refreshing to buy such great cheap porn from the States to fill my Seagate (also bought in Amerika)!

    6. Re:Cash or Backup? by Anonymous Coward · · Score: 0

      93 cents is what US dollars worth against Canadian Dollar

    7. Re:Cash or Backup? by Anonymous Coward · · Score: 0

      Seagate uses Canadian dollars?

    8. Re:Cash or Backup? by dirwin · · Score: 1

      They're giving change for United States purchases in Canadian dollars now?

  10. WTF?? by Techogeek · · Score: 1

    Hard drive manufacturers have always used the ISO specification for defining the capacity of hard drives. This is nothing new.

    1. Re:WTF?? by Lally+Singh · · Score: 1
      Seriously. The Wikipedia definition:

      A gigabyte or Gbyte (derived from the SI prefix giga-) is a unit of information or computer storage meaning either 1000 bytes or 1024 bytes (1000 = one billion). The usage of the word "gigabyte" is ambiguous, depending on the context. When referring to RAM sizes and file sizes, it traditionally has a binary definition, of 1024 bytes. For every other use, it means exactly 1000 bytes. In order to address this confusion, currently all relevant standards bodies promote the use of the term "gibibyte" for the binary definition.
      While I can see how consumers would be pissed, it's the fact that the software misreports the capacity as 2^30, instead of 10^9. As someone who wants to work in this industry, this sends me some chills — It's not about being right, it's about being right to a bunch of lawyers who don't apparently recognize standards organizations like ISO.
      --
      Care about electronic freedom? Consider donating to the EFF!
    2. Re:WTF?? by npistentis · · Score: 1

      I got an email from Seagate last week informing me that I was eligible to receive the refund, and happily went in and checked the "Decline Claim" box. I've explained the discrepancy to 100 different users over the years ("I ordered an 80GB drive and my computer says I only have xx GB of available space?!"), so it would've been hypocritical for me to accept money from a company that I like, offered because a few lawyers saw an opportunity to gouge the company over a technicality.

      --
      Gentlemen, you can't fight in here! This is the War Room!
    3. Re:WTF?? by Techogeek · · Score: 1

      Binary vs Metric .. USA vs THE WORLD!! MUAHAHAHAHAA

    4. Re:WTF?? by I'm+Don+Giovanni · · Score: 4, Insightful

      " When referring to RAM sizes and file sizes, it traditionally has a binary definition, of 1024 bytes. For every other use, it means exactly 1000 bytes. In order to address this confusion, currently all relevant standards bodies promote the use of the term "gibibyte" for the binary definition."

      Seems to me that since hard drives' primary function is storing files, that hard drive capacity should use the same unit of measurment that file size does, no? Doesn't that make simple sense? So if file sizes use 1024 rather than 1000, then hard drive capacity should as well.

      --
      -- "I never gave these stories much credence." - HAL 9000
    5. Re:WTF?? by Choad+Namath · · Score: 1

      Something should have been done at the beginning, but I would hardly blame software developers for the discrepancy. Logically, it makes sense to define capacity using binary numbers. I don't know the history of when the split took place between the different conventions, but it seems pretty convenient for hard drive manufacturers to be able to make their product seem bigger and cite ISO standards as the reason for doing so. It wasn't a bad decision to define files in terms of base two, it was a bad decision to use the standard prefixes kilo-, mega-, and giga- to refer to them.

    6. Re:WTF?? by 10101001+10101001 · · Score: 1

      Hard drive manufacturers have always used the ISO specification for defining the capacity of hard drives.

      Oh, really? Care to point me to the ISO specification that clarifies that there are 8 bits in a byte?

      --
      Eurohacker European paranoia, gun rights, and h
    7. Re:WTF?? by Dachannien · · Score: 1

      Note that those Wikipedia articles are currently in the midst of some minor edit warring. Also, "all relevant standards bodies" refers solely to the IEC.

    8. Re:WTF?? by HybridJeff · · Score: 1

      I wouldn't call it gouging them over a technicality, rather I would call it attempting to discourage a deliberately deceptive marketing tactic. As you said, you've had to explain the difference to many people over the years so you should know that there are a lot of people fooled by this. That said, it would be slightly hypocritical for you to take the money having known about the difference before hand, so kudos for taking the high ground.

    9. Re:WTF?? by drsmithy · · Score: 1

      Hard drive manufacturers have always used the ISO specification for defining the capacity of hard drives.

      No, they haven't. Their nomenclature changed around the late 80s/early 90s, roughly the same time as monitor manufacturers started marketing their screens based on the size of the tube, rather than the visible area, to make them look bigger.

    10. Re:WTF?? by Anonymous Coward · · Score: 0

      You are funny. Now, show us the ISO specification that clarifies that there are 8 bits in a byte, like he asked you. ISO 31 isn't it, as is clearly pointed out by the article you linked to.

    11. Re:WTF?? by Animedude · · Score: 1

      Yes, exactly. If Joe User right-clicks on a large file in Windows and looks at the file size, Windows tells him e.g. "19.9 GB (21.367.462.297 bytes)", so Windows clearly does NOT use the SI units. So a standard user would rightfully be confused if he could not fit five of those files on his 100GB hard disk, after all there should be 0.5 GB free afterwards, or?

      The real problem definitely is that the definitions like K=1024 are so well-known that is is next to impossible to totally overthrow their use. This is not the usual problem of using different units instead of old ones (e.g. cm instead of inch), it is about using the same names for different things. And it does not help that one hardware component (hard disk) uses the new definition, while another component (RAM) uses due to technical reasons the old definition (anybody up for buying a new computer with approximately 4.295 GB of RAM?). It would have been far easier to use the weird GiB etc. as the SI units and leave the old definitons as they are.

    12. Re:WTF?? by prockcore · · Score: 1

      Logically, it makes sense to define capacity using binary numbers


      Why? It makes sense to define capacity using hexadecimal. If you're going to use base10 numbers you should use base10 prefixes.
    13. Re:WTF?? by prockcore · · Score: 1

      In 1973 IBM released the ibm 3340 harddrive. It was known as the "Winchester" or "30-30"... because each platter held 30 megabytes.

      Each platter holds 30 million characters. Not 31457280 bytes.

    14. Re:WTF?? by Mycroft_VIII · · Score: 1

      Not true, I remember being a bit peeved the first time I bought a hard drive and found out it wasn't the size it claimed because they'd switched to base ten usage for the prefix instead of base two.
          I already had one hard drive that size and the second one I bought from a different company was smaller with the exact same formatting. It took a fair amount of digging to find out why.
          I still remember some of the first hd's I bought in the low GB range even said 1MB=1000KB (yet their KB was 1024 bytes!).

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    15. Re:WTF?? by Choad+Namath · · Score: 1

      Why?
      You do know how modern computers work, no?

      It makes sense to define capacity using hexadecimal.
      Hexadecimal is just used as a convenient way to display binary numbers.

      If you're going to use base10 numbers you should use base10 prefixes.
      Agreed, but I don't think they should have started using base 10 to describe capacity in the first place. Computers operate in binary, so it makes sense to use it to define the size of files or disks they use. The only reason for describing a hard drive's capacity in base 10 is marketing.
    16. Re:WTF?? by msslc3 · · Score: 1
      I paid $80 for a Seagate drive, so the refund would be $4. I have slight qualms about taking the money, so I will opt for the software and not file a claim on the second Seagate drive I bought. This is called moral ambiguity.

      Does anyone use this software and know if it is any good?

    17. Re:WTF?? by joeljkp · · Score: 1

      Chicken and egg. Nobody's making Windows define a file as 1MB = 1024KB. To make things consistent, it's either Windows that must change or the HDD industry (and the DVD+-R industry).

      --
      WeRelate.org - wiki-based genealogy
  11. RTFM by Revotron · · Score: 2, Informative

    Do your research - your point is pretty much ass-backwards. The manufacturers are quoting their sizes in gigabytes, which are SI units defined as 10^9 bytes. A gibibyte is the familiar 2^30, 1024MB unit that we all associate as being a gigabyte.

    1. Re:RTFM by Anonymous Coward · · Score: 0, Interesting

      Not in computers. There is no bullshit gibbibyte in computers. Thats some stupid sounding name. Byte is a computer term not found in other technical areas, and its a word of binary bits (and the word size is 8 bits, because we use 8 bit ascii to store our data. Note that this has nothing to do with bus width, or CPU instruction size which may be (now commonly) 32 or 64 bits. Data (the letters you type, and the pictures you drool over late at night) are in 8 bit ascii. Computers are base 2 beasts. They just are, so suck it up. A gigameter has a different base than a gigabyte. SI is base 10. Computers are base 2. Because you used a computer suffix, its base 2 (and all your ranting isn't going to change that). Gigabytes in computers are 1024 * 1024 * 1024 bytes. They just are. Deal with it. There is no discussion. You can take your stupid made up gibbibyte trash and shove it up your bit bucket.

    2. Re:RTFM by Revotron · · Score: 0

      Made up? If you think it's trash, take it up with ISO. Your quarrel is with SI, not me. Go read a Wikipedia article on SI and gigabytes and maybe you'll get some sense knocked into you, Coward.

    3. Re:RTFM by Ledsock · · Score: 2, Informative

      Do your research - your point is pretty much ass-backwards. The manufacturers are quoting their sizes in gigabytes, which are SI units defined as 10^9 bytes. A gibibyte is the familiar 2^30, 1024MB unit that we all associate as being a gigabyte. Actually, 1 GiB=1024 MiB. That's the whole issue of this case. MB!=MiB, as with kB and KiB, and GB and GiB. The difference between a GB and a GiB is roughly 6.87%, yet when you hit the TB/TiB level, the difference is roughly 9.05%. The greater the prefix, the more the inconsistency between the two units of measurement. I view this case as preventative action for the soon coming terabyte and tebibyte hard drives. As sizes grow, so do our losses (although, technically, they are advertising correctly, and the OS makers are using improper notation).
      --
      What is mankind really? Well, it's just two words put together Mank, and ind.
    4. Re:RTFM by Mycroft_VIII · · Score: 4, Insightful

      While he was a bit harsh, the 'gibi' 'mibi' 'mabi' and what not are NOT accepted units of measure irregardless of what any organization (even a 'standards' organization)says.
          The key word word is accepted.
      Computers work in base 2 natively and when the field was first started and the closest prefixes for base 2 'round' numbers in that base were adopted by the vast majority.
            Now this was and is a bit of a kludge, but it's was nearly universal in use (and still dominant) and anyone who was serious about learning computers learned this fairly early on.
          This same numbering scheme continued well into the era of commodity parts including retail hard drives until some nitwit realized they could make more money by selling according to the base 10 numbering system definitions which are smaller.
            The real truth here is that what the hdd makers did was attempt to deliberately create a false impression of size by relying on the fact the for computers mega meant 2^20 and yet changing what they meant by it (after years of using the de-facto standard).

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    5. Re:RTFM by Kickasso · · Score: 1, Insightful

      "irregardless" is not standard either.

    6. Re:RTFM by Anonymous Coward · · Score: 0

      Computers work in base 2 natively and when the field was first started and the closest prefixes for base 2 'round' numbers in that base were adopted by the vast majority. There is no concrete technical justification for the 1024 = k thing, it's a simple case of someone deciding that it was "near enough" to 1000 to use the k suffix, and it caught on from there.
      It's an entirely colloquial, informal "standard" with no technical merit whatsoever.
      The k suffix means thousand. Kilo means thousand. It should have been obvious from the moment someone tried to make mega = 1024x1024 that it was time to get back to the real world, but sadly that didn't happen until so long that idiots like you think there's some technical merit in 1k = 1024

      I find it bizarre that a community that should be concerned about accuracy and respecting international scientific standards can be so mule headed about the 1024 thing.
      So kibi sounds silly, so does "byte" too if you really want to be picky.
    7. Re:RTFM by mrjb · · Score: 1

      While he was a bit harsh, the 'gibi' 'mibi' 'mabi' and what not are NOT accepted units of measure irregardless of what any organization (even a 'standards' organization)says.

      Correct, and gibi/mibi/mabi sounds ridiculous at that. I can't stand to pronounce them. BUT the international metric system uses kilo for 1000, mega for 10^6, giga for 10^9 and so on. So it makes sense that there is confusion about it, especially as most people have grown up with SI units.

      As much as I hate the terms GiBi, MeBi and *shudder* TeBi, when referring to sizes in bytes, I find it useful to explicitly mark the distinction- A regular DVD has a capacity of 4.7GB while my hard drive has a capacity of 200 GiB. Just adding the little 'i' in between helps to make it clear that in the latter case, I'm not referring to SI units but to powers of 2.

      --
      Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
    8. Re:RTFM by ichthyoboy · · Score: 0, Offtopic

      Kind of like how irregardless is not an acceptable word by most major dictionaries?

    9. Re:RTFM by Mycroft_VIII · · Score: 1

      That wasn't meant as a technical justification for the usage, the whole thing was a bit of an unfortunate kludge as I said.
            Though some sort of systematic notation that recognizes the base two nature of modern computing certainly makes sense.
            As to what sounds silly, that's largely a matter of opinion. Though the majority grew up with the byte usage from early on in the computer field (though, early digital computers had all sorts of weird word sizes) and are comfortable with it whereas the *bi prefixes are much newer.
            You confuse people a lot less by sticking to a standard that's fairly well known and has been in use 40+ years (even if it conflicts with use age OUTSIDE the field) than by trying to switch to some new standard prefixes that so far has mostly gotten ridiculed at by the smaller percentage(though growing, I saw something at a store the other day so marked) of people that have heard of it in the last 9 years.
            I'm not saying it was the right way to do it back then, but there is no compelling reason to change now.
            The system is internally consistent unlike the pounds, quarts, inches system and has Bytes or bits as it's suffix so when to use 2^x0 vs 10^3x is clear.
            The real issue is that the H.D. makers switched from what had been the standard usage as a marketing ploy to deceive the buyer. It was certainly not an attempt to 'correct' the usage, else they would have used the new units and possibly an * note to explain or at least a disclaimer NOT in micro-print on the bottom of the box.
          OS's and most software still use the MB=2^30 notation. If the HD is sold by 10^9 notation the difference becomes glaring.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    10. Re:RTFM by Hal_Porter · · Score: 1

      Your quarrel is with SI, not me. Go read a Wikipedia article on SI and gigabytes and maybe you'll get some sense knocked into you, Coward. This post is why I love discussions on the Internet. Can I use that as my .sig?
      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    11. Re:RTFM by Mycroft_VIII · · Score: 1
      From your link:

      Usage Note: Irregardless is a word that many mistakenly believe to be correct usage in formal style, when in fact it is used chiefly in nonstandard speech or casual writing .


      Emphasis mine.

      Mycroft
      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    12. Re:RTFM by Anonymous Coward · · Score: 0

      This same numbering scheme continued well into the era of commodity parts including retail hard drives until some nitwit realized they could make more money by selling according to the base 10 numbering system definitions which are smaller.

      Really? Every hard drive I've ever bought (going back to 1987) has used the decimal prefixes for its capacity. The only storage device I've ever had that used the binary system was a 100K floppy drive from 1982, that actually did have a capacity of 102,400 bytes.

      I agree that the naming system is confusing, but it seems to have been around a very long time.

    13. Re:RTFM by Anonymous Coward · · Score: 0

      It is a retarded made up word, irregardless of where it is used.
      -AC

    14. Re:RTFM by Anonymous Coward · · Score: 0

      Would you enlighten me what "mibi", "mabi" and "irregardless" mean? And what magical formula do you recommend to determine whether "MB" means 1000000, 1024000 or 1048576 bytes? It is a terrible kludge, and it never worked. It doesn't qualify as a "de facto standard" because it has never been consistent.

    15. Re:RTFM by Mattintosh · · Score: 2, Insightful

      What's hilarious here is that most, if not all, of the supporters of SI+RetardedBi prefixes are pointing to what the US Government says about the "standard". Things to think about here include (but are not limited to):

      1) The US Government is in the pocket of any company willing to pay up, including HDD manufacturers that ponied up a bit-o'-cash to get this "standardized".
      2) This is made more hilarious by the fact that the US Government and its citizenry don't use SI units at all. Oh, except for 2-liter soda bottles, which are, surprisingly, about 2 fl. oz. more than a 2-quart bottle would be.

      Here's my suggestion: When talking about non-byte-based values (liters, grams, rods, hogsheads, LoC's, AU's, VW Beetles, etc.), understand the prefixes to be multiples of 1000. When talking about byte-based values (bits, bytes, words, nibbles, long words, etc.), understand that the context means multiples of 1024. The human brain is a wonderful thing, and languages are too. Both are very complex and context-sensitive. Use your brain to understand context. It's not that hard.

    16. Re:RTFM by Toad-san · · Score: 1

      "The real truth here is that what the hdd makers did was attempt to deliberately create a false impression of size by relying on the fact the for computers mega meant 2^20 and yet changing what they meant by it (after years of using the de-facto standard)."

      Exactly. Of course the requirements for refund are so stringent that damn-all people are going to submit claims. Seagate will get away with a slap on the wrist (financially), and I'm sure they can live with being called g*dd*mned liars (since only lawyers will be talking to the public, and lying is their profession).

      I've submitted my half dozen claims for some old Seagates lying about. We'll see. Meanwhile the 4 brand new 80GB Seagates we just bought yesterday .. are NOT within the period permitted, we can NOT claim money or software, yet they still say "80GB", and Seagate continues to lie.

      Pity. But there never was any money in honor.

    17. Re:RTFM by fatphil · · Score: 1

      How can you say that a hard disk with 3 platters or 820 cylinders is "in base 2 natively"?

      What is so natively "binary" about 3 and 820 that isn't equally-natively decimal?

      Are you also unfamiliar with the fact that in the comms industry, which is arguably the most universal computer technology out there, that powers of 10 are used as the multiplier, and not powers of 2. Those modems were never measuring kibibytes, they were always measuring kilobytes. ISDN B channels are 64000 bps, not 65536 bps, for example.

      --
      Also FatPhil on SoylentNews, id 863
    18. Re:RTFM by 2short · · Score: 1

      The link provides that advice so you'll know what people mean when they use incorrect, made up words. It is still desirable to understand people when they misspell or misspeak. The link is pointing out that people tend to use "irregardless" because it sounds like a fancy, more formal version of "regardless", which it is actually not. So they think it makes them seem more intelligent, while actually the opposite is true.

      In all honesty, your discussion of the issue at hand (HD sizes) is perhaps the most reasoned and well informed here. But regardless of that, when you use that word in almost every post it's a struggle to not think you're an idiot.

    19. Re:RTFM by soapthgr8 · · Score: 1

      The modem speeds refer to bits per second (bps), which are single units, not bytes (Bps), which are 2^3 bits. 64Kbps is 64,000 bits per second (8,000 bytes per second). 64KBps = 64 KB per second = 64 * 1024 bytes per second = 64 * 1024 * 8 bits per second = 524,288 bits per second. Bits and Bytes cannot be directly compared since they are different units.

    20. Re:RTFM by edwdig · · Score: 1

      How can you say that a hard disk with 3 platters or 820 cylinders is "in base 2 natively"?

      Those 820 cylinders are made up of 512 byte sectors, which are the addressable units of the disk.

    21. Re:RTFM by zokum · · Score: 1

      No, when we're talking about bytes sensible people use k = 1000, m = 10^6 etc, just liek we do for everything else. Take the following example:

      You're downloading over your 100mbit internet connection (100 * 10^6 bits per second) at 8000kilobit per second, that would be 1000 kilobyte per second. Naturally that means you're writing 1000 kilobytes of data to you harddisk per second as well. And to all the anal people out there, we're overlooking cache issues, protocol overhead, retransmissions, and so on. We're looking at what speed we see in our downloading program.

      The fact is that storage is more or less the only area in computing where this error occurs. It happened due to the fact that in the young days of computing, the difference between 1000 and 1024 was negligeble, so they borrowed the SI-prefix. HDDs have always been quotes using true SI-prefixes, since it puts the manufacturer in a more favourable light. For some reason, it isn't done with most scsi disks though.

      I'm so glad i don't live in the US, in Norway such a matter would never have burdened the justice system. We can instead use the money on more important things like social services, education and sceence. Let's hope you guys over there catch up to us soon..... ;-)

      --
      Rest in peace Malin "looxn" Kristiansen. We miss you...
    22. Re:RTFM by ttfkam · · Score: 1

      Yes, we computer folks have been using prefixes like kilo to mean 1024 unlike *every other field of study in existence*, because we find it too difficult to start using KiB instead of KB. I mean, c'mon! It's a whole other letter! It's not fair!!!

      Please.

      I see folks on Slashdot constantly stating that X is more correct than Y, but when they are forced to look outside their own little corner of academia and business, this group collectively says, "La la la! I can't hear you! Kilo = 1024 uber alles!"

      Every. Other. Field. Of. Study.

      Congratulations! You've now collectively abdicated any moral right to tell anyone else they're being unreasonable. By the way, the word is "regardless," not "irregardless." A dictionary will commonly list that word as nonstandard, and since I studied English Lit in college and it's an English word, we in the English Lit community get to set the rules.

      So which is it? Will you stop using the illogical word "irregardless" or will you start using kibibytes? If you don't change either of those, you will clearly be just a lazy hypocrite.

      --

      - I don't need to go outside, my CRT tan'll do me just fine.
    23. Re:RTFM by Anonymous Coward · · Score: 0

      No, no, no, and fuck you. Seriously. This has to stop.

      As the GP stated, in data communications a thousand is a thousand, a million is a million, and a billion is a billion, all regardless of whether or not one is speaking of a thousand bits or a thousand bytes.

      If you're wondering why I could get so heated up about this subject: I very nearly horribly failed my first data communications course in college (with first class marks in all other courses), and surely would have if not for my professor and I discussing the "issues" I was having with the assignments and finally noticing a pattern emerging in how my answers were usually wrong but always proportionately close to being right. I was using the base 2 colloquialisms. They were (and continue to be) wrong. I'll say it again: in data communications, the base 2 colloquialisms are WRONG.

    24. Re:RTFM by BillyBlaze · · Score: 1

      Nobody's saying mebi- is in general use, but that it ought to be. The SI- prefixes were here first. Just because the computer industry initially misused them doesn't mean that use is correct.

    25. Re:RTFM by paeanblack · · Score: 1

      The link provides that advice so you'll know what people mean when they use incorrect, made up words.

      Words like Mebibytes and Tebibytes?

    26. Re:RTFM by PMBjornerud · · Score: 1

      Computers work in base 2 natively and when the field was first started and the closest prefixes for base 2 'round' numbers in that base were adopted by the vast majority. By who do we STILL insist on reporting the HD size in base 2 to my mother? Trust me, she DOES NOT WANT IT.
      --
      I lost my sig.
    27. Re:RTFM by joeljkp · · Score: 2, Informative

      While he was a bit harsh, the 'gibi' 'mibi' 'mabi' and what not are NOT accepted units of measure irregardless of what any organization (even a 'standards' organization)says. Binary prefixes are supported by the following professional organizations: IEEE, CIPM, SAE, NIST, CENELEC, and the European Union.

      Source: http://en.wikipedia.org/wiki/Binary_prefix#Adoption

      --
      WeRelate.org - wiki-based genealogy
    28. Re:RTFM by 2short · · Score: 2, Funny


      Those are stupid words made up words too, but were made up by knowledgeable people with good intentions.

    29. Re:RTFM by Blkdeath · · Score: 1

      This same numbering scheme continued well into the era of commodity parts including retail hard drives until some nitwit realized they could make more money by selling according to the base 10 numbering system definitions which are smaller.

      The real truth here is that what the hdd makers did was attempt to deliberately create a false impression of size by relying on the fact the for computers mega meant 2^20 and yet changing what they meant by it (after years of using the de-facto standard).

      Going back a few years ago (well, ok, like more than a dozen or more) when I was considering the purchase of a 40MB hard drive, I realized and understood that said drive was 40,000,000 bytes. When partitioned and formatted, it reported some 38MB available. So it's not like this "problem" is new - it's just on a much larger scale because now the difference between 1,000,000,000,000 and 1*1024*1024*1024*1024 is rather larger than the difference between 40,000,000 and 40*1024*1024 so it's way more noticeable.

      Hint: the general public doesn't feel shorted by the base-10 measurements, they feel generally confused by the computer industry's steadfast reliance on reporting base-2 capacities when they bought a base-10 storage unit. They just don't know how to put it into context so we get confused members of lawsuits fighting for their stolen bytes! (Even though most of them wouldn't know a bit from a byte if one bit them in the arse).

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    30. Re:RTFM by bluephone · · Score: 1

      You are incorrect in numerous areas. First, originally, HDDs were not using SI units, but the 1024 base we're discussing. Second, HDDs are not the only area there this is also used; memory, flash, tape storage, bandwidth and transmission rates of various buses, and networking connections. Lastly, sensiv\ble people have been using 1024 per K for decades. It's only recently that any attempt to change that has occurred.

      --
      jX [ Make everything as simple as possible, but no simpler. - Einstein ]
    31. Re:RTFM by vux984 · · Score: 1

      You're downloading over your 100mbit internet connection (100 * 10^6 bits per second) at 8000kilobit per second,

      So far so good.

      that would be 1000 kilobyte per second.

      Er. No.

      1000 kilobytes per second would be 1,024,000 bytes, and you are only moving 1,000,000 bytes, or 976.5 kilobytes.

      bits are *normally* treated in base 10 and kilo/mega/giga refer to 10^3, 10^6, 10^9. A kilobit is 1000 bits.
      bytes are *normally* treated in base 2 and kilo/mega/giga refer to 2^10, 2^20, 2^30 A kilobyte is 1024 bits.

      Naturally that means you're writing 1000 kilobytes of data to you harddisk per second as well. And to all the anal people out there, we're overlooking cache issues, protocol overhead, retransmissions, and so on. We're looking at what speed we see in our downloading program.

      Hate to break it to you but all the downloading programs I'm familiar with count bytes in base 2.

      The fact is that storage is more or less the only area in computing where this error occurs.

      The 'error' occurs whenever the unit is a byte. Few things other than data storage and occasionally data transmission speeds are measured in bytes. After all byte is a fundamentally a unit of storage. So it not surprising that most areas where it occurs are in storage.

      Bytes are the standard unit in storage: RAM, ROM, PROM, EEPROM, Flash, CD, DVD, DAT, DLT, and even, historically, hard drives, back when they were still measured in megabytes. It wasn't until GB plus drives showed up that drive manufacturers started representing things in base 10.

    32. Re:RTFM by vux984 · · Score: 2, Informative

      Actually, most buses are rated in standard SI units, not base-2, this is because the "M" actually arrives by way of the clock speed rather than the storage size which is (often) bytes.

      For example: consider AGP1x, which is rated at 266MB/s:

      This is arrived at by multiplying: 66MHz clock x 4 byte data path (32 bits) = 266MB/s

      (Note: actually 66 x 4 = 264, we get 266 due to round off error. The clock speed is more like to 66.6MHz than actually 66MHz. And 266MB/s is really just twice as fast as 133MB/s, which is the speed rating of regular PCI.)

      The point however is that the M comes from the *M*Hz, and Hz are measured in base-10. 66.6MHz is 66,600,000 Hz

      66,600,000 cycles per second x 4 bytes per cyle = 266,400,000 or rounded 266MB/s

      That said, I agree with you. Storage measured in bytes is, by defacto standard, measured in base-2, where M=2^20, not 10^3.

    33. Re:RTFM by Reaperducer · · Score: 1

      Use your brain to understand context. It's not that hard.
      While we're talking about context, it's important to understand that the U.S. government isn't the only organization subject to political whims when making measurements.

      Remember that one kilometer isn't some measurement derived from an impartial mathematical measurement of nature -- it's the distance from the North Pole to Paris divided by 1,000. Logic would dictate that it's a measurement to the equator or some other neutral location, but the French have hijacked the measurement of distance for their own purposes. So much for SI being "scientific."
      --
      -- I'm old enough to have lived through six different meanings of the word "hacker."
    34. Re:RTFM by Reaperducer · · Score: 1

      We can instead use the money on more important things like social services, education and sceence. Let's hope you guys over there catch up to us soon..... ;-)
      Maybe you could use some of that whale hunting money to learn some manners and humility. Pride goes before a fall.
      --
      -- I'm old enough to have lived through six different meanings of the word "hacker."
    35. Re:RTFM by Reaperducer · · Score: 1

      IEEE, CIPM, SAE, NIST, CENELEC, and the European Union.
      I'll give you the first five, but the E.U.? Who wants the E.U. making standards? These are the people who get store owners fined for selling bananas in the local weight and came up with a 1,000-page constitution only readable by lawyers while the Americans managed to come up with a one-page constitution readable by anyone. If you're going to support your argument, don't weaken it by leaning on the E freaking U.
      --
      -- I'm old enough to have lived through six different meanings of the word "hacker."
    36. Re:RTFM by Reaperducer · · Score: 1

      It seems the simple solution is to just do the counting in base 820. Great. Just when I was getting hex down.

      --
      -- I'm old enough to have lived through six different meanings of the word "hacker."
    37. Re:RTFM by Anonymous Coward · · Score: 0

      Lastly, sensiv\ble people have been using 1024 per K for decades. It's only recently that any attempt to change that has occurred


      Sensible people recognize an opportunity to achieve greater clarity in a simple optimization, and do not argue in favor of (ambiguous!) backwards compatibility out of sheer inertia.
    38. Re:RTFM by eharvill · · Score: 1

      Computers work in base 2 natively and when the field was first started and the closest prefixes for base 2 'round' numbers in that base were adopted by the vast majority. Now this was and is a bit of a kludge, but it's was nearly universal in use (and still dominant) and anyone who was serious about learning computers learned this fairly early on. Lol, no doubt. Nearly 10 years ago as young up and coming HP-UX Jr Sysadmin I learned the difference the hard way. I had to create 20 or so new filesystems one evening and I made the mistake of creating them on base 10 calculations instead of base 2 (can't remember exact details now). I was terribly upset when I realized I was short a good bit of space and had to redo all the work that had taken me a good 3-4 hours to do in the first place.

      I also learned a good bit about creating loops in ksh that night as well. ;-)
      --
      At night I drink myself to sleep and pretend I don't care that you're not here with me
    39. Re:RTFM by Mattintosh · · Score: 1

      Remember that one kilometer isn't some measurement derived from an impartial mathematical measurement of nature -- it's the distance from the North Pole to Paris divided by 1,000.

      I've often heard different "hard measurements" that the meter (and multiples) were supposedly based on, but this one actually seems accurate. (Whereas "The distance between the north and south pole divided by 1,000,000" did not.)

      It also gives me a real reason why "SI" isn't "IS" (seeing how English has been the "lingua franca" for a while now), and where, exactly, the USA got its hubris (the French were best-buddy allies of the US until 30 years ago or so). Maybe that's why the US gets so pissy about the French. They are the French, but less smelly and fatter.

    40. Re:RTFM by zokum · · Score: 1

      Recently? This has been an ongoing debate for 10 years. Without a real change we will still have these problems. Most of the world, including all fields of science, uses SI-units, and in every other area than computer storage kilo without a doubt means thousand, not 1024. If kilo means 1024 like you claim, you run into absurdities like 1019 being less than 1k.

      --
      Rest in peace Malin "looxn" Kristiansen. We miss you...
    41. Re:RTFM by zokum · · Score: 1

      A lot of download programs use SI-units, at least many of the ones I've looked at does that. To put some spice into this pot, check out the definition of space on floppies. The system just isn't consistent, please convert to k = 1000. The unformatted capacity of a 3½-inch double sided high density floppy disk is advertised as approximately 2 million bytes; in its most common low-level format it has a capacity of 1,474,560 bytes or 1.47 million bytes (1.47 Megabytes). In the Base 2 binary prefix numbering system used by computers, 1,474,560 bytes is exactly 1440 kibibytes (1.4 Mebibytes). However, neither of these numbers is generally used. The number most frequently printed on such floppies is "1.44 MB" which incorrectly combines Base 2 (1440 kibibytes) with Base 10 (1.44 kilo-kibibytes). Thus the label "1.44 MB" is not correct usage of the SI terminology and leads to confusion for users. For example, the term 1.44 MB implies that the floppy holds 1.44*1,000,000 == 1,440,000 bytes of data, which is false. Likewise the term 1.44 MiB (mebibytes) implies the floppy holds 1.44*1024*1024 == 1,509,949 bytes, which is also false. A person using either the binary or the decimal prefix would miscalculate the number of floppies needed for the project. (The only proper way to interpret the erroneous "1.44 MB" label is as 1.44 kilo-kibibytes which yields 1.44*1000*1024 == 1,474,560 bytes.) (copied from wikipedia)

      --
      Rest in peace Malin "looxn" Kristiansen. We miss you...
    42. Re:RTFM by catprog · · Score: 1

      Wrong. 1 meter is equal to the distance traveled by light in vacuum during a time interval of 1/299 792 458 of a second. 1Km is 1000 times that.

      --
      My Transformation Website
      Kindle Books http://www.catprog.org/rev
      Interactive CYOA http://www.catprog.org/st
    43. Re:RTFM by bluephone · · Score: 1

      My "claim" about kilo related only to the IT industry. I'm sure you understood that, however, and merely attempted to make a straw man. I can't oblige you, however.

      --
      jX [ Make everything as simple as possible, but no simpler. - Einstein ]
    44. Re:RTFM by JustPutt2 · · Score: 1

      Well said,,,, and thoughtful..... If any remember when memory was measured in Kilobytes, and disks were measured in a few megabytes,,,,, the differences seemed inconsequential... But as an old and very sage politician, once said,,, A few million here and a few million there,,, and soon it adds up to billions,,,,,,,,, E Dirksen, Sen Ill.

    45. Re:RTFM by Mycroft_VIII · · Score: 1

      I picked up the word the same way most pick up their native language, everyone around me uses it with a certain meaning so I tend to do the same. I actually qualified for honors english (and remedial spelling probably) in college, but that's probably because I'm better at spotting bad english than writing good english, the test played to my strengths a bit.
            The simple truth is that at least around here (middle of the USA, not necessarily Slashdot), it's meaning is clear and use so common I seldom think of it's impropriety in formal, or even semi-formal writing. Fortunately this is not a formal setting or even close.
            It's much like the base 2 versions of the K,M,and B prefixes, technically incorrect to formal definitions, but so common and well understood that little ambiguity as to meaning should arise (other than the '1.44MB' floppy). And yet some poster accused me(I think me) of hypocricy for doing both. huh?
            Try not to judge intelligence or reasoning skills based on idiom in an informal discussion. Especially considering the degree of cultural influence on local language and the impact this has in a discussion medium that reaches such a broad range of locals. Also consider that this includes non-native speakers who are prone to grammatical errors and poor choices with regard contextually appropriate synonyms and near synonyms where specific shadings of meaning may vary in very non-obvious ways.
            Had Einstein wrote his relativity work in crayon it still would have been relativity, and a 411 e-mail scam written by Poe is still a 411 scam.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    46. Re:RTFM by waynelorentz · · Score: 1

      Wrong. 1 meter is equal to the distance traveled by light in vacuum during a time interval of 1/299 792 458 of a second. 1Km is 1000 times that.

      Actually, you're both wrong. But the previous poster is closer to correct than you are. According to Wikipedia:

      The other suggested defining the metre as one ten-millionth of the length of the Earth's meridian along a quadrant, that is the distance from the equator to the north pole. In 1791, the French Academy of Sciences selected the meridional definition.

      In order to establish a universally accepted foundation for the definition of the metre, measurements of this meridian more accurate than those available at that time were imperative. The Bureau des Longitudes commissioned an expedition led by Delambre and Pierre Méchain, lasting from 1792 to 1799, which measured the length of the meridian between Dunkerque and Barcelona. This portion of the meridian, which also passes through Paris, was to serve as the basis for the length of the half meridian, connecting the North Pole with the Equator.


      Do you really believe people were able to measure the distance traveled by light in vacuum for 1/299,792,458th of a second back in the 1700's? And you also fail to explain the significance of the 299,792,458 figure.
    47. Re:RTFM by sasdrtx · · Score: 1

      Show me one example of a disk drive capacity *ever* being advertised in binary-power prefixes. I think you're just wishing they once did it.

      The whole confusion comes from using the prefixes to express powers of two that RAM capacity naturally was sized in. Disk drives have never been restricted to powers-of-two capacities.

      --
      Most people don't even think inside the box.
    48. Re:RTFM by Mycroft_VIII · · Score: 1

      Just one old drive I have laying around (Maxtor 51536U3) was advertised as 15.3 gigs formated capacity. By the numbers listed on it, it's unformatted capacity is around 15.7 gigs base 2 system or 16.9 base ten usage. Now what sounds more likely, that they expected formatting and such to use: .4 gigs or 1.6?
          And that's just grabbing one of the few older drives I have , though that's from after most had started renumbering scam.
          Oddly I have slightly newer HD that appears to be using base 2 up to megabyte then switching to base ten for gigs.
          Anyone old enough to remember having to plug in the cylinders heads sectors data into the bios to use a hard drive will remember when base 2 was the norm.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    49. Re:RTFM by 2short · · Score: 1

      Yes, but you are obviously aware of the correct word, and continue to add two extra letters to the front. You come across as less intelligent to me not because you use the word once, but because you go out of your way to use an incorrect word when you are clearly aware of the correct one.

      It's not that "irregardless" is correct in informal settings. "Regardless" is the correct spelling regardless of the context. The link provided was pointing out that some people are under the incorrect impression that "irregardless" is a more formal version, rather than just a wrong one.

      If Einstein had insisted on working in crayon, his bio would note that Relativity was all the more impressive an accomplishment, given his obvious mental deficiency in other areas.

    50. Re:RTFM by Mycroft_VIII · · Score: 1

      He's had quite a few bios done, most note several 'quirks' in his personality and some suggestion he may have had a mild form of auspergers. A lot of highly intelligent people are known to have odd 'glitches' relative to the societal norms.
          I kind of think one the occasional mistake or preference in an informal discussion hardly qualifies as ANY indicator of intellect. Though judging a person by one trivial item might, but probably not, we ALL have our quirks.

      Mycroft

      --
      https://signup.leagueoflegends.com/?ref=4c3ed6600b6ea
    51. Re:RTFM by 2short · · Score: 1

      "... we ALL have our quirks."

      Well, at least neither of us obsessively tries to get the last word in fundamentally pointless arguments with strangers on the internet. That would be retarded.

    52. Re:RTFM by soapthgr8 · · Score: 1

      I agree, they are wrong. But the computer world is using the colloquialisms wrong on a consistent basis and has been since before we never needed more than 640K (640 * 1024 bytes) of RAM. A better naming system could have been created, but nobody thought that at some point in the future, the off by 24 error would increase by more than 24. Using the base 2 colloquialisms have gone on for so long that anyone attempting to try to change it is just going to get unnecessarily frustrated (except HDD manufacturers which take their frustration to the bank). The overall point is that hard drives used to be measured in base 2, then the marketing types decided to market using base 2 prejudices but base 10 actual measurements. Now somebody has taken them to court for doing what we've all grumbled about over the years.

    53. Re:RTFM by Anonymous Coward · · Score: 0

      "the Americans managed to come up with a one-page constitution readable by anyone."

      Sure, but first anyone reading it needs to be reminded that it doesn't mean what it says, many parts mean something contrary to what they say, and it's selectively invalid at the whim of whoever is charged with upholding it at any given time. Add to that the fact that the US Constitution isn't just the contents therein, but also its amendments, interpretations in courts, legislative modifications that aren't amendments and would be illegal *if* the actual text contents of the document actually meant what they say, and the general de facto modifications present because Americans are too lazy to defend whatever rights they might glean from it, and it easily dwarfs anything any European bureaucracy could come up with.

  12. Much like a RAM settlement offer in the mail by phantomlord · · Score: 3, Insightful

    I recently got a class action settlement in the mail offering money for memory that I overpaid for back in the early 2000s. The catch is, to receive anything, I need to provide detailed information about how much memory I bought from what merchant, the brand and how much I paid. To receive the hard drive settlement, they want the same info (serial number, proof of purchase, name of retailer, price paid, etc).

    I have those receipts... somewhere. Who really keeps receipts for computer parts going back a couple generations though? As an individual, I doubt the money I would receive is worth the hassle of digging up the receipts. Sure, MegaCorp may have purchased 1,000 units and have the receipt of that order and will get a hefty sum at 7% for their trouble, but most people are just going to get a couple dollars.

    I'm not sure why they don't offer a token minimum amount for those who can't provide receipts (I don't see all 300 million people in the US clamoring to get a $10 check). Of course, like most class action suits, this was probably just a way for a law firm to cash in on a settlement (they get a cool $1.8 million while you get some free backup software or a couple dollars).

    --
    Don't leave your mind so open that your brain falls out. Don't close it so much that you cut off the blood.
    1. Re:Much like a RAM settlement offer in the mail by Hunter-Killer · · Score: 2, Informative

      The catch for one of the most recent DRAM settlements (pricefixing; Rust Consulting) was that you had to purchase memory directly from the manufacturer. If you were a consumer, this was unlikely unless you bought directly from Micron/Crucial. I put in a CS ticket with Crucial, and received a copy of my invoices for the desired time period (about $400 worth). The settlement terms was compensation on a pro-rata basis; given the amount of memory sold during that time period vs the settlement sum, I believe it worked out to about 10% for Crucial. Still waiting on my check, so I can't confirm.

    2. Re:Much like a RAM settlement offer in the mail by phantomlord · · Score: 1

      I generally buy memory only from Crucial. Thanks for the tip.

      --
      Don't leave your mind so open that your brain falls out. Don't close it so much that you cut off the blood.
    3. Re:Much like a RAM settlement offer in the mail by Anonymous Coward · · Score: 0

      Because you really should be keeping the receipts for everything you purchase. No matter what it is, it not only gives you a realistic picture of your spending habits over time, every cent paid to sales tax is normally tax deductible if you have proof.

      I have them all, nicely sorted by year and month. And, I have records for computer parts (just what, when, and how much) on a piece of paper that's kept with other archival mailings. It really should be trivial to go through one month's worth of receipts to get what I am looking for.

      And it really comes in handy in times of dispute with banks, or merchants, as I at least have reasonable proof of my spending habits, and can help contest charges. That and it makes sure that my banking, and credit cards balance out each month. You'd be surprised how often strange charges in the $1-$10 range show up.

      But then, teaching budgetting and money-management isn't exactly top priority in this debt-loving society.

    4. Re:Much like a RAM settlement offer in the mail by nonos · · Score: 1

      And if your computer is stolen or your house burned/flooded, the insurance companies will need these receipts to compensate you.

    5. Re:Much like a RAM settlement offer in the mail by phantomlord · · Score: 1

      I file all of my important receipts, statements, bills, etc (filed by company, 1 year per folder, sorted chronologically internally). I don't consider a $40 purchase of some memory or a $80 hard drive a major receipt though. Do I have them? Yeah, somewhere in my drawer of unimportant receipts. Would it be just as easy to file those receipts with the rest of my bills? Probably, and I generally do these days. The problem is the receipts from 2001. If I need to dispute a charge, it's going to be from a receipt that is, at most, 40 days old and those are generally still handy (prior to my starting to file stuff a couple years ago). And yes, I balance my accounts every month and check the online records every few days. I resent the implication that, because I don't know precisely where a particular 6 year old receipt is, I must be a fiscal idiot.

      A lot of people simply throw away receipts for those minor purchases. Others get rid of records more than 3-4 years old, once the IRS audit window ends. What is the reasonable duration to hold on to minor (sub $100) receipts? Do I really need to know, 40 years from now, that I stopped at the grocery store to buy chicken last night?

      --
      Don't leave your mind so open that your brain falls out. Don't close it so much that you cut off the blood.
  13. Misleading by being correct? by Empiric · · Score: 1

    Giga-anything is one billion exactly of that thing.

    Wikipedia notes its techie-colloquial usage, and states that it is incorrect according to the SI/metric standard.

    "The prefixes k and greater are common in computing, where they are applied to information and storage units like the bit and the byte. Since 2^10 = 1024, and 10^3 = 1000, this led to the SI prefix letters being used to denote "binary" powers. Although these are incorrect usages according to the SI standards it seems common to apply base 10 prefixes, when relating to computers, as follows..."

    Strange "victory".

    --
    ~ Whence do you come, slayer of men, or where are you going, conqueror of space?
    1. Re:Misleading by being correct? by fredklein · · Score: 5, Funny

      Wikipedia notes its techie-colloquial usage, and states that it is incorrect according to the SI/metric standard.


      Too bad we're "techies" and not scientists. Also too bad we don't use the metric system in the USA. As a matter of fact, we wouldn't touch it with a 3.04800 meter pole.

    2. Re:Misleading by being correct? by Empiric · · Score: 1

      Not sure who "we're" refers to there, but I did enough 6502 Assembly code in the 80's to have the first 16 powers-of-two burned into my brain to this day... and still I wouldn't try to claim my binary predilictions should hold sway over the international standard in court. ;)

      --
      ~ Whence do you come, slayer of men, or where are you going, conqueror of space?
    3. Re:Misleading by being correct? by Anonymous Coward · · Score: 0

      Also too bad we don't use the metric system in the USA

      So you measure electrical potential in foot-pounds per ampere-second, rather than in volts?

      This lawsuit wouldn't have stood a chance at trial. Fortunately for the plaintiff, you don't need to be able to win; you just need to be able to make defending the case more expensive than paying the "protection".

    4. Re:Misleading by being correct? by hitchhacker · · Score: 0, Flamebait

      Indeed. the summary is incorrect. 1GB == 10^9 bytes vs. 1GiB == 2^9 bytes. This isn't new people.

      -metric

    5. Re:Misleading by being correct? by fredklein · · Score: 1

      Not sure who "we're" refers to there

      Geeks. People who deal with computers daily, and actually bother to look at the specs of hard drives.

      You see, computers use Binary. When refering to computers, "1k" is 1024. To a scientist, '1K ' is 1000. Hard drives are not for scientists, they are for computers, therefore memory and storage capacities should use the 'computer' definition of "k".

    6. Re:Misleading by being correct? by drsmithy · · Score: 1

      Wikipedia notes its techie-colloquial usage, and states that it is incorrect according to the SI/metric standard.

      Such terminology grossly misrepresents the scale of the "colloquial" usage of the SI prefixes to denote 2^X values, because it makes it sound like it's limited to the kind of people who work out the back in mom-and-pop computer stores fixing PCs, when in fact that usage has been widespread and common throughout the entire industry for 30+ years. Pretty much the *only* ones insisting on 10^x usage were hard disk manufacturers (starting from about the late 80s) and arseholes feeling the need to look superior (starting from a few seconds after the SI 2^x prefixes were formalised).

    7. Re:Misleading by being correct? by marcansoft · · Score: 1

      18. Beatcha. And I'm younger to boot (though I've still done a whole bunch of assembly, but for PIC16s and PIC18s instead)

      Seriously though, who doesn't have at least the first few memorized? Even Joe Average remembers at least the first 9 or so (whether they like it or not), especially from RAM sizes. 1, 2, 4, 8, 16, 32, 64, 128, 256, 512 will probably ring a bell for most people who have bought a computer at some point.

      Then there's us. 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144.

    8. Re:Misleading by being correct? by xous · · Score: 1
    9. Re:Misleading by being correct? by moderatorrater · · Score: 1

      Not strange at all. The CPU, programming language and every other modern storage device use the binary definition rather than the head-up-the-ass SI definition. This is like you insisting that the term football should properly refer to American Football rather than the European-colloquial usage. 90% of the time anyone hears the term "gigabyte", it's referring to a power of 2.

    10. Re:Misleading by being correct? by darthflo · · Score: 2, Insightful

      Actually, to a scientist, '1K' would be very fucking cold (to the point where the nerves probably wouldn't be quick enough to even transmit the coldness info to his brain). '1k' is a thousand. :)

    11. Re:Misleading by being correct? by Anonymous Coward · · Score: 0

      Actually, I am a scientist, not a techie. I live in the US, and I use the metric system every day at work. This country really should stop pandering to Creationists and other Luddites and fully adopt metric.

    12. Re:Misleading by being correct? by fredklein · · Score: 1

      Metric is a made-up system of measurement, based upon certain arbitrary measurements.

      Imperial is a more useful system of measurements. Everyone has feet. 1 foot= (approx) the length of a foot. Stretch out your arm, and the distance from the end of your index finger to your nose = (approx) 1 yard.
      1 mile? 1000 paces.
      Acre? Amount you can plow in a day.
      A pint of water= a pound
      etc

      See, all these are handy. Sure, it's a little more complicated to convert from one to another, but they are all more useful measurements to begin with. Even temperature- with 180 degrees between freezing and boiling, the Fahrenheit scale provides a finer granularity than Celsius. It's easier to say "75 degrees, oops, no, just changed to 76" (F) then "23.8888889 degrees, just changed to 24.4444444" (C) (Note- both of those round to "24")

  14. Should not have settled. by Xfacter · · Score: 0

    SI Units vs IEEE Standard Units

    If these people wanted to sue someone, they should have sued for the countless other pieces of software which use SI prefixes incorrectly.

    1. Re:Should not have settled. by houstonbofh · · Score: 1

      For the record, the IEEE proposed this in 2005, and the case goes back to 2001. While this was a known issue, it was till misleading. They may have had to spend a lot to win this. And they may have lost...

    2. Re:Should not have settled. by pgn674 · · Score: 1

      Document IEEE 1541-2002 states, basically, that there are 1000 bytes in a kilobyte (kB), and 1024 bytes in a kibibyte (KiB). IEEE considers it a full-use standard.

      I find that if one doesn't know the context, the difference can be most frustrating. Here is a quick lookup reference I put up.

  15. Ridiculous by Anonymous Coward · · Score: 0

    The metric prefixes were always used for the powers of ten, not powers of two. This was made *abundantly* clear when IEC approved different names for the power of two 'equivalents' in 1998.

    See http://physics.nist.gov/cuu/Units/binary.html

  16. Definitions by mduke · · Score: 3, Informative

    IANAL, but I think the reason they lost is not based on whether 1GB is decimal or binary but because they did not specify the system they used to count it. If they said it was 1GB in decimal so 1GB = 1000MB and made that clear, then they probably would have been ok. But since they did not, 1GB = 1024MB was easier to demonstrate as a better, more common, and more readily accepted definition due to the way it was shown in the OS, and there was nothing on the packaging to negate this. So make sure if you use numbers, you say exactly what they are supposed to be.

    --
    Those who would trade liberty for security deserve neither
    1. Re:Definitions by fossilstar · · Score: 1
      "Those who would trade liberty for security deserve neither"

      "Those who trade liberty for security are traitors, not traders."

      --
      "Support our Oops."
    2. Re:Definitions by darthflo · · Score: 1

      Pretty sure the fine print somewhere said something along the lines of "1 GB = 1'000'000'000 bytes". Every Dell ad I see anywhere printed does, most every large online store does. Probably the court just found it to be printed a wee bit too fine.

    3. Re:Definitions by kenh · · Score: 1

      No, Seagate admitted adding that definition to their packaging after the lawsuit was filed - it's noted in the paperwork of this lawsuit.

      This lawsuit goes back a number of years (5?) - the definition is a fairly recent addition to the packaging/marketing campaign.

      Ken

      --
      Ken
    4. Re:Definitions by kenh · · Score: 1

      Seagate didn't lose, they gave up the fight. They offered the lawyers a payoff that made them go away and admitted no wrong-doing.

      Neither a judge nor a jury found them at fault, liable, or guilty.

      Ken

      --
      Ken
    5. Re:Definitions by Anonymous Coward · · Score: 0

      IANAL, but I think the reason they lost is not based on whether 1GB is decimal or binary but because they did not specify the system they used to count it. If they said it was 1GB in decimal so 1GB = 1000MB and made that clear, then they probably would have been ok.

      Ok, now just what do you mean by "MB" up there? 10^6 bytes or 2^20 bytes?

  17. Ahh, another valueless settlement. by Harik · · Score: 5, Insightful

    yeah pretty worthless, I've bought $1000 worth of drive from them, but that's after jan 1 2006. Even if if it was before that, I would have to file 10 seperate claims for ~$5 each. Meanwhile the cocksucking trial lawyers get a cool 1.8mn in cash.

    Seriously - class action lawsuits are utterly worthless. "Whoops we ripped you off by conspiring to raise memory prices tenfold. Here's a 2 dollar coupon that expires the day we get around to mailing it out and is only good at a single retailer in northern alaska. "

    Seriously - How many people here paid nearly a grand for 32 meg SIMMS? Remember the "welp we had a glue factory fire so prices skyrocketed!" bullshit? Special glue just for memory ICs - and that scaled exactly with capacity? Yeah, that "glue factory fire."

    "Oh yeah our batteries in our ipods are horribly defective here everyone who spent $300 on this shitty self-destructing rev of hardware and can cough up documentation gets 2 free songs on our own music store."

    I'd really prefer the courts just fine the fuck out of the companies and it goes to something worthwhile - letting them use legal judgements as cheap advertising is just bullshit.

    1. Re:Ahh, another valueless settlement. by Bemopolis · · Score: 1

      It's not just a valueless settlement. It was a fucking retarded case to begin with. Wait, did I say fucking retarded? Just in case...fucking retarded. It's bad enough when law firms get windfalls from class actions suits with actual merit behind them. This? This is because Americans can't understand THE FUCKING METRIC SYSTEM. Or read the side of the FSMdamned box. Or, you know, take responsibility for not reading the side of the FSMdamned box.

      --
      "I guess the moral of the story is, don't paint your airship with rocket fuel." -- Addison Bain
    2. Re:Ahh, another valueless settlement. by Nuitari+The+Wiz · · Score: 1

      And from what I understand the drives have also had to been bought as a standalone product. Does that mean that OEM drives are out of the settlement?

    3. Re:Ahh, another valueless settlement. by megaditto · · Score: 1

      I known people that mailed in rebates for $0.50; having to pay $0.32 postage didn't matter either! For a company, those class-action lawsuits could still be pretty pricey due to all the penny-pinchers claming their dimes.

      --
      Obama likes poor people so much, he wants to make more of them.
    4. Re:Ahh, another valueless settlement. by bill_mcgonigle · · Score: 1

      Meanwhile the cocksucking trial lawyers get a cool 1.8mn in cash.

      Right, so everybody who feels this way needs to opt out of the settlement. There's a form letter on my blog you can copy and paste if you'd like.

      The real meat of the blog post is bitching about how much it'll cost the class to opt out vs. what it costs the lawyers to create the class. This is an asymmetrical attack against society. It makes it really easy for the lawyers, but hard for everybody else. I wonder who wrote those laws!

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    5. Re:Ahh, another valueless settlement. by __aajfby9338 · · Score: 3, Informative

      Remember the "welp we had a glue factory fire so prices skyrocketed!" bullshit? Special glue just for memory ICs - and that scaled exactly with capacity? Yeah, that "glue factory fire."

      That was a fire at a factory which made the epoxy resin used to encapsulate ICs. This wasn't "special glue just for memory ICs"; it was the black plastic stuff molded around each IC on the SIMM (or any other kinds of ICs with plastic packages, for that matter). Without that plastic overmold to protect the bond wires and support the leadframe, the ICs can't be handled, shipped, soldered down, etc. That fire messed up the whole electronics industry for a while. I'm not saying that the memory suppliers didn't gouge anybody (I have no information either way), but the resin factory fire really was a big deal. It caused problems at my company at the time, which made ICs used in hard disk drives.

    6. Re:Ahh, another valueless settlement. by Smauler · · Score: 2, Funny

      yeah pretty worthless, I've bought $1000 worth of drive from them, but that's after jan 1 2006. Even if if it was before that, I would have to file 10 seperate claims for ~$5 each. Meanwhile the cocksucking trial lawyers get a cool 1.8mibillion in cash.

      Don't exaggerate, there, I fixed that for you.

    7. Re:Ahh, another valueless settlement. by Atario · · Score: 2, Insightful

      *SIGH*

      Ok, let's cover this one more time. Class action lawsuits are only sometimes intended to give a substantial settlement to all members of the class. The real point of them is not to get you rich, but to take down a wrongdoing company a few notches so that, with any luck, they'll know better next time — or at least think twice.

      --
      "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    8. Re:Ahh, another valueless settlement. by Anonymous Coward · · Score: 0

      I remember that glue fire. I was about 9 years old and hoping to buy some RAM, but until you pointed it out just now I hadn't ever realized that the 32 meg SIMMS should have had the same markup as the 4 meg SIMMS. I agree. Fine the living shit out of them.

    9. Re:Ahh, another valueless settlement. by darthflo · · Score: 2, Funny

      Wait, the Flying Spaghetti Monster damned the box?

    10. Re:Ahh, another valueless settlement. by alejandronova · · Score: 1

      You are COMPLETELY WRONG. Class action lawsuits feed lawyers and enable them to buy BMWs. They are worthy for sure.

    11. Re:Ahh, another valueless settlement. by trudyscousin · · Score: 1

      "Here's a 2 dollar coupon that expires the day we get around to mailing it out and is only good at a single retailer in northern alaska."

      On top of all that, the guy behind the counter is probably a vampire.

      --
      Those who can, do. Those who can't, write technology blogs.
    12. Re:Ahh, another valueless settlement. by R2.0 · · Score: 2, Insightful

      Wrong. Class action suits are largely based in common law, not criminal law. Criminal law deals with punishment, common law with equity. At least, that's how it was...

      Class actions started as a matter for convenience for the courts - if there are a lot of people with the same basic claim, just litigate once instead of many times. Saves costs/more efficient.

      Punitive damages were supposed to be a secondary function of the court, where particularly egregious behavior was punished.

      Then came Congress, and the Trial Lawyer Association.

      Congress at some point decided that, instead of making certain activities subject to criminal law, they would be subject to civil law. So if some corporation does something bad, the FBI doesn't bust ass - someone sues. And to make sure that there was punishment meted out, we got statutory punitive damages, mandatory, and set at 3x the judgement. Lawyers loved this - they get to make a shitload of money doing the Fed's dirty work.

      At the same time, mega law firms developed. In order to increase revenue, they becan the rampant campaign of class action suits we see today, which are specifically designed NOT to punish, or to give their clients redress - they simply occurr to make the law firms more money. Witness the silicosis debacle, and the "tobacco settlement", where select, politically connected law firms made profits orders of magnitude greater than their cost (I'm looking at you, Angelos).

      Class actions have been abused into a legal sham and a public laughing stock. as an instrument of equity, they are useless, and that's because a bunch of large law firms want it that way.

      --
      "As God is my witness, I thought turkeys could fly." A. Carlson
    13. Re:Ahh, another valueless settlement. by Anonymous Coward · · Score: 0

      Did anybody notice that the "injury" was 7% (of disk capacity) but the "compensation" was 5% (of price paid)?

      "First thing we do, let's kill all the lawyers" -Shakespeare

    14. Re:Ahh, another valueless settlement. by Anonymous Coward · · Score: 0

      Sorry, can't resist: What's 1.8mn? That's a little confusing, don't you think.

    15. Re:Ahh, another valueless settlement. by Atario · · Score: 1

      Well, it would certainly be nice if the government resurrected their role of prosecuting corporations in consumers' interest, but the goal posts have been moved so far by now that now the proposal you hear is to do away with even the paltry role of class action lawsuits and just let them run roughshod, as in the great grandparent post.

      Sad.

      --
      "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    16. Re:Ahh, another valueless settlement. by Gnavpot · · Score: 1

      Sorry, can't resist: What's 1.8mn? That's a little confusing, don't you think.

      Perfectly clear to me:
      1/1000 of an n. Also called a milli-n.
    17. Re:Ahh, another valueless settlement. by dlevitan · · Score: 1

      Seriously - class action lawsuits are utterly worthless. "Whoops we ripped you off by conspiring to raise memory prices tenfold. Here's a 2 dollar coupon that expires the day we get around to mailing it out and is only good at a single retailer in northern alaska. "


      While in general I'd agree with you, with the right lawyers, enough movement behind the lawsuit, and all the planets in alignment, good things can happen. I used to think the same thing as you, until I got a new phone from Verizon Wireless after the Motorola V710 lawsuit. Basically, they had claimed Bluetooth compatibility, but all it was good for was headsets and dial up networking. People sued and verizon settled to accept the phone and all accessories they had sold you for return in exchange for a credit amount at their store (there were some other options as well). Not great, but I wanted their service anyway, so I got a brand new phone that cost less (and was better) than my original phone, a top of the line bluetooth headset, and a new case. True, they got another year long contract out of me, but I was pretty happy with how things worked out.
    18. Re:Ahh, another valueless settlement. by NateTech · · Score: 1

      There's a growing body of evidence that "opt-in" would be better for Class Action lawsuits versus the current "opt-out" system. Many reasons. One would be that the lawyers would have to hunt down and get permission from all the people to represent them, so there'd be a very big damper put on the lawyers who just troll for Class Action suits constantly to make money, with little or no benefit to the consumer.

      --
      +++OK ATH
  18. Re:wow.... are you clueless! by Anonymous Coward · · Score: 0

    seagate owns maxtor!

    seagate is the REASON maxtor drives are now crap.

  19. Either way.. we will pay by Maxo-Texas · · Score: 2, Insightful

    and some lawyer is going to be flushing the money on hot cars and girls or boys.

    Here is your $5.99.

    By the way.. did we mention our $5.99 price increase on our drives?

    --
    She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  20. Yeah.. by mikkelm · · Score: 5, Interesting

    I must be eligible for at least $100 over all the Seagate gear I bought in that period, but it'll be a cold day on the sun before I demand money from any corporation for the ignorance of other people.

    Seagate has produced great drives for a long time, and they've never strayed from industry standard definitions to advertise the storage capacity. Anyone taking advantage of this settlement is either morally dishonest or technologically incompetent.

    1. Re:Yeah.. by reikoshea · · Score: 1

      This is the comment I've been waiting for. I've been a Seagate proponent for a long time, and I could not imagine taking their money. I would hope to God no self respecting geek could either.

    2. Re:Yeah.. by Anonymous Coward · · Score: 0

      Seagate has produced great drives for a long time, and they've never strayed from industry standard definitions to advertise the storage capacity. Anyone taking advantage of this settlement is either morally dishonest or technologically incompetent.

      Exactly. I have never seen them advertise that their GB was 1024MB and therefore this class action suit really stinks.

    3. Re:Yeah.. by KKlaus · · Score: 1

      >>morally dishonest or technologically incompetent.

      Can't I punish Seagate on behalf of the technologically incompetent? It's not morally dishonest for the police to be the ones to jail a robber, even when YOU were the one he robbed. And don't forget that the technologically incompetent encompass a huge swath of hard drive purchasers, so I wouldn't feel bad grabbing the rebate even if they didn't mislead you in particular. That their dishonesty was common, or easy to see through, doesn't seem like an adequate defense to me. So like I said, grab the rebate, and use it to buy someone you like a gift, or donate the money to charity. Even if you weren't PERSONALLY mislead.

      --
      Relax I just want some peanuts.
    4. Re:Yeah.. by WK2 · · Score: 1

      According to the settlement agreement, it looks like I can get $2 for a 160GB drive that I paid $40 (after rebates) about 2 years ago. It isn't really worth my time for that $2 - $0.41 for a stamp, as it will probably take me most of an hour to print the form, open my computer, write the proper numbers, and mail the form. But I plan to mail in the form to show Seagate that I do not appreciate their attempt at deception. I would like to do my part to encourage HDD manufacturers to label their drives properly.

      --
      Write your own Choose Your Own Adventure. http://www.freegameengines.org/gamebook-engine/
    5. Re:Yeah.. by mikkelm · · Score: 1

      You're actually suggesting that incompetence on behalf of the user justifies ripping off a company?

      No customers were mislead here. Base 10 is the industry standard. No (at least major) permanent storage device manufacturer sizes their drives in base 2. Storage space in base 2 is a common misconception that's being perpetuated by OS developers. If anything, sue them.

      Not understanding the product that you're purchasing does not mean that you were mislead.

    6. Re:Yeah.. by mikkelm · · Score: 1

      So you're saying that you feel mislead because you based your purchase of their product on an incorrect assumption, instead of actually getting to know the readily available details of product that you're buying?

      It's like buying "one chicken" and complaining about it not being as big as "one cow", on the grounds that it's still "one", and you're used to buying cows.

    7. Re:Yeah.. by reikoshea · · Score: 1

      The fact that someone that actually reads slash dot made a comment like that is just.......disheartening. Even my fellow geeks have joined the dark side (had to make a Star Wars reference).

    8. Re:Yeah.. by WK2 · · Score: 1

      So you're saying that you feel mislead because you based your purchase of their product on an incorrect assumption, instead of actually getting to know the readily available details of product that you're buying?

      No, I'm not saying that at all. I had no incorrect assumption. I knew what I was buying. I still didn't like it though. If the drive is only 150GB, they should label it so. The fact that their measurement could be considered correct does not negate the fact that they were being intentionally misleading. The fact that I knew this beforehand does not negate the fact that I dislike this practice.

      It's like buying "one chicken" and complaining about it not being as big as "one cow", on the grounds that it's still "one", and you're used to buying cows.

      It is more like I wanted a cow, and went to the cow store, and all they had were chickens labeled as "cows." I was already there, and the prices were reasonable, so I bought a chicken for dinner instead. Two years later, due to a court settlement, I am entitled to a refund, and I will take it to encourage chicken-sellers to not intentionally mislabel their stock for profit.

      --
      Write your own Choose Your Own Adventure. http://www.freegameengines.org/gamebook-engine/
    9. Re:Yeah.. by mikkelm · · Score: 1

      No, I'm not saying that at all. I had no incorrect assumption. I knew what I was buying. I still didn't like it though. If the drive is only 150GB, they should label it so. The fact that their measurement could be considered correct does not negate the fact that they were being intentionally misleading. The fact that I knew this beforehand does not negate the fact that I dislike this practice.


      When a drive is 150GB, they label it as such. A gigabyte is one billion bytes. Regular SI units. If you had one party telling you that a kilometre is 1000 metres, and another telling you that a kilometre is 1024 metres, who would you consider right? The officially recognised one, of course. When you're talking about kilometres, you're using SI units. Why shouldn't you insist on SI units when talking about kilobyte? There's kilo, and there's kibi. As much as you seem to dislike it, base 2 is kibi, and base 10 is kilo.
       
       

      It is more like I wanted a cow, and went to the cow store, and all they had were chickens labeled as "cows." I was already there, and the prices were reasonable, so I bought a chicken for dinner instead. Two years later, due to a court settlement, I am entitled to a refund, and I will take it to encourage chicken-sellers to not intentionally mislabel their stock for profit.


      The problem here is that the ones labeling the chickens as cows are the OS manufacturers. Not the disk drive manufacturers. You aren't entitled for a refund when you buy a product advertised as having 160 billion bytes of storage capacity if you get a drive that DOES have 160 billion bytes of storage capacity. Kilo, mega and giga are base 10 SI units. Just because you have a piece of software telling you that they aren't, you aren't justified in seeking refunds from the company that sold you the disk.

      There's absolutely no "intentional misleading" practices here as you seem so intent on. These are decades long industry standards that are followed by everyone. The ignorance of users isn't an excuse.
  21. Re:wow.... are you clueless! by mrbcs · · Score: 1, Informative

    Can't read can you asshole. I said I stopped buying Maxtor over 4 years ago.. that would be 2003. If you read this: http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=Seagate_Technology_To__Acquire_Maxtor_Corporation&vgnextoid=1e8a814fef83e010VgnVCM100000dd04090aRCRD Segate bought Maxtor 2 years after that.

    --
    I'm not anti-social, I'm anti-idiot.
  22. If only.... by MrKevvy · · Score: 5, Funny

    "In its out-of-court settlement, Seagate proposed to pay $1000000 in damages. When the plaintiffs signed off on the agreement, Seagate lawyers indicated that this was a binary figure, paid the plaintiffs sixty-four dollars in cash and departed, apparently in some haste."

    --
    -- Insert witty one-liner here. --
    1. Re:If only.... by jez9999 · · Score: 1

      Actually, it was $10000000, representing a signed integer.

  23. Another enhancement for Newegg! by frankmu · · Score: 4, Funny

    i think Newegg can add a "class-action lawsuit" button next to the rebate button, so they can help their customers use their money responsibly. it's the only place i buy my stuff from, and they would have proof of purchase information on file. heck, they can be like Steve Jobs, and just credit me for more purchases from their store!

    --
    Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony.
    1. Re:Another enhancement for Newegg! by evilviper · · Score: 1

      it's the only place i buy my stuff from,

      Newegg has the most unbelievably dysfunctional order system I've ever seen.

      For the first time ever, I had to cancel my order. It was placed late Saturday night (PST). Less than an hour later, I used their web interface to send an e-mail asking to have the order canceled. Then, 7am Monday morning I used "Live Chat" and asked to have the order canceled. Then 8am Monday, I called their telephone support line to have the order canceled. Ironically, late Monday I got a nasty message from e-mail support telling me the telephone support operator took care of everything, and that I shouldn't have e-mailed... This despite the fact that the e-mail was sent two days before I phoned.

      The order shipped sometime Tuesday afternoon... GAH! It arrived within about two hours, before I could call up and "refuse" the package. So I have to wait another day to get a mailing label I have to print out, and take the box in. And my thanks for going through all this extra work for them (because their order system is so dysfunctional)??? They are still charging me shipping on the non-order... I'm still arguing with them about this one. No doubt I'm going to end up having to call-up my CC company to get anything done.

      Seriously now, a one-man web-shop, located out in the middle of nowhere, can hold a package. Why is Newegg so incompetent that they can't handle the most basic of operations?

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  24. Next stupid lawsuit... by Forbman · · Score: 3, Interesting

    Well, now someone needs to go after OS makers for "lying" because of all the wasted space depending on data block size. Sure, you can have a 1-byte file, but it'll use up 512 bytes or more space on the HD... So, which is it? Is it a 1-byte file, or really a 512-byte (or 1024 or 2048 or 4096 or...) file?

    I have a 1TB HD, and, well, I want to be able to actually use every byte of it!!!

    A gigabyte here, a gigabyte there, pretty soon we're going to be talking about some actual wasted disk space...

    1. Re:Next stupid lawsuit... by SanityInAnarchy · · Score: 1

      A gigabyte here, a gigabyte there, pretty soon we're going to be talking about some actual wasted disk space...

      The higher you get, the more the difference will be.

      1 kilobyte, as labeled by Seagate (and every other storage manufacturer), is actually 0.98 kilobytes -- big deal, you lose 24 bytes.

      1 megabyte is actually 0.95 megabytes, or 976 kilobytes, so you lose 47 kilobytes.

      1 gigabyte is actually 0.93 gigabytes, or 953 megabytes, so you lose 70 megabytes.

      1 terabyte is actually 0.90 terabytes, or 931 gigabytes, so you lose 92 gigabytes.

      I don't know about you, but even with a terabyte of space, 92 gigabytes hardly seems insignificant. And at a petabyte, it becomes 115 terabytes. And so on.

      Sure, you can have a 1-byte file, but it'll use up 512 bytes or more space on the HD... So, which is it? Is it a 1-byte file, or really a 512-byte (or 1024 or 2048 or 4096 or...) file?

      First off, modern OSes generally do have a way of telling you both values -- both how big a file logically is, and how much space it uses on-disk.

      Second, both ReiserFS and Reiser4 -- and pretty much no other FS, sadly -- do a form of "tail packing". Essentially, if the last block of a file doesn't use the whole block, they pack it somewhere -- in ReiserFS, they pack it right into the directory structure. In Reiser4, they use something akin to extent lists to pack the files as tightly as possible, separate from the metadata (directory structure), though.

      I believe this does tend to fragment things more, but if you want to use all that space, you can. In Reiser4, it gets even better -- you could have transparent, read/write compression on top of that, with no loss of performance. (I've read the whitepaper; it would work, but it's also not trivial.)

      And there's a really good reason for using such a filesystem: Mailservers. Webservers are getting less relevant, as they can pretty much store everything in a database, which will throw all the data for all the pages into only a few physical files on-disk, as seen by the filesystem. However, at least a few UNIX-based mailservers do what I consider the "right thing" -- they store the mail in Maildir format, which makes it very interoperable, and ludicrously easy to script for. It also performs well -- better than mbox, the only other standard format for an on-disk representation of a mailbox -- mbox uses single files, basically all your mail concatenated together with special characters marking the beginning of a new message. So yeah, mbox sucks, maildir rules, except maildir means you'll be dealing with many hundreds of thousands of files. Could be as much as 2-3 times smaller on a Reiser-based (or similar) filesystem.

      That's 2-3 times over pretty much the entire mail spool and folders (if you're doing IMAP). That means, if you were running a mailserver (I'm assuming you're not), simply switching filesystems could mean the difference between a 500 gig hard drive and a 1 terabyte array.

      Or, if you want a solution right now for the more archived files, just pack the files in an archive of some sort -- .tar.bz2 for long-term storage, or something like zip for quick access. There are FUSE drivers to actually be able to mount these -- or you can use things like cramfs, squashfs, etc.

      Finally, a real-life example from work: Sure, all our source files for HD-DVD development are stored individually on NTFS, FAT32, ext3, etc. But most of the interactive content (scripts, XML, PNG images) gets thrown into an aca file on-disk. This isn't for storage purposes, actually, but performance -- the HD-DVD player can, presumably, just slurp the whole aca into RAM and run it from there, and it can do it as a sequential read (no seeks).

      Even if you don't want that extra space, may as well use it for something, right? Maybe some parity bits?

      Well, that was quite a lot of work put into proving you wrong. Hope it was educational, at least...

      --
      Don't thank God, thank a doctor!
    2. Re:Next stupid lawsuit... by Anonymous Coward · · Score: 0

      Think back to all those 1.44 MiBiByte floppies that where marketed as 2 MiBiByte. Unformatted that is.

      Its just a shame I've never seen a program utilize that full capacity.

    3. Re:Next stupid lawsuit... by Anonymous Coward · · Score: 0

      Windows gives a "size", and "size on disk".
      Linux has "du" which gives the actual size on the disk.
      ReiserSF for linux gives you the option to put allow multiple files in a single sector.

      Now, what where you asking again?

  25. It's not a longstanding history by Solandri · · Score: 5, Insightful

    Seriously, the blame could just as easily be laid at the feet of the OS developers. There is a long standing history of disk manufacturers using base 10 counting numbers.
    It's not a longstanding history. It started in mid-1990s. In the early 1990s, if you bought a 300 MB drive, you got 300*1024^2 = 314,572,800 bytes.

    In the mid-1990s, one marketing dweeb at a low-end hard drive manufacturer (I want to say Maxtor but don't recall for sure) convinced his company to start defining 1 MB = 1,000,000 bytes. It let them sell a smaller (and thus cheaper to manufacture) drive while labeling it as the same capacity as everyone else's drives. The others resisted for about a year, then gave in and started mis-labeling their drives. IBM was the last holdout, I think they went for 3 years selling bigger drives than everyone else labeled with the same capacity. Eventually they gave in too, shortly before selling their hard drive division to Hitachi.

    Around 1998, the international standards bodies mandated that MB = 1,000,000 and GB = 1,000,000,000, while MiB = 1,048,576 and GiB = 1,073,741,824. But like metric in the U.S., these units have never really caught on in the computer industry. Personally I can see the standards bodies' point, but they're going to have to collaborate with OS, memory, hard drive, and other computer hardware manufacturers to get the change implemented. They can't just stand on a pedestal mandating that this change be made, and expect it to happen.

    The whole fiasco is an example of a class of situations I haven't found a name for but which is similar to the Tragedy of the Commons. In these situations, one member of the group does something which gives him an advantage of the others. The others then follow suit to remain competitive, and in doing so eliminate the advantage. The end result is that the situation is now identical to what it was before the change (everyone's 500 GB drives are the same size), but now everybody is worse off because of the change (1 GB on a drive does not equal 1 GB in memory). Other situations within this class include campaign spending in politics (everyone has to spend more on advertising each year just to stay even with everyone else), and net neutrality (if everyone pays the Telecos more money for priority, they have gained nothing because the total bandwidth hasn't increased, and are now losers because they're paying more for the same bandwidth).

    1. Re:It's not a longstanding history by Anti_Climax · · Score: 2, Informative

      Your description seems to be a hybrid of the tragedy of the commons and the Red Queen

      I say we call this hybrid theory the Tragedy of the Queen.

      --
      Even people that believe in pre-destiny look both ways before crossing the street.
    2. Re:It's not a longstanding history by Zapek · · Score: 1

      It already started with floppy disks.

      1.44MB where in fact it was 1440KB.

    3. Re:It's not a longstanding history by julesh · · Score: 1

      It already started with floppy disks.

      1.44MB where in fact it was 1440KB.


      1.44 "MB" floppy disks are strange:

      1. Most manufacturers at the time they were introduced labelled them with an "unformatted capacity" of 2MB.

      2. a 1.44MB formatted floppy has an actual capacity of 2880 x 512 byte sectors = 1,474,560 bytes. This is neither using the original definition of 1MB=2^20 bytes (which would mean 1.44MB = 1,509,949 bytes) nor the 1MB=10^6 bytes definition (where 1.44MB = 1,440,000 bytes).

      I've actually seen some hard disk manufacturers use this definition, too.

    4. Re:It's not a longstanding history by Anonymous Coward · · Score: 0

      It's not a longstanding history. It started in mid-1990s. In the early 1990s, if you bought a 300 MB drive, you got 300*1024^2 = 314,572,800 bytes


      You must be very young then. This is from Seagate ST506/412 disc drive manual (year 1982):

      The ST-506/413 disc drive is a random access storage device utilizing two removable 5¼ inch discs as storage media. Each disc surface employs one movable head to service 153/306 data track. The total formatted capacity of the four heads and surfaces is 5/10 megabytes (32 sectors per track, 256 bytes per sector, 612/1224 tracks).

      http://www.bitsavers.org/pdf/seagate/ST412_OEMmanual_Apr82.pdf

      So 32 sectors per track * 256 byte per sector * 1224 track = 10027008 bytes

      On bitsavers you can find many old documents from IBM (Winchester). They use megabytes as millions of bytes everywhere.

    5. Re:It's not a longstanding history by Atario · · Score: 1

      The whole fiasco is an example of a class of situations I haven't found a name for but which is similar to the Tragedy of the Commons. In these situations, one member of the group does something which gives him an advantage of the others. The others then follow suit to remain competitive, and in doing so eliminate the advantage.
      I want to say Race To The Bottom.
      --
      "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
    6. Re:It's not a longstanding history by KKlaus · · Score: 1

      It is the tragedy of the commons. The tragedy is that no one is better off after the commons is abused, and the commons is public perception of what GB (or MB) means, and the size of the drivers they are purchasing.

      --
      Relax I just want some peanuts.
    7. Re:It's not a longstanding history by LS · · Score: 1

      The end result is that the situation is now identical to what it was before the change ... but now everybody is worse off because of the change

      Not really... In the case of hard drive manufacturers, they are better off because they are all selling cheaper drives at the same price. With campaign spending, advertising channels are better off, as well as the political status quo being protecting by a large barrier to entry for people without money. With net neutrality, the telcos are better off, as they get more money for the same product. These examples are more like descriptions of cartels/monopolies. Though I guess it is still a tragedy for common people.

      LS

      --
      There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
    8. Re:It's not a longstanding history by shadanan · · Score: 1

      The name you are looking for is "prisoner's dilemma".

    9. Re:It's not a longstanding history by Anonymous Coward · · Score: 0

      It's not a longstanding history. It started in mid-1990s.


      How could a post that is blatantly wrong end up with +5 insightful? There was a discussion here on this exact topic only a week or so ago, and it was pointed out that it goes back to at least the 1970s for IBM's winchester drives. A quick search of Google verifies that IBM quoted 4 70MB drives (the maximum capacity of the System/360 model 115) as holding 280 million bytes, rather than 293 million bytes.
    10. Re:It's not a longstanding history by Anonymous Coward · · Score: 0

      The end result is that the situation is now identical to what it was before the change (everyone's 500 GB drives are the same size), but now everybody is worse off because of the change This principle can work in your favour, too. For example in competing prices. A bunch of companies agreeing to not follow the above wrt pricing would be equivalent to price fixing.
    11. Re:It's not a longstanding history by Kremmy · · Score: 1

      This reminds me of the Great Internet Access Rate Hike.

      There was a time when dial-up internet was, fairly consistently, $20 monthly in the USA. After many years of this, one Internet Access Provider (I believe it was AOL, but I may be mistaken) decided that they were going to change the rate from $20 monthly to $21.95 monthly. Less than a year later I received notice from my provider (Prodigy before the SBC buyout) that they were also raising their rate to $21.95 "to stay competitive."

      I never did see the logic in that. If all of your competitors are raising their prices, you are not staying competitive by raising your prices as well. It is in fact anti-competitive, rather than offering the market a better value you are gouging them in the same way your competition has decided to. The loser being the consumer, as usual.

    12. Re:It's not a longstanding history by 140Mandak262Jamuna · · Score: 1
      The whole fiasco is an example of a class of situations I haven't found a name for but which is similar to the Tragedy of the Commons.

      Tell me about it! I found this site where geeks congregate and make very insightful and informative comments. Then comes this dweeb who makes inane jokes and gets a funny moderation. Then everyone else is forced to make funny comments to stay in synch. And eventually it degenerates with everyone saying the same thing about welcoming the overlords and what happens in Soviet Russia when a beowulf cluster runs the linux of the year. This is how democracy dies. Tragedy of the commons, indeed!

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    13. Re:It's not a longstanding history by jefu · · Score: 1

      It is the tragedy of the commons. The tragedy is that no one is better off after the commons is abused, and the commons is public perception of what GB (or MB) means, and the size of the drivers they are purchasing.

      Actually, I believe that the "tragedy of the commons" pertains to a number of individuals making rational decisions and by so doing ruining the "commons". The wikipedia article backs this up (I think - I've not had my morning coffee yet).

    14. Re:It's not a longstanding history by Anonymous Coward · · Score: 0

      Thing is one manufacture could stand out and say 'we label OUR drives right' and look like the good guys. It could go the other way too. Or in marketing terms 'OUR GB IS BIGGER THAN THE OTHER COMPANIES!!!!'

    15. Re:It's not a longstanding history by damn_registrars · · Score: 1

      In the mid-1990s, one marketing dweeb at a low-end hard drive manufacturer (I want to say Maxtor but don't recall for sure) convinced his company to start defining 1 MB = 1,000,000 bytes. It let them sell a smaller (and thus cheaper to manufacture) drive while labeling it as the same capacity as everyone else's drives. I think the one you're thinking of was Samsung, and their 560MB drives, when everyone else was selling 540MB drives. I remember that debacle as well, and I even bought one for myself to replace my old Seagate 130MB drive. It did seem like too good of a deal at the time, but I was young and dumb enough to buy into it anyways.
      --
      Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    16. Re:It's not a longstanding history by Solandri · · Score: 1

      How could a post that is blatantly wrong end up with +5 insightful? There was a discussion here on this exact topic only a week or so ago, and it was pointed out that it goes back to at least the 1970s for IBM's winchester drives. A quick search of Google verifies that IBM quoted 4 70MB drives (the maximum capacity of the System/360 model 115) as holding 280 million bytes, rather than 293 million bytes.
      Interesting. I started buying hard drives in the late 1980s, around the time typical PC RAM amounts reached and exceeded 1 MB. All hard drives at that time were labeled using 1 MB = 1024^2 bytes. So it would seem the definition used by hard drive manufacturers has changed several times.
    17. Re:It's not a longstanding history by atraintocry · · Score: 1

      Sounds somewhat like the Prisoner's Dilemma. Of course, game theory covers other types of situations, of which PD is just one. But it's a pretty relevant one. I stand to gain by screwing everyone else, but only if they don't do the same to me. The difference here, though, is that the consumers become collateral damage.

    18. Re:It's not a longstanding history by joeljkp · · Score: 1

      In the mid-1990s, one marketing dweeb at a low-end hard drive manufacturer (I want to say Maxtor but don't recall for sure) convinced his company to start defining 1 MB = 1,000,000 bytes. Absolutely wrong. The first hard drive ever made was the IBM 350, in 1956. Its storage capacity was a simple 5e6 bytes (actually 7-bit characters).

      Source: http://en.wikipedia.org/wiki/Binary_prefix#Hard_disk_drives

      --
      WeRelate.org - wiki-based genealogy
    19. Re:It's not a longstanding history by Anonymous+Cowhead · · Score: 1

      It's not a longstanding history. It started in mid-1990s. In the early 1990s, if you bought a 300 MB drive, you got 300*1024^2 = 314,572,800 bytes. Please provide some proof for that claim.

      I bought a Quantum Q105 (still have it) back in the late 80's and I can assure you that it has 105 million bytes on it. The Amiga OS, thought different, of course, and is just as broken today as it was then.

      I've been working on computers with hard drives for a long time, possibly before you were born. As long as I can remember, hard drive capacity has been measured in powers of 10, so I don't believe any of your mid-90's claim unless you'd like to back it up with some specifics.
    20. Re:It's not a longstanding history by arrenlex · · Score: 1

      Your "tragedy of the commons" reminds me of this anecdote:

      Marketer 1: You can only sharpen a pencil so much until you can't write with it anymore, so let's not put any graphite in the last inch.
      - later -
      Marketer 2: There is no graphite in the last inch of the pencil! Why waste wood on that section? Shorten the pencil.
      - later -
      Marketer 1: You can only sharpen a pencil so much until you can't write with it anymore, so let's not put any graphite in the last inch.
      - later -
      Marketer 2: There is no graphite in the last inch of the pencil! Why waste wood on something that's not useful? Shorten the pencil.
      - later -...

    21. Re:It's not a longstanding history by KKlaus · · Score: 1

      Isn't that what I said?

      --
      Relax I just want some peanuts.
  26. Custom low-level format for more capacity by larfojoe · · Score: 1
    Seagate should have just told the judge that the defendants could do a custom low-level format and get at least 7% more capacity. Even if no OS could use it.

    http://en.wikipedia.org/wiki/Disk_formatting#Low-level_formatting_.28LLF.29_of_hard_disks

    1. Re:Custom low-level format for more capacity by julesh · · Score: 1

      Seagate should have just told the judge that the defendants could do a custom low-level format and get at least 7% more capacity.

      Wouldn't have worked. The difference between 2^30 and 10^9 definitions of GB is nearly 10%.

    2. Re:Custom low-level format for more capacity by Anonymous Coward · · Score: 0

      How about counting the inter-sector buffer bytes, servo control bytes, etc? I bet you get more than 10% out of that.....

    3. Re:Custom low-level format for more capacity by julesh · · Score: 1

      I suppose you could write without the ECC for each sector, and get 576 bytes rather than 512. That'd do it.

  27. Pointless by ewhac · · Score: 4, Insightful
    Hard drive makers have, for some considerable time, have meant 10**9 (1,000,000,000) when referring to a gigabyte. They always so declare in their literature. I have some old IBM Deskstar drives with exactly this clarification.

    However, the various SI prefixes -- kilo, mega, giga, exa, and others -- were overloaded by the computer industry to refer to powers of two ("kilo" = 2**10, "mega" = 2**20, "giga" = 2**30) which were "pretty close" to their SI counterparts.

    This has actually caused some confusion as computer people speaking of "kilo" this and "mega" that have worked with scientists who have always used the traditional SI meanings. These differences in interpretation can mean your chemical process doesn't work, the patient dies, you miss Jupiter, etc.

    To help redress this problem, a new set of prefixes have been coined to refer to powers of two. These new prefixes have seen uneven but increasing adoption in the industry (if you have a recent Ubuntu/Debian release, run the command ifconfig -- the byte counts have the new prefixes).

    So, the hard drive makers have been using the SI meanings for "giga" and, in case there was any confusion, explicitly printed in their literature, "One gigabyte is equal to 1000000000 bytes."

    So, at first reaction, I think Seagate got screwed here. This makes me wonder if there aren't other layers of nuance that came out in court, but are lost in these stories.

    Schwab

    1. Re:Pointless by julesh · · Score: 1

      Hard drive makers have, for some considerable time, have meant 10**9 (1,000,000,000) when referring to a gigabyte. They always so declare in their literature.

      Could you tell me when, to an approximate decade, was the last time you read a drive manufacturer's literature before buying their drive? And take a guess at what the answer is for the average computer buyer?

      This has actually caused some confusion as computer people speaking of "kilo" this and "mega" that have worked with scientists who have always used the traditional SI meanings. These differences in interpretation can mean your chemical process doesn't work, the patient dies, you miss Jupiter, etc.

      Could you cite some real cases? I seriously do not believe that this has ever been a real issue. Nobody ever uses K = 2^10 for *any* unit other than bits or bytes, so I don't see how it would have any effect on the things you just mentioned.

      To help redress this problem, a new set of prefixes have been coined to refer to powers of two. These new prefixes have seen uneven but increasing adoption in the industry (if you have a recent Ubuntu/Debian release, run the command ifconfig -- the byte counts have the new prefixes).

      Sure, and I use them when necessary. But the average user has not yet been exposed to them, because mainstream software manufacturers (primarily Microsoft and Apple) do not use them yet, so you cannot expect the average user to understand the difference.

      So, the hard drive makers have been using the SI meanings for "giga"

      Which they started doing before SI weighed in on this topic, and besides, why does SI have any more right than anyone else to dictate the meaning. For instance, the first dictionary definition of "gigabyte" in my dictionary is "A unit of computer memory or data storage capacity equal to 1,024 megabytes (2^30 bytes)." Why does SI have more right to determine what an English-language word means than the lexicographers who compiled this dictionary?
        and, in case there was any confusion, explicitly printed in their literature, "One gigabyte is equal to 1000000000 bytes."

  28. What a crock by SurturZ · · Score: 5, Insightful

    What a crock. Anyone that knows enough about computers to know that GB, MB, and KB are usually base-2 should also know enough to check whether the HDD measurement is in base-2 or base-10. Non-computer people would probably assume that they are base-10... or, more likely, merely that the bigger the number, the better. In my experience non-computer people have difficulty distinguishing between hard-drive space and RAM. Saying that they are somehow miraculously able to distinguish between base-2 and base-10 measurements is ridiculous.

    The Kilo-, Mega- and Giga- prefixes are always base-10 in SI. The IT industry should come up with different terms. Misusing them was a mistake in the '60s and it is a mistake now.

    1. Re:What a crock by Cairnarvon · · Score: 1

      Anyone that knows enough about computers to know that GB, MB, and KB are usually base-2 should also know enough to check whether the HDD measurement is in base-2 or base-10.
      Good luck doing that without buying the damn thing, or hearing it from someone else who had to buy it to find out. That's the whole point of this lawsuit: it wasn't indicated on the box whether it was base-10 or base-2.
      The fact that most non-computer people wouldn't be able to tell the difference doesn't excuse what is essentially a scam, and even if you think the IT industry is misusing kilo-, mega-, and giga-, that doesn't change the fact that that's how it's being used, and Seagate is taking advantage of that to rip off their customers.
    2. Re:What a crock by julesh · · Score: 2, Informative

      What a crock. Anyone that knows enough about computers to know that GB, MB, and KB are usually base-2 should also know enough to check whether the HDD measurement is in base-2 or base-10. Non-computer people would probably assume that they are base-10... or, more likely, merely that the bigger the number, the better. In my experience non-computer people have difficulty distinguishing between hard-drive space and RAM. Saying that they are somehow miraculously able to distinguish between base-2 and base-10 measurements is ridiculous.

      To the average person, the distinction between base-2 and base-10 is meaningless, yes. That doesn't mean, however, that they aren't being cheated. Their interface with the computer, when they examine a file, will tell them how large it is using base-2 units. Disk space requirements on the back of software packages are written in base-2 units. Everything they see is in base-2 units, so this is how they estimate their requirements of disk size. And then they find out that the disk is being sold using different units.

      It's a confusing situation, and the disk manufacturers deliberately switched in order to take advantage of it.

      The Kilo-, Mega- and Giga- prefixes are always base-10 in SI. The IT industry should come up with different terms. Misusing them was a mistake in the '60s and it is a mistake now.

      While I agree with you, and try to use Ki etc myself, I don't think this is a problem that can just disappear like that. People are used to thinking in terms of 1GB as ~1.1*10^9 bytes. They might not realise that they do, but they do. Changing perceptions is a long and slow process, and software manufacturers (the only people who can realistically change these perceptions) are reluctant to start because they fear confusing their users. They're probably right.

    3. Re:What a crock by Anonymous Coward · · Score: 0

      You're simultaneously right and wrong.

      You're right: expecting people to easily tell the difference between base 10 and 2 is ridiculous.

      What that really means, then, is that if the hard drive makers were being honest, they'd be labeling drive capacity in GiBs, because that's the relevant information we need to know. We can't do the conversion in our heads. The chipmakers can't make their memory in base 10 increments (it'd be deeply, deeply insane to do so). And it'd be trivial for the drive makers to label in the base 2 prefixes. That they originally did it in base 2, then switched to base 10, and stayed in base 10 for nearly a decade after handy dandy base 2 prefixes were decided on is telling.

    4. Re:What a crock by thue · · Score: 1

      To the average person, the distinction between base-2 and base-10 is meaningless, yes. That doesn't mean, however, that they aren't being cheated. Their interface with the computer, when they examine a file, will tell them how large it is using base-2 units. Disk space requirements on the back of software packages are written in base-2 units. Everything they see is in base-2 units, so this is how they estimate their requirements of disk size. And then they find out that the disk is being sold using different units.

      The base two thing is a low-level technical detail. It has no relevance to consumers.

      The fact that some operating systems choose to let that low-level detail show to the consumers is because of poor operating system design, not because of any logic reason. And it is not the fault of the hard drive makers, who just use the SI units.

    5. Re:What a crock by mpcooke3 · · Score: 1

      A non computer person goes to a shop to buy a 200GB drive, then they go home, plug it in and their computer shows it only has 185GB.
      Trust me, it happens and they are usually pissed off.

      Also, I have to say I'm inclined to agree with them, whatever technical justification (for which there is little IMO) it has clearly been done to mislead consumers.

    6. Re:What a crock by maxume · · Score: 1

      So how many people who go out to buy a disk to hold their 500 Gigs of data have no freaking clue what the silly number on the box means and bought too small a disk? 4?

      The hard drive market operates in decimal bytes, so it is hard to say that people are getting cheated(because buying a 500GB seagate gets you nearly exactly the same thing as buying a 500GB western digital). Seagate got sued because people *felt* cheated, not because they ripped anybody off.

      --
      Nerd rage is the funniest rage.
    7. Re:What a crock by julesh · · Score: 1

      The fact that some operating systems choose to let that low-level detail show to the consumers is because of poor operating system design, not because of any logic reason.

      The fact that _all mainstream operating systems_ choose to let it through is because it was a de-facto standard years before they started. Changing it at any point would have been confusing to existing users (and, yes, the first users really did care).

      And it is not the fault of the hard drive makers, who just use the SI units.

      Which, interestingly enough, they were doing long before the SI standardised them. But you can bet the switch was made for marketing reasons, not because of any desire to follow standards.

    8. Re:What a crock by Anonymous Coward · · Score: 0

      hard drive come in boxes? shit every one i've ever bought has either been and an anti-static bag or an anti-static shell

    9. Re:What a crock by Rich0 · · Score: 1

      Which, interestingly enough, they were doing long before the SI standardised them.

      Uh, the SI standardized the unit prefixes in 1960 (well, at least the prefixes relevant to consumer hard drives). Before that they were standardized by just about anybody using the metric system - starting around the 18th century or so (the concept is much older, but that is when it really took off).

      Lazy programmers started using the base-2 prefixes because it was easier to say 1 KB than 1.024KB. However, for any other application worldwide the kilo prefix would mean 1000.

      The only thing the SI did recently is point out that everybody is misusing the prefixes that have been standardized for centuries - and suggest some new ones for lazy programmers to use.

      I think the whole lawsuit is silly. Who could have possibly been confused by the claims of hard drive makers? Those who are computer illiterate would assume that 1 MB = 1*10^6 bytes - and they'd be right with respect to hard drive claims. Those who are computer literate would know that hard drive manufacturers routinely measure everything in powers of 10.

    10. Re:What a crock by Rich0 · · Score: 1

      Uh, when you factor in partitioning, filesystems, etc, they're going to be disappointed no matter what.

      And they wouldn't be disappointed if the OS reported disk space in SI units and not IT-units. The problem is that for whatever reason nobody in the IT world can agree on one set of units to use for everything. Most of the rest of the world formed SI for this reason, and for whatever reason IT had to do its own thing...

    11. Re:What a crock by julesh · · Score: 1

      Uh, the SI standardized the unit prefixes in 1960 (well, at least the prefixes relevant to consumer hard drives).

      Oh, right, so the SI are the only people who have the right to use the letters 'K' 'M' and 'G', then?

      No?

      There wasn't an internationally standardised unit of data storage until 2000. Until then, with no official standard meaning to the letters "KB", "MB" and "GB", they were available for use for whatever the innovators who started using them wanted them to mean. And they were first used with the meaning of 2^10, 2^20 and 2^30 bytes.

      think the whole lawsuit is silly. Who could have possibly been confused by the claims of hard drive makers? Those who are computer illiterate would assume that 1 MB = 1*10^6 bytes

      Those who are computer illiterate have little or no concept of what a byte is. They only know about file sizes by looking at what their computer tells them. And their computer (or at least the software installed on it) uses the binary definitions.

    12. Re:What a crock by Rich0 · · Score: 1

      Oh, right, so the SI are the only people who have the right to use the letters 'K' 'M' and 'G', then?

      No, but since the 18th century the prefixes have ALWAYS meant the same thing.

      Suppose personally-tailored medications take off and I start a business selling them. I define the term "high quality" to mean "completely counterfeit and likely to kill you". I get sued after 45 people die. I point out that nobody owns a monopoly on the english language. Am I right?

      Ignoring international conventions that are 200 years old is a recipe for confusion, which this issue completely highlights.

      There wasn't an internationally standardised unit of data storage until 2000. Until then, with no official standard meaning to the letters "KB", "MB" and "GB", they were available for use for whatever the innovators who started using them wanted them to mean.

      Ok, you have to pick one or the other. If no standard existed then why bash hard drive manufacturers for making up whatever they wanted to? If a standard existed then point to it.

      It seems like a lot of folks around here are arguing "SI, who do they think they are?" Uh, they would be the most recognized standards body on the planet. And for the most part they're actually interested in standards and not politics (unlike so many other standards bodies that promote technology standards that are patent-encumbered). The only thing they are really concerned with is making sure that everybody's meterstick is the same length, and that people use terms that are unambiguous.

      And they were first used with the meaning of 2^10, 2^20 and 2^30 bytes.

      And the people who decided to do things this way laid the foundation for all the current problems. What were they thinking, anyway?

      Most sciences/technologies deal in odd numbers. When they come up the usual solution isn't to just redefine SI prefixes to make the numbers nice and even. The solution is to round when appropriate, and just write out lots of digits when it isn't appropriate. Or to invent new units as convenience-units and register them with the SI.

      There is no real compelling reason that the computer industry has to use base-2 to measure things. Sure, at the implementation level it comes down to base-2, but for practical use I care more about whether I have 1GB or 20GB of disk space free, and less about the possible 10% error in the ambiguous definition of a gigabyte.

      The fact that SI took the side of the hard drive manufacturers should really tell you something...

    13. Re:What a crock by mpcooke3 · · Score: 1

      Uh, when you factor in partitioning, filesystems, etc, they're going to be disappointed no matter what.

      True, but I'd be lying if I claimed that most of the space difference was caused by partitioning and the filesystem block size. The biggest problem is drive manufacturers using a misleading unit to measure the disk space.

      The problem is that for whatever reason nobody in the IT world can agree on one set of units to use for everything. Most of the rest of the world formed SI for this reason, and for whatever reason IT had to do its own thing...

      This is just nonsense, the entire IT world except disk manufacturers has always used 1meg=1024bytes for *binary* storage devices it doesn't make any sense at all to use SI units when the underlying device is binary because the size of the disk only fits exactly if you work in Base2.

      With 10 bits you can store 2^10 different value which equals 1024 and *not* 1000. Perhaps you'd like us to stop using the last 24 values so it more conveniently fits into the SI scheme??!

    14. Re:What a crock by Rich0 · · Score: 1

      This is just nonsense, the entire IT world except disk manufacturers has always used 1meg=1024bytes for *binary* storage devices it doesn't make any sense at all to use SI units when the underlying device is binary because the size of the disk only fits exactly if you work in Base2.

      I am a part of the IT world. I do not have anything to do with disk manufacture, and never have. I prefer the use of SI units. So clearly there is debate. The fact that we're going back and forth about this only reinforces that there is debate...

      And not all storage devices fit on an address boundary (virtually nothing but ram chips do actually). And many that do don't need to out of engineering necessity.

      With 10 bits you can store 2^10 different value which equals 1024 and *not* 1000. Perhaps you'd like us to stop using the last 24 values so it more conveniently fits into the SI scheme??!

      No, use all 1024. Just don't call it 1.000KB - call it either 1KB (rounded off) or 1.024KB if you must be precise. Or just call it 1024 bytes. DNA has a pitch of 3.6nm - for some reason biochemists manage to deal with not being able to simply redefine the nm to make it come out at an even 4. Most professions have to deal with non-even numbers. The IT world has even managed to figure it out with floating data types...

    15. Re:What a crock by mpcooke3 · · Score: 1

      lol. The problem is if you keep rounding off, the extra 24's really start to add up after while!

      If you really do naturally think in SI units for digital data storage then just take pleasure in the fact that you get 24 extra free with every 1000 as a "bonus".

  29. how bout a refund for my macbook HD? by kabrakan · · Score: 1

    How about seagate gives me a refund for me and the many other people whose hard drive has crashed as a result of crappy hardware?

    --
    Slartibartfast:"Is that your robot?"
    Marvin:"No, I'm mine."
    1. Re:how bout a refund for my macbook HD? by Phroggy · · Score: 1

      How about seagate gives me a refund for me and the many other people whose hard drive has crashed as a result of crappy hardware? I believe you'll find that your dead hard drive is a Fujitsu. I just replaced the Fujitsu drive in my iBook with a Seagate. The Fry's salesguy seemed surprised at my refusal to buy Fujitsu, after the problems I've had with the last two (the original, and the one Apple replaced under warranty).
      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    2. Re:how bout a refund for my macbook HD? by kabrakan · · Score: 1

      Nope. Seagate momentus 5400.2 80GB. Although you're right, if you look at the very long discussion thread I posted a link to, that some of the busted hard drives are fujitsus, or other models of seagate HDs. So, it seems that it is more a problem of the macbooks frying the hard drives than the hard drives going on their own.

      --
      Slartibartfast:"Is that your robot?"
      Marvin:"No, I'm mine."
  30. Are you kidding me? by joe_n_bloe · · Score: 2, Insightful

    I understand that a "gigabyte" of RAM is 2^30 bytes, but that's just because memory addresses come in powers of two. I don't expect bytes on a hard disk to be counted in powers of two, because there is no need for them to be counted that way. But apparently there are some bargain-hunters and their lawyers who have a more self-serving style of counting.

    Oh well.

    1. Re:Are you kidding me? by Anonymous Coward · · Score: 0

      Why would you expect them to have a different base unit for memory and disk drives? That would be stupid. The real problem here is that they just put the fine print on the side of the box and the general public doesn't see it. If they clearly labeled the exact size in both base 10 and base 2 it would be much easier. All it would take is a line of text on the side with the specs saying (Usable disk space: 54.5GB) on a 60GB drive box.

    2. Re:Are you kidding me? by bestinshow · · Score: 1

      Well you can have your hard drive that is formatted with 500 byte blocks and has software struggling to handle things efficiently because of this.

      I'll take my block sizes in powers of 2 thank you very much. What is it now, 4KB per block - that's 4096 bytes btw.

      That's why hard drive capacities should be expressed using the defacto standard, not the imposed SI standard meaning of GB/MB/etc. However if the capacities were expressed in MiB, GiB, etc, that would be a fair compromise between the SI nerds and the desire to have an accurate capacity given.

  31. correction by hitchhacker · · Score: 0

    woops. 1GiB == 2^30 bytes, not 2^9.

    -metric

  32. ..this same issue by thebigbadme · · Score: 1

    frustrated me to no end when I went purchased a DVD±R ... and blank discs.

    I could not seem to fit exact files onto a blank disc when I had done intensive organizing to back up my entire recording database (I fix sounds to medium... sometimes this means I make music)...

    I called up the company that made the discs... which seemed like the faster route between that and getting out a magnifying glass to read some fine print that I hadn't known to look for in the first place. A half-hour later I was told they count how they do, and there was nothing I could do about it.

    DAMN THEM!

    So I sucked it up and did what Renton in Trainspotting does with the suppository....
    so to speak that is.

    Anyways, glad to see someone had some sense

    --
    "It's the Law of the Universe, and I'm the sheriff." Slash-cott 2/10-2/17
  33. Look again... by Anonymous Coward · · Score: 0

    'k' mean 1000, by definition and it did so for a long, long time. Reusing the term for something different is the first stupidity, claiming it is right is the second. Now, if you want to say 1024 bytes, there is a different term for that: 1kiB. Similarly, ISO-normed terms like MiB or GiB exist and are more and more accepted in the educated computer scene.

    Now, don't get me started on the meaning of a byte, which isn't 8 bits either....

    1. Re:Look again... by __aaxwdb6741 · · Score: 1

      I'm not sure, man. I sit in office with some pretty smart dudes - They're pretty hardcore - and really, they laugh at the MiB's that you claim they accept, because it sounds like candy.

      Any moron should know that kB = 1024B, 1kb=1000b

    2. Re:Look again... by darthflo · · Score: 1

      Thank you for introducing yet another extremely pointless irregularity. If we're going on like this, we could just use the French language instead of SI units, lots of irregularities there too.
      Seriously: Think about it for more than three seconds: What does the unit "kB" consist of? The prefix "k", representing "kilo", representing 1000 (in pretty much any counting system this wonderful world has to offer) and the unit "B", representing a byte, commonly representing eight bits? Interrupt me if I'm wrong, but isn't the only part that changes if you look at a "kb" instead the unit? Now we're talking about a kilo of bits, which would (logically) be exactly one eight of a kB? Why change that? Actually, why not americanize the system? Introduce inchbits, each being 2.54 bytes and footbits, short for 42/4 inchbits? We could also make it a bit less consistent by figuring in atmospheric pressure expressed in centi-headaches and the temperature expressed in drops of sweat per square gobblywock of skin per a 200th of the period of one of Jupiter's moons.

  34. (rubbing hands together) by nedder · · Score: 1

    So I have 6 Seagate drives, paid about $120 each = $720

    I get a 5% refund, or about $36 (assuming I can find 6 receipts).

    BFD.

  35. Given that the primary beneficiaries are lawyers by patio11 · · Score: 1

    ... you are two for two.

  36. SI by Kenoli · · Score: 1

    Oh, whoops. A byte is not a SI unit. The terms kilobyte, megabyte, etc. where just sort of "made up" based on SI prefixes.
    They're approximations of what would be their meaning if they were SI. It's too bad people can't just accept it.

    Why would a company advertise with "kilobyte = 1000", etc.?
    Obviously not because that's the correct meaning. The fact that they're the only ones that use it throws that right out.
    They just want to have a higher number on their box so it looks like their product has more memory that it really does.

    So what if they've been doing it for years? It's bullshit. Everyone should use the same definition. We can't magically make 2^10 = 1000, so guess who's got to change.

  37. Bubba Gump shrimp company was never the same... by Anonymous Coward · · Score: 0

    Management told him to take a hike. And that was the last we heard of him.

    At least his first-mate didn't run-off to Commodore...he wheelied to Apple.

  38. Not going to claim that refund by TheLink · · Score: 1

    I'm fine with Seagate saying that for their drives 1GB is 1000000000 bytes, since there is some technical justification for that. So I suppose their mistake was they didn't label their drives accordingly.

    Still, I have NEVER encountered a problem with this, whether at work or elsewhere. Who goes out and buys only 200GB of HDD storage if they know they need at least 190GB? I bet most slashdotters also knew HDD GBs were different ;).

    I'll feel cheated if the drives weren't reasonably reliable and died after only just over a year (just an example NOT saying that Seagate drives are unreliable or reliable). 5 year warranty or not, doesn't matter.

    So, though I have a fair number of seagate drives (I've maxtors and WDs too), I'm not going to claim a refund - I knew I was getting HDD GBs and bought them that way. Call me stupid if you want.

    --
    1. Re:Not going to claim that refund by networkzombie · · Score: 1

      I will not claim either, but mostly because Seagate made decent products. I say -made- because they bought Maxtor and I'm waiting to see if their manufacturing changes. Now if this was Maxtor, I would be fighting for every penny I could get from those bastards.

    2. Re:Not going to claim that refund by Nazlfrag · · Score: 1

      I bet most slashdotters also knew HDD GBs were different

      Yes, we know hard drive manufacturers were the first in the computer industry to disingenuously alter the meaning of first megabyte then gigabyte, and then the horrific SI kibibyte came out and we collectively have been howling in protest for about a decade. My solution? Don't mess with the roots of words by mangling them so hideously and you might have had a better reception. As it stands, that SI prefix will never be accepted by any proud computer geek. Just deal with the fact that the suffix bit or byte alters the SI definition of kilo, mega, giga, peta etc. See? That wasn't so hard now was it? Ever computer nerd for the last 50 odd years has managed it, I think scientists should be smart enough to handle it too.

  39. Re: Cold Days on the Sun by TaoPhoenix · · Score: 1

    Wikipedia says that the new Solar Cycle is beginning this year. Sunspots are slightly cooler areas on the sun.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  40. Concerning this Gibi nonsense by PaladinAlpha · · Score: 4, Insightful

    Ok, there's people everywhere in here saying it's stupid to say 1GB = 1024 MB, instead use GiB, blah blah, but I have an honest question: if everyone did, for whatever reason, use GiB and MiB and whatnot, of what use would MB and GB be? None, right? No one in their right mind would ever measure units on binary hardware in powers of ten. Just like I don't measure grams of soup or whatever in powers of two. I guess what I'm saying is if the switch to GiB and MiB was made in earnest then GB and MB would be utterly, completely useless -- and I see that as an argument that we might as well just use GB and MB, since it involves no conflict, fewer meaningless terms, and a more intuitive, uh, interface, if you will.

    1. Re:Concerning this Gibi nonsense by Aluvus · · Score: 1

      It's not merely that it's stupid to define "1 GB" as 1024 MB (which it is, but tolerably so), it's that defining it as "sometimes 1024 MB and sometimes 1000 MB, based on context" is really stupid. If the whole world decided that, now and forever, 1 GB is 1024 MB, that would be an improvement on the status quo. It would remove the ambiguity problem. It's an imperfect solution, but it gets the job done. However, it seems very unlikely that will happen any time soon (especially since every hard drive manufacturer and every system seller has now settled into using a footnote to define "gigabyte"). It looks like we are stuck with the status quo for a while.

      As for your claim that a switch in earnest to using GiB, MiB, etc. would make GB, MB, etc. (the base-10 definitions) useless, that is not true. Those meanings are used extensively (and consistently) in communications systems (for serial systems, Gb, Mb, etc. are usually used). It's only storage that has fallen into this particular quagmire.

      --
      Never mistake "can" for "should".
    2. Re:Concerning this Gibi nonsense by thue · · Score: 1

      No one in their right mind would ever measure units on binary hardware in powers of ten.

      The fact that on a low level computers are based on base 2 should have no consequence for the end-user. It should be a detail abstracted away by the operating system, like the fact that your CPU has N pipelines.

      The fact that deep down the computer operates using base 2 has no relevance for the end user when he is using it to store a 4.7GB DVD movie.

      Our whole system of measurements use base 10. No one in their right mind would use some hybrid base 2 system for showing enduser computer storage capacity, as we do today...

    3. Re:Concerning this Gibi nonsense by Anonymous Coward · · Score: 0

      Our whole system of measurements use base 10.
      well, yours and mine are, but those silly americans dont bother with base 10. how many inches in a foot? 12. how many onces in a pound? fucked if i know? why would you measure anything in lots of 28.xx grams, or 456 grams? they're a bunch of fucking monkeys who refuse to get with the program

      and to the first bitch who tries to tell me how their stupid-ass imperial units are better for reason X, how many inches are in a mile? how many gallons of water weigh 1 imperial ton (sp?) why is it that scientists who actually have to do real fucking work choose to work in SI units?

      I'll give you a hint, it's because your units are completely fucking retarded
    4. Re:Concerning this Gibi nonsense by Bee1zebub · · Score: 1

      The Americans don't even use normal Imperial units, for example, their Pints are 16floz rather than 20floz. And I bet thet you measure the insulation on your house in R-values, which are the most insanely f*cked up units imaginable, foot^2 x degree Fahrenheit x hour per British Thermal Unit. There are otehr areas where Imperial units, for example in quilting inches are used because 12 is divisible by 2, 3, 4, and 6, whereas 10 is only divisible by 2 and 5, and an foot happens to be a good size for blocks, and model-makers use a mixture of imperial and metric, depending on the context, but except for 1:100 models, the prototype is usually measured in feet, and model materials specified in thou or fractions of an inch. Then I bet your kitchen cabinets, adn probably most of the rest of your furniture, is specified in multiple of 150mm, or near enough to 6 inches.

      Metric was invented because several of Napoleon's senior officers were innumerate, and hte French had an even worse system than teh Imperial one.

    5. Re:Concerning this Gibi nonsense by metamatic · · Score: 1

      No one in their right mind would ever measure units on binary hardware in powers of ten.

      Tell that to modem and network hardware manufacturers.

      Why would you want to measure your file in base 10 units? So you can tell how long it will take to upload/download.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    6. Re:Concerning this Gibi nonsense by Selivanow · · Score: 1

      Of course Americans don't use Imperial units. Imperial units didn't exist until 1824, far after the American Revolution. Americans use something closer to the English system. We could use the metric system but then how could we confuse all of the foreigners who come and visit? Actually, the US is more "Soft Metric". Most things are labeled with metric in parentheses.... 12oz (355mL)

      I've heard rumors that someday this will be reversed......

      Oddly enough, Soda is frequently labeled in metric here....wierd.

      --
      -- ...trying to make digital files uncopyable is like trying to make water not wet. -Bruce Schneier
    7. Re:Concerning this Gibi nonsense by dan+the+person · · Score: 1

      No one in their right mind would ever measure units on binary hardware in powers of ten.

      Just because something is binary, it doesn't follow that it units abbreviations should be powers of two. So if people moved to GiB for power of two units, people would still use GB for power of ten units.

      There are plenty of things to measure in the IT context that use powers of ten, networking equipment always has used ^10 and disc storage uses it more often that not.

      Hence the need for separate unambiguous terminology.

  41. What came first you idiot? by SmallFurryCreature · · Score: 1

    Computers were working with powers of 2 LONG before HD's were invented.

    It is just the way things are done, and it seems pretty clear why HD makers use base 10 instead of what is widely accepted, it makes their drives seem bigger.

    I can't think of a single OS in 20 years of computing that does not go 1024 bytes is 1 kilobyte.

    Imagine if the entire world car used miles but suddenly the petrol industry decided to use kilometers instead. It would then look as if their distance per gallon was a lot better then it really is.

    It is a fraud and Seagate knows it, else they would have let it come to court. Stop being such a tool.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:What came first you idiot? by darthflo · · Score: 1

      Computers were working with powers of 2 LONG before HD's were invented.
      Yep. They were also working with NOT powers of 2 long before HDs (no apastrophe, ffs) were invented. Remember 1.44 MB floppy disks? Oh and just to have said it: nano ftw.
    2. Re:What came first you idiot? by Detritus · · Score: 1
      Many early computers worked with decimal numbers, even in memory addresses. For an example, see the IBM 1620. Base memory for the system was 20,000 decimal digits.

      What about OS/8? It used mass storage organized in 12-bit words. There use to be a wide variety of word-addressed systems that were not designed around 8-bit bytes and block sizes that were 2^N.

      --
      Mea navis aericumbens anguillis abundat
  42. Re:wow.... are you clueless! by Anonymous Coward · · Score: 2, Interesting

    Maxtor became crap shortly after the Quantum merger. They adopted Quantum's ways and their "No Quibble" warranty service went out the window shortly after the merger.

    Getting a replacement drive could take weeks if they didn't have your capacity in stock. Maxtor would just upgrade you and send you a drive right away. Sadly, most other driver manufacturers followed their lead. When Maxtor shortened their warranty to 1 year, Western Digital followed and others followed. Seagate started offering longer warranties and reversed this trend. What was worse was Western Digital would insist on going by the manufacture date instead of the purchase date for the start of the warranty. I'd have to complain to a supervisor before they'd admit to allowing a pad of 90 days. This was the best they'd do no matter what your receipt showed as the purchase date.

    I just had to have my Western Digital notebook drive replaced. It took them over a week to tell me I'd have to wait two more weeks for a replacement drive due to inventory not being available. The warranty was useless and I had to go out and buy another drive from another manufacturer. From now on, I plan to stick with Seagate.

    And, I too, will be declining any settlement owed to me for the Seagate drives I've purchased. Seagate is the best of the bunch and they don't deserve this.

  43. WRONG, they have not by SmallFurryCreature · · Score: 0, Offtopic

    They only started using base 10 relatively recently. I can't tell you the exact date things started to change, somewhere in the 90's but I am 100% certain that the first HD's for home computing labelled in base 2. They had to offcourse because it is only logical as EVERYONE else used that as well.

    Then some marketting genius probably noticed that their new disk was just shy of somemagic number in base 2, but reached it in base 10. But in the early days HD makers simply respected convention.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  44. Not a monopoly. by SanityInAnarchy · · Score: 1

    Thanks for the $5.99.

    Next time I buy a hard drive, if Hitachi, Maxtor, Western Digital, Dell, etc, has it for $5.99 cheaper -- the same amount of space; I'll be checking per byte -- guess where my money goes?

    With hard drives, I have pretty much no brand loyalty. If the drive fails, and it's under warranty, I get a new one, and if I wasn't backed up, that's my fault. If the drive fails, and I'm not under warranty, great excuse to get more space. I try to pay attention to reviews, etc, even the little Newegg things, but frankly, a hard drive's a hard drive -- it's pretty well commoditized now. I'll be paying much more attention to things like video cards and processors, even RAM.

    --
    Don't thank God, thank a doctor!
    1. Re:Not a monopoly. by j_sp_r · · Score: 1

      5 year warranty to 3 or 1 on other drives is a reason to pay $5,99 more

    2. Re:Not a monopoly. by Maxo-Texas · · Score: 1

      So you think with this precedent set, the same group of lawyers isn't going after the other hard drive makers yet?
      Using 1GB that way is common to other manufacturers as well. It has been for years. This is just some lawyer taking home a few hundred grand to a couple million while we get a coupon for free backup software or a couple bucks.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  45. Re:Given that the primary beneficiaries are lawyer by mikkelm · · Score: 1

    So I'm morally dishonest and technologically incompetent because lawyers make money off of litigation?

    How on Earth does that work?

  46. If the comments here make one thing clear.. by lpontiac · · Score: 1

    .. it's that there's no meaning of giga/mega/kilo that's solidly, universally accepted.

    The whole thing is a mess of attempted redefinitions (MB, MiB, the 1.44meg floppy abomination) and context-dependent exceptions with varying degrees of acceptance.

    If you really care, you should be checking the precise number of bytes.

  47. What? by msimm · · Score: 2, Insightful

    If a megabyte is counted as 1024 kilobytes how's your math working? Still 8 bits to a byte right? I mean I thought a byte was a byte, are you telling me a hard disk follows different conventions? Because last time I checked binary units were pretty stable, not a lot of 'wiggle room' in the interpretation.

    --
    Quack, quack.
    1. Re:What? by Anonymous Coward · · Score: 0

      I mean I thought a byte was a byte Yes, it is (duh !), but its size is undefined.

      Now if you would have said "octet" we would have known you ment eight bits. The size of a "byte" is dependant on the underlaying achitecture, and does not need to be eight bits.
      That its normally regarded as meaning eight bits is because of our current dominant use of x86 systems.
    2. Re:What? by Jah-Wren+Ryel · · Score: 1

      I mean I thought a byte was a byte, are you telling me a hard disk follows different conventions? Yes, hard disks follow the same conventions as data transmission like 100mbps ethernet. Fundamentally a hard disk is just a bunch of concentric rings of bits. The bits are divided up into groups, aka 'sectors' that include data payload, servo addressing, ECC and some other misc bits. The sizes of these sectors are almost never a precise power of two.

      RAM is pretty much the only hardware that is naturally sized in powers of two.
      --
      When information is power, privacy is freedom.
    3. Re:What? by Anonymous Coward · · Score: 0

      I don't know where you people got the notion that bytes are always 8 bits! I've worked on machine (yes, in modern times) that have 32- or 36-bit bytes. The PDP-10 had 5-bit bytes, others have had 9-bit bytes.

    4. Re:What? by joe_n_bloe · · Score: 1

      Yo, what he said.

      In particular, ECC turns things into convenient non power of size two lumps like, for example (from Wikipedia):

      - A standard 74 min CD contains 333,000 blocks or sectors.
      - Each sector is 2352 bytes, and contains 2048 bytes of PC (MODE1) Data, 2336 bytes of PSX/VCD (MODE2) Data, or 2352 bytes of AUDIO.

      When you factor in all the error correction, physical limitations of the media and hardware, and so on, the only place that powers of two really come into play is at the I/O block level, and at some point in the logical (but not physical) structure of the disk. This applies to absolutely everything that spins and holds readable data.

    5. Re:What? by joe_n_bloe · · Score: 1

      Not really. "Octet" is just one of those ITU-T neologisms that is designed to carry with it no preexisting meaning. The term was invented as part of the process of writing telecommunications standards documents. "Octet" specifically does mean "eight bits," but it does in no way mean that the word "byte" doesn't also mean "eight bits." Practically speaking, in 2007, as well as in 1997, and 1987, and 1977, "byte" was still "eight bits." Aggregations of bits in funny non power of two formats were usually called "words" (along with larger grouping of bytes).

      It's not that you can't find exceptions to this rule, but as a practical matter, they don't exist.

      ITU-T is the International Telecommunications Union - a standards organization belonging to the United Nations.

  48. My Salary Calculation by bangzilla · · Score: 2, Funny

    I received an offer letter for employment many moons ago that stated that my salary would be "$65k" - When they tried to pay me $65,000 a year there was hell to pay (so as to speak). We settled on $66,560 :-)

    --
    Rich people are eccentric. Poor people are strange. Me, I'd be happy with odd.
  49. um... precedent? by ephedream · · Score: 1

    So... does this mean that all other hard drive companies are now open to being sued?

    Will Seagate now advertise all its HDs with the incorrect binary prefix?

    WTF is wrong with the trial judge? If Seagate wanted to advertise Gibibytes, then they would have written GiB! That's why they wrote GB instead! Is this not totally simple? What else were they supposed to write?!?!? They were technically correct in advertising the total disk space. I don't understand the judge's reasoning.

  50. Let's break down who's on what side here by fo0bar · · Score: 4, Interesting
    Base 2:
    • Operating systems/software
    • Memory
    • Flash storage (CF, etc)
    • PROMs
    • CD media
    Base 10 (LAWSUIT TARGETS):
    • Evil, evil hard drives
    • Bandwidth-related hardware:
      • Line cards
      • Ethernet interfaces
      • Modems
      • Your broadband provider's advertised line speeds
    • DVD media
    • HD-DVD media
    • Blu-Ray media
    • Most (not all) USB stick-style flash storage devices
    • Digital cameras' resolution
    • CPU clockrate (I thought the argument against base 10 was "computers" were natively base 2)
    • Latency (opposite of kilo, of course -- 1millisecond is not 1/1024 second)
    A weird hybrid between the two:
    • Floppy disks
    Units of measurement that use an international SI standard's prefix to describe something "close enough" but not equal to said international SI standard's prefix:
    • byte
    Units of measurement that use an international SI standard's prefix:
    • hertz
    • pixel
    • gram
    • meter (or metre, it's all good)
    • watt
    • volt
    • newton
    • ohm
    • joule
    • pascal
    • lux
    1. Re:Let's break down who's on what side here by Repossessed · · Score: 1

      Given that you are never in a million years going to get better than 80% of the advertised bandwidth (at the very least, packet loss will ensure that), I'd say going after bandwidth people for gigabits being in base 10 is pointless. (I get about 4 Mbit of Comcast's advertised 6 Mbit, and consider myself lucky to have that much, it was three for a while).

      For the most part though, only places were there is a discrepancy in how people measure do you see a real issue, nobodies camera software pops up and tells them they have 5.7 megapixels instead of the 6 they payed for, but I have to deal with explaining to people at work (tech support) why they're new 320 Gigabyte drive is showing as a 292 in Windows (part of that is partitioning).

      I hope Seagate appeals this though, I'd like to see them not have to pay (they're hardly the only ones doing it, and shouldn't be persecuted, at least not unless everyone else gets hit too (not just drive manufacturers, but OEMs as well). I would, however, like to se a higher court judge set a more major precedent (and ruling, for the area in question) that might force all manufacturers and OEMs to be honest about these things.

      --
      Liberte, Egalite, Fraternite (TM)
    2. Re:Let's break down who's on what side here by Draco_es · · Score: 1

      Bandwidth has been always counted on bits per second not bytes, so there is no reason for using base 2 notation there(never has been). Changing Mbps to MBytes/sec would confuse users more than anything (my ADSL has been downgraded from 12 to 1.43!!!)

    3. Re:Let's break down who's on what side here by Tuoqui · · Score: 1

      For the record latency is a unit of time which you are measuring in fractions of how much it takes the earth to rotate 360 degrees. As a result we have one revolution split up into a fraction of 24 which we call hours and into 1440 which we call minutes and 86400 which we call seconds. But its alright we'll split the second into SI units of millisecond, microsecond, nanosecond and picosecond.

      As for your base 10 list in a more serious manner...

      Seconds are a unit of time which is built on a non-SI system until you get down to divisions of seconds.

      Clockrate is measured in hertz this is true but the internals of the system uses base 2 for everything. This is why RAM is listed in base 2 notation and why Hard Drives used to be.

      As for bandwidth related things, all of those are marketed as 'Up to' a certain speed. You never ever get those 'up to' in a real world scenario because line quality, distance and other factors will sap away potential. Also many of the broadband providers say you have a 512Kb/s line and frequently you can see your downloads doing well over that at least up here in Canada depending on the time of day though.

      --
      09F911029D74E35BD84156C5635688C0
      +2 Troll is Slashdot's way of saying groupthink is confused
    4. Re:Let's break down who's on what side here by jez9999 · · Score: 1

      Base 10 (LAWSUIT TARGETS):

      Don't forget to mention that all these measurements are being prefixed in MB, etc. rather than MiB, so the base 10ers are technically correct.

    5. Re:Let's break down who's on what side here by prockcore · · Score: 1

      This is why RAM is listed in base 2 notation and why Hard Drives used to be.


      The very first harddrive, from 1956 had exactly 5 million bytes. Where's your base2 now?
    6. Re:Let's break down who's on what side here by Anonymous Coward · · Score: 0

      Base 2:

              * Operating systems/software

      Modern Linux distros use IEC prefixes (Mebi-, Gibi-).

      * Flash storage (CF, etc)

      All of my Flash Memory cards and USB storage use decimal prefixes. 1GB cards have a little bit more than 10^9 bytes.

    7. Re:Let's break down who's on what side here by Nazlfrag · · Score: 1

      So SI can use base 24 for hours, base 60 for minutes and seconds yet can't handle base 2 for bits? As for your 'against' list, let's look.

      - Evil, evil hard drives
      Yep, they started it.

      - Bandwidth-related hardware:
      Like hard drives, this didn't used to be the case.

      - DVD media
      - HD-DVD media
      - Blu-Ray media
      If CDs can do it right, why not these?

      -Most (not all) USB stick-style flash storage devices
      So there are still some honest players left in that market.

      -Digital cameras' resolution
      No big issue, as they usually refer unambiguously to millions of pixels in their documentation, unlike HDDs, flash sticks etc.

      - CPU clockrate
      - Latency
      Both measure time, not bits or bytes. No issue there.

      So all that needs to happen is harddrive, optical and flash media manufacturers come in line with what the rest of the entire industry has been doing for decades, and there is no issue. It just makes sense to use base two in computing, like it makes sense to use base sixty in time measurements.

    8. Re:Let's break down who's on what side here by Anonymous Coward · · Score: 0

      add to the "Units of measurement that use an international SI standard's prefix:"

      bits

      which covers anything to do with bandwidth (always measured in bps = bits per sec.).

      which brings up the point: why didn't HDD manufacturers just measure in Mb, Tb etc.? that would have solved the confusion, since the pople they were trying to fool with the inflated numbers would ot have noticed the difference between MB and Mb...

    9. Re:Let's break down who's on what side here by Anonymous Coward · · Score: 0

      Well, the reasoning behind using base 2 prefixes for computer memory is that the hardware is fundamentally base 2 digital logic. That can't be changed. And while how much you fit on a hard drive platter is arbitrary, you're reading and storing base 2 data in base 2 quantities from base 2 machines through base 2 controller chips, so the drive capacity measurements really should be in base 2.

      Clock speeds, transfer rates, and latencies are measures of frequency, and they have nothing tying them to any particular number base. The CPU clock runs off of a pulsing bit of quartz, just like my wristwatch does, and the number of pulses per second doesn't have to be a power of two, and we don't ever have to compare it to some other base 2 numbers so it doesn't matter. Transfer rates are bound by signal:noise ratios in their medium, and bound by the clock speed of the equipment on each end, so, again, there's nothing really forcing it to be in base 2.

      You could indeed make a convincing argument that since, like with hard drives, the data going to and from the network cable is base 2 and therefore the network transfer rate should be labeled in base 2, but you could also make the counterargument that it doesn't matter as much because it's a time-based medium that is mostly idling anyway.

    10. Re:Let's break down who's on what side here by Rich0 · · Score: 1

      So SI can use base 24 for hours, base 60 for minutes and seconds yet can't handle base 2 for bits?

      Yes, but they would be right to complain if somebody started calling minutes centihours, or hectoseconds. A month could be a kilohour.

      And the Americans could be metric after all - miles could be kilofathoms.

      So now kilo could mean anywhere from 500ish to 1500ish, and we'd just know what factor to use based upon the application. Isn't this metric system easy?

      The whole point of the metric system is that EVERYTHING uses the standard SI prefixes - in powers of 10. For whatever reason we tolerate seconds, minutes, hours, and days, but I don't think that every new discipline that comes along should go ahead and violate the SI. Switching to metric can be a painful transition - why on earth would we invent new disciplines that AREN'T metric already?

      SI's complaint wasn't that IT folks were using powers-of-2. Their complaint was that they were using the SI prefixs to mean something different than what they mean EVERYWHERE else. The SI doesn't complain about Americans measuring stuff in miles, but they would complain if they just redefined the meter to equal the yard and the kilometer to equal the mile (with the kilo prefix now being an easy-to-remember 1760).

    11. Re:Let's break down who's on what side here by Rich0 · · Score: 1

      And while how much you fit on a hard drive platter is arbitrary, you're reading and storing base 2 data in base 2 quantities from base 2 machines through base 2 controller chips, so the drive capacity measurements really should be in base 2.

      I don't see how one follows the other.

      The numbers in my spreadsheet are probably stored as some crazy combination of binary mantissa and exponent with signs and twos-complement and all that - and yet we just display them in good-old base 10.

      Sure, back when drive sizes tended to fall on addressing boundaries the distinction probably mattered more (sticking a huge drive in a computer with 16-bit sector addressing would be wasteful). However, these days everybody is thinking 64- or even 128-bit - it will be a while before hard drives catch up with the addressing schemes like they used to back in the 90s.

      Everything your computer does is in base-2. Even the clock counts in base-2 - just so far to the right of the decimal point that you don't notice it (sure, the ticks might come at some odd interval, but the actual time calculated after any tick is rounded to a power of 2 at some point). Software is just kind enough to store more precision than is rendered on-screen so that when you type in 12.3 you don't see 12.299999999999999964532 show up (or whatever it ends up being stored as internally).

      Considering that 99% of the time use of disk space is presented to the user in rounded form, why not go ahead and just use the SI units? If a filesize of 18.2 MiB is good enough, then a size of 18.3MB should be fine too. If somebody really cares about a difference of 1% then they'll want to know that the file size is 18221048 bytes (plus x bytes of allocated empty space).

  51. I've told you once... by wildsurf · · Score: 1

    I've told you once, I've told you 1,073,741,824 times: don't approximate!!!

    --
    Weeks of coding saves hours of planning.
  52. Re:wow.... are you clueless! by Calinous · · Score: 1, Interesting

    Next time when I buy a kilogram of sugar, I will insist to be made from 1024 grams. I will request auto manufacturers to give the fuel efficiency in liters per 100 (1024 meters). Why wouldn't nuclear weapon yield be measured in equivalent of (1024 tons) of TNT?
          Seagate don't deserve this. Hell, nobody doesn't deserve this (even if now when we reach 1TB, the difference between 10^12 and 2^40 is just a smidge under 10%

  53. Free backup software? Great... by Hanners1979 · · Score: 1

    Now I can back up the data I couldn't store to space I don't have.

  54. About Time! by Orphaze · · Score: 1

    I could care less about the ~$5 rebate, I'm just happy to know that Seagate (and hopefully other manufacturers) will be using the correct definition from now on. I know it's relative, but every year it seems like I'm losing more space on new drives. The 35 "missing" gigabytes from a 500GB drive is definitely a sizable chunk of storage.

  55. idiots ? ignorants ? no, "professionals" by l3v1 · · Score: 1

    I really miss the days (and I'm only in my twenties) when everyone just accepted what in computer-land kilo/mega/giga/terra bytes mean, and how and where they are used in which ways, and just went along to live their lives end of story. But then, a gazillion members of sixpack professionals came along who always know better, and they just couldn't stand the use of a system besides their good old 10-based. So they created the kibi, the mibi and the gibi, the three little moron ducklings whose names can't even be whispered without an idiotic smile. Better yet, they even tell you you're a f*cking moron if you don't use their names. Well, there is strength in numbers indeed, so fight or flight. What I've kept saying is, the sixpacks have time to argue about this, the rest of us just keep working, knowing what we mean by what we say in what context, and mind our own business. Let the rest keep arguing about non-issues that they made issues by their infinite wisdom. About suing Seagate, well, we all know there are certain people on this planet whose only goal in life is to find reasons to sue someone for their cash.

    As a sidenote, if I were to hire someone who'd keep arguing about this topic, I'd kick his ass so far away I'd never have to see it again until I'm ninety years old and don't give a flying f*ck anymore.

    --
    I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
    1. Re:idiots ? ignorants ? no, "professionals" by Anonymous Coward · · Score: 0

      Oh, you twenty-something miss those days, huh? So, tell us old-timers, what *does* byte mean?

  56. But what about the tape backup business? by Anonymous Coward · · Score: 0

    They're usually market their products with how much compressed data their products will store. (2x physical capacity) That doesn't work with my pr0n folder...

  57. What software? by will_die · · Score: 1

    Could not see it in the article but does anyone have information on the software that will be provided?

  58. Re:Given that the primary beneficiaries are lawyer by patio11 · · Score: 1

    I meant "You made two predictions and were correct on two of them". But I suppose it could work the other way, too, if you were a lawyer.

  59. Re:wow.... are you clueless! by kongit · · Score: 1, Insightful

    Well no, they do deserve this. The actual capacity of the hard drives is not what is specified; unlike in your examples where a kilogram of sugar is a kilogram of sugar: what Seagate (and other companies) say is 1GB is not 1GB. While I like Seagate hard drives, I am following this for the software -- which I will never use -- because I think all digital storage manufacturers should use the correct measurement. The only reason I can think of the for the current manufacturer's measurement is retail. Their current method makes hard drives appear to have more space then they really do.

    If we ignore this and Seagate has to do hardly anything, all the other manufacturers will see that people don't care that they are getting cheated and will continue selling their products with false information.

  60. Perhaps we don't have to ... by SplatMan_DK · · Score: 1

    Why rewrite all software, and god forbid, patch all old software going back however many DECADES into the past to implement this change, when harddrive manufacturers could simply start labelling their drives correctly? Perhaps we don't have to. Perhaps it would be easier to correct the error on the graphical output of the computer, controlled by a setting in the system BIOS.

    Imagine a new setting in your onboard system BIOS menu.

    When "Use Moronic Byte Values" is enabled, a specially designed add-on GPU could graphically scan pixels for evidence of byte values displayed to the user. It would then alter the graphical output to the any number of Moronic Byte Value systems, including the famous "Moronic Kibibyte" (which replaces Kilobytes with Kibibytes, Megabytes with Mebibytes, etc) or the less-known "Moronic SI Recalculation" (which scans the numbers, recalculates them into SI units, and replaces the original value with the moronic SI value).

    If produced as a standard chip, any vendor of graphical adaptors would be able to embed it into their products. There could even be a spin-off industry where the concept is applied to internal or external adapters with VGA plugs (like the old Voodoo VGA loopback cable) in order to ensure that older computers could benefit from this great innovation?

    Hell ... I love the idea already. I can't decide if I should submit it as a new open standard, or patent it...

    - Jesper
    --
    My security clearance is so high I have to kill myself if I remember I have it...
  61. It started in 1992... by redstar427 · · Score: 1

    I remember when this started, I believe it was 1992.

    It was at the time of the 120 MB hard drives.
    Most manufactures would sell a drive larger than 120 MB, such as 124 MB, which was the nearest size of the drive, that matched the platers total, and was at least 120 MB.
    For example: 124 MB = 130,023,424.
    Well, one brand, I think Maxtor, called that 130 MB.

    IIRC there was a threat of a lawsuit, and soon Maxtor stated on the boxes of their drives, that 1 MB = 1,000,000.
    Soon after that, it seemed all the hard drive manufacturers did the same.

    I think the confusion continues today, because other types of memory, such as 1 GB ram is a true binary Gigabyte = 1,073,741,824.
    Plus, as many have stated already, when a hard drive is formatted on a computer, it shows binary Gigabytes, and does not use the marketing-speak of a decimal gigabyte.

    Since the hard drives are used in computers, which use binary numbers for all types of memory, all manufacturers should be required to use the same.

    --
    "Two things are infinite: the universe and human stupidity; and I'm not sure about the universe." Albert Einstein
  62. Re:wow.... are you clueless! by name*censored* · · Score: 1, Informative
    For starters, you could easily get an extra 24g of sugar (just as easily as you could get 24g less), whereas with hard drives you'll always get the same number of bytes in every identical model. Secondly, it'd be closer to buying a bag of sugar advertised as 1kg when it's really 2 pounds of sugar, or buying a car with an advertised fuel efficiency of 16 L/100mi when it's really 16 L/100km. Thirdly, computers work in base 2, so it makes sense to make disks in base 2 (unlike cars/explosives/sugar, which work in base 10).

    I think it's about time that hard disk advertisers started claiming responsibility for what is perhaps the only unit disparity of it's kind (nothing else fudges the definition of a measurement unit to save a few bucks, as far as I'm aware). It's doubleplusgood that it's Seagate who's doing it, considering that they're leading the field and therefore will (hopefully) set an example to WD/Samsung/etc.
    --
    Commodore64_love: I don't comprehend people who're so frightened of death that they'll bankrupt themselves to stay alive
  63. Re:wow.... are you clueless! by pipatron · · Score: 3, Insightful

    Apparently you didn't understand what we are talking about here, and what the parent argued.

    The SI-prefix G has always been 1,000,000,000. When you buy a hard drive with one gigabyte of storage capacity, it will always have a little bit more than this, due to cylinders/sectors/platters rounding. When they sell a hard drive with 500 gigabyte, it will have slightly more than 500,000,000,000 bytes. No one is trying to fool anyone here.

    Now, if you go to the store and want to buy one gigagram of sugar, you expect to get no less than 1,000,000,000 grams. Anything else would be cheating. But when you go to the store and want to buy one gigabyte of storage, you suddenly expect to get a lot more?

    --
    c++; /* this makes c bigger but returns the old value */
  64. This is Nonsense by Lachlan+Hunt · · Score: 2, Informative

    The whole hard drive industry quotes storage capacities in base 10 SI units. Just because some ignorant consumers don't understand the difference between a Gigabyte and a Gibibyte doesn't mean that Seagate should have to pay for their ignorance. The customer got what he paid for. He should instead sue Operating System vendors for calculating storage capacities in base 2 and reporting as GB instead of either calculating in decimal or reporting as GiB.

    --
    By reading this signature, you hereby agree with the content of the above comment.
    1. Re:This is Nonsense by swordgeek · · Score: 1

      Bullshit.

      The whole base-10 kibi/gibi/mebi crap was a retrofit into a system to justify hard drive manufacturers misleading people.
      1MB RAM = 1MB ROM = 1MB cache = 1MB transfer speed unit != 1MB disk space. Who should change here? Hint: It's the industry who had the most to gain in sales by changing their definition.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  65. Chicken or egg? by leehwtsohg · · Score: 1

    Notice that the SI standard was published in 1998, and IEEE accepted these new units in 2005.
    Hard drive manufacturers have been fooling the public for much longer than that.

  66. Keep SI consistent! by paaki · · Score: 1

    What good is an international standard (SI) if it's not homogeneous? I personally love the binary prefix and will try to start using it even more in daily speech.

    1. Re:Keep SI consistent! by Anonymous Coward · · Score: 0

      Homogeneous to what??? There is no SI unit for megabyte, etc. Base-10? What about time? How many seconds in a "mega-minute"? Should we change that to be in powers of 10?

    2. Re:Keep SI consistent! by paaki · · Score: 1

      I was referring to the prefix. I mean for nothing is to be changed - except the misconception that when referring to bytes, mega means 2^20. 1 megaminute is, have "always" been, and will always be 1.000.000 minutes (minute is however not an SI unit, but i think the term megaminute is fairly correct, technically speaking).

  67. So if accuracy is needed by Anonymous Coward · · Score: 0

    It isn't a "160Gb" Hard drive anyway. It's probably 167,284,512,048 bytes.

    Because the drives use "512 byte sectors" and so fitting in 160 billion bytes doesn't take a whole number of sectors.

    That is merely one refutation to your statement that there's no technical merit behind using "1024=1k".

    1. Re:So if accuracy is needed by BillyBlaze · · Score: 1

      There's technical merit behind using powers of two. No shit. The technical merit is lacking in the practice of abusing existing terminology that refers to powers of 10. We should have made up our own words from the start. We fucked up. Thus we don't have a right to whine.

  68. Re: "Common usage" ... by Joce640k · · Score: 1

    You ask anybody* on the street how big a file with 1,000,000 bytes is and they'll say "a megabyte", or maybe "a gigabyte" if they're clueless.

    NOBODY except the most anal uber-geek will say "oh, that's about 0.95 megabytes".

    * {Well, anybody who knows the basics of using a computer)

    --
    No sig today...
  69. oh brother by Anonymous Coward · · Score: 0

    another class action suit where the lawyers get rich, a few people get a check for a couple cents, and the rest of us eat higher hard drive prices...can we class action sue the class action lawyers?!

  70. Even in metric britain by Anonymous Coward · · Score: 1, Interesting

    where you buy planks of wood, it'll be "1720mm" long. Which, oddly, is exactly 6ft.

    How many scientists are there in the world? Who needs to calculate how many 30cm tiles are needed to stretch 2km? OK, the calculation is easy. then again, how many 1ft tiles does it take to cover 20ftx10ft ceiling? Just as easy a calculation.

    1. Re:Even in metric britain by Anonymous Coward · · Score: 0

      metric britan? give me a fucking break? a country cant call itself metric just becuase it put metrics units on things. as long as your milk still comes in pints and your road signs are in miles you're not metric

  71. 6.2 million or 6.5 million? by Anonymous Coward · · Score: 0

    With all the debating going on whether harddrive (correct) or memory (incorrect) interpretations of labels, I have a good example of the confusion it can cause if people start listening to "a million is more than a million" stuff.

    The article says Seagate refunds 6.2 million hard drives. There is no doubt that they mean 6 200 000 hard drives.
    However, if people start having varying definitions of M (SI unit for million, 1 000 000) we might end up with a world that thinks they perhaps meant 6.5 million drives.
    6.2 confusing M * 1024^2 ~= 6.5 real world million
    That would be a world with the memory manufacturer definition of M.

    Good practice would be for software developers to learn the difference. BitTorrent/Tornado and DC++ are two softwares which I know have implemented the binary SI units.

    Don't redefine mathematical entities, please.

    --
    [Non-]anonymous coward MMN-o

  72. 1GB is really 1,000,000,000 bytes by OrangeTide · · Score: 3, Insightful

    They were using the correct measurement. Why don't you sue Intel and 3COM because your 100Mbps ethernet card is actually 100,000,000 million bits per second.

    The problem is some OS vendors, like Microsoft, incorrectly report the drive size using a strange base-1024 system. While this system might make sense for RAM which due to technical reasons must be a power of 2. (due to binary encoding for the addressing and inability to support "gaps")

    Also it's not false or misleading if everyone knows what is being done. And did you overlook that * on the box that says "* 1GB is 1,000,000,000 bytes."

    --
    “Common sense is not so common.” — Voltaire
    1. Re:1GB is really 1,000,000,000 bytes by LocalH · · Score: 1

      Why is it suddenly incorrect for hard drives when, except for 1.44MB diskettes, the advertised capacity of most mainstream disk formats (at least for 8-bit micros) was correctly identified in the binary units? You're telling me that Windows should display sizes for floppies in different units than hard drives? That 720KB diskettes should report at 737KiB?

      --
      FC Closer
    2. Re:1GB is really 1,000,000,000 bytes by LocalH · · Score: 1

      Yeah, slight correction, I wrote KiB when I shouldn't have. I haven't woke up fully yet.

      --
      FC Closer
    3. Re:1GB is really 1,000,000,000 bytes by AvitarX · · Score: 1

      I think the OS should report GiB and KiB and MiB as such. Let the HD manufacturers do as they please using GB or GiB. Then everything reports accurately and no one is lieing. People who don't know the difference are then just people who don't know, and the OS is accurately reporting information.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    4. Re:1GB is really 1,000,000,000 bytes by Spleen · · Score: 2, Insightful

      In the old days we learned:
      1 Byte = 8 bits
      1 kilobyte = 1024 Bytes
      1 megabyte = 1024 kilobytes
      1 gigabyte = 1024 megabytes
      1 terabyte = 1024 gigabytes
      Which means that: 1 gigabyte = 1073741824 bytes This isn't a strange "Microsoft" scale. If you've ever watched your memory count on boot it uses the same scale. Harddrive manufacturers for as long as I can remember have not used the correct scale, but the hardware and OS's do. They've also had a notice on the packaging that states the scale they measure by, and probably on their website too. I never liked that they didn't follow the correct scale, but its a stupid lawsuit.

    5. Re:1GB is really 1,000,000,000 bytes by tilandal · · Score: 3, Insightful

      A bit is not an SI unit. A Byte is not an SI unit. A GB and a Gb are not accepted SI notation. Each has its own accepted context. A bit is a base 10 unit a byte is a base 2 unit. If you want to report your storage space in bytes it is accepted that you are reporting in base 2. If you would rather report in base 10 thats fine. You can advertise 8Gigabits, You can advertise 1 Billion Bytes, but you can not say that a GB is anything other then 2^30 bytes.

    6. Re:1GB is really 1,000,000,000 bytes by BillyBlaze · · Score: 1

      Interestingly, according to Wikipedia, the formatted capacity of a floppy is actually 1.44 kibi-kilobytes.

      I'm adding "kill the first person to use SI prefixes for powers of 2^10" to my list of things to do when I get my time machine.

    7. Re:1GB is really 1,000,000,000 bytes by Calinous · · Score: 1

      Very well. One of the computers from here have 11111100000000000000000000000 bytes of RAM. My computer here have a hard drive capacity of 10011000100101101000000000 bytes.

            This is reporting in base 2. Have fun

    8. Re:1GB is really 1,000,000,000 bytes by tiker · · Score: 1

      A few companies got away with using the meg / gig terms rounding off... once a few got away with it the rest started following.. For example, Sandisk flash storage cards all round down the same way. Their website indicates that their term gig = 1,000,000,000 bytes. That caused me a lot of problems trying to use their product for a proprietary file system which corrupts if it's not the true size. I personally hope Seagate loses this and I hope other storage companies smarten up from this.

    9. Re:1GB is really 1,000,000,000 bytes by Wolfrider · · Score: 1

      > Harddrive manufacturers for as long as I can remember have not used the correct scale

      --Yup; if I ever buy a 500-gig HD, when I put (2) of them together I want an ACTUAL TERABYTE OF STORAGE, not 900-odd Gigabytes!!

      --I totally HATE the way HD manufacturers are ripping me/us off on storage capacities anymore. 320GB should be 320*1024*1024!!!

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
    10. Re:1GB is really 1,000,000,000 bytes by Sangui5 · · Score: 1

      a bit is a base 10 unit

      Good luck finding a 1 megabit memory IC that has only 1,000,000 bits of storage...
    11. Re:1GB is really 1,000,000,000 bytes by Physics+Dude · · Score: 1
      if I ever buy a 500-gig HD, when I put (2) of them together I want an ACTUAL TERABYTE OF STORAGE, not 900-odd Gigabytes!!

      Um... if you want a terabyte when you put them together, you better start with two 512 Gig hard drives instead. ;)

      Personally, I'm used to and prefer kB == 1024bytes and MB == 1024kB etc. because that was their ORIGINAL meaning. Those quantities were never used as even powers of ten until the marketers of hard drives started marketing using these terms.

    12. Re:1GB is really 1,000,000,000 bytes by ttfkam · · Score: 1

      Math and, later, CompSci folks invented the concept of a byte, but they did not invent the prefixes kilo, mega, etc. Those were already in common use before the first electronic computer with vacuum tubes was a glimmer in Alan Turing's mind.

      Their ORIGINAL meaning corresponds to the SI standard. Early computer folks used those prefixes INCORRECTLY to approximate the amount of memory/storage in use because 2^10 is close to 10^3. The approximation made it easier to grasp for the base-10 mind, but it's still just an approximation. Unfortunately, as seen here, the approximation became blind dogma.

      EVERY OTHER FIELD OF STUDY uses kilo- to signify one thousand and mega- to mean one million. When one industry uses a term one way and thousands of other industries all use a term in a consistent but different way, what justification can you give for the single inconsistency.

      You don't need to rewrite all of your software. Just start writing MiB instead of MB from now on and accept the inconsistency in older software. It's really not that hard to change and it will work itself as older software fails to the wayside.

      Pop quiz: how many bits per second are theoretically transmitted by a GigE network adapter?
      Hint: it's not a power of two.

      Even our own industry can't get it straight.

      --

      - I don't need to go outside, my CRT tan'll do me just fine.
    13. Re:1GB is really 1,000,000,000 bytes by ttfkam · · Score: 1

      Good luck finding a 1 gigabit network adapter that transmits 1,024 megabits of data.

      --

      - I don't need to go outside, my CRT tan'll do me just fine.
    14. Re:1GB is really 1,000,000,000 bytes by ttfkam · · Score: 1
      Bits and bytes may not be SI units, but the prefixes kilo-, mega-, giga-, tera-, etc. most certainly are specified by SI.

      Quoting from the NIST page on binary SI units:

      Once upon a time, computer professionals noticed that 210 was very nearly equal to 1000 and started using the SI prefix "kilo" to mean 1024. That worked well enough for a decade or two because everybody who talked kilobytes knew that the term implied 1024 bytes. But, almost overnight a much more numerous "everybody" bought computers, and the trade computer professionals needed to talk to physicists and engineers and even to ordinary people, most of whom know that a kilometer is 1000 meters and a kilogram is 1000 grams.

      Then data storage for gigabytes, and even terabytes, became practical, and the storage devices were not constructed on binary trees, which meant that, for many practical purposes, binary arithmetic was less convenient than decimal arithmetic. The result is that today "everybody" does not "know" what a megabyte is. When discussing computer memory, most manufacturers use megabyte to mean 2^20 = 1 048 576 bytes, but the manufacturers of computer storage devices usually use the term to mean 1 000 000 bytes. Some designers of local area networks have used megabit per second to mean 1 048 576 bit/s, but all telecommunications engineers use it to mean 106 bit/s. And if two definitions of the megabyte are not enough, a third megabyte of 1 024 000 bytes is the megabyte used to format the familiar 90 mm (3 1/2 inch), "1.44 MB" diskette. The confusion is real, as is the potential for incompatibility in standards and in implemented systems.

      Faced with this reality, the IEEE Standards Board decided that IEEE standards will use the conventional, internationally adopted, definitions of the SI prefixes. Mega will mean 1 000 000, except that the base-two definition may be used (if such usage is explicitly pointed out on a case-by-case basis) until such time that prefixes for binary multiples are adopted by an appropriate standards body.


      Bold items are my own emphasis.
      --

      - I don't need to go outside, my CRT tan'll do me just fine.
    15. Re:1GB is really 1,000,000,000 bytes by Doctor+Morbius · · Score: 1

      It wasn't some OS vendors. 1024 = 1K, when referring to memory, has been used for at least 30 years. When I bought my first Apple II in 1978 it had 64KB of memory. I knew that it really had 65,536 bytes not 64,000. When computers came with 1MB of memory everyone knew that it really meant 1,048,576 bytes not 1,000,000. The confusion began when some marketing scumbag figured out he could scam people into thinking that hard drives had more storage than they really had. Now because of it we have to deal with nonsense terms like Gibibytes. I'm happy that Seagate got sued and lost and now has to pay millions of dollars. They deserve it.

      --
      If I disagree with you it's because you are wrong.
    16. Re:1GB is really 1,000,000,000 bytes by Anonymous Coward · · Score: 0

      Early computer folks used those prefixes INCORRECTLY to approximate the amount of memory/storage in use because 2^10 is close to 10^3. The approximation made it easier to grasp for the base-10 mind, but it's still just an approximation.
      The early computer folks used these terms prior to the establishment of the SI, and there is no approximation or "base-10 mind" shit going on. 1024 was chosen for matters of convenience, just as was 1000 in the SI system(both allow you to dispense with 3 digits in your representations of quantities). If computing people chose 1000 to be a kilobyte, then they would constantly be speaking of 1.024 kilobytes which would render the entire exercise pointless. The prefixes were used for convenience remember, so that people do not have to constantly write out zeros as place holders. In computing it makes far more sense to use them to represent powers of two so that people do not have to be constantly writing them out.

      By the way, the byte was invented and popularized by early computing engineers at IBM, not math people.

      Additionally, you are right that computing used the prefixes differently than all other disciplines, but this is because computing is different that all those other disciplines. It is closer to mathematics(where the SI prefixes are not useful for much at all) than it is to physics(where the SI prefixes are very useful).
    17. Re:1GB is really 1,000,000,000 bytes by jedidiah · · Score: 1

      This is like back when monitor sizes weren't really stated as the usable size.

      Just because everyone is a lying sack of shit it doesn't make it right.

      Twernt no lie. It was salesmanship.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    18. Re:1GB is really 1,000,000,000 bytes by OrangeTide · · Score: 1

      My two 500GB make 1000GB. and Actually 1TB (not 1TiB) of storage.

      I think manufacturers should label on the box how many 512 byte sectors are on the drive (in small letters). That would be more useful, especially if you're trying to find compatible drives for RAID. (full geometry would be even better)

      --
      “Common sense is not so common.” — Voltaire
    19. Re:1GB is really 1,000,000,000 bytes by OrangeTide · · Score: 1

      So Windows should just be an upgraded version of CP/M with no concern for usability? I'm going to side with companies like Seagate for doing the right thing. The only thing that should be using the funny sizes of kilo, mega, giga are the RAM manufactures because they have no choice. Why should their funny sizes infect the rest of the industry when it serves no purpose but to mark who is computer literate and who is not.

      Again I point to networking industry, which all use SI prefixes. Storage industry as well. Your CPU's 2.2GHz is not 2362232012Hz.

      The first harddrives for Apple's computers used standard SI prefix 10^(3*n) system, not binary prefix 2^(10*n) system. The first harddrive for PCs was 5.25" 5MB from Seagate and was measured with SI prefix. although in this case the SI and the binary forms both yielded 5, but Seagate already established in their product literature how they measured megabytes. The 20MB drives the came after the initial 5MB and 10MB drives were obviously SI prefix because using binary prefix they were only 19.8MiB.

      --
      “Common sense is not so common.” — Voltaire
    20. Re:1GB is really 1,000,000,000 bytes by Spleen · · Score: 1

      EVERY OTHER FIELD OF STUDY uses kilo- to signify one thousand and mega- to mean one million. When one industry uses a term one way and thousands of other industries all use a term in a consistent but different way, what justification can you give for the single inconsistency. I believe every other field of study you refer to uses as base10 numbering system. When you use a base2 numbering system, you've changed the rules. Whomever originally decided to adopt the SI unit names into binary measurement probably wishes they did something else at this point to eliminate the confusion.
    21. Re:1GB is really 1,000,000,000 bytes by ttfkam · · Score: 1

      Exactly my point, which is why the names for binary units should change: to avoid confusion.

      --

      - I don't need to go outside, my CRT tan'll do me just fine.
  73. Complete bullshit.. by brxndxn · · Score: 1

    During that time, I was in college. I upgraded my computer often - but I also built computers for other students for some extra cash. I bought maybe 30-40 Seagate hard drives during that interval.

    So.. that's ~$150 (assuming around $100 per drive) that I should get back. But.. I have to show proof of purchase and fill out a claim form for every one of them! That's not even worth my fucking time! WTF kind of settlement is this?

    --
    --- We need more Ron Paul!
  74. Re:wow.... are you clueless! by xaxa · · Score: 1

    The next HDD I buy will be Seagate, I can't believe the court ruled against them!

  75. data transfer speed by agw · · Score: 1

    How long does it take to transfer 1GB over an 8MBit/s link if 1 byte is 8 bits?

    134 seconds?

    How long does it take to transfer 1TB over an 8MBit/s link if 1 byte is 8 bits?

    137438 seconds?

    Yeah, seems very logic....not.

  76. Um.... by dentar · · Score: 1

    Why settle in 2007??? I've been buying hard disks advertised with "salesman's meg" since 1987! All the hard disks have been advertised with K=1000, M=1000000, G=1000000000. Why start now that we're all used to it?

    --
    -- I am. Therefore, I think!
    1. Re:Um.... by Anita+Coney · · Score: 1

      Yeah, why stop corporations from ripping us off?! It makes no sense. If they have a history of ripping us off, we should bend over and take it. Heck, it's our civic duty.

      I remember the good old days when a 19" monitor was actually 18" or less. Now I go into stores and monitors are actually sized accurately. It's so damn confusing.

      --
      If someone says he and his monkey have nothing to hide, they almost certainly do.
  77. Long ton by tepples · · Score: 1

    This "gibibyte" nonsense hasn't caught on because it isn't needed, and even worse, the name sounds pretty lame. Then pronounce it "long gigabyte", by analogy with the long ton which is 2240 pounds (about 1016 kg), compared to the metric tonne of about 2205 pounds (1000 kg).
  78. this bytes by Anonymous Coward · · Score: 0

    I have a bit of a problem with this whole lawsuit

  79. Y2038 and Y2012? by tepples · · Score: 1

    So instead they have a calender which starts at Jan 1, 1970 and is measured in seconds from that point on. Were 32-bit microcontrollers still in use around 2.1 Gs (2038) in this universe? And did anything special happen at the end of this creation in the Maya calendar (which happens 42 and change years after the UNIX epoch)?
  80. Retail drives only by WD · · Score: 1

    If you look at the notice, you'll see that this applies to purchase of retail drives only. Basically, the ones in the official Seagate boxes that would indicate the misleading size. "OEM" drives, which I would think most people here would be buying, don't appear to apply.

  81. Who else can we sue? by Ed+Avis · · Score: 1

    Awesome! Now to get a refund from those sneaky 'gigabit Ethernet' vendors who are offering 7% less network capacity than promised, or the dishonest processor makers selling '2.4 gigahertz' chips...

    --
    -- Ed Avis ed@membled.com
  82. How to explain file system overhead by tepples · · Score: 1

    I find that I spend more time explaining why their 105gb (converted to base 2) device shows much less than that (also in base 2) when they click on it to non technical people. "Notice that the inside of a file cabinet is smaller than the outside. Also, files go in folders, and if you've ever bought a box of folders at Office Depot, you'll understand that folders take up space too."
  83. 5$ per a 100$ disk by denzacar · · Score: 1

    But you get these new, inflation/war weakened dollars.

    Not the 2001. or 2002. or even early 2007. dollars.

    If nothing else, this is a very good time for cash settlements.

    --
    Mit der Dummheit kämpfen Götter selbst vergebens
  84. SI units were around first... by mungtor · · Score: 1
    No, the word 'Kilobyte' had established a consistent meaning of 1024 bytes

    And that's where the problem started. A bunch of computer designers mis-used the kilo prefix because it was "good enough". Well, obviously it wasn't and they are the ones ultimately responsible for this mess. But they aren't a big, evil corporation that we can sue, so we'll ignore the facts for now. Right?

    Common usage of something doesn't suddenly make it correct.

    1. Re:SI units were around first... by uglyduckling · · Score: 1
      Common usage of something doesn't suddenly make it correct.

      In this case, yes it does. Way before computer hardware was a consumer product, the standard that a kilobyte is 1024 bytes was established. It's a bit like a nautical mile - within a particular field a well-known unit has a very specific and different meaning. When the manufacturers started selling hard drives to the public they were well aware of the specific meaning of Kilo and Mega in the context of computer hardware but deliberately took the SI definitions in order to make their drives appear bigger. That's not the fault of the computer scientists who coined those phrases. Do you think if the computer scientists had chosen terms that made hard drives look bigger and that the manufacturers would have looked worse by using the 'correct' SI definitions they would have gone for it?

    2. Re:SI units were around first... by mungtor · · Score: 1

      No, it still isn't correct. What manufacturers would have done isn't relevant to the fact that the kilo prefix means 1000 of whatever follows it. I could understand the evolution of the language if kilo was no longer used anywhere else, but since in common usage there are still kilometers, kilograms, and kilopascals -- all of which mean 1000 of the following -- it's just plain incorrect.

      Hard drive manufacturers are selling you exactly what they are claiming. 1GB = 1,000,000,000 bytes is printed right on the box and SI units agree. It's pedantic, and maybe annoying, but it is correct. As far as I'm concerned, the HD manufacturers should contemplate a suit against Microsoft for incorrectly reporting disk size.

    3. Re:SI units were around first... by Anonymous+Custard · · Score: 1

      Hard drive manufacturers are selling you exactly what they are claiming. 1GB = 1,000,000,000 bytes is printed right on the box and SI units agree. It's pedantic, and maybe annoying, but it is correct. As far as I'm concerned, the HD manufacturers should contemplate a suit against Microsoft for incorrectly reporting disk size.

      Yes but they're highlighting a very misleading fact.

      And it wasn't always this way - they switched around 1997-1998, many years after the PC took off. So knowing that they had already been selling hard drives under a different counting system, and knowing that the popular OS's would still be using the old counting system, they changed what they put on the box.

      The only possible reason could be to mislead the average customer into thinking he was getting a bigger drive than he actually was getting.

      What if the hard drive industry set up their own standards group, making 1 megabyte = 750,000 bytes? They're still correct, but they're only doing it to trick the customer with inflated expectations of usable drive capacity.
  85. Re:wow.... are you clueless! by Mozk · · Score: 2, Funny

    I like how your username sort of matches with your ID. :P
    A bit off-topic, but I did post with no karma bonus.

    --
    No existe.
  86. Re:wow.... are you clueless! by Mozk · · Score: 2, Funny

    Oops, apparently I didn't.

    --
    No existe.
  87. i hate these suits by Loconut1389 · · Score: 2, Interesting

    I'd love to get what I supposedly deserve, only I don't keep receipts for hard drives I bought over a year ago. What's wrong with going by serial and date of manufacture?

    The 75GXP refund bit me (I had the receipts for some reason) because I bought OEM- bastards. I've bought mostly retail seagates (about 15 maybe in the window for the suit) but I don't have the receipts.

    A few will benefit, the rest get tossed.

    1. Re:i hate these suits by evilviper · · Score: 1

      I'd love to get what I supposedly deserve, only I don't keep receipts for hard drives I bought over a year ago. What's wrong with going by serial and date of manufacture?

      If you had read TFA more carefully, you'd have seen that you can, indeed, fore-go receipts, and submit your HDD's serial number instead.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:i hate these suits by Loconut1389 · · Score: 1

      the forms all say that, but then still require date of purchase, etc- as far as I can tell. They also stipulate retail only- as did IBM, so Newegg customers, etc are out of luck!

  88. Base 16 number system by Twinbee · · Score: 1

    A super long term solution, but if everyone switched to using base 16 as the default number system, not only would this issue be solved completely, but we'd have a nicer number system in general (well apart from base 12 arguably...)

    --
    Why OpalCalc is the best Windows calc
  89. Kilo was officially adopted in 1795 by Anonymous Coward · · Score: 0

    and in common use before that-

    guess what it was defined as then? 1000 or if you wish, 10 raised to the third power.

    There's no precedent, and no excuse-

    OS/RAM/SW are wrong, and everyone else is right. The fact that Seagate lost is a testament to our worthless legal (not justice) system. They apparently didn't have a large enough warning label declaring "Warning: Giga- still means 1,000,000,000 (but your OS will lie to you)"

    Asking the US public to understand base 10 prefixes is tough enough but explaining that the same prefixes are used for base-2 as well (and not consistently either) is just a nightmare. We need two different terms. Since kilo=1000 has been around longer and is being used in millions of more places (see list above) it makes complete sense to me that it is 1024 that needs a new term. They chose kibi- and yes it sounds stupid, but that's what they picked.

    When two different definitions of the same prefix are used in the same industry (computing) it is simply asking for trouble (as this case is evidence of). RAM vs HD, kilobits (base 10) versus kilobytes(base 2), and so on- it gets confusing even for those of us in the industry (1.44MB anyone?) So let's straighten out the mess and set things right. Is it so much to ask to be unambiguous? For that Seagate is wrong in using giga to mean 1,000,000,00 what are you proposing? Seagate switch to base 2? who else should switch? the entire telecom industry? CPU manufacturers? Where does "computing industry" end?

    Computers use a lot of base-2 things, sure- but this is a simply matter of accurate representation of numbers. 1024 happens to be 2**10, wow that's neat, but it doesn't mean I can call it one-thousand and still be accurate. I'd be wrong. The OS does exactly this when reporting HD capacities. 1001 bytes is 0.9775390625 "kilo"bytes? no, that's wrong. it's 1.001 kilobytes.

    (for the record, I can't remember ever seeing any OS declare that KB = 1024 )

  90. What about my 21" CRT with it's 19.8" screen? by Ezza · · Score: 2, Interesting

    When's the lawsuit for that? At least LCD's are (mostly) accurate in their size ratings.

    The more of this stuff the better. IT is even worse than the car in industry in exaggerating its products performance.

    Plus I've seen "128MB" flash drives that were 128,000,000 bytes..

    --
    I'm a perfectionist but I'm trying to cut back.
  91. The current situation: only chaos by Anonymous Coward · · Score: 0

    Let's have a look at different storage devices and media:

    * DVD-5: holds "4.7 GB", that's decimal GB.

    * CD: "700 MB", that's binary GB! (GiB)

    * USB-keys: Binary? Decimal? Neither!
    In the case of my USB pen drive, the "MB" in "256 MB" actually equals 1000*1024 bytes!

    In other words: it's about time that we standardize our units. Let MB, GB, etc. be SI units and MiB, GiB be binary units! BTW, linux (the kernel) already does it.

  92. Context by SillyNickName · · Score: 1

    The engineers who introduced this notation were well aware of its different meanings in different contexts. And that context is different for main memory than it is for hard drives. Just as the word "foot" can refer to a unit of measure, the lower extremity of the vertebrate leg, the lower edge of a sail, etc. depending upon context. It was only when non-engineers started trying to meddle with things that they didn't really understand that problems arose. But who needs to understand things when you can just file a lawsuit instead?

  93. Yes there was. by camperdave · · Score: 2, Insightful

    There wasn't an ambiguity before hard disk manufacturers decided to invent one.

    Yes, there was an ambiguity, and it started with marketing people. Back in the Early Eighties, in the days when music didn't suck, when the 6502 microprocessor ruled supreme in the personal computer arena, that this trouble started. Prior to this time, it was universally accepted that in the computer world K=1024. The 6502 microprocessor, found in the Apple II, the Commodore PET, the Atari 400/800, and a host of other machines, had a 16 bit address bus which means it was capable of addressing 64K of memory. In fact, that's the basis of the name Commodore 64.

    Now somewhere along the line, some marketing bonehead read that 64K meant 65536 bytes, and thought "If we use K=1000, like the science nerds instead of K=1024 like the computer geeks, then we can say our machines have 65K instead of 64K. The sheeple buying these widgets will buy ours instead". And it worked. Sheeple bought the more expensive Commodore64 that had "over 65K" instead of the cheaper Commodore64 with only 64K, not knowing that they were being fleeced. Soon everyone was marketting their 64K machines as having 65K. These machines were rarely sold with hard drives. And when they were, the K from the manufacturer was 1024 bytes, but the K from the marketer was 1000.

    It got worse when the IBM, Amiga, Mac, and the Atari ST lines hit the market. These machines could deal in Megabytes. The field was muddied by the folks saying a megabyte was 1000K, instead of 1024K, and further muddied by the crowd saying that 1K was 1000 instead of 1024. So, the megabyte came in three sizes, 1,000,000 bytes, 1,024,000 bytes, and it's true size, 1,048,576 bytes.

    --
    When our name is on the back of your car, we're behind you all the way!
    1. Re:Yes there was. by HBI · · Score: 1

      People being stupid is never a good reason to apply an arbitrary standard. There was a time when the base 2 measurement was nearly 100% accurate and anyone who failed to adhere to it would be assured a short lifetime in the industry.

      The fact that morons are able to tread water in the industry is not something that an SI standard can correct.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    2. Re:Yes there was. by vidarh · · Score: 1
      The C64 is a bad example, because it actually had 65K of RAM (notice, btw., that "K" is not a valid SI-prefix - the SI prefix is "k") - the 64K "normal" RAM, and 1K hardwired to be used as color data for the VIC chip.

      But I can't remember ever seeing the C64 advertized as having 65K. Perhaps they did that in the US, but all of the magazines I have from the 80's say 64K.

  94. Re:wow.... are you clueless! by tilandal · · Score: 3, Insightful

    A Byte is not an accepted SI unit of measurement therefore there is not a reasonable expectation that a gigabyte be 1 billion bytes. Since a byte is 2^3 bits to begin with its is even more unacceptable to think of as a base 10 operation. If seagate was advertising 8 Gigabits instead of 1 Gigabyte that would be more acceptable. 1 Gigabyte has always been accepted to mean 2^30 Bytes. 1 gigabit has always been 10^9 bits. They could have advertised as 1 Billion Bytes as well. You can not change the accepted notation just because it suits you. A mile is 5280 feet if you are in a car but 1852 meters if you are in a boat. Context matters.

  95. Sue MS! by Endo13 · · Score: 1

    So after reading through most of the thread, it becomes apparent that it is in fact Microsoft that should be sued here, not Seagate! What a shock!

    Yes, I'm kidding, but only half. Sure, Windows isn't the only OS that reports disk size in GB when it really means GiB... but then, Seagate is also not the only HD manufacturer using the "false" numbering system.

    Sadly, by now the misuse of the prefixes in OS's has become so widespread that by far the easiest solution is for HD manufacturers to just given in and use the same incorrect nomenclature. What I'd really like to see though is a lot of OS patches.

    --
    There is no -1 Disagree mod. Slashdot.org/faq defines mod options. USE IT.
  96. The tech-laity run amuck by Unconventional · · Score: 1

    Now, seems to me, from the VERY beginning, this has been the convention. Every hard drive manufacturer uses decimal to describe the capacity of the drive, and that is, in fact, accurate. There have long been proposals of differentiating between gigabyte (decimal) and gibabyte (binary), terabyte and tibabyte, etc. It never caught on. So, now some person(s) with no knowledge of personal computer history wins a lawsuit? Considering that Seagate is the successor of Shugart, the guys who invented the personal computer hard drive, shouldn't they have had a say in the definitions of terms? Western Digital is next on the hit list...

  97. Nope by Kludge · · Score: 1

    http://physics.nist.gov/cuu/Units/history.html
    The name "SI" came about in 1960, but the units and prefixes existed long before that in standards and scientific usage.

  98. Re:wow.... are you clueless! by networkBoy · · Score: 1

    While that is true, in all reality every one knew what they were doing, it's not like it was a secret. Sure we may have griped about it, but it's nothing new and not worth it (to me) to initiate a lawsuit over. Also, even if I wanted to collect on this for all my Seagate drives, there is no reasonable way I could. Since Seagate is so awesome about their warranty I don't bother saving receipts, as a scan of the top of the drive is all they've ever needed from me at work for a replacement drive (without requiring the old one back because of security implications), for my home drives I fill out the RMA and send in my bad drive and a refurb comes back in quick order. I'm a happy customer...
    -nB

    --
    whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
  99. Last time I checked by CPNABEND · · Score: 1

    That's how EVERYONE calculates disk space, including IBM, EMC and HDS. Is everybody going to be sued, too?

    --
    My wife doesn't listen to me either...
  100. Re:wow.... are you clueless! by MikeTheMan · · Score: 1

    I believe you are missing the point entirely. The hard drive manufacturers (and other makers of storage) changed to this 1 MB = 1,000,000 bytes measurement because they could sell less storage for the same money by misleading people.

    It doesn't matter what the SI prefix means, because in the computer world, 1 MB = 1,048,576 bytes. That's the end of the argument. Go make a 1,000,000 byte file and see what your OS says the size is. It's not 1 MB.

  101. Seagate on a death spiral? by damn_registrars · · Score: 1

    Maybe I'm alone on this (though I doubt it). I personally think this is about par for the course with Seagate. From my own experience, the quality of both their product and their customer service has really gone down the crapper in the past several years - at least for consumer hard drives.

    One of the very first drives I ever purchased was a 130MB Seagate IDE drive (yes, megabytes.). I think I paid around $220 for it, as an OEM drive. Without getting excessively nostalgic, that was one of the better drives I ever owned in terms of longevity.

    I also managed many servers over the years with Seagate 'cudas or cheetahs, and those drives were also great.

    But then I bought a drive for myself more recently and was sorely disappointed. Something in the neighborhood of 250gb (reporting as 286168MB in FreeBSD). The capacity is not my complaint, however - the reliability is. The first drive lasted about 2 months before it started coughing up endless errors and had to be replaced. And Seagate was a nightmare to deal with for support. The person I talked to on the phone - I'll call him Habib - told me that Seagate no longer offer cross-shipping for replacement drives (as certain other manufacturers still do). Habib then also cheerfully told me that if I shipped the drive in anything other than "approved" shipping material, they would void the warranty and I would not receive a replacement. Once I found the list of "approved" shipping material, I found that the materials most normal people use were all excluded - things like bubble wrap and foam peanuts are just not good enough for Seagate anymore! The specifically required that I use their clamshell packaging to send back my drive, which of course I couldn't buy locally - though they did suggest a friendly internet reseller who would sell me the packing for $20!

    Eventually, I talked to Habib long enough that he talked to his "manager" and got "approval" to cross ship anyways. This all took a good 20 minutes or more out of my life - not including time on hold before Habib first answered the phone. They also included a friendly note with Habib's version of the conversation, where he said I was "very irate" and "refused to pay for packaging materials".

    I don't know what happened, but I know I for one miss the old Seagate...

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
  102. Only the lawyers win by Jeff1946 · · Score: 1

    If you didn't know the two meanings of megabyte (base 10 or base 2) then the difference in storage capacity is meaningless to you. Who really cares. Only the class action lawyers that go after companies for crap like this. Customers get tiny minimal settlements. Lawyers get about 1/3 of the total settlement. Company has less money for R&D etc. For the life of me in this case I can't figure how the customer was harmed.

    1. Re:Only the lawyers win by KillerBob · · Score: 1

      For a 1GB drive, you lose a little.
      For a 500GB drive, you lose a lot.

      I've had customers complain that their shiny new 500GB drive is only 460GB formatted. It's a case of caveat emptor, yes, but it's also a case of misleading advertising. A difference of 40GB is significant.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
  103. Re:wow.... are you clueless! by mrchaotica · · Score: 1

    Seagate don't deserve this. Hell, nobody doesn't deserve this...

    That may be true, but it sure would be nice if this causes manufactuers to start offering drives that actually contained a round number of GiB!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  104. Re:wow.... are you clueless! by edwdig · · Score: 1

    The few times I've had to deal with Maxtor's warranty service, everything went incredibly quickly (I believe I had the replacement within a week of noticing the disk failure). They sent back a replacement drive of the exact same model, which was convenient considering the drives were being used in a RAID array.

    As for warranty, all hard disk manufacturers go by the manufacture date. But they also pad it by 6 months or so - or at least Maxtor does. You can enter the serial number on Maxtor's website and check the time remaining. It's usually been a few months more than the warranty period listed on the box.

  105. 1000 when people assume 1024 is misleading by MindKata · · Score: 1

    Its not just about SI units. This is about marketing in the context of the tech industry. Within the industry, its known that 1 megabyte is 1048576 bytes etc..

    It was a deliberate attempt to make their products look like they had more memory. The sales people at Seagate knew what they were doing, because that is part of the job of sales people, to bias and manipulate information to make products sound more favorable, but these sales people pushed it to far and got caught out.

    I like Seagate drives, but I have no sympathy for them getting caught out.

    --
    There are 10 kinds of people in the world... those who understand binary and those who don't.
  106. Lets file lawsuites that reflect our own ignorance by Anonymous Coward · · Score: 0

    Since when has GB WRT to hard disk drive capacity NOT been measured as 1000000000 bytes? This has *always* been the case and is uniform across HDD manufacturer. Seagate settled because they didn't want to be bothered paying lawyers to defend this nonsense.

    The author is wrong to assume that GB can only mean 1024^3.

    http://en.wikipedia.org/wiki/Gigabyte

  107. Re:wow.... are you clueless! by DarkSarin · · Score: 1

    Slight correction: cars/explosives/sugar etc do not work in base 10--humans do. This is likely (my own personal theory, nothing more) a reflection of the fact that we have 10 readily available digits that make counting quite simple if you use base 10. I rather strongly suspect that if humans had 12 digits, then we would use base 12 instead. The reason computers use base 2 is analogous: there are 2 states for the transistors. I rather suspect that at some point we will figure out a simple and reliable state system that lets computers use base 10, 12, or even 16, and they will process much more information in the same number of units (can't say digits or bits--maybe hits? hexadecimal digits?). That might make them more efficient if (and I stress the iffiness of this) the energy to switch states for a particular amount of information is less than the energy to convey that same information in the lesser base.

    To illustrate, hexadecimal can store in two units 16^2 different states, or peices of information--never mind what they are. Binary requires 8 (16=2^4; 4*2=8) bits to convey the exact same amount of information. Thus if switchings states costs x in binary and anything less than 8x for hexadecimal (I think--someone else might want to run through this--I am not an engineer, mathemetician or anything like that, just a lowly psychologist with delusions of computer science), then the hexadecimal is more efficient,and would potentially result in vast energy savings. Now we just need to figure out how to make this happen. I leave that as an exercise for the reader.

    --
    "We don't know what we are doing, but we are doing it very carefully,..." Wherry, R.J. Personnel Psychology (1995)
  108. Inaccurate dates in article - summary e-mail below by graphicsguy · · Score: 1

    Apparently, you can only get cash refund if purchase is before January 1, 2006. Here's the complete, proposed summary e-mail: To: [Customer email address] From: Settlement Claim Administrator Subject: Notice of Seagate Hard Drive Class Action and Proposed Settlement ________________________________________________________ If you purchased a Seagate brand hard disc drive between March 22, 2001 and September 26, 2007, a proposed class action settlement may affect you. A hearing has been scheduled in San Francisco Superior Court to approve the settlement. Under the settlement, you may have the right to make a claim for cash or software. You also may choose to exclude yourself from the settlement. Alternatively, you may file written objections to the settlement and appear (or have your own attorney appear) at the court hearing. If the settlement is approved and you do not exclude yourself, you give up the right to sue for the claims the settlement resolves, and you will be bound by the terms of the settlement. To learn more about or exercise any of your rights, please read below and visit www.harddrive-settlement.com. The lawsuit is Cho v. Seagate Technology (US) Holdings, Inc., San Francisco Superior Court, Case No. 453195. In the suit, the plaintiff alleges that in the sale and marketing of hard disc drives, Seagate stated that purchasers of the drives would receive approximately 7% more usable storage capacity than they actually received. Seagate has denied and continues to deny each and all of plaintiff's claims, and denies that anyone has been harmed or deserves compensation. The Court has not made a decision on the merits. You are a member of the settlement class if, between March 22, 2001 and September 26, 2007, you purchased in the United States a new Seagate brand hard disc drive from an authorized Seagate retailer or distributor, separately as a Seagate product that was not pre-installed into and bundled with a personal computer or other electronic device. As part of the settlement, Seagate will make certain disclosures regarding the storage capacity of its retail hard drives. In addition, if you submit a valid claim, you will receive free backup and recovery software, or a cash payment equivalent to five percent of the net amount you paid for the hard drive (excluding taxes or rebates). To receive the software or the cash payment, you must submit a claim form available at www.harddrive-settlement.com by March 10, 2008. You may submit a claim form for each qualifying drive you purchased. To obtain the cash payment, you must have purchased your drive before January 1, 2006 and you must submit appropriate documentation or the serial number for each drive. If the settlement is approved, plaintiff's counsel will apply for an award of attorneys' fees, expenses and incentive awards not to exceed $1,792,000, to be paid separately from and in addition to the benefits available to settlement class members. All claims of settlement class members which were or could have been asserted in the litigation, based upon the facts alleged in the litigation (as well as in a related case entitled Lazar v. Seagate Technology LLC, et al., San Francisco Superior Court, Case No. 439700; and California Court of Appeal, Case No. A116350) will be released. This means that if you do not exclude yourself from the settlement class, you will give up the right to sue for the claims the settlement resolves, and you will be bound by the terms of the settlement. If you do not want to participate in this class action or be bound by this settlement you must exclude yourself from the settlement class by submitting a written request for exclusion which includes your full name and address and your request to be excluded from the class. Mail your request for exclusion to Hard Drive Settlement, c/o Rust Consulting, Inc., P.O. Box 1240, Minneapolis, MN 55400-1240. Your written request for exclusion must be received by December 21, 2007. If you exclude yourself, you will not receive the benefits of the settlement, and you cannot object to the

  109. Yes there is because it's wrong by Sycraft-fu · · Score: 1

    Long before any computers came around, there were the SI prefixes and they mean "ten to the whatever". It's a base 10 system. A kilometre is 1,000 metres, a megajoule is 1,000,000 joules, and so on. This is universal. Length, area, volume, all the same, same for all materials, same for all disciplines, etc, etc.

    Then along come computers and change this. Some people decided that 2^10 was pretty close to 10^3 so they'd steal kilo and use it to mean 2^10 for computers. Ummm ok, I suppose, that's an error of about 2% so not huge, but whatever. However then computer storage kept growing so they needed bigger terms. Again they appropriated the SI term, but again they defined it to base 2. Mega was 2^20 instead of 10^6. Well, now the error is more like 5%. For giga, it's up above 7%.

    None of this usage changes that it is wrong. I could see your argument if SI was some quaint little standard that nobody uses, but it is the standard used for every nation except the US for EVERYTHING. Even in the US it is used in all scientific applications. So that the prefixes are base 10 is not only well defined, but also common usage.

    So really, it seems computers need to get their shit changed. Especially since they aren't consistent. For example Ethernet is rated in megabits per second using the base 10 meaning. 10base Ethernet signals at 10,000,000 bits per seconds.

    Computer OSes need to get in line with the rest of the world, not the rest of the world in line with computers.

  110. Re:wow.... are you clueless! by bravo_2_0 · · Score: 1

    Hell, nobody doesn't deserve this
    So you think everyone deserves this then!
    --
    I AM A SEXY SHOELESS GOD OF WAR!!!
  111. Imperial system, anyone? by Anonymous Coward · · Score: 0

    There's a reason the standards were bent a bit fifty years ago. The SI units just don't work. They can't work. They will never work. How about the imperial system?
    It has never worked, it can't work, it will never work!

    Brought to you from Europe.
  112. Gibirish!? by ThanatosMinor · · Score: 1

    Seriously, how many people think that this is how you spell "gibberish"

    1. Re:Gibirish!? by Shadyman · · Score: 1

      The "gibirish" tag is a cross between 'gibibyte' (10^9 bytes) and 'gibberish'.

      (I thought it was obvious?)

  113. The work is not worth the small refund. by Futurepower(R) · · Score: 1

    MOD PARENT UP. Quote: "The problem is some OS vendors, like Microsoft, incorrectly report the drive size using a strange base-1024 system."

    As usual, there are useless discussions on Slashdot with little clarity. Thanks for the parent comment which makes the issue clear.

    No one seems to have mentioned that there is no real refund, because the same trick is used as with rebates. The time that it takes to do the paperwork will be, for most people, worth more than the 5% refund. Lawyers may make money, but few customers will get anything.

  114. "Mislead" or "Misled" ? by Slur · · Score: 1

    Although I do tend to pronounce the word "misled" as "myzled" I still know how to spell it.

    --
    -- thinkyhead software and media
  115. Seagate is the ONLY company that... by JackMeyhoff · · Score: 1

    gets my money. Period and for good reason. Reliable hardware and golden guarantee.

    --
    http://www.rense.com/general79/wdx1.htm
  116. offtopic: how "no karma bonus work"? by doti · · Score: 1

    Does it also mean "no karma onus", if I'm moderated down?

    --
    factor 966971: 966971
  117. Re:wow.... are you clueless! by dgatwood · · Score: 1

    Computers use base 2 because it is the most stable detectable base. You can always detect an on-off set of states even if you have a lot of degradation of the signal. Computers don't even use tri-state because it isn't reliable enough. You honestly think computers will move to a ten-state system? That's bordering on analog right there. Short of a very fundamental change in the way computers operate from using electrical signals to something else, that's not very likely.

    More to the point, while quantum computing has a slight potential for doing this, you still need to have some sort of electrical interface with the outside world to make it useful... which will probably still be in binary. Thus, moving to base-10 computing would require something even more drastic than the introduction of quantum computing....

    Base 2 computing isn't likely to go away for a very, very long time.

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  118. It is? by Sycraft-fu · · Score: 1

    What about modems? I remember owning a 28.8k modem. Turns out, that means it operated at 28,800 bits per second, not 29,491.2 bits per second as the "computer" definition of kilo would imply. In fact seems to be this way, Ethernet is also using mega and giga to mean base-10 defined. How about your processor? Best as I can tell those are also using decimal notation. A 3GHz processor is 3*10^9 Hz, not 3*2^30 Hz. Seems like in the computer context, sometimes kilo is 1024, sometimes it isn't. That's the problem.

    1. Re:It is? by dgatwood · · Score: 1

      Hertz is not a unit of storage. The kbps argument is a long-standing division between the computer industry and the telecom industry which have always worked in different units. That said, one is a measurement of a number of bits, while the other is a measure of a number of bytes, so there is a fairly significant distinction.

      Also, a kilobit of comm bandwidth has only a rough bearing on the actual amount of data sent anyway due to highly variable overhead of different protocols. It could be anywhere from 800-1000 bits of usable data. In fact, we routinely say to divide by 10 and that's the approximate number of bytes sent. Thus, base-10 units (of bits) do make more sense for telecom, if only because the way data is organized and transmitted is fundamentally different. Now if they start using "megabytes" to refer to base-10 units of bytes, however, I'll take exception.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    2. Re:It is? by trentblase · · Score: 1

      It's true that we need to standardize -- bad mojo when your 128kpbs mp3 won't play over a 128kbps network connection (or do mp3 bitrates use base-10?). The argument isn't against standardization, it's about which component must change it's definition. Although I am coming around to the SI standard, I loathe the word "kibibit", and the "SI was there first" argument is fallacious because SI co-opted the prefixes to begin with (mega = great, as in a megaplex does not have a million movies)

    3. Re:It is? by Sycraft-fu · · Score: 1

      No it isn't fallacious. Here's the thing: In every country but the US and two others, everything is done in SI. I don't care what it is, metric units and thus prefixes are used. It's what you buy groceries in, what you measure distance in, what your power is reported in and so on. It is a complete and total standard in life. Even in the US, it is the standard for all science everywhere, and the prefixes are often used in other parts of life (kilowatt-hours for example). As such you cannot argue that it is not the standard way of doing things and it has been for a long time, longer than computers. As such there is nothing wrong with noting it was there first. While the prefixes and unit names weren't pulled out of thin air, it was when they all became a well designed standard, and that standard is not only one in terms of being defined and having a body oversee it, it is standard in terms of being universally used.

      Further, the computer base-2 crap gets confusing. For example I just installed a system with a RAID-5 of 3 320GB drives. Easy enough, I have 640GB of usable space where G means giga means 10^9. I can easily convert that to other scales. For example I can say that means I have 640,000MB of space where M means mega means 10^6. I can do that math in my head, no problem. Not so with the computer units. When I installed the system it reported I had 610,315MiB (it said MB but I'm using the correct terms here for clarity) of space, how would I like that partitioned? So, one might thing "Ahh, I'll have over 600GiB when the system is ready." Not so, in fact I have 596GiB. The reason, of course, is that there isn't a base-10 difference between MiB and GiB. I can't do the conversion in my head, it isn't just decimal point shifting and my base-2 math is not strong.

      Had it just all been in GB, it would have been fine. Even if the numbers don't fall along nice boundaries, it'd still be fine. I can do 639,493MB to GB no problem, just as easy as I can do 640,000. However I can't do the MiB to GiB without a calculator.

  119. Re:wow.... are you clueless! by Austerity+Empowers · · Score: 1

    A dollar isn't an SI unit of measurement either, but when the realtor tells me the house is $1M, I assume $1,000,000, not $1,048,576. Since a dollar is 2^2 quarters it is not a base 10 operation, thus I should expect this, correct?

    All that we've accomplished here is forced Seagate (and friends) to put more fine print on their boxes qualifying exactly how many bytes are on the hard drive, and possibly caused them to lose a lot of money. Meanwhile nobody was really misled or damaged in any tangible way. Way to screw America!

  120. Not at all by Sycraft-fu · · Score: 1

    Because not everything is measured binary. 100Mb Ethernet is 100 million bits per second (100*10^6). I don't care if you don't like it, I don't care if you'd rather it was 104,857,600 (100*2^20) bits per second, the standard is defined, that's how it is and how it shall be. Network speeds, going all the way back to the modem days, are done decimal. Not sure why, but that's how it is. As such using the SI prefixes makes sense. As such if you simply have two prefixes, correctly defined, there isn't any confusion. You see G(whatever) you know it's 10^9, you see Gi(whatever) you know it's 2^30. It's always clear which is being talked about since both are used in computers.

  121. If my computer can't convert base-2 to 10 by Sycraft-fu · · Score: 1

    Then I've little use for it. Turns out my computer is also much better at dealing with large lists of numbers, not so good at dealing with graphs. I don't give a shit, I like graphs, the computer will display graphs or I'll get a different one. A computer is a tool to help us, humans, do our work better. It is designed to accommodate our likes and needs, not its own. This is more true as time goes on. You think a GUI is the ideal way from a computer's point of view to interact? Hardly. However it is much better for us humans, so we'll teach the computer to do it.

    Any modern system and do a 2-10 conversion with no problem, as often as required.

  122. Mature industries use 1000 by PMBjornerud · · Score: 1

    Within the industry, its known that 1 megabyte is 1048576 bytes Which is extremely unprofessional of us. Can you tell me any other industry where mega is not exactly 1.000.000 ?

    Big thanks to the power industry for not selling me kilowatts by the 1013 watts or something. I am sure there are some almost-1000 numbers that are really neat for measuring 110v/60Hz power, but the electricity industry measures with 1000 watt per kilowatt. Why? Because it makes sense for everybody!

    Sure, so we use binary numbers a lot. That does NOT allow us to choose our own wacky redefinition of kilo. I can assure you that no other industries have machines and calculations that always come out in nice little 1000s. You just don't know about it, because they are considerate enough to report it to you in units of 1000 anyway.

    1024 - Because IT people care about a binary fetish instead of ordinary people... (No, this is not a good thing.)
    --
    I lost my sig.
    1. Re:Mature industries use 1000 by MindKata · · Score: 1

      Its not unprofessional, but its certainly a less than consistent way to communicate and so its a less than optimally effective way to communicate. But then many industries have their own definitions. For example acronyms from one industry are used in another industry to mean other things etc.. but then unfortunately human communication (and progress) is less than optimal. There are so many optimizations which are possible to tidy up and improve communications. (Come to think of it, it'll be easier if we all spoke the same language around the world, which is another example of the un-optimal nature of human civilization). We need to clean source it all :)

      --
      There are 10 kinds of people in the world... those who understand binary and those who don't.
    2. Re:Mature industries use 1000 by PMBjornerud · · Score: 1

      Its not unprofessional, but its certainly a less than consistent way to communicate and so its a less than optimally effective way to communicate. But then many industries have their own definitions. For example acronyms from one industry are used in another industry to mean other things etc.. Really, this is exactly why the SI-standard was introduced. A single standard across industries.

      Good luck trying to explain to a civil engineer why we redefined the kilo to 1024. Bonus points if he considers it "professional" to redefine international standards to support nice hacks based on internal workings of our equipment.
      --
      I lost my sig.
    3. Re:Mature industries use 1000 by jedidiah · · Score: 1

      A civil engineer is no MORON.

      He will readily understand that 10 is not a power of 2.

      --
      A Pirate and a Puritan look the same on a balance sheet.
  123. Mod parent up. by PMBjornerud · · Score: 1

    Parent allows us to: Blame Windows! Yay!

    Oh, and he also had a point, too, if you care about that ;) Ordinary people have no need to relate to base 2 systems and the OS should report disk size in units of 1000.

    My family will never understand why a disk may have 6,92GB (7,434,502,144 bytes) free. And they would not apreciate an explanation about how neat that is if you suddenly need to... er... quicksort their free space or something. I mean, is there anything useful AT ALL about reporting HD size to the end-user in base2, except showing them how inconsiderarte technologists we are?

    --
    I lost my sig.
  124. Genuine megabytes (TM) ? by PMBjornerud · · Score: 1

    Hopefully, other manufacturers will get the hint and start changing their plans. I could just see this going after other manufacturers too, who insist on using smaller sizes for their measurements to seem bigger. I like standards, so I support kilo = 1000.

    I would market my drives as GENUINE gigabytes. Exactly 1.000.000.000 bytes or more per megabyte. I am sure they will be able to continue using these measures, and I fully support it.

    (Yeah, I know base 2 is handy, but it's my job to do that calculation. No need to bother the end user with it.)
    --
    I lost my sig.
  125. Exactly home many rebates? by dsojourner · · Score: 1

    So ... will that be 6200000 rebates, or 6501171 rebates?

  126. History repeats itself?? by Eyeball97 · · Score: 1

    Didn't we go throught he same crap a few years ago with monitor sizes, that led to monitor specs needing to be "actual size" rather than some "actual viewable size" in the (very) fine print?

    All that's going to happen here, is that drive manufacturers will be forced to dial down their figures a bit, to comply with what *everybody except them* calls a gigabyte...

    Flash in the pan, folks... nothing to see here other than a trend towards not getting a drive that's actually only 90% in "real life" of what it's advertised as.

    Personally never had a problem with it, tbh, being something 99.999% of us knew about and lived with.

  127. Re: "Common usage" ... by Firethorn · · Score: 1

    people on the street also tend to round.

    My answer would be 'slightly less than a megabyte', or 'a megabyte' if I'm in a hurry.

    That's why this took so long to become a problem - even 7% difference can be explained by rounding, but when you start approaching TB levels, it's significant enough to matter.

    --
    I don't read AC A human right
  128. Re:wow.... are you clueless! by mollymoo · · Score: 1

    [...]computers work in base 2, so it makes sense to make disks in base 2 (unlike cars/explosives/sugar, which work in base 10).

    Humans work in powers of ten. Computers should accommodate humans, not the other way round. RAM comes in powers of two for technical reasons, but nothing else in a computer which the user is exposed to uses powers of two. It is not natural for disks to use powers of two (except for the bus) and certainly not natural for the human interface to information about a disk to use powers of two. Using a standardised prefix (giga) to mean something other than 10^9 is the fudging of a definition.

    --
    Chernobyl 'not a wildlife haven' - BBC News
  129. Commonly accepted? by PMBjornerud · · Score: 1

    Regardless of whether the IT sector is _technically_ in the wrong it's commonly accepted that in this area we work with powers of two. Can you drop by my mom and explain to her why it is commonly accepted that her 6,92GB free space is exactly the same as 7,434,502,144 bytes? This part of the UI makes absolutely no sense to her.
    --
    I lost my sig.
  130. Terabits and a toilet plunger, please! by PMBjornerud · · Score: 1

    Your examples do not contradict the point. Bits are not bytes. Excellent.

    Waiter! Bring me a 100 TERABIT drive, please. And a toilet plunger, - I'm gonna flush this fucking "7-bit ascii / 8-bit byte / 2-byte unicode character" stinking pile of shit we have as a standard down into the sewage where it belongs!
    --
    I lost my sig.
  131. Geeks by PMBjornerud · · Score: 1

    1Km = 1000 meters. 1KW = 1000 Watts. 1KB = 1024 bytes. Or we could go with 1000 like everyone else?

    You know, there is a reason IT people are considered geeks and oddballs.

    Trying to push our binary fetish down the throats of others instead of using a standard approach...
    --
    I lost my sig.
  132. My mother by PMBjornerud · · Score: 1

    Please, tell me what is unreasonable about that? Come over to my mom and try to explain to her why 512GB + 512GB = 1TB, and you will understand whay is unreasonable about that.

    Oh, and you know that 2mbps ADSL line I have? How much time to fill a 2GB drive?

    That's why we have standards. The above is supposed to be a simple mental arithmetic... We fucked it up, guys.
    --
    I lost my sig.
  133. IMO... by Roadkills-R-Us · · Score: 1

    This is just another case of two jackasses (a pathetic consumer and an even more pathetic lawyer) jerking things around, and a deranged court system allowing it. There's plenty of historical precedent for the way the drives were marketed.

    While I'm glad we don't live in a perfect state of "buyer beware", the current nany state is even scarier.

  134. Finally by Cervantes · · Score: 1

    I was around in the 90's when those bastard cheap hard drive companies decided to start measuring in base-10 instead of base-2. I complained bitterly at how crappy and cheap and market-speak it was.
    Now, 10 years later, something finally happens, but it's too late for anything to change, any money to realistically be returned, or for us to go back to the old, proper way.
    Ahhh, the sweet smell of justice....

    --
    If I knew the wedgies I gave you back in 6th grade would have resulted in this . . . I might have taken a moments pause.
  135. Let the bastard know what you think by pseudorand · · Score: 1

    Well, this is a rather divisive issue, isn't it. Although I agree that HD manufacturers used powers of 10 to make a buck long ago, Mrs. Cho and her lawyer, Brian R. Strange of Strange and Carpenter, are greedy so-and-so's out to make a buck TODAY. And who pays that buck? Well, now that there's a precedent, and other drive makers are likely to follow, people who buy hard drives in the future (that's us) pay it. Of all the things non-geeks have trouble understanding about computers, this is hardly the most worthy of a lawsuit. So Mr. Strange, shame on you for your horrible abuse of the legal system and unwarranted attack on an outstanding company that provides great products to the marketplace (and yes, I am a Seagate customer, not an employee, or stockholder, or P.R. rep).

    For those of you who agree with me, please take the time to let Mr. Strange know what you think of his despicable actions. I couldn't find his direct email address, but the address posted under "Contact Us" on the Strange and Carpenter web site is: tjhood@strangeandcarpenter.com

    1. Re:Let the bastard know what you think by pseudorand · · Score: 1

      tjhood@strangeandcarpenter.com bounced, but bstrange@strangeandcarpenter.com seemed to go through. Try that instead of you'd like to let your voice be heard.

  136. Re:wow.... are you clueless! by The+Great+Pretender · · Score: 1

    What I don't get here is why didn't they argue significant figures? That way 1073741824 would be equal to 1000000000. Oh and remind me to sue my local bar next time they overpour my bourbon.

    --
    A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort.
  137. Yay!!! by swordgeek · · Score: 1

    Can we now officially and formally declare the kibi/mebi/gibi prefix notation dead and buried? Nobody likes it, nobody uses it, and nobody wants it. Now, as of this ruling, nobody needs it either.

    Good-bye and good riddance to the Gibibyte. Long live the Gigabyte!

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  138. I have a solution by similar_name · · Score: 1

    Use KB MB GB TB etc for base 2 and kB mB gB tB for base 10. One would be the 'proper' computer term, the other would be the more 'generic' SI term. Of course confusing gb for GB would be huge mistake

    1. Re:I have a solution by xaxa · · Score: 1

      m is already used for milli. The small letter prefixes are for fractions of the base unit, centi, milli, micro, nano, pico etc are c, m, , n, p. The big letters are for multiples, kilo, mega, giga, peta, tera are k, M, G, P, T (I'm not sure why k isn't K).

      The solution, as you've probably noticed in the thread, is to add an 'i' for binary (2^10 etc) multiples, i.e. kiB, MiB, GiB etc. Some software already uses this correctly.

  139. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  140. MB, MiB, GB, GiB, and Parted by BrianGKUAC · · Score: 1

    I had this brought up to me by my supervisor not long ago when we were trying to find the precise spot on a drive that an HFS+ partition began, so that we could properly replace it with 2 ext3 partitions without freaking out the software that was running on the machine. It turns out, software that's been out for a while already understands the distinction between MB and MiB, even if the people using the software do not.

    I keep seeing on here that the (X)iB units are made fun of relentlessly in various public forums, but if it works, it works. In the case of precisely defining partitions in parted, the distinction works.

    I think it's laughable that a technical community that is constantly adapting to new things and creating stuff faster than the rest of the world can keep up with is so incredibly resistant to a change that went into effect roughly ten years ago.

    --
    Menus: Linux=function, Windows=vendor, OS X=as little as possible. Makes a statement, don't you think?
  141. Re:wow.... are you clueless! by ttfkam · · Score: 1

    Then the OS is wrong, not the drive.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  142. I wish I had mod points by ttfkam · · Score: 1

    Kudos for the excellent point.

    --

    - I don't need to go outside, my CRT tan'll do me just fine.
  143. Re:wow.... are you clueless! by ePhil_One · · Score: 1
    You can not change the accepted notation just because it suits you.

    Exactly. Thats why I intend to sue Microsoft for lazy programing. By redefining "Giga" to mean 2^30 instead of 10^9 like the accepted notation, they have virtually robbed me of about 7% of my drive by understating the size of my files, etc.

    The Kilo- Mega- Giga- etc prefixes were well defined before lazy programmers started substituting the faster for binary computers 2^10, 2^20, and 2^30 calculations for well established and easy for humans 10^3, 10^6, and 10^9 calculations. Why are you so willing to accept the OS's reinterpretation of these figures? The lawsuit against CRT Monitor manufacturers had merit, they measured corner to corner of the physical tube, and left off that almost 1" was covered by plastic an unusable. This had a serious economic impact on Apple in the early days, who sold their 14.1" visible monitor as a 14" monitor against competitors that sold the same thing as a 15" display (as a computer salesman in that period, I always had fun explaining that to customers...)

    --
    You are in a maze of twisted little posts, all alike.
  144. Re:wow.... are you clueless! by XdevXnull · · Score: 1

    No no no... You don't expect "a lot more" than a gigabyte. You expect at minimum exactly one gigabyte. In the computer industry, a gigabyte is exactly 1024 megabytes, which each of which is exactly 1024 kilobytes, which in turn is exactly 1024 bytes. It doesn't matter what something "has always been" because in this context it means something different; they are domain-specific technical jargon which are well defined to be 2^30 bytes, 2^20 and so on.. So the common usage of "the SI-prefix G" really is not directly applicable. But to get to the point, if you tell someone they are getting a gigabyte and you knowingly only give then one billion bytes, then you are either incompetent or dishonest. So which is it, Seagate? Assholes or liars?

    --
    "I'm a Laver, not a Phyto[plankton]"
  145. mm km by datadigger · · Score: 1

    Lower case (eg; 'm') equates to less-than such as "mm = millimetres", or one millionth of a metre.
    Sigh. ITYM one millimeter is one thousandth of a meter.
    A millionth is a micro, Greek letter micro, AKA mu, HTML entity &micro;

    Upper case (eg; 'K') equates to greater-than such as "Km = Kilometres", or one thousand metres.
    One thousand meters is simply 1 km.
    K is not a factor but a unit by itself: Kelvin, for temperature. Sigh.
    --
    Aphorisms don't fix code. (Bart Smaalders)
  146. Re:wow.... are you clueless! by vidarh · · Score: 1

    Bytes isn't a SI unit, so what the SI-prefix has always been has no relevance.

  147. Mod parent funny! by darthflo · · Score: 1

    Thank you very much for the best slashdot laugh I've had all week (at least) :D

  148. sometimes you need them all by fred133 · · Score: 1

    I had occasion to need all the bits on the drive.
    Rebuilding a mirror and got a replacement 160G drive,with just that,160gigs, total space.
    Whereas the drive that was the other 1/2 of the mirror was a 160G,usable space.
    Just another online order away,mirror got fixed but not as soon as it could have been.
    Now what do I do with this other drive?Buy another to match it for another mirror??
    Still,that would have to be a new clean install.
    I know,repartition?
    I paid for 160, I should get 160.

  149. Are you serious? by ttfkam · · Score: 1
    Are you seriously suggesting that the fact that 2^10 and 10^3 are close together is merely a historical coincidence? Seriously?

    0, 1, 2, 3, 4, 5, 6, 7, 8, 9... oops, ran out of numbers. I know! Let's assume there is a zero in front of the 9 like this: 09. So the front number goes from 0 to 1 and we reset the second number. We end up with 10.

    Why 10? What's so special about it? Wouldn't 8, which is a power of 2, be more useful? Or some other base? Nope, we've got ten fingers and ten toes. We've got ten on the brain from a young age, hence my term "base-10 mind."

    They chose 1,024 because it was the closest they could get with binary to 1,000, a number we are all comfortable with.

    PMBjornerud said it best in his/her post:

    Really, this is exactly why the SI-standard was introduced. A single standard across industries.

    Good luck trying to explain to a civil engineer why we redefined the kilo to 1024. Bonus points if he considers it "professional" to redefine international standards to support nice hacks based on internal workings of our equipment.

    It doesn't hurt computer scientists and programmers to say mebibyte instead of megabyte or gibibyte instead of gigabyte. It would solve the issue for everyone involved in that computer technology would accurately and unambiguously codify their distinct needs while everyone else would know exactly what we intend to signify. The only impediments are laziness and stubborness: resisting change for the sake of resisting change. There really isn't any other good reason not to switch other than, "We've always done it that way, and we don't want to change."
    --

    - I don't need to go outside, my CRT tan'll do me just fine.
    1. Re:Are you serious? by Anonymous Coward · · Score: 0

      Are you seriously suggesting that the fact that 2^10 and 10^3 are close together is merely a historical coincidence?
      No. Reread my post as you seem to have missed quite a lot.

      They chose 1,024 because it was the closest they could get with binary to 1,000, a number we are all comfortable with.
      1,000 is not a number we are all comfortable with. If it were then we would not have developed a notation to shorten it.

      Good luck trying to explain to a civil engineer why we redefined the kilo to 1024.
      Computing is not civil engineering, I mentioned this in my post.

      The bottom line is that there were reasons why kilo, mega, and so on came to mean what they do in computing, and it wasn't just because computing people were lazy and ignorant. It may well be that these reasons are trumped by other concerns, but there were actually good reasons for the choice.
    2. Re:Are you serious? by ttfkam · · Score: 1
      I never said there weren't good reasons for them to do so. Reread my post. I *never* said that. I'm simply saying that the choice has not worked out well in the long term now that it touches beyond just binary numerics; everyone has a computer now and the 1,000/1,024 dichotomy is causing confusion. In addition, the difference between 1,000 and 1,024 is greatly exacerbated once you hit the ranges of giga-, tera-, and beyond. An honest question: do you think early computer scientists would have used these terms had they envisioned terabyte storage units at the time?

      1,000 is not a number we are all comfortable with. If it were then we would not have developed a notation to shorten it. If you show "1,000" to any individual over the age of seven, they will know what it means. If you show "0xFF" to a typical adult, they will stare at you blankly.

      If you say that a kilometer is 1,000 meters, anyone with an eighth grade education will either understand or pick it up in less than 30 seconds.

      If you say that a kilobyte is 1,024 bytes and a megabyte is 1,048,576, that same person will stare at you blankly, will not pick it up in less than 30 seconds, and will forget it within the hour.

      I can't believe I actually had to persuade someone that kilo=1,000/mega=1,000,000 is an easier concept for general society than kilo=1,024/mega=1,048,576. And while I am aware that computing is not the same as civil engineering, you should be aware that the two fields -- in addition to the thousands of other fields -- need to communicate with one another from time to time. That was my point, not that they are the same field.
      --

      - I don't need to go outside, my CRT tan'll do me just fine.
  150. Re:wow.... are you clueless! by jedidiah · · Score: 1

    This is just assinine.

    Kilo has always ALWAYS meant 1024 in computing.

    What it means in any other context is IRRELEVANT.

    We aren't talking about a billion granules of sugar.
    We're talking about a particular technology that's
    based on base 2 and base 16 numbers.

    Seagate KNEW they were perpetrating a fraud. It was
    their intended outcome. They thought they could get
    one over on the clueless not aware that computers
    are not based on base 10.

    Seagate intended fraud even if what they did isn't
    defined in criminal law as such. They meant to mislead
    people and give them less than what people were expecting.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  151. Re:wow.... are you clueless! by jedidiah · · Score: 1

    Bullshit.

    ALL the drive manufacturers intended to defraud everyone.

    Law & Order finally did what it was supposed to. It slapped
    down those who apparently can't work or play well with others
    and try to take advantage of everyone else.

    Caveat emptor is not acceptable.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  152. Re:wow.... are you clueless! by networkBoy · · Score: 1

    I understand your sentiment, but my point is not BS. They (on the box) state 1 MB is 1,000,000 bytes. It's not "right" but it is not fraud either. It is the fine line those marketing asshats walk every day.
    -nB

    --
    whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
  153. http://www.m-w.com/dictionary/giga by Anonymous Coward · · Score: 0
  154. Re:wow.... are you clueless! by StrongAxe · · Score: 1

    By redefining "Giga" to mean 2^30 instead of 10^9 like the accepted notation, they have virtually robbed me of about 7% of my drive by understating the size of my files, etc

    How, exactly, have they robbed you? Your files occupy exactly the same number of sectors and tracks on the disk, regardless of whether the operating system displays them in Bytes, or Kilobytes (/1024), Megabyres (/1048576). On Windows, look at a file in the directory listing, and it shows binary kilobytes/megabytes. But right-click/Properties and it shows you the exact number of bytes as a decimal number. Chosing one display or another does not alter the actual storage capacity of your drive at all - only your own perception of it.

    It's like operating systems (like Unix and Windows/XP) that store the system date in GMT rather than local time. The time signature of a file does not change, regardless of what symbolic representation you choose to display it in.

  155. Re:wow.... are you clueless! by StrongAxe · · Score: 1

    Humans work in powers of ten.

    Actually, this is merely a cultural thing. Many cultures find it convenient to use base 10 because (most) people have 10 fingers to count with. However, the human brain does not inerently favor decimal arithmetic. Some cultures have used other bases in the past (for example, Babylon used base 60 - and you can see how pervasive that was, since we still use such numbers in circular measurement). I also believe that Unicode includes some number systems that are in base 12 (although I might be mistaken).

  156. Yeah! I bought one by MP2Kmag · · Score: 1
    I bought a Seagate external hard drive last year, I ended up keeping a lot of data on it exclusively so I really need another one to mirror to actually have some redundancy i.e. a backup so this cash refund might help convince my wife we can afford the expense.

    Eric

    http://www.mapelves.com/ and http://www.windychat.com/

  157. Re:wow.... are you clueless! by ePhil_One · · Score: 1
    Chosing one display or another does not alter the actual storage capacity of your drive at all - only your own perception of it.

    Exactly. Note I said "Virtually" and not "actually" or "Literally". They gave me the perception my files were smaller than they were by misrepresenting their size as smaller than they truly were. This led me ("me" being a fictional idiot who felt the need to sue honest law abiding hard drive manufacturers for misrepresentation when the used the common base 10 numerology instead of the esoteric base 2 numerology) to believe a 200,000,000,000 byte drive would hold my 199 "gigabytes" of data, when in fact, it wouldn't.

    The grandparent claims the hard drive manufacturers misled the public when they used the standard notation instead of the binary notation. I disagree, I've known for over 25 years the OS is the one miscalculating the size, and think this case would only have a basis if Seagate were the only company using decimal representations, when in reality every manufacturer used this method for calculating disk size and has for decades. The OS often also grabs a portion of the disk for partitions, FAT, and other tables, (up to 12% in some cases), should they take that into account hen giving sizes as well?

    --
    You are in a maze of twisted little posts, all alike.
  158. Re:wow.... are you clueless! by StrongAxe · · Score: 1

    Right.

    I have always been disgusted by the disingeunousness of memory manufacturers by inflating the sizes of their devices, but at least they DO actually put a note on the side of the box stating what they mean. The fact that they rely on the fact that most people can't be bothered to read the fine print may be despicable, but hardly actionable.

    (And this choice is deliberate - they KNOW that their disks will be used on operating systems that use binary metrics to display disk sizes, yet they always use decimal metrics themselves. This has irritated me in much the same way that my entire life, grocery stores have sold hot dogs in packages of 10 and hot dog buns in packages of 8, knowing full well that these products were designed to be used together).

    I also always used to hate the fact that RAM was typically measured in bytes, wheras ROMs were typically measured in bits - making them seem to be 8x as large unless you paid attention. This was most notable on video game cartridges, where 128KB games were called "Mega cartridges" because they had a megabit of data.

    (And let's not get into the confusion between KBps/MBps and Kbps/Mbps for measuring bandwidth...)

  159. GIBIBYTE SOUNDS RETARDED. by danielsfca2 · · Score: 1

    > It doesn't hurt computer scientists and programmers to say mebibyte instead of megabyte or gibibyte instead of gigabyte

    Um, YES IT DOES FREAKING HURT. "Gibibyte" has got to be the #1 asswipe word I've ever heard in my life.

    Hello, how many Gibibytes is that drive? I DARE you to go into a store and ask that. They'll think you're a retard with a speech impediment. And if you said gibibyte, you would be.

    Whoever invented these stupid-ass terms probably thought they were solving this whole 1000 vs 1024 problem. Too bad that asshole hadn't ever left his parents' basement.

    1. Re:GIBIBYTE SOUNDS RETARDED. by ttfkam · · Score: 1

      Too bad that asshole hadn't ever left his parents' basement. Pot, meet kettle.
      --

      - I don't need to go outside, my CRT tan'll do me just fine.
  160. ha ha ha. so witty. (nt) by danielsfca2 · · Score: 1

    nt

  161. Re:wow.... are you clueless! by DarkSarin · · Score: 1

    Which is why I am not a computer scientist--or maybe I don't know these things because I'm not a computer scientist.

    I still maintain that if we _could_ move away from binary, it would have some serious benefits.

    What about optical processing/storage/transmission? Would that work?

    By the way, though, note that I do not, and would not, suggest a move to base-10. base 4, 8, 16, or whatever worked within the system would be my preference. With that in mind, base 10 would make the whole argument about hdd space obsolete.

    --
    "We don't know what we are doing, but we are doing it very carefully,..." Wherry, R.J. Personnel Psychology (1995)
  162. Re:wow.... are you clueless! by Anonymous Coward · · Score: 0

    Well said! Let's all start using bits. It makes the recent misleading "1 terabyte" hard drives seem less amazing. After all, that's just 8 terabits. I think I'll wait for 10. That's a much more pleasing number and more deserving of attention.