Binary to hexadecimal is very easy because hexadecimal numbers are designed specifically so that each hex digit is exactly 4 bits (i.e. 16 different values). So if you had this binary number:
binary: 100011011011110101000100001
You could put in commas every four places (starting on the left):
binary: 100,0110,1101,1110,1010,0010,0001
Then you could write the hex values immediately below:
binary: 0100,0110,1101,1110,1010,0010,0001
hex: 4 6 D E A 2 1
and the hex value would be 46DEA21.
Assuming the original was in binary, the answer is 36.A
ABCD1 = 10101011110011010001
It is CEF0.
58880 cannot be binary. Please check the base for 58880 and then what base you want to convert it to and then resubmit.
Because - Hex is an exact multiple of binary - whereas decimal numbers need to be converted from base 10 to base 2.
The answer depends on what you are converting from: binary, ternary, octal, hexadecimal ...
Assuming the original was in binary, the answer is 36.A
Okay, I'm pretty sure that 864 binary is 30 hexadecimal. - RG
The answer depends on what form you wish to convert binary and hex 2011 to.
Octal = 52746757 Binary = 101010111100110111101111
4F7B: Binary = 100111101111011 Decimal = 20347
The binary equivalent of the hexadecimal number EF16 is 1110111100010110.
01
ABCD1 = 10101011110011010001
It is CEF0.
It is used because it is easier to convert to and from binary to hexadecimal than decimal, and it uses less characters than binary. For instance: decimal: 65535 hex: FFFF binary: 1111111111111111
Well, honey, in assembly language, you convert binary to hexadecimal by grouping the binary digits into sets of four, then converting each group into its hexadecimal equivalent. You can use bitwise operations like shifting and masking to make the conversion process smoother. Just remember, in the end, hexadecimal is just a fancy way of saying "base 16."