shockrah/csnotes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

asdf

Browse Source
This commit is contained in:
Medium Fries 2018-09-04 19:49:07 -07:00
parent bc54f7a60f
commit 3fbaf3ce40
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
cst337/lec/lec2.md
View File

@ -34,6 +34,20 @@ More convinient than binary for obvious reasons; namely it doesn't look like spa
Our 4-bit range from earlier {0000-1111} now becomes {00-ff}. Our 4-bit range from earlier {0000-1111} now becomes {00-ff}.
More pedantically our new hex range is 0x00 to 0xff. More pedantically our new hex range is 0x00 to 0xff.
### Ascii in Hex Dumps > Binary mapped \
It happens that 1 nibble makes up 0x00 to 0xFF.
So for now just get used to converting {0000-1111} to one of it's respective values in hex and evetually it should be second nature.
Then just move on to using hex(like immediately after these lessons).
Even the most obfuscated binary files out there don't resort to architectural obfuscation; until they do.
> Ascii in Hex Dumps \
Kind of a side note but most ascii text is from 0x21 to 0x66ish[citation needed] Kind of a side note but most ascii text is from 0x21 to 0x66ish[citation needed]
## 32 v 64 bit \
For those with a 32 bit background know that these notes deal with 64-bit architecutres mostly. So some quick terminology which might randomly throw you off anyway.
> double-byte/ half-word \
The latter is dumb but soemtimes used so wtever.
> word = 4 bytes
Etc onward with doubles, quads...