"Peter Pan" <(E-Mail Removed)> hath wroth:
>8 bits = 1 Byte
>
>What comes after the Byte ?
>1024 Bytes = 1 Kilobyte
>
>What comes after the kilobyte ?
>1024 Kilobytes = 1 Megabyte
(...)
If only life were so simple. See:
<http://en.wikipedia.org/wiki/Byte>
<http://en.wikipedia.org/wiki/SI_prefix>
and from the NIST, we have:
<http://physics.nist.gov/cuu/Units/binary.html>
<http://physics.nist.gov/cuu/Units/prefixes.html>
Of course, standards are made to be broken:
<http://en.wikipedia.org/wiki/Non-SI_unit_prefix>
For entertainment value, try using these:
2 bits: crumb, quad, quarter, tayste, tydbit
4 bits: nibble, nybble
5 bits: nickle, nyckle
10 bits: deckle
16 bits: plate, playte, chomp, chawmp (on a 32-bit machine)
18 bits: chomp, chawmp (on a 36-bit machine)
32 bits: dinner, dynner, gawble (on a 32-bit machine)
48 bits: gobble, gawble (under circumstances that remain obscure)
I once proposed the pseudobyte as equal to 1012 bytes. That's the
arithmetic average of 1000 bits and 1024 bits, which should serve as a
suitable compromise value thus satisfying both camps. It was
summarily rejected as counterproductive by all that took me seriously.
It also gets ugly with speed abreviations, such as Bps, bps,
Bytes/sec, bits/sec, etc. I won't go there and simply suggest that
one should not abrev.
Try not to byte off more than you can chew.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558