Technical Details

Encrypted Lisp Compatibility

Encrypted Lisp files, as well as encrypted "container" files are both upward and downward compatible.
In opposite to AutoCAD's VLX "container" files, DEScoder also encrypts embedded DCL and Text resources.

The following table shows the relations between DEScoder versions and Bricscad versions :

Bricscad V8, V9, V10

Bricscad V11 (and higher)

DEScoder before V2.0

- encrypted Lisp files

Yes

DEScoder V2.0 and higher

- encrypted Lisp files (no DCL, no Text)
- encrypted Lisp "container" (incl. DCL, Text)

Yes

Yes (ignores embedded resources)

Yes

All DCL and Text resources are included into the encrypted "container" file as a special kind of Lisp comment - in result, all Lisp engines of Bricscad V8, V9 and V10 can load such encrypted "container" files, but will simply ignore embedded DCL and Text resources.

New Bricscad V11 version does recognize and use embedded DCL and Text resources.

Encrypted "container" files without included DCL and Text files are not different to normal encrypted files at all - so any Bricscad Lisp engine will completely load and use the files.

Windows Registry

DEScoder stores dialog related settings and MRU file list under :

HKEY_CURRENT_USER\Software\TM-CAD Engineering\DEScoder

If necessary, this main Registry entry can be removed without any risk.