The program on the 64 bit system. Windows XP x64: promises and reality. Example: Using indicative data types

This is an article based on issues on the forums: "How can I return the line from DLL?", "How to transfer and return an array of records?", "How to transfer to the DLL form?".

In order for you not to spend half of life to figure out - in this article I will bring everything on a scenery.

The topics of this article in varying degrees have repeatedly affected this blog, but in this article they are collected in a bunch, justifications are given. In short, reference to this article can be thrown in those who develop DLL.

Important note: The article needs to be read sequence. Examples of code are given only as examples, at each step (paragraph) of the article, the code of examples is added with new details. For example, at the very beginning of the article, there is no error handling, "classic" methods (such as, using GetLastterror, SDTCALL agreements, etc.), which in the course of the article are replaced with more adequate. Made so for the reason that the "new" design ("unusual") designs did not cause questions. Otherwise, when I had to insert a note of the species to each example: "This is discussed at that point below, but what is this. In any case, at the end of the article there is a link to the ready-made code, written in the whole of what has been said in the article. You can just take it and use. And the article explains why and why. If you are not interested in "why and why", leaf at the end to the conclusion and link to download the example.

The appearance of 64-bit Windows caused a lot of questions. Support for 32-bit applications, drivers and all that is designed for the X86 architecture. Installation and features of the use of programs. Entered restrictions for 32-bit applications. Support for old modes and much more. All this could not stay aside. After all, the 32-bit heritage layer is too large, and in the 64-bit environment it can be replaced, even now.

This article reviews Windows Subsystems on Windows 64 (WOW64) and its methods that allow Windows to support 32-bit applications on a 64-bit system.

Note: The first attempt to introduce 64-bit systems was sufficiently fail. Hard restrictions and lack real advantages gave itself to know. At that time, even the drivers under 64-bit systems was quite difficult to find. Not to mention the programs on which the difference would somehow be noticeable. Removing the limit on 3GB of RAM is definitely a strong advantage today, but at that time it resembled a beautiful slogan.

32-bit apparatus support device in 64-bit Windows

Windows 32 on Windows 64 (WOW64)

Wow64 emulates 32-bit windows

In Windows 64, 32-bit applications are performed in an emulated 32-bit operating system, which is called Windows 32 on Windows 64, or WOW64 for brevity. The main task of WOW64 is the interception and processing of all system calls from 32-bit applications.

For each intercepted system call, WOW64 creates a 64-bit system call, turning 32-bit data structures into suitable 64-bit. Subsequently, a 64-bit system call is transmitted to the kernel operating system for processing. All obtained output 64-bit call will be converted and transmitted in the format to which the application calculated. In other words, real requests The system of the system is always 64-bit. The Wow64 subsystem only acts as an intermediary, attracting data into suitable formats.

Like 32-bit applications, WOW64 is executed on behalf of the user, so errors that can occur while converting system calls will occur at the user level. And the 64-bit kernel of the operating system will not affect.

The fact that WOW64, like a 32-bit application, is performed in user mode, explains the reason for the lack of support for 32-bit drivers. If you speak in other words, for the correct startup, the drivers require a kernel mode that cannot provide WOW64. Therefore, if you have 64-bit Windows, then all drivers must be 64-bit.

Wow64 emulator consists of the following 64-bit libraries:

Note: These are the only 64-bit libraries that are loaded into a 32-bit process.

Wow64.dll - the core infrastructure of the emulation system. Links calls to the entry point ntoskrnl.exe
Wow64win.dll - links calls to the entry point Win32k.sys
Wow64cpu.dll - switches the processor between a 32-bit and 64-bit mode
Ntdll.dll - 64-bit version of WOW64.

WOW64.DLL loads the 32-bit version (x86) ntdll.dll and all the necessary 32-bit libraries that have mainly remained unchanged. However, some of these 32-bit libraries were still changed to be correctly executed in WOW64. As a rule, such changes were made due to the fact that they use the RAM together with 64-bit components of the system

Manage files and registry settings in WOW64

In addition to the functions of interception and processing system calls, the WOW64 interface should also ensure that the files and registry parameters of 32-bit applications will be stored separately from the files and key registry keys of 64-bit programs. To achieve this goal WOW64 uses two mechanisms. Redirect files and registry, as well as duplication of registry keys. Redirect supports a logical view of data and displays them as if the application was launched in 32-bit Windows. The registry key duplication ensures that the change in the parameters that does not depend on the bit will be available both 32-bit and 64-bit applications.

File redirection

File redirection allows you to ensure that the files and directory of 32- and 64-bit applications will be stored separately and do not interfere with each other.

32-bit applications, default, are installed in:

C: \\ Program Files (x86)

32-bit system files Installed in:

C: \\ Windows \\ syswow64

For 64-bit applications, files are installed in:

C: \\ Program Files
C: \\ Windows \\ System32

WOW64 redirection mechanism ensures that queries from 32-bit applications to the "C: \\ Program Files" and "C: \\ Windows \\ System32" catalogs will be redirected to the appropriate directories for 32-bit versions.

However, there is one problem with file redirection. Users and developers should be aware of this feature.

Many 64-bit applications still use 32-bit mode and procedures. And do not take into account this when creating the installer. In order for the application to be installed correctly. those. In "C: \\ Program Files", the installer must make a system call to the operating system, so that the system has suspended the WOW64 file redirection mechanism. And after installation, make another system call to turn on the redirection again. If you install without stopping redirection, the program will be installed in "C: \\ Program Files (x86)". The classic example of this error is 64-bit firefox version 3.5 Under the code name "Shiretoko", which is installed in "C: \\ Program Files (x86) \\ shiretoko". Of course, Firefox will continue to function normally. The only thing you can do is change the application icon.

Note: Perhaps now this error in Shiretoko has already been corrected. However, in early versions It was so.

Registry redirection

Registry keys specific to 32-bit applications, will be redirected from the branch:

HKEY_LOCAL_MACHINE \\ SOFTWARE.

HKEY_LOCAL_MACHINE \\ SOFTWARE \\ WOW6432Node

Also, sometimes, you can meet the registry entries in another branch (although it is unusual):

HKEY_CURRENT_USER \\ SOFTWARE \\ WOW6432NODE

This approach allows 32- and 64-bit applications normally coexist, without problems with overwriting each other settings.

Duplication of registry

Some redirected keys and registry values \u200b\u200bmust be duplicated. This means that if a 32-bit application makes changes to the registry redirected section, then these changes are also used to apply for branches of 64-bit applications. In this case, the principle of "who is the last, that and right" is valid. For example, if you set three applications that attribute themselves to the same file extension, the association with the file extension must be with the latest application.

Install a 32-bit application that associates itself with XYZ extension
Set the 64-bit version of the application that binds itself to the XYZ file extension
Install another 32-bit application that associates XYZ extension with you

As a result of these actions, double-click on the file with the xyz extension in windows Explorer The application must be opened, which was installed on the 3rd step. After all, it is it that the latter associated itself with the expansion.

All this is transparent for 32-bit applications in WOW64, which independently intercepts circulation and duplicates the necessary parameters and registry keys. In other words, 32-bit applications can be carried out in the standard way, the necessary changes for them will contribute to WOW64.

There are a number of restrictions of the Wow64 subsystem

Some, but not all, 64-bit features are available 32-bit applications.

WOW64 allows 32-bit applications to use some functions and capabilities of 64-bit systems. For example, for proper settingSuch applications will be able to use up to 4GB RAM. Access to other functions is limited due to the features of the device 64-bit systems. For example, a 64-bit Windows OS supports 64-bit logical operations. However, 32-bit applications will not have access to them, they can only use 32-bit logical operations.

Note: The main cause of restrictions is the difference in presenting data for 32- and 64-bit applications. The 32-bit application is simply not calculated on 64-bit data types.

Cannot mix 32-bit and 64-bit applications

In the 64-bit Windows OS, 32-bit code cannot be launched in a 64-bit process, as can not be launched a 64-bit code in a 32-bit process. Applications using code injection (Code Injection) to add functionality to existing applications, as a rule, will issue errors.

This fact explains why most 32-bit extensions windows shells Do not run under 64-bit Windows. Most of these extensions use code inject (code injection) to embed into Windows Explorer

WOW64 does not support 16-bit installers

WOW64 provides support for 16-bit Microsoft installers by replacing the installer to a compatible 32-bit version. However, this support does not apply to third-party products. So if you need to use old program, Most likely, you will have to look for an emulator or portable version.

Additional features for running 32-bit applications in Windows 64

Windows Virtual PC.

Windows Virtual PC is a free software that allows you to run multiple operating systems on one computer. Virtual PC provides a special execution environment that supports outdated equipment and software that will not be determined and run in Windows 7. All running operating systems under Virtual PC will be performed in a virtual machine. This means that running operating systems will not be aware that they are running in another system.

System requirements and a set of functionality differ significantly between VIRTUAL PC versions and Windows versions. So, before you attempt to use Virtual PC, you need to check that the program supports both your operating system and those OS that will be launched on it. For example, one of recent versions No longer supports windows version Below Windows XP SP3.

Windows XP (XPM) mode

Windows XP Mode is a specific and trimmed implementation of Windows Virtual PC, which comes with pre-installed copy of Windows XP Professional SP3. This mode is available only in the ENTERPRISE, ULTIMATE and PROFESSIONAL Windows 7 64-bit versions.

Although it would be necessary to submit this regime, many who used XPM, strongly advise using this mode only as last remedy. Compared to other virtualization products, performance disappoints, and the default configuration calls a number of security issues.

Note: Some more denational settings of the compatibility mode can still be applied. More detailed information Can you find in a review How to run old programs on Windows 7 / Vista? (cm. Microsoft Application Compatibility Toolkit).

Multiple of Windows

You can set more than one version of Windows on one computer using a multi-loader. For example, install 32-bit and 64-bit versions of Windows next to each other. Each operating system is installed on a separate disk section, and the download manager is set to the default section. Download manager Allows you to select and run the operating system you want to use now.

Although you cannot simultaneously use more than one operating system, this functionality is quite useful. Compared with virtual machinesThis method has no problems with compatibility and such systems are much easier to customize and maintain. Among other things, installing the 32-bit version next to the 64-bit, you save the ability to run 16-bit applications.

Summarizing the above-mentioned 32-bit in 64-bit Windows

Most 32-bit applications will be quite happily feel in Windows 64. The main exceptions will be:

32-bit devices drivers
Applications that cannot function without 32-bit device drivers that they use. Bright examples are antiviruses and other security programs.
Extensions that use code injection (Code Injection). For example, shells for Windows Explorer

Some applications will be able to run with limitations. It also concerns uninstallastors, program for cleaning the registry and tuning programs, as they have access only to that part of the registry that WOW64 shows them.

If you can not start a 32-bit application, then consider the option with virtualization or multizlect of multiple operating systems.

What applications faster 32-bit or 64-bit?

This question sounds quite often. But there is no general rules or multiplication factor, since it all depends on the tasks and the functions of the processor.

If you compare 32- and 64-bit applications in your native environments, the 32-bit application usually uses less memory than an equivalent 64-bit application. This is because 64-bit versions use 64-bit data structures that are twice as much space. Additional size directly affects the start time and closing of the program, as well as on other types of operations related to access to disk drives. Usually, this means that 32-bit applications will be performed faster. However, the use of 64-bit programs of the 64-bit processor features potentially allows the application to be performed by 25% faster, compared with 32-bit programs.

In addition, it is necessary to remember that the launch of a 32-bit application on a 64-bit Windows means starting WOW64, so the performance analysis on a 32-bit processor can be deposited aside. WOW64 starts not only the cost of converting calls, but also to account for redirection and duplication mechanisms, which require not only processor time, but also rAM. Therefore, perhaps a 32-bit application will be performed faster than 64-bit, but it will definitely be performed slower than with an equivalent start on a 32-bit processor.

Rating 5.00 (6 votes)

Modern computers in most cases are supplied with the Windows 10 64 Bit operating system installed. Even budget models already have 3 and more GB of RAM, which allows the system to use the system all the power of 64-bit data processing.

Read more about the benefits of 64 bit over 32 Bit Windows you can read in our article "".

But, no matter how an attractive 64-bit system was attractive, often the user simply has no 64-bit program at its disposal, with which it has long been working and which is completely satisfied with it, because The manufacturer simply did not release her. As a rule, such programs are installed in Windows in separate folder \\ Program Files (x86) and their launch is carried out in 32-bit mode.

If during the startup process the program gives an error or does not start at all, and in Windows 32 BIT it worked without problems, there is a chance to start it in a special mode, which developers called "compatibility mode".

To do this in Windows 7, click right-click Mice on a label necessary programAnd then select Properties in the context menu. In the window that opens, go to the Compatibility tab and select the "Run a program in compatibility mode with ..." checkbox and in the drop-down list, specify the system option to start.
Click the OK button. After that, try running your program.

In addition, in the context menu, the conductor also makes sense to try to automatically solve the task by clicking on the "Compatibility Problem Correction" line - in Windows 7.

In Windows 10, when configuring startups in compatible mode, on the Compatibility tab, there is a separate button "Run a compatibility problem". After that, you will be offered or use the recommended parameters, or to diagnose the program.

If the program does not start after this, it is worth it to approach the problem more thoroughly and try the options specified on the official website of Microsoft.

A more radical method of starting the program is to install it and use in a virtual machine with installed windows 7 32 Bit. Read more, how to install and configure virtual Machine You can read in our article "".

Today I propose to discuss advantages and disadvantages. 64-bit OSwhich is equipped with most of the modern computers with the Windows 7 operating system.

Before 64-bit systems were the lot of professionals and were used for programs requiring enormous resources. Home users accounted for a 32-bit version of Windows. And although 64-bit processors appeared on the market already in 2003, (in 2005, 64-bit Windows XP appeared), on new computers, the 64-bit system was installed only with Windows 7 output.

So, what is good 64-bit architecture? What advantages do we get and whether it works faster? With what problems to us, simple users, have to face?

On the 32-bit screen and 64-bit versions of Windows 7 look absolutely the same. The possibilities are identical, the programs are the same, however, the differences are essential!

1. Processing speed data above 2 times. The 64-bit processor is capable of processing a 64 data bits (8 bytes) in contrast to a 32-bit, processing only 32 bits (4 bytes) per unit of time, that is, the data processing speed is 2 times higher! Accordingly, the programs for 64-bit operating systems work much faster than similar, working on 32-bit OS.

2. Available more RAM.A 32-bit version of Windows maximizes only 3.5 GB of memory, while it is not fully available to programs. For example, the operating system takes 1 GB of memory, plus to 1 GB can be reserved for video memory, and only 1.5 GB will remain for programs. And if the programs are particularly "voracious", memory is not enough.

64-bit versions of Windows have these problems. Windows 7 Home Premium uses a maximum of 16 GB of operating memory and thanks to this Windows less often uses the paging file (used by the system to place data that are not placed in RAM), and the computer works much faster.

Requirements of the 64-bit system to a computer

1. Processor. As you already guessed, one of required conditions for work 64-bit OS - This is a 64-bit processor architecture. Intel this technology is called EM64T, and one of the largest producer AMD processors it calls AMD64.

2. RAM. 64-bit Windows requires at least 4 GB of RAM. And unlike 32-bit operating systems 64-bit OS other special requirements Do not have a computer package.

To check the version of your operating system, click "Start" -\u003e Right-click on "Computer" and select "Properties" in the drop-down menu -\u003e in the window that opens, on the right side, the version of your operating system is displayed.

Disadvantages of the 64-bit system

1. Requires new drivers. As you already guessed, for 64-bit Windows 7, new drivers are required (similar drivers for a 32-bit operating system are not suitable). Latest models Devices are already available with new drivers, but problems can arise with the desired modules, since manufacturers do not develop drivers for the 64-bit version of Windows. Be careful before switching to 64-bit Windows, go to the device manufacturers sites and check the presence of 64-bit versions of drivers for your equipment.

2. Need more memory. It must be remembered that most of the 64-bit programs have the size of the data structure of 8 bytes (64 bits) and on hard disks They occupy about 10-20% more space than 32-bit software versions with 4 bytes structure. Runger consumption rises by about 15%

Is it possible to install 64-bit Windows 7 on a netbook?

With the advent of the 64-bit processors "PineView" (N450 and above), the netbooks have the ability to use 64-bit software. However, the stumbling block can be the RAM. Most netbooks are equipped with 1 GB of memory. And even if you do up up to 2 GB, it will barely reach minimum requirements 64-bit Windows 7. So, friends, about effective use 64-bit system on netbooks, it is not yet (not less than 4 GB of RAM).

Is it possible to use 32-bit programs for a 64-bit OS?

In 64-bit Windows, there is a Windows-On-Windows 64-bit conversion subsystem (WOW64), which ensures 32-bit compatibility software with a 64-bit OS. Most of the 32-bit programs are immaculately working with WOW64, however, there are some exceptions:

Programs for reserve copy . When creating backups, the program directly appeal to systemic windows foldersAnd wow64 in some cases redirects the access of 32-bit software to other folders. Those. If you do not recover reservation programs, the result of their work may be incomplete and erroneous.
Programs for windows optimization . Programs created to optimize 32-bit Windows in no case can be used on 64-bit Windows 7, harm from their work will be much more than help.
PC Programs. If you need excellent computer protection, then for 64-bit Windows, use only 64-bit versions. antivirus software. Old 32-bit software is not able to provide reliable protection and miss viral attacks developed for a 64-bit OS.
Speed \u200b\u200bof work. Outdated 32-bit on 64-bit Windows runs slower than in the native 32-bit environment. The reason for the extra temporary costs of converting the WOW64 subsystem.

To see what 32-bit programs work in a 64-bit system, it is enough to start the task manager (press the Ctrl + Shift + ESC keys), and find programs marked with * 32 icon.

So, dear friends will summarize

When you go to work with a 64-bit Windows 7, you should pay attention to several significant factors.

1. Computer configuration requirements:

64-bit processor architecture;
4 GB of RAM.

2. Software compatibility:

availability of necessary new drivers for your devices;
availability of updates to the newest 64-bit programs.

1. Check the software compatibility of your devices from 64 bit OS can be in the Center windows compatibility 7.

2. When working with a 32-bit program failures on a 64-bit system, an update software has been helped new versionwhich can usually be found on the manufacturer's website.

Shortly after the release of Windows XP Professional X64 Edition, Microsoft tried to attract consumers to the new version, offering free program Windows replacement. Windows XP Professional Owners can go to version X64 completely free - only the license for the 32-bit version will already be invalid.

But buying a cat in a bag is not too convenient, because 64-bit drivers for a number of old devices and peripherals did not come out. After switching to x64, scanners and multimedia devices like WEB cameras can simply not earn, since small manufacturers and so-called "No-Name" companies often do not rush to translate drivers under Windows XP x64. One of the reasons is limited resources. Another - to encourage the consumer to buy a new product with the X64 driver, if he wishes it.

Solving many problems with the launch, Windows XP Professional X64 Edition supports 64-bit processors. The system allows you to address more than 4 GB system Memory, And the enlarged bit of data allows you to increase the performance of applications transferred or written for 64-bit Windows.

However, the advantage of memory can easily become a disadvantage if you have little. Since each data element has a length of 64 bits, 32-bit elements for hereditary 32-bit applications will be two times more memory compared to the 32-bit OS. From this point of view, it is unlikely to make sense to go to Windows XP x64 with a small amount of memory. If you want to go to x64, then we recommend installing at least gigabyte RAM.

For our project, we took most of our standard test package (only 32-bit applications) and compared 32-bit Windows XP performance with Windows XP X64 Edition. Test system Athlon 64 was equipped with two 512-MB DIMM DDR400. We conducted tests both at the most quickly single-core Athlon 64 FX-57 processor and on its sonar opponent Athlon 64 x2 4800+.

Determine whether your system is ready for running 64-bit Windows, you can on the processor. As for AMD, the AMD64 support processor is needed here - like Athlon 64 or new SEMPRON. In the case of Intel, you should look for a chip with EM64T extensions (previously known as Yamhill or Clackamas) like a Pentium 4,600 line, Pentium D, Pentium Extreme Edition or Celeron D if the number of the 300th model ends at 1 or 6.

From the point of view of a set of features, there is no reason to go to Windows XP Professional X64 EDITION. The system for sensations and work is exactly the same as 32-bit Windows. In addition, the X64 Edition is selling today, for the most part, in the form of an OEM version along with new computers, so it is quite problematic to buy it in retail.

The most important problem of the new OS is support for drivers for devices and peripherals. Therefore, before the transition to X64, it should be carefully weighed. If you have a device that you can't or do not want to replace, and for which there are no 64-bit drivers, it is better to stay on a 32-bit Windows. This is especially true of the periphery: printers, scanners, multimedia devices, etc.

The X64 version can work with memory up to 32 GB and 64-bit and 32-bit applications simultaneously. Windows X64 uses the broadcast level called Wow64 (Windows On Windows 64), which converts 32-bit commands, parameters and data for the 64-bit kernel. Although the traditional Windows XP is capable of addressing up to 4 GB of memory (2 32), only 2 GB are available for applications. At the X64 Edition version, the situation is different: all 4 GB of memory are available for 32-bit applications. An even greater advantage is achieved when using 64-bit applications, since the amount of the addressable memory here is limited only by the volume of the installed RAM.

Since in one beat now you can handle more data, then 64-bit applications under Windows XP can give a significant productivity gain. However, before most of the applications are translated into a 64-bit platform, there will be a lot of time. If you are using, basically 32-bit applications, then mentioned problems should be taken into account.

Today, AMD and Intel produce processors with support for 64-bit calculations. However, the role of the pioneer in this transition belongs to AMD, as the Athlon 64 line has come out almost two years ago. Intel, opposite, did not see any advantages for 64-bit calculations on mass desktop PCs before the beginning of this year.

On the this moment everything aMD processors Athlon 64 And the Intel desktop chips row for Socket 775 support 64-bit calculations. They include:

Pentium 4 from 630 to 670;
Pentium d 820, 830, 840;
Pentium Extreme Edition (Double);
Celeron D 326, 331, 336, 341, 346, 351, 355.

If only Mobile Sempron does not support 64-bit calculations, then Intel does not plan to translate mobile processors By 64 bits in the near future - simply their architecture is not yet ready. As we expect, the Yonah processor is both a single-line 7x6 line and dual-core processors, most likely, from the 800 line - will enter the market at the beginning of the first quarter of 2006, after which the version of Merom must follow 64-bit computing.

64-bit processor modes

AMD Athlon 64 works with a 32-bit Windows in hereditary mode, while the expansion X86 64 is not used. If you run the 64-bit OS, the AMD64 processor will work in a 64-bit long mode, and Intel chips will turn on the IA32E. Both modes, of course, are the same because Intel uses AMD64 technology, thanks to license Agreement with AMD.

In the Long Mode mode, the processor is capable of performing 64-bit "native" instructions, the compatibility regulations are available in which the processor becomes compatible by binary Coda With 16-bit and 32-bit applications. Although today the difference is not tangible, but the physical address space is limited to AMD 52 bits, and Intel has 40 bits. However, it is unlikely to manifest itself in the near future, since 40 bits are enough to address 1 TB (Terabyte) or 1024 GB of memory.

For more information on 64-bit support can be found on the following resources.

Test configuration

CPU
Single-core CPU.	AMD Athlon 64 FX-57 (2.8 GHz, L2 Cache 1 MB)
Double CPU.	AMD Athlon 64 x2 4800+ (2.4 GHz, 2x 1 MB cache L2)
Memory
AMD platform (DDR400)	2x 512 MB - DDR400 (200 MHz) Corsair Pro Series CMX512-3200XL (XMS3208 V1.1) (CL2.0-2-2-5-1T @ 200 MHz)
Motherboard
AMD Platform	ASUS A8N-SLI DELUXE (Rev. 1.02, BIOS 1007) NVIDIA NForce4 SLI chipset
System hardware
Graphic Map (PCIE)	nVIDIA GeForce. 6800 GT (reference) GPU: NVIDIA GeForce 6800 GT (350 MHz) Memory: 256 MB of DDR SDRAM (500 MHz)
HDD	Western Digital WD740 Raptor 74 GB, Cash 8 MB, 10 000 rpm
Net	Built-in NVIDIA GBE Ethernet
DVD-ROM.	Gigabyte GO-D1600C (16x)
Power Supply	Tagan TG480-U01, ATX 2.0, 480 W
Software
Drivers chipset	nVIDIA FORCEWARE 6.53.
X64 chipset drivers	nVIDIA FORCEWARE 6.66.
Processor driver	AMD CPU DRIVER 1.1.0.18
Graphic driver	nVIDIA FORCEWARE 71.84
DirectX	Version: 9.0c (4.09.00 20.0904)
32-bit OS	Windows XP Professional 5.20.3790, SERVICE PACK 2.
64-bit OS	Windows XP Professional 5.10.2600, SERVICE PACK 2.

Tests and settings

OpenGL
Doom III.	Version: 1.0.1262. 1024x768 - 32 Bit Video Quality \u003d High Quality "CUSTOM TIMEDEMO" Graphics Detail \u003d High Quality
Wolfenstein.	Version: 2.56 (Patch v 1.02)
Enemy Territory.	1280x1024 - 32 Bit Timedemo 1 / Demo Demo4 Geometric Detail \u003d High TEXTURE DETAIL \u003d HIGH
DirectX 8.
Unreal Tournament 2004.	Version: 3204. 1280 x 1024/32 Bit / Audio \u003d OFF THG8-Assault-Single
3DMark2003.	Version 3.6.0. 1024x768 - 32 Bit
DirectX 9.
Farcry.	Version 1.1 Build 1256 1280x1024 - 32 Bit QUALITY OPTIONS \u003d LOW
3DMark 2005.	Version 1.0. 1024x768 - 32 Bit Graphics and CPU DEFAULT BENCHMARK
Video
MainConcept Mpeg Encoder.	Version: 1.4.2. 1.2 GB DV TO MPEG II (720x576, Audio) Converting
Pinnacle Studio 9 Plus	Version: 9.1.2 From: 352x288 MPEG-2 41 MB to: 720x576 MPEG-2 95 MB Encoding and Transition Rendering to MPEG-2 / DVD no audio.
AUTO GORDIAN KNOT. DivX 5.2.1 XVID 1.0.2.	Version: 1.95 Audio \u003d AC3 6CH Custom Size \u003d 100 MB Resulution Settings \u003d Fixed Width Codec \u003d Xvid and DivX 5 Audio \u003d CBR mp3, kbps 192 182 MB VOB MPEG2-Source
Windows Media Encoder.	Version: 9.00.00.2980 720x480 dv to wmv 320x240 (29.97 FPS) 282 kbps streaming
Windows Media Player. 10	Version: 10.00.00.36.46
Audio
LAME MP3	Version 3.96. Wave 17:14 Minutes (182 MB) to mp3 32 - 320 kbit VBR \u003d LEVEL 3
Applications
WinRar	Version 3.42. 283 MB, 246 Files Compression \u003d Best. Dictionary \u003d 4096 KB
3D Studio Max 6.0 Discreet.	Characters "Dragon_charater_rig" Pixel: 1024 x 768 Rendering Single
Synthetic tests
PCMark 2004 Pro.	Version: 1.3.0. CPU and Memory Tests
Sisoftware Sandra Pro.	Version 2005, SR1 CPU Test \u003d Multimedia / CPU ArithMetic Memory Test \u003d Bandwidth Benchmark
Wstream	Version: 5. 100 Operations With 25 MB File

Similar comparison results between 32-bit and 64-bit versions of the same and for single-core, and for dual-core processors.

Given the lack of difference in the performance of 32-bit applications, it is unlikely to make sense to go to Windows XP Professional X64 Edition, if you, for the most part, you work with them. Of course, if you do not want to feel like a pioneer. In principle, the level of Microsoft Wow64 (Windows On Windows 64) works well and allows 32-bit applications under Windows X64 without a noticeable drop in performance. Actually, the situation reminds us of the transition from Windows For Workgroups 3.11 to Windows 95: If enough memory is installed in the computer, the performance problem is not.

In the coming months, we plan to carefully test the performance of 64-bit applications, as they appear on the market ..