Author Topic: Lisp files in startup suite not loading  (Read 5617 times)

0 Members and 1 Guest are viewing this topic.

TJK44

  • Guest
Lisp files in startup suite not loading
« on: June 06, 2012, 01:18:28 PM »
I have noticed that if a user accidentally starts AutoCAD Mechanical and then starts AutoCAD, the files they have in their startup suite do not load automatically. To get them to load again you need to manually load the file by double clicking on it and then it will work again when AutoCAD is started. Has anyone else experienced this and found the reason this happens?

Thanks,

Ted

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #1 on: June 06, 2012, 02:28:22 PM »

I've long noticed problems with settings in one application, when another is also started (i.e., the Shortcuts added to the Open dialog, etc.), but do not experience this behavior... Due to my not using Startup Suite.

Instead, I use Acad.lsp + AcadDoc.lsp + [SomeCuixName].mnl to load all of my LISP routines, without any issues.

HTH

Moderator: This must have accidentally been started in the .NET forum, can this be moved?
"How we think determines what we do, and what we do determines what we get."

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #2 on: June 06, 2012, 03:45:40 PM »
"How we think determines what we do, and what we do determines what we get."

TJK44

  • Guest
Re: Lisp files in startup suite not loading
« Reply #3 on: June 06, 2012, 06:30:18 PM »
Apologies Kerry. So used to posting questions to .NET I didn't even think to look elsewhere to post this.

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #4 on: June 06, 2012, 07:11:46 PM »
No worries; did AcadDoc.lsp help your situation, Ted?
"How we think determines what we do, and what we do determines what we get."

TJK44

  • Guest
Re: Lisp files in startup suite not loading
« Reply #5 on: June 07, 2012, 08:13:22 AM »
Is Autocad.lsp and AutoCADDoc.lsp loaded when AutoCAD is run? I'm using lisp files in startup suite to automatically load some dlls.

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #6 on: June 07, 2012, 10:41:46 AM »
Is Acad.lsp and AutoCADDoc.lsp loaded when AutoCAD is run? I'm using lisp files in startup suite to automatically load some dlls.

Yes, Acad.lsp is loaded once per session (by default), and AcadDoc.lsp is loaded each time a drawing is opened.

I Netload each assembly using Acad.lsp personally.
"How we think determines what we do, and what we do determines what we get."

cvcolomb

  • Guest
Re: Lisp files in startup suite not loading
« Reply #7 on: June 07, 2012, 07:27:32 PM »
I'm with RM on this one. I've done it both ways (Startup Suite vs acad.lsp & acaddoc.lsp) in multiple offices and the Startup Suite, although easy to figure out and run has issues. The acad**.lsp approach is not hard to learn, and is a lot more flexible & robust.

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #8 on: June 07, 2012, 11:23:50 PM »
Another reason for using Acad.lsp and AcadDoc.lsp is being able to easily manage multiple platforms, and even multiple versions of the same.
"How we think determines what we do, and what we do determines what we get."

TJK44

  • Guest
Re: Lisp files in startup suite not loading
« Reply #9 on: June 08, 2012, 08:11:47 AM »
I'm putting one of my lisp commands to netload a dll, but it's not loading when I start AutoCAD. Could you attach an example of how you setup your Acad.lsp file? My Acad.lsp file is located in the Acadm folder, I need this to netload when regular AutoCAD is started... Thanks for the help.

cvcolomb

  • Guest
Re: Lisp files in startup suite not loading
« Reply #10 on: June 08, 2012, 10:48:32 AM »
Code: [Select]
(setvar "FILEDIA" 0)
(command "NETLOAD" "<Path to .dll>")
(setvar "FILEDIA" 1)

This is a fairly typical approach. Make sure the folder you're using is in your support path, check this on the Files tab of Options.

Right?

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #11 on: June 08, 2012, 11:09:07 AM »
Code - Auto/Visual Lisp: [Select]
  1. ((lambda (arxLoadList dllLoadList arxList)
  2.  
  3.    ;; Load arx apps
  4.    (acad-push-dbmod)
  5.    (foreach x  arxLoadList
  6.      (if (not (vl-position (vl-filename-base x) arxList))
  7.        (vl-catch-all-apply 'arxload (list x))))
  8.    (acad-pop-dbmod)
  9.  
  10.    ;; Load net apps
  11.    (foreach dll  dllLoadList
  12.      (if (findfile dll)
  13.        (progn
  14.          (terpri)
  15.          (command "._netload" dll))))
  16.    
  17.    (terpri))
  18.   '("doslib\\DOSLib18x64.arx"
  19.     ;; <- Other arx apps here
  20.     )
  21.   '("[FilePathIfNotInSupportPath\\]SomeAssemblyName.dll"
  22.     ;; <- Other net apps here
  23.     )
  24.   (arx))
  25.  
« Last Edit: June 09, 2012, 02:47:59 AM by RenderMan »
"How we think determines what we do, and what we do determines what we get."

Keith™

  • Villiage Idiot
  • Seagull
  • Posts: 16899
  • Superior Stupidity at its best
Re: Lisp files in startup suite not loading
« Reply #12 on: June 08, 2012, 12:26:09 PM »
The startup suite is profile dependent. If you check out the Mech profile and the standard Acad profile, you will see that Mech loads all of the mechanical stuff through the mechanical profile while the default profile for acad doesn't load anything.

Different profiles can be loaded from the shortcut .. to have the startup suite loaded with every profile, you will need to copy it to every profile.
Proud provider of opinion and arrogance since November 22, 2003 at 09:35:31 am
CadJockey Militia Field Marshal

Find me on https://parler.com @kblackie

cvcolomb

  • Guest
Re: Lisp files in startup suite not loading
« Reply #13 on: June 09, 2012, 01:07:18 AM »
Went and got all fancy on us, didn't you RM 

BlackBox

  • King Gator
  • Posts: 3770
Re: Lisp files in startup suite not loading
« Reply #14 on: June 09, 2012, 02:46:13 AM »
Went and got all fancy on us, didn't you RM

Naww... That's not [fancy], this is [fancy].

"How we think determines what we do, and what we do determines what we get."