Community
AutoCAD Forum
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Extra messages on command line at startup (acad2023)

10 REPLIES 10
SOLVED
Reply
Message 1 of 11
PDACTL
725 Views, 10 Replies

Extra messages on command line at startup (acad2023)

On first launch of AutoCAD I get the following after the final (princ) command from my custom menu's .mnl

 

Setup Completed.  [my final command]
*Cancel*

Command: *Cancel*
COMMANDLINE


Command:

 

When I open subsequent drawings I do not get the extra two *Cancels* and COMMANDLINE.

 

How can I determine the source/cause of these?

10 REPLIES 10
Message 2 of 11
Kent1Cooper
in reply to: PDACTL

Look for an acad.lsp file that could be doing it, which as Help describes it, is run on starting AutoCAD, but not in every drawing as the acaddoc.lsp file is.  If that doesn't find it, get into the APPLOAD dialog box and look in the Startup Suite [the briefcase icon] for a possible source.

Kent Cooper, AIA
Message 3 of 11
PDACTL
in reply to: Kent1Cooper

acad2023.lsp and acad2023doc.lsp are present (unmodified from as-installed) but these load before my menu and its lisp files. There is nothing in the startup suite at all.

 

My .mnl file just loads a few lisp functions all of which end with a (princ "xxx loaded") message.

 

The other stuff seems to come after this has loaded.

Message 4 of 11
Kent1Cooper
in reply to: PDACTL


@PDACTL wrote:

acad2023.lsp and acad2023doc.lsp are present (unmodified from as-installed) ....


Is there a plain acad.lsp file?

Kent Cooper, AIA
Message 5 of 11
PDACTL
in reply to: Kent1Cooper

I cannot see one anywhere in my support file search paths.

Message 6 of 11
pendean
in reply to: PDACTL


@PDACTL wrote:

... after the final (princ) command from my custom menu's .mnl...

 

How can I determine the source/cause of these?


You seem to have answered it right there: if your custom MNL file was not there this does not happen, yes? Share that file here.

Message 7 of 11
PDACTL
in reply to: pendean


@pendean wrote:

@PDACTL wrote:

... after the final (princ) command from my custom menu's .mnl...

 

How can I determine the source/cause of these?


You seem to have answered it right there: if your custom MNL file was not there this does not happen, yes? Share that file here.


No, it still happens if I remove my MNL and also if I unload my menu entirely!

 

The full output without my menu:

 

Customization file loaded successfully. Customization Group: ACAD
Customization file loaded successfully. Customization Group: CUSTOM
Customization file loaded successfully. Customization Group: MODELDOC
Customization file loaded successfully. Customization Group: EXPRESS
Customization file loaded successfully. Customization Group: APPMANAGER
Customization file loaded successfully. Customization Group: INSIGHTSGROUP
Customization file loaded successfully. Customization Group: FEATUREDAPPS
Regenerating model.

 

AutoCAD menu utilities loaded.*Cancel*

Command: *Cancel*
COMMANDLINE


Command:

Message 8 of 11
ВeekeeCZ
in reply to: PDACTL

I wouldn't worry about them. I have some too. Having C3D as AutoCAD.

 

Regenerating model.
*Cancel*

Loading AECC Point Cloud...


AutoCAD menu utilities loaded.

c:/Users/***/_Autocad/ACADDOC.lsp loaded.*Cancel*

Command: *Cancel*
_RIBBON
*Cancel*
COMMANDLINE

 

COMMANDLINE comes from the workspace setting (tested). RIBBON and some of *Cancels* probably too - but did not test them and don't know what setting causes *Cancel*.

 

BeekeeCZ_0-1650899552903.png

 

Message 9 of 11
pendean
in reply to: PDACTL

@PDACTL From my R2021's startup:
...
_RIBBON
*Cancel*
COMMANDLINE
SHEETSET
*Cancel*
TOOLPALETTES
BlocksPalette
EXTERNALREFERENCES
properties

R2022 and R2023 do the same.

Looks like no one ever noticed before, seems normal.
Message 10 of 11
PDACTL
in reply to: PDACTL

I understand the COMMANDLINE bit but don't see why it has to tell me that part of the user interface is active every time I launch AutoCAD!

 

More concerned with the spurious *Cancel* messages that indicate to me that something is not right. I guess I'll have to live with it!

Message 11 of 11
james_moore
in reply to: pendean

This isn't doing the trick now, but I'm pretty sure the problem is coming from one of the .pgp files, as I have solved this before by doing this.  I found it once by eliminating .lsp and .pgp files that autoload until I found the right one.

 

 

 

This problem probably is coming from acadSynonymsGlobalDB.pgp.  It has a commented near the top that when shortened, the problem goes away.

Change this:

; Each synonym can point to only one command and should not conflict with
; any command alias defined in the product PGP file.

 

To this:

; Each synonym can point to only one command and should not conflict
; with any command alias defined in the product PGP file.

 

 

OR  I've seen this version:

; This .pgp file contains a list of command synonyms. You can also add your own synonyms.
; Each synonym can point to only one command and should not conflict with any command
; alias defined in the product PGP file.

 

which I change to this:

; This .pgp file contains a list of command synonyms. You can also add
; your own synonyms.
; Each synonym can point to only one command and should not conflict with
; any command alias defined in the product PGP file.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Technology Administrators


Autodesk Design & Make Report