To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
Why does WoW64 use register and file sy…

Why does WoW64 use register and file system redirection?

Jan 23 2012
Author:

So, why does WoW64 employ the mechanism of redirecting the register and file system instead of simply assigning the obsolete register keys and "%windir%\system32" to 32-bit applications and allowing 64-bit applications to define new keys and use, for instance, "%windir%\system64" for 64-bit system libraries? It would be rather logical especially if to remember that something similar was done when moving from Windows 3.x to Windows 95/NT.

A bit of history at first. The first Itanium was released in 2001. At the same time the first version of Windows XP 64-bit Edition for Itanium systems appeared. The first 64-bit processors by AMD appeared two years later - in 2003. And two more years later - in 2005 - Windows XP Professional x64 Edition was released. So, Itanium had been a target 64-bit platform long before AMD64 processors appeared.

Unlike x64 (AMD64), the difference between 32-bit and 64-bit code on Itanium (IA-64) is huge. Execution of x86 instructions is either emulated by the chip itself (it is a so called x86 hardware support) or the program emulator IA-32 EL. In the both cases, the mechanism of executing 32-bit applications is very similar to a virtual machine and therefore implies low performance of 32-bit applications. So, Intel makes it abundantly clear that support of 32-bit applications exists only to simplify the process of moving to 64-bit software. It did not mean to be long because there are just a couple of main applications running on a server unlike customer desktops where there are hundreds of programs of unknown origin.

Well, let us put Itanium aside for a while and look at the second factor - the complexity of porting applications to a 64-bit platform. Microsoft tried to make this port as smooth as possible. Actually, it were just enough to recompile an existing 32-bit application with a 64-bit compiler and that is all. But in practice it is not so easy of course - basically because programmers do not follow all the recommendations 100%. There will always be somebody who would like to "cut off a corner", and such optimization turns out badly then.

Now we may answer the question put in the title. We need to virtualize the register and file system because the names of the register keys and disk catalogues used by an application being recompiled remain the same after recompilation as these are just text constants in the program code. Well, it is not so bad with catalogues on the disk though, because you may (and must) get the names of the most system catalogues with the help of the functions GetSystemDirectory, GetWindowsDirectory, SHGetFolderPath and the like. But in case of "System32" it was too bad, because the fixed "System32" was everywhere.

All in all, it was clear that mere recompilation was not enough while search and correct replacement of many string constants in all the applications intended to be ported promised if not to cost much money but at least significantly slow down the process of moving to a new platform. The main problem was not to change the code but to convince software developers to do it. Solving this problem with the least troubles (i.e. using redirection in WoW64) seemed very nice.

As AMD64 appeared - or perhaps it was explained by rather poor sales of Itanium (in comparison with the forecast) - the move to a platform free from 32-bit applications dragged. Most applications are still 32-bit and there is no bottom to it.

All this resulted in what we can see now. Windows XP and Vista x64 has inherited the architecture WoW64 from Windows XP 64-bit Edition for Itanium systems, the move to pure 64-bit systems is dragging while people begin to notice some architectural contradictions (despite which, we should say, the system works rather well).

Popular related articles
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept