The Migrate Custom Settings dialog box includes the following options:
User profiles contain the settings for the drawing environment. These settings include the drawing window color, cursor size, command line window font, and the dictionary to use for checking spelling.
User profiles also include the folders in which the application searches for support, driver, customization, and other files. If you customized files in a location other than the default location, the path to the location is migrated. The files themselves in those locations do not get migrated.
The data from these files defines how the user interface elements in AutoCAD 2006-based products and later were arranged. These elements include: toolbars, pull-down menus, ribbon panels and tabs, palettes, and many others. Based on the release from which you are migrating, the Migrate Custom Settings dialog box looks for CUI or CUIx files.
The data from these files defines the user interface elements in AutoCAD 2005-based products and earlier. These elements include: toolbars, pull-down and image tile menus, and many others. The Migrate Custom Settings dialog box looks for MNS files first, and then MNU files.
These files are referenced by commands defined in a CUI or CUIx file, and stored in the folder defined under the Custom Icon Location node on the Files tab of the Options dialog box.
These files contain a set of user-defined and standard tools that shipped with the product, and are stored in the folder defined under the Tool Palettes File Locations node on the Files tab of the Options dialog box.
If custom tools were added to a tool palette that shipped with a AutoCAD 2009-based product or earlier, the tools are not migrated and need to be added back to the tool palettes that shipped with the current release.
When migrating tool palettes, custom tool palette groups are merged with the default tool palette groups.
Tool palette groups are stored in user profiles. You can see the default tool palette groups that ship with the product by switching to the <<Product Name Unnamed Profile>>. (User Profiles are not available in AutoCAD LT.)
The user-defined linetypes from these LIN files are added to a user-defined section of the file with the same name in the current release.
These LIN files are copied from the earlier release to the current release.
The user-defined hatch patterns from these PAT files are added to a user-defined section of the file with the same name in the current release.
These PAT files are copied from the earlier release to the current release.
This file represents the Favorites library in the Material Browser. Image files referenced by materials in a library are not moved or copied.
The user-defined command aliases from this file are added to the user-defined section of the file with the same name in the current release.
You cannot use the Migrate Custom Settings dialog box to migrate shell commands or comments that you made to your acad.pgp (or acadlt.pgp in AutoCAD LT) file.
The following table lists the files and file types that are migrated with the Migrate Custom Settings dialog box. A description of each file and file details are also listed to help you decide if you want to migrate a file.
Files Migrated with the Migrate Custom Settings Dialog Box |
||
---|---|---|
File Name |
File Description |
Details |
FavoriteMaterials.adsklib |
Contains materials that were added to the Favorites library. |
File is created and managed with the Materials Browser and is migrated. Note: Not available in AutoCAD LT.
|
*.atc |
Defines a tool palette and its tools. |
User-defined tool palettes, and new or changed tools on a standard tool palette are migrated if you are migrating from AutoCAD 2010-based products or later. User-defined tool palettes created in releases prior to AutoCAD 2010-based products are migrated, but not changes made to the shipping tool palettes. |
*.arg |
Used to back up user profile information from the Windows registry. ARG files are not migrated, but user profiles are migrated. |
Changes made to your user profiles are stored in the Windows registry and are migrated. Note: Not available in AutoCAD LT.
|
*.lin |
Stores your user-defined linetypes. |
User-defined linetype files are migrated. |
acad.lin (AutoCAD-based products) acadlt.lin (AutoCAD LT) |
Contains standard linetype definitions. |
The file itself is not migrated; however, any custom linetypes added to this file are migrated to the User Defined Linetypes section of the product .lin file. |
acadiso.lin (AutoCAD-based products) acadltiso.lin (AutoCAD LT) |
Contains metric linetype definitions. |
The file itself is not migrated; however, any custom linetypes added to this file are copied to the User Defined Linetypes section of the product .lin file. |
*.pat |
Stores user-defined hatch patterns. |
User-defined hatch pattern files are migrated. |
acad.pat (AutoCAD-based products) acadlt.pat (AutoCAD LT) |
Contains standard hatch pattern definitions. |
The file itself is not migrated; however, any custom hatch patterns added to this file are copied to the User Defined Hatch Patterns section of the product .pat file. |
acadiso.pat (AutoCAD-based products) acadltiso.pat (AutoCAD LT) |
Contains metric hatch pattern definitions. |
The file itself is not migrated; however, any custom hatch patterns added to this file are copied to the User Defined Hatch Patterns section of the product .pat file. |
acad.pgp (AutoCAD-based products) acadlt.pgp (AutoCAD LT) |
Stores external commands and command alias definitions (a program parameters file in ASCII text form). |
The file itself is not migrated; however, any external commands and command aliases you created in this file are copied to the User Defined Command Aliases section of the product .pgp file. |
*.mnu |
Contains menu customization from AutoCAD 2005-based products or earlier. |
The file itself is not migrated; a copy of the file is made and converted into a CUIx file with the same name. The new CUIx file is stored in the same folder as the main CUIx file. The program uses a MNU file when an MNS file with the same name is not found. |
*.mns |
Contains menu customization from AutoCAD 2005-based products or earlier. |
The file itself is not migrated; a copy of the file is made and converted into a CUIx file with the same name. The new CUIx file is stored in the same folder as the main CUIx file. The program looks for a MNS file first, and if it doe snot locate an MNS file it then looks for a MNU file to convert. |
*.cui |
Contains customization from AutoCAD 2006-based products through AutoCAD 2009-based products. |
The file itself is not migrated; a copy of the file is made and converted into a CUIx file with the same name. The new CUIx file is stored in the same folder as the main CUIx file. Enterprise CUI files are not automatically migrated. You must do so manually. |
*.cuix |
Contains customization from AutoCAD 2010-based products and later. |
If the CUIx file is supplied with the product, the custom changes made to the file are migrated to the newer version of the CUIx file. If the CUIx file is not supplied with the product, the file is copied to the location of the main CUIx file and then migrated, unless the CUIx file is in a network location. In that case, the CUIx file is migrated only. Enterprise CUIx files are not automatically migrated. You must do so manually. |
Before MNU, MNS, CUI, and CUIx files are migrated, a backup copy of each file is saved in the following directory:
<drive>:\Users\<user profile>\AppData\Autodesk\<product version>\<release number>\<language>\Previous Version Custom Files