What does binary code 10101010 mean?

Answer 1

• 170/2 = 85 R 0. Therefore binary number so far is 0.
• 85/2 = 42 R 1. Therefore binary number so far is 10.
• 42/2 = 21 R 0. Therefore binary number so far is 010.
• 21/2 = 10 R 1. Therefore binary number so far is 1010.
• 10/2 = 5 R 0. Therefore binary number so far is 01010.
• 5/2 = 2 R 1. Therefore binary number so far is 101010.
• 2/2 = 1 R 0. Therefore binary number so far is 0101010.
• 1/2 = 0 R 1. Therefore binary number so far is 10101010.
• The integer portion of last division was 0 so for the decimal number 170, the binary equivalent is 10101010.

Answer 2

01001101 01110010 00100000 01001011 01100001 01110010 01101001 01101101 is a 64-bit binary value with the decimal integer value ‭5,580,558,396,394,989,933‬.

What this value actually means is unknown -- there is insufficient information. Is it a distance? A weight? A quantity? Is it even an integer? There no way to know outwith the context in which it is used.

Converting to hexadecimal (base 16), it has the value:

0x‭4D72204B6172696D‬

Converting to 64-bit IEEE-754 double-precision floating point, it has the (approximate) decimal value:

119,306,651,158,134,775,996,654,109,111,791,088,101,763,443,836,713,942,340,767,580,160

Treating the value as an array of 8-bit ASCII characters we get:

{'M', 'r', ' ', 'K', 'a', 'r', 'i', 'm'}

This last representation appears to form the name "Mr Karim". Could this be what is being represented? Quite possibly. However, the value is not a valid string because it lacks a null-terminator. If we were to actually allocate the string:

char x[] = "Mr Karim";

we'd find the length of array x is nine bytes, not eight, because the compiler implicitly inserts a null-terminator at the end of the string. One way to recreate the original binary value is as follows:

char y[8] = {'M', 'r', ' ', 'K', 'a', 'r', 'i', 'm'};

However, we cannot treat y as a string because it has no null-terminator:

printf ("%s\n", x); // ok!

printf ("%s\n", y); // error!

In practice we may find that y does in fact print correctly, but this would be sheer luck because that can only happen if the next byte just happens to be 00000000 (the binary representation of the null-terminator) and only if that byte happens to be accessible to our code. In programming, we never rely on luck!

Answer 3

This is binary and decodes as the following hex: 45 30 30 34 In decimal, this would be: 69 48 48 52 In ASCII, it represents the following characteristics: E004

Answer 4

K pasa tios, ya lo

I don't know this means what either.

Answer 5

It doesn't mean anything. It's not a real binary code.

Answer 6

This looks like a binary number. It would be 718 in base 10.

Answer 7

acid

Answer 8

0x2F75

Answer 9

Attack on White House

Answer 10

01010011 01101111 00101100 00100000 01101000 01101111 01110111 00100000 01101101 01110101 01100011 01101000 00100000 01110100 01101001 01101101 01100101 00100000 01100100 01101001 01100100 00100000 01001001 00100000 01110111 01100001 01110011 01110100 01100101 00111111