Autodesk 057A1-05A111-10MB Installation Guide - Page 16

Move to AutoCAD LT 2009 from a Previous or Same Release, with AutoCAD LT 2006. - 10

Page 16 highlights

Files Migrated with the Migrate Custom Settings Dialog Box File Name File Description Details acadlt.pgp Stores shell commands and command alias definitions (a program parameters file in ASCII text form). The file itself is not migrated; however, any command aliases you created in this file are copied to the AutoCAD LT 2009 acadlt.pgp file. *.mnu Contains menu customization from a version of AutoCAD LT earlier than AutoCAD LT 2006. The file itself is not migrated; however, a copy of the file is created and 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. *.mns Contains menu customization from a version of AutoCAD LT earlier than AutoCAD LT 2006. The file itself is not migrated; however, a copy of the file is created and 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. *.cui Contains customizations from a If the CUI file is supplied by Autodesk, version of AutoCAD LT starting the custom changes made to the file with AutoCAD LT 2006. are migrated to the newer version of the CUI file. If the CUI file is not supplied by Au- todesk, 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. 10 | Chapter 2 Move to AutoCAD LT 2009 from a Previous or Same Release

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58

Files Migrated with the Migrate Custom Settings Dialog Box
Details
File Description
File Name
The file itself is not migrated; howev-
er, any command aliases you created
Stores shell commands and com-
mand alias definitions (a program
acadlt.pgp
in this file are copied to the AutoCAD
LT 2009
acadlt.pgp
file.
parameters file in ASCII text
form).
The file itself is not migrated; howev-
er, a copy of the file is created and
Contains menu customization
from a version of AutoCAD LT
earlier than AutoCAD LT 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; howev-
er, a copy of the file is created and
Contains menu customization
from a version of AutoCAD LT
earlier than AutoCAD LT 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 AutoCAD LT starting
with AutoCAD LT 2006.
*.
cui
are migrated to the newer version of
the CUI file.
If the CUI file is not supplied by Au-
todesk, 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.
10
| Chapter 2
Move to AutoCAD LT 2009 from a Previous or Same Release