CompuServe Messages

acad.lsp

    29-Mar-88 13:38:50
Sb: #21267-acad.lsp
Fm: Jamie Clay [Adesk] 76703,4204
To: Lansing Pugh 74375,457
Well, I wasn't "jesting". But I think there is a fairly clear issue you yourself brought up. In the Software Licence Agreement it does state you promise not to change the software. It also says you promise not to modify any copyright or trademark notice in the software. I would say that removing a software's protection code violates both of these promises. Now all I meant to establish was the extent of support he could expect when these elements have been breached. As support techs we can not offer much experience nor endorsement of this type of "experimentation" with the software. No one is going to ask him to fork over his software or deny him legitimate support. As for the stability of AEC, I don't think it is so fragile one can not alter some of it's functionality, but unfortunately AEC is not designed for too much customization. It is not as open as AutoCAD. The package has some specific parameters that need to remain intact, like block names and layers, so one can not apply the theory that because AutoCAD can be completely customized, et tu AEC. I will pass your last comments along to Product Management as I am sure the would like to see them. Jamie