About Exporting and Importing Custom Settings From the Same Release
Custom settings can be transferred between computers with the same release of the
product installed, or to create a backup of your custom settings.
Export Custom Settings
When exporting custom settings, a transfer package is created that contains an XML
file. This file contains custom settings, a listing of the custom files from local
locations used by the program, and optionally, custom files in network locations.
The transfer package is a compressed archive with a ZIP file extension. During the
import process, you select the ZIP file archive that contains the exported custom
settings.
The following table lists the file types that are most commonly included in the transfer
package.
Most Common File Types Included in the Transfer Package |
|
---|---|
File Name |
File Description |
FavoriteMaterials.adsklib |
Contains materials that are added to the My Materials library with the Materials Browser. NOTE:Not available in AutoCAD LT.
|
*.atc |
Tools defined in a tool palette and the tool palette catalog. |
*.aws |
Order of the tools as they appear in a tool palette and other local settings. The |
*.bmp,*.dib,*.png,*.rle |
Images used for custom commands defined in a customization file. |
*.ctb |
Settings used to control the appearance of objects when plotting; the settings are |
*.cuix |
Information used to define many of the user interface elements for the program and |
*.cus |
Custom dictionary used to check the spelling of words in annotation objects. |
*.fmp |
Information about font mappings for True Type Fonts used in the In-Place Text Editor. |
*.ini |
Configuration settings for some features. |
*.lin |
Standard and custom linetype definitions. |
*.mln |
Standard and custom multiline style definitions. NOTE:Not available in AutoCAD LT.
|
*.mnl |
AutoLISP commands and procedures that a customization file is dependent on; must have NOTE:Not available in AutoCAD LT.
|
*.pat |
Standard and custom hatch pattern definitions. |
*.pc3 |
Configuration information for a plotter or printer. |
*.pgp |
External commands and command alias definitions. NOTE:External commands are not available in AutoCAD LT.
|
*.pmp |
Calibration and paper size settings that are used with a PC3 file. |
*.psf |
Information about font substitution when exporting to a Postscript file. NOTE:Not available in AutoCAD LT.
|
*.shx |
Information about text characters or shapes in complex linetype definitions. |
*.stb |
Settings used to control the appearance of objects when plotting; the settings are |
*.xml |
Information about the user profiles in the product and the original locations of the |
The following table lists the file types that are not included in the transfer package.
Some of the File Types Not Included in the Transfer Package |
|
---|---|
File Name |
File Description |
*.actm |
Action macro file. |
*.arx |
ObjectARX application file. |
*.dcl |
Definitions for custom dialog boxes used with AutoLISP or ObjectARX applications. |
*.dvb |
Visual Basic for Applications project file. |
*.fas |
Fast-load AutoLISP format file. |
*.fdc |
Definitions for fields; should not be modified. |
*.lsp |
AutoLISP source file that contains definitions for custom commands and functions. |
*.mnr |
Resource images for a customization file; must have the same name as a customization |
*.udl |
Data connection settings used with dbConnect. |
*.unt |
Unit definitions used for converting a value from one unit type to another. |
*.vlx |
Visual LISP file that might contain multiple AutoLISP and DCL files compiled into |
Import Custom Settings
After successfully importing the transfer package, a message box is displayed that
gives you the option of viewing the migration log file. If any errors are encountered
during the import process, they are recorded in this file.
If files from a network location were added during the creation of a transfer package,
the files are copied to a different location only when the original network locations
are not available when importing a transfer package. If the files from a network location
are found in the same location on the network, the files are not copied to the network
location and are ignored during the import operation.
If the user profile <<Unnamed Profile exists, the user profile is automatically
backed up before the transfer package is imported.
Local paths that exist as part of a user profile in a transfer package are created
automatically during the import process, but paths that are on a network drive or
a drive that uses removable discs, are not created automatically.
>Custom settings can be transferred between computers with the same release of the product installed, or to create a backup of custom settings for the installed …custom settings between computers with the same release of the product installed, or you can create a backup of your custom settings. Export …import the custom settings and files after exporting them to a transfer package with Export Settings. Do one of the following: Windows 7: …Custom Settings From Previous Releases Use the … Use the following tools to transfer custom settings and files between computers with the same release of … Exports and imports user profiles between different computers.custom settings between computers with the same release of the product installed, or you can create a backup of your custom settings. Do one …Custom Settings From Previous Releases The following tools … About Exporting and Importing Custom Settings From the Same Release …settings from an older version you specify to the … AutoCAD 20xx > Migrate Custom Settings > Migrate From a Previous Release … To be successful, the language version of AutoCAD must be the same . … under the Migrate Custom Utilities menu to export settings from the old computer.