New updates for the AUTO-CODE software are distributed over the Internet. You can download the updates at any time. There are two kinds of updates for users.

• Updating the software to remove "unwanted features". Sometimes problems are found after the software has been released or are caused by subtle AutoCAD changes. In these cases, the corrected software is placed on the web for immediate access. Follow the directions below for preserving your authorization code(s) when implementing one of these updates.

• New versions of AutoCAD and/or Mechanical Desktop often require new versions of AUTO-CODE to be built.  AUTO-CODE uses the Object ARX system for maximum integration and through put thus you must have the correct version to run with your AutoCAD. In rare cases, significant changes may be needed inside AUTO-CODE to conform with the newer standards and features of AutoCAD. If too many versions are skipped, a new authorization code will be needed as well as the updated software. Your custom post may require changes as well.  There will be variable charges when you upgrade your AutoCAD and AUTO-CODE.

Preserving your Authorization Code(s) and Custom Interface(s)

When updating the AUTO-CODE software within the same version of AutoCAD, you must preserve your authorization code file and any custom interfaces created.  The following procedure will clear out your old AUTO-CODE copy (make a backup first) and allow you to work with the newer version right away.

• Copy the file LIC found in the AUTO-CODE program directory to a diskette or another directory. There should only be one LIC file found in the AUTO-CODE program directory.
• Copy the post processor files found in the \POSTS\ directory inside the AUTO-CODE program directory. The post processor files will all have the same file name (such as MILL.*) with multiple extensions (.PAT, .CFG, .CTL, optional .LSP and others).
• Remove the AUTO-CODE program directory using the File Manager/Windows Explorer program. The entire directory, programs and all should be removed.
• Install AUTO-CODE following the directions in the SETUP.HLP file (load SETUP.LSP for installation).
• After installation is completed, copy the file LIC into the new or updated AUTO-CODE program directory.
• Then copy the custom interface files to the \POSTS\ directory.

Updating Custom Interfaces

The amount of updating required to a custom interface will be based what version you are updating from.  In some cases, no changes are required while in others significant changes will be needed.  These changes can be done by AUTO-CODE the company for a nominal charge.  Contact our sales department to find out what that cost would be for your interface.

If you are updating AUTO-CODE from a 3.x to another 3.x version or from a 4.x to another 4.x version, your interface should run as it presently exists. It is recommended that you load the custom interface into the editor (using Edit CFG from the AUTO-CODE main dialog box) and check out all of the settings before use. Interfaces created for version 4.x can be updated to the 5.0 and 2005 versions with minimal changes.

Custom interfaces can be updated from Version 3.x to Version 4.x by changing all symbol references in associated AutoLISP (LSP) files. For example, if you modified the TURN.LSP file in Version 3.x to suite your needs, the updated file will not run properly in Version 4.x due to symbol name changes. In essence, all names that start with GEA must be changed to NCG. This is to comply with Autodesk requirements for shared applications running inside AutoCAD. It insures that AUTO-CODE will work properly with other enhancements to the base AutoCAD system that also comply to these standards. Other changes to the LSP source code will be the addition of some new variables. Exactly what variables need to be added will vary depending on the application and interfaces used in creating it.

There have been significant improvements in the interfaces and tools available in AUTO-CODE from these earlier versions. In most cases, it is best to use the Custom Interface Wizard in Version 4.x to create a new custom interface. Some changes for special AutoLISP routines or patterns may still be required.  Existing tool libraries will convert directly to the latest version with the possibility that additional data can be added if needed.