4.3.5. Determining application bitness and using applications of different bitness


<< Prev   Next >>

You can select client application bitness only if the computer runs 64-bit Windows. If your computer runs Linux, use the application whose bitness matches the operating system bitness. If the computer runs macOS, only 64-bit version of the applications is available.

Several versions of the client application with different bitness can be installed on the client computer. In some situations, you might need to specify not only the version of the client application but also its bitness for a specific infobase. You can specify client bitness for each infobase if necessary.

To specify bitness of a client application, you can use (in descending priority order):

  1. /AppArch startup command line parameter
  2. Infobase property
  3. Interactive launcher property

Use any of these methods to select one of 4 client bitness options:

  1. 32 (x86). Always starts the 32-bit version of a client application. The 64-bit versions will be ignored regardless of their release date.
  2. 64 (x86-64). Always starts the 64-bit version of a client application. The 32-bit versions will be ignored regardless of their release date.
  3. 32 (x86) priority. Gives priority to the 32-bit version of a client application. However, if a 64-bit version has a later release date, it will be used instead.
  4. 64 (x64) priority. Gives priority to the 64-bit version of a client application. However, if a 32-bit version has a later release date, it will be used instead.

If bitness of a client application is not explicitly specified, the 32 (x86) priority option is used by default.

Consider that the system performance does not depend on the bitness (operating system and processor) of client applications or a server cluster (for client/server mode). It means that the infobase can be simultaneously operated by client applications with different bitness, on different processors, and in different operating systems. In client/server mode, cluster server bitness can differ from client application bitness, operating system, and processor. Application bitness and the operating system it is intended for are important when:

  • COM connection is used (only for Windows).
  • Add-ins are used. Add-in must include the add-in file whose characteristics match the application where you plan to use the add-in. The add-in contains a manifest that specifies appropriate startup options stipulated by the add-in developer.

See also:

  • Startup window settings
  • Command line parameters
  • 1cestart.cfg
  • 1cescmn.cfg
  • *.v8i

<< Prev   Next >>

Icon/Social/001 Icon/Social/006 Icon/Social/005 Icon/Social/004 Icon/Social/002