User Guide

Files Migrated with the Migrate Custom Settings Dialog Box
DetailsFile DescriptionFile Name
User Defined Hatch Patterns section
of the file.
The file itself is not migrated; how-
ever, any command aliases you cre-
Stores shell commands and com-
mand alias definitions (a program
acad.pgp
ated in this file are copied to the
AutoCAD acad.pgpfile.
parameters file in ASCII text
form).
The file itself is not migrated; how-
ever, a copy of the file is created and
Contains menu customization
from an AutoCAD version earlier
than AutoCAD 2006.
*.mnu
then is converted into a CUI file with
the same name. The new CUI file is
placed in the same folder as the main
CUI file. A MNU file is converted
when a MNS file with the same name
is not found.
The file itself is not migrated; how-
ever, a copy of the file is created and
Contains menu customization
from a version of an AutoCAD
earlier than AutoCAD 2006.
*.mns
then is converted into a CUI file with
the same name. The new CUI file is
placed in the same folder as the main
CUI file. A MNS file is converted
when a MNU file with the same
name is present or not.
If the CUI file is supplied by Autodesk,
the custom changes made to the file
Contains customizations from a
version of an AutoCAD starting
with AutoCAD 2006.
*.cui
are migrated to the newer version of
the CUI file.
If the CUI file is not supplied by
Autodesk, the file is migrated and is
copied to where the main CUI file is
located, unless the CUI file is in a
network location. In that case, the
file is migrated but is not copied to
the location of the main CUI file.
Enterprise CUI files are not migrated
automatically. You must migrate
them manually.
28 | Chapter 2 Migrating and Customizing