AutoLISP Compatibility Analyzer details AutoCAD® 2004 compatibility issues found in AutoLISP and Menu LISP files. AutoLISP Compatibility Analyzer searches for known AutoCAD 2004 compatibility issues. When an issue is found, an explanation of the compatibility issue and suggestions on how to correct it are provided.Menu and Toolbar Porter
Menu and Toolbar Porter was designed to help you bring your menus and toolbar items from previous versions of AutoCAD into AutoCAD 2004. You can also use this tool to add or remove menu and toolbar items from any AutoCAD MNU file.Command Alias (PGP) Porter
Command Alias (PGP) Porter was designed to help you bring your custom command aliases from previous versions of AutoCAD into AutoCAD 2004. You can also use this tool to add, replace, or remove command aliases from any AutoCAD PGP file.ScriptPro
ScriptPro takes AutoCAD scripting to a new level with an easy-to-use interface, logging, reusable project files, enhanced scripting with new keywords and utilities, and robust error recovery. Using ScriptPro you can apply a set of commands to multiple drawings by simply specifying a script file and the list of drawings that you would like to apply the script to.Layer State Converter
Layer State Converter allows you to convert between the layer states created by LMAN (one of the AutoCAD® Express Tools) and the saved layer states introduced in AutoCAD® 2000i software.
To use Layer State Converter, type one of the following commands on the AutoCAD command line:
Note: This product is not intended to operate with any version of AutoCAD LT®.
To install the Autodesk Customization Conversion tools:
AutoLISP Compatibility Analyzer
AutoLISP Compatibility Analyzer examines complete lines of text; therefore, it may not recognize function calls that are spread over multiple lines, as in the following example:(defun c:testit ()
Menu and Toolbar Porter
When using the Menu and Toolbar Porter, toolbars described after the **TB_STANDARD group in the MNU or MNS file may not be displayed. To work around this problem, move the **TB_STANDARD group to the end of the ***TOOLBARS section using a text editor (such as Notepad).
Custom toolbars in AutoCAD 2004 are not listed in the Menu and Toolbar Porter.
Toolbar icons appear as question marks when you migrate toolbars from previous releases of AutoCAD to AutoCAD 2004. To correct this, you need to edit the toolbar icons in AutoCAD 2004.
The MNU file you create with Menu and Toolbar Porter is not automatically loaded by AutoCAD. Use the MENU command in AutoCAD to compile and load your new MNU file.
If there is a blank line between pop menu items and the subitems below them in the file, Menu and Toolbar Porter fails to add all subitems. Remove the blank line to correct the error.
Adding a menu item to a partial menu causes a parsing error. To resolve the error, remove the line ***MENUGROUP=ACAD from the bottom of the menu file.
A child menu added to a partial menu appears to be incorrect because it is placed on the same level as the parent menu in Menu and Toolbar Porter. The child menu is added correctly to the MNU file, however.
Adding a toolbar to an MNU file that does not already contain a toolbar may result in parsing errors.
Before you open a file in Menu and Toolbar Porter, check whether it is read-only. If you do some work in a read-only file that you want to save, use the SAVEAS command to save the file with a new name, and then rename it after you exit Menu and Toolbar Porter. If you use the SAVE command, no message is displayed to warn you that your changes are not being saved.
Command Alias (PGP) Porter
No known limitations or issues.
The Migration Tools sample files, located in C:\Program Files\Autodesk\Migration Tools, are intended for the AutoCAD 2004 product only. Do not use these sample script files with Autodesk® Architectural Desktop 2004, Autodesk Map™ 2004, Autodesk® Land Desktop 2004, Autodesk® Mechanical Desktop® 2004, or AutoCAD® Mechanical 2004.
It's a good idea to make backup copies of your files before doing any kind of automated batch processing.
If ScriptPro closes unexpectedly during execution of a project file, you may need to clean up some temporary files that were left behind in your temp directory. These files have the following naming syntax: "ScriptPro[NUMBER]"
You may also need to reset the following AutoCAD settings to your preference the next time you start AutoCAD:
LOGFILEMODE (log file on or off)
LOGFILEPATH (location of AutoCAD log files)
Layer State Converter
No known limitations or issues.