Windows Vista x64

Today, I released my new article about Windows Vista and the x64 platform.

Here’s the article’s index:

Introduction
x64 Section
x64 Assembly
C/C++ Programming
Inline Assembly
Windows On Windows
File System And Registry Redirection
Interprocess Communication
Portable Executable
Exception Handling
.NET Framework
Vista Section
Editions
Microsoft Visual Studio
User Account Control
Compatibility Verification
Obtaining Admin Rights
Disable It
Address Space Layout Randomization
Driver Signing
Patch Guard
Attacks
Registry Filtering
Power Management
.NET Framework 3.0
Windows Presentation Foundation
Windows Communication Foundation
Windows Workflow Foundation
Conclusions

I hope you enjoy the article and don’t dislike the idea of such a general overview about two really extensive subjects like x64 and Windows Vista. I noticed during the writing that I had to put a lot of images in the article and that this might be problem for slow connections. I’m sorry for that, but it’s the direct consequence of not subdividing this paper in more articles.

This entry was posted in Uncategorized. Bookmark the permalink.

4 Responses to Windows Vista x64

  1. Anonymous says:

    A great article, thank you.

    -andrewl

  2. Anonymous says:

    Great article about Vista – didn’t realize there were so many valuable new things.

  3. hiru says:

    This is the greate artical. that helped me to solved my problem. Please can you guide me for my one problem. i am working on MFC dialog base application then how can give manifest file support to this application. i have done same process with this application as you done in your demo application but it’s not working with MFC dialog base application. Please guide me … hiren@promactinfo.co.in

  4. Ntoskrnl says:

    Be careful, MFC has its own manifest, if your new manifest is not defined with ID = 1, then you’ll end up with two manifests in your application. The first one is the MFC one and has ID 1 and yours with ID, let’s say, 101. Of course, yours will be ignored, only the manifest with ID 1 is considered. Check this situation with the CFF Explorer. The solution is easy, just make sure that in resource.h your manifest ID is defined as 1.

Leave a Reply

Your email address will not be published. Required fields are marked *

*