PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Overview
  • How to proceed?
  • Enabling the 64-bit mode
  • Compilation error management mode
  • Compilation errors specific to the 64-bit mode
  • Deploying a site compatible with the 64-bit mode
  • Limits
  • Various limits
  • Registry and system files
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
Recent computers (servers and desktop computers) are now equipped with "64-bit" operating systems.
The main difference between a "32-bit" and a "64-bit" system is as follows: in "64-bit", the applications and the system no longer have memory allocation limitations.
In "32-bit" configurations the operating system is limited to 4 GB, while in "64-bit", there is nearly no limit (the limit is set to 18 billions GB).
Operating mode of 32-bit/64-bit sites: A site compiled in 64-bit can be used with a 32-bit or 64-bit server. A 64-bit server can only display 64-bit sites. If the site was not generated in 64-bit, an error will occur when the site is started.
How to proceed?

Enabling the 64-bit mode

To switch a WEBDEV site from 32-bit to 64-bit:
  1. Open the 32-bit WEBDEV project in the editor.
  2. Display the description of the project configuration corresponding to the site. One of the following methods can be used:
    • select "Description" in the popup menu of the project configuration ("Project explorer" pane).
    • on the "Project" pane, in the "Project configuration" group, click "Current configuration".
  3. In the "Compatibility" tab, check (if necessary) "Enable the compilation errors for the 64-bit compatibility".
  4. Validate.
Remark: From version 16, the sites are created with the 64-bit option enabled by default.

Compilation error management mode

64-bit errors are enabled by default for sites, components, libraries and Webservices.

Compilation errors specific to the 64-bit mode

If the "32-bit" application was using Windows APIs or external DLLs, the switch to "64-bit" mode may generate compilation errors. These compilation errors are specific to the "64-bit" mode.
The most common error consists in using an "integer" variable to store a memory address. On 64-bit machines, pointers take up 8 bytes of memory, whereas on 32-bit machines, they take up 4 bytes. In this case, if a "standard" integer is used, the application may access a truncated memory address, therefore an invalid address.
To avoid this problem, you must use the System Integer type of WLanguage: this type is uses an 8-byte integer in 64-bit and a 4-byte integer in 32-bit!
Tips:
  • Don't forget to check that the APIs used exist in "64-bit" mode. And make sure that the DLL does not have a different name in "64-bit" mode and that its operating mode is identical.
    If differences are noticed, you have the ability to use In64bitMode to call the API corresponding to the current system.
  • In 64-bit, if a value that is too large is assigned to a 1, 2, 4 or 8-byte Integer variable, the value of the variable will not be the same as in 32-bit.

Deploying a site compatible with the 64-bit mode

The method for deploying a site compatible with the 64-bit mode is the same as the method for deploying a 32-bit site: on the "Project" pane, in the "Generation" group, expand "Deploy site". See Deploying a WEBDEV site for more details.
Remark: A site compiled in 64-bit can be used with a 32-bit or 64-bit server. A 64-bit server can only display 64-bit sites. If the site was not compiled with the "64-bit" option, an error will be displayed when the site is started.
Limits

Various limits

  • Hasp is not available in 64-bit.
  • NetXXX functions: Only the client part is available in 64-bit, and is compatible with a 32-bit server. The server part (NetStartServer and NetEndServer) is not available.
  • 64-bit external languages: only C and C++ are available.

Registry and system files

  • Registry: On a 64-bit system, the 32-bit applications write to the registry from the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
  • Access to the system files: On a 64-bit system, the 32-bit applications use different system directories.
    For example, an access to the "\Windows\system32\" directory will be performed in this folder from a 64-bit executable.
    On the contrary, from a 32-bit executable, the access will be performed in the "\Windows\SysWOW64" folder.
Minimum version required
  • Version 11
Comments
Click [Add] to post a comment