How Does an Installation Affect My Computer?

This section describes the principal impacts of the installation on your computer on Windows.

Installation Folder

This section specifies the install folder location on Windows.

The software is installed (if you used the default location) in the folder:

C:\Program Files\Dassault Systemes\B211\intel_a 
C:\Program Files\Dassault Systemes\B211\win_b64

Desktop

This section specifies the impact on the Windows desktop.

The installation:


  • creates the default environment shortcut on the desktop.

Only one environment is created: a global environment (not a user environment). For more information about global and user environments, refer to What are Global and User Environments?

The environment is created in a text file located in:

C:\Documents and Settings\All Users\Application Data\DassaultSystemes\CATEnv

and the environment file name is MyProduct.V6R2012.B211.txt. For example: CATIA.V6R2012.B211

Note that all environments created at installation are server-type environments. Server-type environments enable users to log onto the server from different computers and retrieve their personal preferences.


  • sets up the Start > All Programs > MyProduct > Tools menu containing the Environment Editor, Local Key Management, Software Management commands.

Registry

This section specifices the impact on the Windows registry.

Whenever you perform an installation (or run a command using the

/regserver

command option), the following registry keys are modified:


  • HKEY_LOCAL_MACHINE

  • HKEY_CLASSES_ROOT

HKEY_LOCAL_MACHINE


  • HKEY_LOCAL_MACHINE\SOFTWARE\DassaultSystemes

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Dassault 
    Systemes B2110 

HKEY_CLASSES_ROOT

This key registers the document types and extensions:


  • HKEY_CLASSES_ROOT\PLM.MsgDoc

  • HKEY_CLASSES_ROOT\.PLMMsgDoc

Registry entries, folders and files are not protected. You can protect access to these entries using system tools, for example the regedit command. Please note that this command is only recommended for advanced users because it is potentially dangerous.

Administrator Setting Environments

This section specifices the impact on the administrator setting environments on Windows.

When running a session at the end of the installation procedure (as administrator), permanent administrator settings are created in:

C:\Documents and Settings\user\Application Data\DassaultSystemes\CATSettings\R208\Authoring

Temporary administrator settings (CATTemp, CATReport, etc.) are stored in:

C:\Documents and Settings\user\Local Settings\Application Data\DassaultSystemes\CATTemp,CATReport

Communications Backbone Files

This section specifies the communications backbone files.

The installation procedure allows you to declare on your computer:


  • a port reserved for the communications backbone process
  • a port reserved for starting the communications backbone process automatically
  • a port reserved for processing events when using peripheral devices (spaceball, spacemouse, joystick).

To do so, check the option "Set up communications ports (strongly recommended)" when prompted.

The communications backbone is an implementation of message-oriented middleware (MOM), used to support process interoperability for distributed application networks in heterogeneous environments. Installing the code sets up the communications backbone on your computer. The backbone needs to be set up on each computer running applications which need to communicate.

When one application attempts to communicate with another, the backbone process is started automatically. If the process is already running, it is not restarted. A timeout is triggered once there are no more clients attempting to communicate with other applications.

When installing from scratch, the installation procedure sets up the communications backbone by creating the following lines:

catiav5bb 55555/tcp

catiav5run 55556/tcp

in the file:

%windir%\system32\drivers\etc\services

Note that the line:

CATDeviceBroker 55557/tcp

which concerns peripheral device handling is also added to this file.

If you do not want to set up communication ports during the installation, you can always edit the above-mentioned files manually later.

The following line is also added:

IVDeviceBroker 55557/tcp