acad.lsp update problems

[Anonymous]

Everyone in my department has their own personal acad.lsp with their
favorite shortcut commands in it. We just upgraded from R14 to 2002.
My acad.lsp loaded fine with no problems. Two other designers in my
department cannot get their shortcut commands to work. AutoCAD says
that acad.lsp is loaded. There is only one file with that name on their
machines. Is there something about the acad.lsp file that needs to be
changed for 2002. Any ideas would be appreciated.

Thanks,

Annette Graham

[nhunter]

The first thing I would do is to copy your acad.lsp file to their computer. DO NOT OVERWRITE THEIR ACAD.LSP FILE. Save their acad.lsp file somehere else so they do not loose it. After you copy yours in I would try to run AutoCAd and see if you get the same errors. If you do you know it is something else on there computer.

I don't think there is anything in acad.lsp that would cause an error this is why I am having you check yours on their computer.

I hope this helps

[Anonymous]

"Annette Graham" wrote:

> Is there something about the acad.lsp file that needs to be
> changed for 2002. Any ideas would be appreciated.

In 2000 and newer the acad.lsp file only loads upon startup (by default),
thus the "shortcut" keys will only be available in the first drawing. You
have a few options here.
1) Set the ACADLSPASDOC variable to 1
2) Create an acaddoc.lsp file for the stuff that you want loaded into each
drawing.

I would suggest using option 2 as that is what AutoCAD does by default.

hth
Kevin

[Anonymous]

Look if there is not a ".fas" same name. Autocad charges the most recent
version between the "lsp" and the "fas". If necessary, erase the "fas" and
recompile "lsp" to create a new "fas" (what is not obligatory)

Or you could use the "mnl".

BTO
(sorry for my english level)

Annette Graham a écrit dans le message :
3BBDF8D5.F22785A7@arc-ag.com...
> Everyone in my department has their own personal acad.lsp with their
> favorite shortcut commands in it. We just upgraded from R14 to 2002.
> My acad.lsp loaded fine with no problems. Two other designers in my
> department cannot get their shortcut commands to work. AutoCAD says
> that acad.lsp is loaded. There is only one file with that name on their
> machines. Is there something about the acad.lsp file that needs to be
> changed for 2002. Any ideas would be appreciated.
>
> Thanks,
>
> Annette Graham
>

[patrick]

Rename your Acad.lsp to Acaddoc.lsp. You can more than one Acaddoc.lsp. These will load in the order you have set your support path.
This is from the AutoCAD help file.
The acaddoc.lsp file is intended to be associated with each document (or drawing) initialization. This file is useful if you want to load a library of AutoLISP routines to be available every time you start a new drawing (or open an existing drawing). Each time a drawing opens, AutoCAD searches the library path for an acaddoc.lsp file. If it finds one, it loads the file into memory. The acaddoc.lsp file is always loaded with each drawing regardless of the settings of ACADLSPASDOC and LISPINIT.
Most users will have a single acaddoc.lsp file for all document-based AutoLISP routines. AutoCAD searches for an acaddoc.lsp file in the order defined by the library path; therefore, with this feature, you can have a different acaddoc.lsp file in each drawing directory, which would load specific AutoLISP routines for certain types of drawings or jobs.
The acaddoc.lsp file can contain AutoLISP code for one or more routines, or just a series ofload function calls. The latter method is preferable, because modification is easier. If you save the following code as an acaddoc.lsp file, the files mydocumentapp1.lsp, build.lsp, and counter.lsp are loaded every time a new document is opened.
(load "mydocumentapp1")
(load "build")
(load "counter")
AutoCAD searches for an acaddoc.lsp file in the order defined by the library path; therefore, you can have a different acaddoc.lsp file in each drawing directory. You can then load specific AutoLISP routines for certain types of drawings or jobs.
Patrick
<>