#acad.lsp
8 messages in this thread
Dick, first unprotecting AEC's lisp routine voids the warranty.
Second the invalid character can come from a HIGH level ASCII character in
the file, one that a word processor would leave.
Check to make sure your Word Proc isn't leaving stuff behind.
You can't currently add to ACAD.LSP that comes with AEC. There have been a
few attempts to alter it but none have been proven reliable.
Some have tried to Create a NEW ACAD.LSP, add their routines, then on the
last line add (load "AEC") renaming the AEC ACAD.LSP to AEC.LSP.
For some reason this will not work for all users, and it is a non-supported
method.
I suggest you create a menu pick that loads the routine for you. Add it
either the screen menu or tablet menu. This is THE BEST WAY. You don't have
the routine loaded till needed and it is done automatically!
Jamie
Thanks for your help. I really didn't think about the fact that I could void
the warrantee by opening up the ACAD.LSP file. I used a couple of spaces
[B01] and [B02] on the AEC template, and they work fine.
Well, what I should explain is, by "warrantee" I meant support warrantee. As
in, we will offer support to you through normal channels as long as you don't
alter the package's integrity.
Like patching a driver, .OVL using non supported methods within LISP or in
this case breaking the protection scheme on the ACAD.LSP for AEC.
Perhaps I worded it too strongly, anti-protection utilities are a sensitive
issue with me.
What I want to point out, is this is a support issue and I just wanted you to
know that the method you were experimenting with was "pushing the envelope of
our support range" as we don't use nor endorse such methods.
Your final technique is the best way to go.
It would be nice to add code to ACAD.LSP and I think that is on the wish list
for the future AEC releases.
Jamie
"Changing the ACAD.LSP file voids the warranty".
..
Good grief. Surely you jest.
..
Reviewing my "Software License Agreement", I am reminded that I have not
actually purchased a product, but have paid a one-time fee for the limited
right to use your software for up to 20 years. When I signed my
registration card, I agreed to a lot of things, including not changing the
software. Autodesk agreed to nothing, except to replace the disks if they
are defective (not buggy (as AEC used to be, in spades)).
..
Hmmm. This is curious…this is the same form that I signed when I bought
my AutoCAD. How odd. I thought I remember something about the manual
mentioning customizing AutoCAD's menus. I must be thinking of some other
software package – one that emphasizes an open architecture.
..
Or maybe AEC is so fragile in its design that the slightest bit of
customizing brings the whole tower of cards down.
..
To quote from the AEC manual: "Autodesk, Inc. and Archsoft, Inc. make no
warranty, either expressed or implied, including but not limited to any
implied warranties of merchantability or fitness for a particular purpose,
regarding these materials and makes such materials available solely on an
"as-is" basis."
..
I like AEC. I think it is a great second shot at an architectural add-on
to AutoCAD. But I still contend it should be re-written from the ground up
with the understanding that architects need as much flexibility in their
drawing systems as other disciplines vary from each other. Most of us
don't like the complex layering system. All of us need easier and more
reliable wall drawing routines. AEC fails to address most of the sheets in
a typical set of drawings with its focus on plans. And on, and on. Bitch,
bitch, bitch. Let me put it another way – Autodesk's real job is not to
write third party software, it is to provide a sufficiently powerful set of
tools for others to produce manageablely compact modules that plug into it.
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
Lansing:
Go get 'em, buddy. Architects that use ACAD without AEC must be masochists.
I, too, didn't read the fine print about OPEN architecture when I bought AEC
along with ACAD. I guess if I had, I wouldn't be so disturbed by the things
that I don't like that I couldn't have fixed if I wasn't a criminal.
Craig "Lefty" Sharp.
Yea !!!!! , Lansing I see I'm not the only one who hauled out his soap box.
Corky Deeds LightSpeed Corp.
Jeez, Lansing. What are trying to do? Be a bigger pest than me?