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


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

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.


VLX NameSpace Compatibility


Since DEScoder.exe v2.7 :

The "VLX NameSpace" feature to isolate Lisp code running in an own "NameSpace" (prevents clashes of same-named functions, between different Lisp files).is available since DEScoder v2.7, and supported since BricsCAD V18.
But the internal DES data format and options strage has been made backward + forward compatible, to provide best level of compatibility possible.


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


Lisp files encrypted by

works in BricsCAD V11 - V17

works in BricsCAD >= V18

DEScoder <= V2.6

no NameSpace support


Yes


Yes

DEScoder >= V2.7

NameSpace feature disabled
NameSpace feature enabled


Yes

Partially (no NameSpaces available !)


Yes

Yes



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.