<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Ninety gigs, down the toilet</title>
	<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/</link>
	<description>the blog that is not dansdata.com</description>
	<pubDate>Thu, 28 Aug 2008 19:19:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: kibibyte</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-2349</link>
		<pubDate>Sun, 13 Apr 2008 18:03:52 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-2349</guid>
					<description>&quot;In computer usage, though, those SI prefixes are perverted to refer to powers of two, not ten&quot;

... except for hard drives, and DVDs, and tape drives, and older floppy drives, and networking speeds, and processor speeds, ...

&quot;the rip-off factor, in other words&quot;

What a bunch of baloney.

Hard drives have always been measured in correct power-of-10 units.  The first hard drive ever sold was the IBM 350 RAMAC in the 1950s.  It featured 50,000 sectors, each of which held 100 alphanumeric 7-bit characters.  I'm not seeing a connection to powers of two, are you?  Through the 60s, 70s, 80s, and 90s, hard drives continued to be measured in powers of 10, as they are today.  Operating systems that used &quot;binary K&quot; like CP/M and DOS didn't even come out until the 70s.

Early floppy drives (8-inchers) were also measured in decimal kbytes and megabits.  Meanwhile, your 56K modem was 56,000 bits per second, not 57,344.  Today, your Ethernet connection is 100,000,000 bits per second, not 104,857,600.  Your MP3 files are 128,000 bps, not 131,072.  Your 50 GB Blu-Ray disc holds about 50,000,000,000 bytes, not 53,687,091,200.  The ONLY thing that's inherently powers of two is memory.  If you have evidence to the contrary, please present it, because all I've seen is complaints of fraud against drive manufacturers with no evidence to back it up.

The problem isn't deceitful marketing; it's Microsoft.  What conceivable benefit is there to reporting a 100,000,000,000 byte drive as &quot;93 GB&quot; in one place and &quot;95,367 MB&quot; in another place? None. Microsoft's notation is stupid and useless.  Western Digital was absolutely correct in their response to getting sued:

'Surely Western Digital cannot be blamed for how software companies use the term &quot;gigabyte&quot;—a binary usage which, according to Plaintiff's complaint, ignores both the historical meaning of the term and the teachings of the industry standards bodies. In describing its HDD's, Western Digital uses the term properly. Western Digital cannot be expected to reform the software industry. ... Apparently, Plaintiff believes that he could sue an egg company for fraud for labeling a carton of 12 eggs a &quot;dozen,&quot; because some bakers would view a &quot;dozen&quot; as including 13 items.' http://paulhutch.com/wordpress/?p=214

Using &quot;G-&quot; to mean &quot;1,073,741,824&quot; is just wrong, plain and simple.</description>
		<content:encoded><![CDATA[	<p>&#8220;In computer usage, though, those SI prefixes are perverted to refer to powers of two, not ten&#8221;</p>
	<p>&#8230; except for hard drives, and DVDs, and tape drives, and older floppy drives, and networking speeds, and processor speeds, &#8230;</p>
	<p>&#8220;the rip-off factor, in other words&#8221;</p>
	<p>What a bunch of baloney.</p>
	<p>Hard drives have always been measured in correct power-of-10 units.  The first hard drive ever sold was the IBM 350 RAMAC in the 1950s.  It featured 50,000 sectors, each of which held 100 alphanumeric 7-bit characters.  I&#8217;m not seeing a connection to powers of two, are you?  Through the 60s, 70s, 80s, and 90s, hard drives continued to be measured in powers of 10, as they are today.  Operating systems that used &#8220;binary K&#8221; like CP/M and DOS didn&#8217;t even come out until the 70s.</p>
	<p>Early floppy drives (8-inchers) were also measured in decimal kbytes and megabits.  Meanwhile, your 56K modem was 56,000 bits per second, not 57,344.  Today, your Ethernet connection is 100,000,000 bits per second, not 104,857,600.  Your MP3 files are 128,000 bps, not 131,072.  Your 50 GB Blu-Ray disc holds about 50,000,000,000 bytes, not 53,687,091,200.  The ONLY thing that&#8217;s inherently powers of two is memory.  If you have evidence to the contrary, please present it, because all I&#8217;ve seen is complaints of fraud against drive manufacturers with no evidence to back it up.</p>
	<p>The problem isn&#8217;t deceitful marketing; it&#8217;s Microsoft.  What conceivable benefit is there to reporting a 100,000,000,000 byte drive as &#8220;93 GB&#8221; in one place and &#8220;95,367 MB&#8221; in another place? None. Microsoft&#8217;s notation is stupid and useless.  Western Digital was absolutely correct in their response to getting sued:</p>
	<p>&#8216;Surely Western Digital cannot be blamed for how software companies use the term &#8220;gigabyte&#8221;—a binary usage which, according to Plaintiff&#8217;s complaint, ignores both the historical meaning of the term and the teachings of the industry standards bodies. In describing its HDD&#8217;s, Western Digital uses the term properly. Western Digital cannot be expected to reform the software industry. &#8230; Apparently, Plaintiff believes that he could sue an egg company for fraud for labeling a carton of 12 eggs a &#8220;dozen,&#8221; because some bakers would view a &#8220;dozen&#8221; as including 13 items.&#8217; <a href='http://paulhutch.com/wordpress/?p=214' rel='nofollow'>http://paulhutch.com/wordpress/?p=214</a></p>
	<p>Using &#8220;G-&#8221; to mean &#8220;1,073,741,824&#8243; is just wrong, plain and simple.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Coding Horror</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-2088</link>
		<pubDate>Thu, 14 Feb 2008 05:13:43 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-2088</guid>
					<description>&lt;strong&gt;Gigabyte: Decimal vs. Binary&lt;/strong&gt;

 Everyone who has ever purchased a hard drive finds out the hard way that there are two ways to define a gigabyte. &amp;nbsp; When you buy a &quot;500 Gigabyte&quot; hard drive, the vendor defines it using the decimal powers...</description>
		<content:encoded><![CDATA[	<p><strong>Gigabyte: Decimal vs. Binary</strong></p>
	<p> Everyone who has ever purchased a hard drive finds out the hard way that there are two ways to define a gigabyte. &nbsp; When you buy a &#8220;500 Gigabyte&#8221; hard drive, the vendor defines it using the decimal powers&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Daniel Rutter</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-571</link>
		<pubDate>Mon, 08 Jan 2007 22:15:19 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-571</guid>
					<description>Uh, abb3w - I think you'll find there's no such agreement about the upper and lower case status of bits and bytes. The old fashioned way of doing it is to give B to bits (because they came first, and have a definite value) and b to bytes (which came second, and can vary in size; you whippersnappers and your assumptions about eight-bit bytes).

The upshot is that anybody hoping to make themselves clear &lt;b&gt;must&lt;/b&gt; define their terms every single time, not just dive in with a blithe assumption that other people will understand the way they happen to do it.

I wrote about this in &lt;a href=&quot;http://www.dansdata.com/danletters001.htm&quot; rel=&quot;nofollow&quot;&gt;the very first Dan's Data letters column&lt;/a&gt;.</description>
		<content:encoded><![CDATA[	<p>Uh, abb3w - I think you&#8217;ll find there&#8217;s no such agreement about the upper and lower case status of bits and bytes. The old fashioned way of doing it is to give B to bits (because they came first, and have a definite value) and b to bytes (which came second, and can vary in size; you whippersnappers and your assumptions about eight-bit bytes).</p>
	<p>The upshot is that anybody hoping to make themselves clear <b>must</b> define their terms every single time, not just dive in with a blithe assumption that other people will understand the way they happen to do it.</p>
	<p>I wrote about this in <a href="http://www.dansdata.com/danletters001.htm" rel="nofollow">the very first Dan&#8217;s Data letters column</a>.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: becakman</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-570</link>
		<pubDate>Mon, 08 Jan 2007 21:26:18 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-570</guid>
					<description>I z a we the new sherriff?
Iz a da drooler also the ruler, to measure size, standards are nice.  Back in the day we would partition different portions of the biggest drives according to the type of data files that would best written into that partition.  with the &quot;{[(modern)]}&quot; paging sizes of virtual memory (sp?) these days, I feel that nothing matters anymore, unless you are trying to lay off HD broadcast quality video full size 1920x1080px (hundreds of MB per second versus DV which is a mere 3-4 MB disk used per second of footage!) to a Sony HD deck that is more than 12.9' away via 4-way fiber channel network, oh and the 4 terabyte RAID must be hard wired directly into your G5, otherwise none of this is even glimmerrable.  

Have long wind edly said that, my point was that back in the day we actually cared about the block size of the partition, so that the partition that I stored all my BS 2k docs on would be a 600 mb partition with a .5k block size, and the partions that I set up for photoshop skratch disk and Video Capture would have the max block size, (32k or 64k) depending on what hard drive formatting utility was in use.
We were using FWB Hard Disk Toolkit and RAID toolkit back in 1990-92.  so if I saved a 2k file on the partition with 64k block size, it would take up 64k. Again that was back when we cared and actually controlled all processes and applications on our EXPENSIVE little macs. QUADRA 640av....blog...blah blog a blam!

PEACE no warts on rolling logs peas in yurtz 

ERic PIt Crew out  :-)</description>
		<content:encoded><![CDATA[	<p>I z a we the new sherriff?<br />
Iz a da drooler also the ruler, to measure size, standards are nice.  Back in the day we would partition different portions of the biggest drives according to the type of data files that would best written into that partition.  with the &#8220;{[(modern)]}&#8221; paging sizes of virtual memory (sp?) these days, I feel that nothing matters anymore, unless you are trying to lay off HD broadcast quality video full size 1920x1080px (hundreds of MB per second versus DV which is a mere 3-4 MB disk used per second of footage!) to a Sony HD deck that is more than 12.9&#8242; away via 4-way fiber channel network, oh and the 4 terabyte RAID must be hard wired directly into your G5, otherwise none of this is even glimmerrable.  </p>
	<p>Have long wind edly said that, my point was that back in the day we actually cared about the block size of the partition, so that the partition that I stored all my BS 2k docs on would be a 600 mb partition with a .5k block size, and the partions that I set up for photoshop skratch disk and Video Capture would have the max block size, (32k or 64k) depending on what hard drive formatting utility was in use.<br />
We were using FWB Hard Disk Toolkit and RAID toolkit back in 1990-92.  so if I saved a 2k file on the partition with 64k block size, it would take up 64k. Again that was back when we cared and actually controlled all processes and applications on our EXPENSIVE little macs. QUADRA 640av&#8230;.blog&#8230;blah blog a blam!</p>
	<p>PEACE no warts on rolling logs peas in yurtz </p>
	<p>ERic PIt Crew out  :-)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jimmy</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-568</link>
		<pubDate>Mon, 08 Jan 2007 10:59:26 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-568</guid>
					<description>This is hearsay, so I may be wrong on this.

I remember reading a post by someone about this and they stated that prior to the 100Mb Drive, disk sizes were accurate. It was the maker of the first &quot;100Mb&quot; Disk that broke the rule, it was probably because they were short by a little, and someone suggesting using 1000 bytes to the kilobyte system as a way around it.

James</description>
		<content:encoded><![CDATA[	<p>This is hearsay, so I may be wrong on this.</p>
	<p>I remember reading a post by someone about this and they stated that prior to the 100Mb Drive, disk sizes were accurate. It was the maker of the first &#8220;100Mb&#8221; Disk that broke the rule, it was probably because they were short by a little, and someone suggesting using 1000 bytes to the kilobyte system as a way around it.</p>
	<p>James
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: phrantic</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-567</link>
		<pubDate>Mon, 08 Jan 2007 10:37:37 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-567</guid>
					<description>But they're marketing people! It's what they do! Just look at the now-confusing numbers used in CPU and GPU naming. Even Toyota rounded off my 1968cc 18R engine to two litres.

And don't get me started on PSU ratings.

Their job is to be as kind to their product's capabilities as possible, and our job call bullshit on it.</description>
		<content:encoded><![CDATA[	<p>But they&#8217;re marketing people! It&#8217;s what they do! Just look at the now-confusing numbers used in CPU and GPU naming. Even Toyota rounded off my 1968cc 18R engine to two litres.</p>
	<p>And don&#8217;t get me started on PSU ratings.</p>
	<p>Their job is to be as kind to their product&#8217;s capabilities as possible, and our job call bullshit on it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: UnderLord</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-566</link>
		<pubDate>Mon, 08 Jan 2007 05:14:54 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-566</guid>
					<description>I whinged about the same thing last Friday
http://www.bluesnews.com/cgi-bin/board.pl?action=viewthread&amp;amp;threadid=74271
At least you got some response!
I was the engineer at one of the first real PC companies in the U.K, back in the day, and the dates in those hard-drive capacity lists look off to me.
I left Keen Computers in 1982 after years of fixing Corvus Drives.
I do recall though that we sold the Corvus drives as 5, 9 and 18MB capacities, maybe honesty was the rule back then in the U.K.
True enough, at the price per gigabyte of storage, why should we care, but I don't like to see dodgy numbers mandated by competitive marketing go unchallenged.
</description>
		<content:encoded><![CDATA[	<p>I whinged about the same thing last Friday<br />
<a href='http://www.bluesnews.com/cgi-bin/board.pl?action=viewthread&amp;threadid=74271' rel='nofollow'>http://www.bluesnews.com/cgi-bin/board.pl?action=viewthread&amp;threadid=74271</a><br />
At least you got some response!<br />
I was the engineer at one of the first real PC companies in the U.K, back in the day, and the dates in those hard-drive capacity lists look off to me.<br />
I left Keen Computers in 1982 after years of fixing Corvus Drives.<br />
I do recall though that we sold the Corvus drives as 5, 9 and 18MB capacities, maybe honesty was the rule back then in the U.K.<br />
True enough, at the price per gigabyte of storage, why should we care, but I don&#8217;t like to see dodgy numbers mandated by competitive marketing go unchallenged.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: abb3w</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-565</link>
		<pubDate>Mon, 08 Jan 2007 04:50:55 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-565</guid>
					<description>OK, while we're being anal about units, &quot;1 Tb&quot; is one terra&lt;strong&gt;bit&lt;/strong&gt;; &quot;1 TB&quot; is one terra&lt;strong&gt;byte&lt;/strong&gt;. Regardless of your feelings about the T-vs-Ti prefix destinctions, this distinction is clearly recognized industry wide. This is why every ISP gets away with advertising speeds in Mbps, instead of MBps, and why I've had to explain to half of my collection of clueless end-lusers why their DSL seems to be a factor of eight slower than what they thought they were buying.

That said... you can blame this on the same short-sighted techies from days of yore who never thought code would still be in use by Y2K, and certainly not by orders of magnitude more machines than existed when they wrote it. The 1024 = 1000 approximation is the same kind of sloppiness. Fortunately, the decimal/binary SI distinction is mostly just cosmetically irritating. It would be nice if Google would add the binary SI prefixes to Google Calculator, though.</description>
		<content:encoded><![CDATA[	<p>OK, while we&#8217;re being anal about units, &#8220;1 Tb&#8221; is one terra<strong>bit</strong>; &#8220;1 TB&#8221; is one terra<strong>byte</strong>. Regardless of your feelings about the T-vs-Ti prefix destinctions, this distinction is clearly recognized industry wide. This is why every ISP gets away with advertising speeds in Mbps, instead of MBps, and why I&#8217;ve had to explain to half of my collection of clueless end-lusers why their DSL seems to be a factor of eight slower than what they thought they were buying.</p>
	<p>That said&#8230; you can blame this on the same short-sighted techies from days of yore who never thought code would still be in use by Y2K, and certainly not by orders of magnitude more machines than existed when they wrote it. The 1024 = 1000 approximation is the same kind of sloppiness. Fortunately, the decimal/binary SI distinction is mostly just cosmetically irritating. It would be nice if Google would add the binary SI prefixes to Google Calculator, though.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: qupada</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-564</link>
		<pubDate>Sun, 07 Jan 2007 21:23:13 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-564</guid>
					<description>topdeck: actually only cd manufacturers have it right.  A &quot;700MB&quot; CD has 360,000 frames (80 min, 75 frames/sec), with 2352 (44100*16*2/75/8, for what it's worth) Bytes per frame (audio), or 2048 data Bytes/frame once error correction is factored in, for a total of 703.125 real megabytes.

However, DVDs do, in fact, cheat us.  A single layer dvd holds 4,700,000,000 Bytes and a dual layer 8,500,000,000 Bytes.  4.38GB and 7.91GB respectively.</description>
		<content:encoded><![CDATA[	<p>topdeck: actually only cd manufacturers have it right.  A &#8220;700MB&#8221; CD has 360,000 frames (80 min, 75 frames/sec), with 2352 (44100*16*2/75/8, for what it&#8217;s worth) Bytes per frame (audio), or 2048 data Bytes/frame once error correction is factored in, for a total of 703.125 real megabytes.</p>
	<p>However, DVDs do, in fact, cheat us.  A single layer dvd holds 4,700,000,000 Bytes and a dual layer 8,500,000,000 Bytes.  4.38GB and 7.91GB respectively.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lanthanide</title>
		<link>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-563</link>
		<pubDate>Sun, 07 Jan 2007 20:50:23 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/01/07/ninety-gigs-down-the-toilet/#comment-563</guid>
					<description>I really wonder why some hard drive manufacturer just doesn't come out with *correctly* sized hard drives. Are you going to buy a hard drive from manufacturer X that only has 298 gigs on it, or a hard drive from manufacturer Y that actually has the advertised 320 gigs on it?

It looks like an easy way to gain marketshare and I think that the hard drive platters probably have that much space on them right now anyway, just it isn't all being used.

Also, a while back there was a class action suit filed in the US for buyers of WD hard drives claiming that the size advertised wasn't correct. Surprisingly, the court actually upheld the complaint and awarded damages; people affected got to download a data backup program that usually cost something like $39 for free from WD. In other words, the compensation was pretty much worthless and hardly anyone would have actually taken the offer up.</description>
		<content:encoded><![CDATA[	<p>I really wonder why some hard drive manufacturer just doesn&#8217;t come out with *correctly* sized hard drives. Are you going to buy a hard drive from manufacturer X that only has 298 gigs on it, or a hard drive from manufacturer Y that actually has the advertised 320 gigs on it?</p>
	<p>It looks like an easy way to gain marketshare and I think that the hard drive platters probably have that much space on them right now anyway, just it isn&#8217;t all being used.</p>
	<p>Also, a while back there was a class action suit filed in the US for buyers of WD hard drives claiming that the size advertised wasn&#8217;t correct. Surprisingly, the court actually upheld the complaint and awarded damages; people affected got to download a data backup program that usually cost something like $39 for free from WD. In other words, the compensation was pretty much worthless and hardly anyone would have actually taken the offer up.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
