Windows 32 64-bit Dll Storage

Windows 32 64-bit system Dll storage sometimes people doubt whether the underlying structure of a system can ensure that the system is safe and efficient when used. The 64-bit version of Windows is perfect in this regard. Windows XP and Windows Server 2003 are both 64-bit operating systems that run 64-bit hardware. The 64-bit Windows operating system runs 64-bit code, and WoW64 (Windows on Windows 64) can also run 32-bit code. You can see that this is not a big problem. After all, different Windows operating systems of the 32-bit version are used to run 32-bit and 16-bit code simultaneously. (Technically speaking, it does not run at the same time. Relevant explanations will be presented to you in future skills) 32-bit Windows has a complicated mechanism in how to allow 32 to run side by side with 16-bit code. However, whether you are a system administrator or a temporary user, you do not need to know how these mechanisms work. However, the 64-bit version of Windows is different. From the standpoint of a user, 64-bit applications and 32-bit applications run at the same time. However, for an administrator (and a person who helps desktop users), this is very different: 32-bit code is isolated from 64-bit code. This isolation is so important that 64-bit Windows has two registries, one for 64-bit and the other for 32-bit. Www.2cto.com although the 64-bit Windows XP and Windows Server 2003 seem to be the same as their 32-bit versions, they are actually quite different in appearance. If you execute some programs in 64-bit Windows based on the 32-bit version, you may cause some trouble. Where is the DLL stored? The first rule of a 64-bit application is: you must not mix 32-bit and 64-bit code in the same application. If you have a 64-bit application, all the things related to this application, including DLL files, must be 64-bit. This has an interesting challenge, because sometimes many applications rely on a common DLL file. Fortunately, Windows keeps 32-bit DLL files and 64-bit DLL files isolated. If you look at the/Windows folder in a 32-bit operating SYSTEM, you will find two sub-directories: one named SYSTEM and the other named SYSTEM32. The SYSTEM directory is a legacy of Windows 3.x to maintain Windows's downward compatibility with some old applications. Generally, 16-bit DLL files (and other supported files) are stored in the/Windows/System folder, 32-bit DLL files and different support files are stored in the/Windows/System32 folder. In 32-bit Windows, it is very easy to maintain 16-bit and 32-bit DLL files, however, the 64-bit version of Windows does not support 64-bit and 32-bit DLL files. In theory, Microsoft will create a folder named/Windows/System64 to store 64-bit DLL files, but instead, microsoft has created a new folder named SysWOW64 to store 32-bit DLL files. At first glance, it seems that this folder should store 64-bit applications, but note that 32-bit applications should have stored their DLL files in the/Windows/System32 folder. The www.2cto.com/Windows/System32 folder still exists in 64-bit Windows. However, Microsoft uses this folder as a 64-bit DLL repository, instead of a 32-bit DLL file. I do not know why Microsoft uses the/Windows/System32 folder to store 64-bit DLL files, but I have heard that this is done for backward compatibility. So should all 32-bit applications store their DLL files in the/Windows/System32 folder? This makes things messy. As I mentioned earlier, 32-bit code cannot run in 64-bit Windows by default. To run 32-bit applications, Windows uses WOW64 emulator to enable these applications to run in 32-bit Windows. When you install a 32-bit application, the installation wizard runs through WOW64 emulato. The 32-bit and 64-bit codes are not mixed. Once an application (including an installation wizard) starts running from WOW64 emulator, it must continue running within WOW64. This means that when you install an application, the installation wizard does not know that the program is installed in a 64-bit version of Windows, and write the DLL file to the/Windows/System32 folder like the 32-bit operating system. Of course, WOW64 knows the 32-bit application that runs through emulator in the installation wizard. We also know that 64-bit and 32-bit codes cannot be mixed together. Therefore, WOW64 emulator creates an alias for/Windows/SysWOW64. This means that the 32-bit application will be written to the/Windows/System32 folder or read from the/Windows/SysWOW64 folder at any time, and WOW64 emulator will be able to change it to the/Windows/SysWOW64 folder. Www.2cto.com all of these means that if you need to manually operate the content in the/Windows/System32 folder, you may be very troublesome. I recently learned that an administrator needs to install some small support scripts to an installed application. The script instructions indicate that these scripts need to be stored in the/Windows/System32 folder. Of course, the description of these scripts assumes that the application runs on a 32-bit operating system. These scripts did not cause a system crash. However, Windows never requires updates. When the Administrator runs the application, it will be redirected to the/Windows/SysWOW64 folder. The Administrator knows that he has put these scripts in the/Windows/System32 folder and can see these scripts in the Windows browser, but does not indicate why the application cannot see these scripts. Considering that this issue is related to permissions, he spent some time studying this issue, so he learned how to save DLL file isolation in 64-bit Windows, so he can put these scripts in the/Windows/SysWOW64 folder. 64-bit Windows is very important for an administrator to understand the underlying system structure. In a 64-bit system, store the 32-bit DLL file in the/Windows/SysWOW64 folder.