All off topic discussions go here. Everything from the funny thing your cat did to your favorite tv shows. Non-programming computer questions are ok too.
Hi, I would like to get my self a copy of intel manuals.
Last time I checked (about half year ago) they were free, I wonder if they are still free? Nothing said about this issue on intels site (so I assume they are).
Now how the procedure is going? I found the ordering form on intels web-site, but they force to enter a company name? What should I write here (I want the manuals for my self, I'm not working in any company, yet)?
Oh and last one: what manuals you suggest me to get? Can I order them all (The developer's manuals)?
Is there any reason you can't just download the PDFs? The Intel manuals do get updated every once in a while, so it is probably better to use the online ones if you can instead of ordering paper copies which will eventually become out of date.
If you really hate the pdfs, you could just print the manual out on normal paper and staple it. I do that sometimes with manuals or specifications, like ELF, but put four pages per sheet to save space. It's cheaper than buying a real manual. But I wouldn't do it unless you refer to the manual very frequently, or where you don't have internet access, because it wastes a lot of paper.
Whats the problem with ordering the manuals? Intel gives free shipping and everything so it's not like your going to waste anything but trees. And paper is easier to read than LCD especially if you will be studying a lot of things from it. Why not use the PDFs to search then read on paper cause its easier?
I don't understand how it's easier to program by reading an actual book. The only plus side of it is that you don't have to stare at the screen, so you could basically sit in a park and read it. But you shouldn't read a manual without being in front of a PC to begin with, there's no way you're going to remember everything just by reading and not trying things out. Otherwise people would read 3 books without touching a PC and become "expert programmers". An assembly programmer is most probably going to spend alot of time in front of a PC screen because he's going to, you guessed it, be typing and reading his own code. So if you can't read text of a computer screen for a while, how are you supposed to read thousands of lines of assembly code?
Edit: Also, fatigue is in play here. If you have your book on your desk and a turned on screen, you're going to get neck pains and eye fatigue very soon if you keep swapping between the two. Personally, I rather read books of the screen. And when my eyes get weary I just take a 20 minute break, look into the distance and relax. Then I can resume working again. But that's just me I guess.
Malevol3nt wrote:I don't understand how it's easier to program by reading an actual book. The only plus side of it is that you don't have to stare at the screen, so you could basically sit in a park and read it. But you shouldn't read a manual without being in front of a PC to begin with, there's no way you're going to remember everything just by reading and not trying things out. Otherwise people would read 3 books without touching a PC and become "expert programmers". An assembly programmer is most probably going to spend alot of time in front of a PC screen because he's going to, you guessed it, be typing and reading his own code. So if you can't read text of a computer screen for a while, how are you supposed to read thousands of lines of assembly code?
Edit: Also, fatigue is in play here. If you have your book on your desk and a turned on screen, you're going to get neck pains and eye fatigue very soon if you keep swapping between the two. Personally, I rather read books of the screen. And when my eyes get weary I just take a 20 minute break, look into the distance and relax. Then I can resume working again. But that's just me I guess.
true.. but I've read through programming stuff on my bed(where I'm more comfortable) and then anything I didn't understand I compile the test code and try it out..
I personally dont care if the books do get outdated in a year or two. They still contain alot of information that will be around for awhile. Of course, this is just me - I personally prefer the books and use them more then the PDFs.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
neon wrote:I personally dont care if the books do get outdated in a year or two. They still contain alot of information that will be around for awhile. Of course, this is just me - I personally prefer the books and use them more then the PDFs.
I'm in the same boat. I prefer the books over the PDFs: I can have them open in front of me without using up screen real estate (because I already use both screens extensively).
Also, I can find what I'm looking for faster in the paper manuals than I can in PDF format (fulltext search gives false positives and the table of contents and index are more accessible in paper form IMHO).
