Windows Internals book

This is a discussion on Windows Internals book within the Windows Programming forums, part of the Platform Specific Boards category; I'm not sure whether I'm posting it in the right forum. My question is about the Windows Internals book. I'm ...

  1. #1
    Registered User
    Join Date
    Apr 2008
    Posts
    49

    Windows Internals book

    I'm not sure whether I'm posting it in the right forum. My question is about the Windows Internals book. I'm trying to determine which edition I should buy.

    Each new edition is updated to cover a new version of Windows (4th edition focuses on Windows XP, 5th edition focuses on Windows Vista and 6th edition focuses on Windows 7). Are the changes from one edition to the other only incremental, or is material related to older versions of Windows deleted?

    If I buy the 6th edition, will the theory and hands-on experiments in this edition be valid for understanding Windows XP? If I want to understand Windows XP and Windows 7, do I have to buy two different editions?

  2. #2
    Registered User ledow's Avatar
    Join Date
    Dec 2011
    Posts
    435
    I think that pretty much they only cover the OS they state they cover. Old information is removed, I believe, to stop people trying to use it in newer programs.

    So really you're probably looking at two copies of different versions but, to be honest, I'd question why you think you need that particular book. Or why you can't just buy one version and extrapolate the information to cover the other OS using MSDN and similar.

    To be honest, I've never bought a book on Windows programming specifically. Sure, I've never written a device driver or anything deeply internal, but I don't see the need for something that's available as API listings and tutorials all over the Internet that will have more information than any one book could ever give you.

    - Compiler warnings are like "Bridge Out Ahead" warnings. DON'T just ignore them.
    - A compiler error is something SO stupid that the compiler genuinely can't carry on with its job. A compiler warning is the compiler saying "Well, that's bloody stupid but if you WANT to ignore me..." and carrying on.
    - The best debugging tool in the world is a bunch of printf()'s for everything important around the bits you think might be wrong.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Book for learning C under windows
    By Hritik in forum C Programming
    Replies: 5
    Last Post: 12-26-2012, 08:56 AM
  2. Windows GUI book recommendations c++
    By Freem in forum C++ Programming
    Replies: 4
    Last Post: 07-10-2011, 11:43 PM
  3. Internals of OPENMP?
    By chiku123 in forum C++ Programming
    Replies: 1
    Last Post: 10-23-2007, 11:19 AM
  4. The internet's internals revealed
    By valis in forum A Brief History of Cprogramming.com
    Replies: 22
    Last Post: 07-29-2006, 09:13 AM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21