This file contains the application startup settings and is separated into two main sections [ACAD] and [LOAD]. The ACAD section contains all startup options and the LOAD section defines the modules (arx/dll) and menu files (which/cuix) to load into the CAD.

Let's look in detail at the various options in the ACAD section:

Path

Indicates the path to the main CAD executable. Supported CADs are AutoCAD, AutoCAD LT, and BricsCAD.

Ver

Indicates the platform version of the application (AutoCAD/BricsCAD and 32/64 bit).

TopVer

Indicates the version of QS Informatica application.

InstallApplications

Specifies the commercial products that have to be licensed in the installation.

templatepath

Indicates the location of the template file to upload. The template file is a .dwt.

defaultCui 

Allows to set a menu file to be restored in any case when the CAD closes.

RunBefore

Specifies a customizable batch file. If set, the application will run the batch file before starting the CAD. This tool can be useful if you need to have special startup conditions.

RunAfter

Like the RunBefore option, it runs a batch file after the CAD session is complete. It is typically use with RunBefore to restore standard startup conditions.

DisableAero

This option disables the Windows Aero option. This option has historically presented various issues to the proper functioning of CAD. You can ensure that it is disabled before each start of the work session.

Let's look in detail at the various options in the LOAD section:

arx

Indicates an arx module to load. Arx modules are regular native dlls that contain CAD command definitions.

dll

Indicates a dll module to load. Dll modules contain command definitions made with the .NET platform.

menu

Indicates the path to a menu file (cuix in the case of AutoCAD,cui in the case of BricsCAD).

Solo per BricsCAD:

Profile and other sections, like BricsCAD profiles, where you can force a specific model file to be loaded for each BricsCAD profile.