Support\acad2024.lsp runs automatically in accoreconsole

Support\acad2024.lsp runs automatically in accoreconsole

bwagnerAUWGA
Participant Participant
817 Views
9 Replies
Message 1 of 10

Support\acad2024.lsp runs automatically in accoreconsole

bwagnerAUWGA
Participant
Participant

My company uses accoreconsole for processing various things.  In older versions, it starts up with very little fanfare.  But in accoreconsole 2024, it launches Support\acad2024.lsp (an Autodesk supplied script), which launches Acad2024doc.lsp (our own custom script), which launches other .lsp scripts, which require full AutoCAD to run and aren't compatible with with accoreconsole, and the whole thing fails, and it refuses to run the script that was passed with /s.

 

How do we make it not run those scripts?  Is there a way to detect accoreconsole and exit the script?  Has anyone else run into this?  Is this a bug in accoreconsole 2024, or an intentional change?

0 Likes
Accepted solutions (1)
818 Views
9 Replies
Replies (9)
Message 2 of 10

bwagnerAUWGA
Participant
Participant

I have tested it with different AutoCAD versions, and it looks like this behavior changed between accoreconsole 2021 and 2022.  So it has apparently been like that for at least 3 years, and nobody has complained about it yet.  So I'm guessing detecting accoreconsole from Lisp and take an early exit is going to be the best bet.  Does anyone know how to detect such a thing?

0 Likes
Message 3 of 10

paullimapa
Mentor
Mentor

what if you designate in your batch file/code to only run accoreconsole 2021 and not the current AutoCAD version?


Paul Li
IT Specialist
@The Office
Apps & Publications | Video Demos
0 Likes
Message 4 of 10

Sea-Haven
Mentor
Mentor

"which launches Acad2024doc.lsp (our own custom script)" that is why I stay away from the likes of acaddoc.lsp etc and use custom lisp's that are loaded through "Start Up Suite" You may be able to pull your custom stuff out of Acad2024doc.lsp and use Appload, Start up Suite, yourcustom.lsp, NOT TESTED.

0 Likes
Message 5 of 10

bwagnerAUWGA
Participant
Participant

Running an old version of AutoCAD is only a temporary fix.  Eventually they will force us onto newer versions.

0 Likes
Message 6 of 10

bwagnerAUWGA
Participant
Participant

I tested appload.  It appears to be tied to a specific profile, so while it could be deployed by a registry edit, it would only be active while the <<Unnamed Profile>> is the current one.

0 Likes
Message 7 of 10

paullimapa
Mentor
Mentor

Who's going to force you? You just leave the old install there for coreconsole purposes but work on latest AutoCAD....problem solved.


Paul Li
IT Specialist
@The Office
Apps & Publications | Video Demos
0 Likes
Message 8 of 10

bwagnerAUWGA
Participant
Participant

AutoDesk only licenses AutoCAD back to a certain age, before that the license server won't let you use an old version.

0 Likes
Message 9 of 10

paullimapa
Mentor
Mentor

As long as you're on subscription, you can have up to five versions back installed.

And if you need even older versions than that then it's as easy as contacting them to request for leaving the older version on your system. You have a very good reason for it....that is until you find a better solution.


Paul Li
IT Specialist
@The Office
Apps & Publications | Video Demos
0 Likes
Message 10 of 10

bwagnerAUWGA
Participant
Participant
Accepted solution

I found a reference on how to detect it.  AcCoreConsole doesn't load the VBA functions that AutoCAD does.

 

https://stackoverflow.com/questions/51720302/lisp-function-exists-or-not-checking

 

So (type vla-put-textstring) returns nil in accoreconsole, and returns SUBR in AutoCAD.

0 Likes