Topic: Error Base.dcl not found

[lamarn]

I am getting errors on different computers where a Base.dcl error keeps popping up in every function that has a dcl (through a vlx file) I tried it with fresh profiles and different settings, nothing seems to work.

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/DCL-errors-when-starting-AutoCAD-products.html

Any other suggestions than this one?

[mjfarrell]

verify that it is missing....then place a known good copy in the location it's supposed to be in.

[lamarn]

correction for the title. It is not missing, there is something wrong with it in relation with the vlx. I can't be checking all and every autocad install. It really seems there is something wrong with how the vlx ia made. When I rum the lsp/dcl separate the is not a problem.

[mjfarrell]

I see someone else was having this issue....

they were directed to delete a particular registry key to clear it up:

HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R17.1\ACAD-6018:409

It is version specific....so you would want to look under whatever version you are having the issue with.

[dgorsman]

I see someone else was having this issue....

they were directed to delete a particular registry key to clear it up:

HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R17.1\ACAD-6018:409

It is version specific....so you would want to look under whatever version you are having the issue with.

Aaahhhh yeah.  No, don't do that.  That registry key points to the top-level of the AutoCAD settings for that user.  It will nuke *all* settings, profiles, everything, for that user.  Deleting that is the same as doing a re-install.

[mjfarrell]

I see someone else was having this issue....

they were directed to delete a particular registry key to clear it up:

HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R17.1\ACAD-6018:409

It is version specific....so you would want to look under whatever version you are having the issue with.

Aaahhhh yeah.  No, don't do that.  That registry key points to the top-level of the AutoCAD settings for that user.  It will nuke *all* settings, profiles, everything, for that user.  Deleting that is the same as doing a re-install.

Which might be exactly the cure for the problem...

[MP]

[mjfarrell]

Sometime....it is the right tool for the job....

sometimes it just feels good to use it. 

[lamarn]

LOL 😁  would you believe today I got a brand new laptop after 4 years of good service.
First I need to get AutoCAD installed, than I will try again. Maybe start with just one lsp in one vlx to load.. To be continued

[MP]

Maybe start with just one lsp in one vlx to load.

[lamarn]

.. 1 DCL..

[lamarn]

New Laptop, new installations, Same shit.
My tools installed on 2017 work but not on 2019 pre release on laptop 1 (new), and 2017 doesn't works but 2018 works on laptop 2 (old)


This can be found in acad.dce about when testing one of the dcl files.
I'm now looking into difference between base.dcl in the different versions, are there any differences?

====== DCL semantic audit of C:\Users\hala6\AppData\Local\Temp\$VL~~001.DCL ======

Error. Widget named "row" is undefined.
    Widgets of this type cannot have children.

Error. Widget named "column" is undefined.

Error. Widget named "boxed_row" is undefined.

Error. Widget named "boxed_column" is undefined.

[lamarn]

previewing in *: no result, ..
 
; warning:cannot create tmp file for DCL: "C:/Program Files/Autodesk/AutoCAD Pi Release Candidate Beta/$vld$.dcl"
(other warning because apparently it needs administer rights..)

Previewing the same dcl in Vlide in 2018, it's ok

What am i doing 'illegal' ??

[dgorsman]

Ermmm... BETA content should never be discussed in a public forum.  Check the date for the embargo being lifted.

Also, BETA installs have a tendency to bugger up some of the VLISP registry stuff - in the past I've had to do a full-reinstall of previous commercial releases (a repair install didn't work).

[MP]

NDAs, how do they work?