Migrating LISP files

LISP (List Processing) is an interpreted programming language used to automate tasks, create custom commands, and extend BricsCAD functionality. LISP routines can interact with BricsCAD commands, system variables, dialog boxes, and drawing entities.

BricsCAD is compatible with AutoCAD® AutoLISP, so it can load and run LSP files. However, the VLX and FAS file formats are AutoCAD® specific encrypted LISP files, and BricsCAD cannot load such files.

To migrate LISP routines, locate the desired LSP files, then copy and save them in the corresponding BricsCAD file. LISP files are usually stored in the Support folder (from the installation folder) but can also be stored in a folder added to the support search path using the SRCHPATH system variable.

Note: Make sure that all dependent resources, such as DCL files, scripts, custom icons and configuration files, are also transferred and that any referenced file paths are updated accordingly.

Migrating LISP files from AutoCAD®

Two LISP files are automatically loaded in AutoCAD® from acad.lsp and acaddoc.lsp. The equivalents of these two files on BricsCAD are on_start.lsp and on_doc_load.lsp.

Important: It is not recommended to edit on_start_default.lsp and on_doc_load_default.lsp. Instead, you should create two new files named on_start.lsp and on_doc_load.lsp.
Migrating ACAD.LSP into ON_START.LSP
Go to AutoCAD® Support folder and open in a text editor the acad.lsp file. Select the custom content and copy it.

Then, go to BricsCAD Support folder and create a new text editor file named on_start.lsp. Paste the custom content and save it.

Migrating ACADDOC.LSP into ON_DOC_LOAD.LSP
Go to AutoCAD® Support folder and open in a text editor the acaddoc.lsp file. Select the custom content and copy it.

Then, go to BricsCAD Support folder and create a new text editor file named on_doc_load.lsp. Paste the custom content and save it.

Migrating encrypted VLX files, FAS files, VLX projects (PRV) and FAS projects (PRJ)
Compiled and encrypted VLX and FAS files cannot be loaded in BricsCAD. Migration of VLX and FAS based applications requires access to the original LISP source files and the PRV or PRJ project files.

BricsCAD supports the creation of encrypted applications through DEScoder.exe. Using DEScoder.exe, multiple LISP, DCL, and other application resource files can be packaged and encrypted into a single DES application file. PRV and PRJ project files are used to define the application contents and generate the encrypted DES file.

Migrating LISP files from a previous BricsCAD version or a different computer

Go to the Support folder in the previous version of BricsCAD or in BricsCAD on a different computer. Open with a text editor the default.lin file for imperial custom linetypes or the iso.lin file for metric custom linetypes and copy the linetype definition.

Note: If the files are stored in a custom folder or location, copy and save the files accordingly. Make sure that the destination folder is included in the support search path (SRCHPATH).
Migrating ON_START.LSP or ON_DOC_LOAD.LSP
Go to the Support folder in the previous version of BricsCAD or in BricsCAD on a different computer and open in a text editor the on_start.lsp or on_doc_load.lsp file. Select the custom content and copy it.

Then, in the current version of BricsCAD go to the Support folder and create a new text editor file named on_start.lsp or on_doc_load.lsp. Paste the custom content and save it.

Migrating encrypted DES files
DES files are encrypted BricsCAD application files created with DEScoder.exe. They are typically stored in the Support folder (from the installation folder) or in a folder added to the support search path using the SRCHPATH system variable.

To migrate DES files, locate each file, copy and save it to the corresponding file in the current version of BricsCAD.

Note: When migrating DES files from a previous BricsCAD version, it is recommended to verify application functionality. If the application does not work as expected, recreate the DES file by re-encrypting the original source files with DEScoder.exe.

Migration Tips

  • After migration, the on_start.lsp is loaded per session by default, but it can also be loaded for each drawing if the ACADLSPASDOC system variable is set to 1. The on_doc_load.lsp file is always loaded for each drawing.
  • Another way to load your LISP routines is with the APPLOAD command. After you run the command, the Load Application Files dialog box is displayed to select the application files you want to run inside BricsCAD. The AutoLoad option specifies whether a file is loaded automatically or not in the next BricsCAD session (see the Load Application Files dialog box article for more information).

Encrypting files with DEScoder.exe

The path of the DES Encoder is: C:\Program Files\Bricsys\BricsCAD V26 en_US.

  1. Open the encoder.
  2. Select the LISP file in the Source field.
  3. Click the Convert selected source Lisp file into DES encrypted file button next to the Target field.
  4. After the DES file is converted, copy it to BricsCAD Support folder (from the installation folder): %AppData%\Bricsys\BricsCAD\V26x64\en_US, or to a folder you have added to the support path using the SRCHPATH system variable.