"The OpenDCL RUntime module failed to load."

AutoCAD Message:
"The OpenDCL Runtime module failed to load. Please repair the OpenDCL installation and try again."

This is my first post. Hello. :) bummer first post though.

I currently have AutoCAD 2008 and 2010 installed on this 64bit machine.

The order of events I have went through:

>Installed OpenDCL Studio 5.1.2.3 (at least that is what the About says)
>After install - Drag and drop the _MasterDemo.lsp file into 08. I got the message above.
>Closed ODCL and AutoCAD
>Drag and drop _MasterDemo.lsp into 2010. Same message.
>ran OpenDCL.Runtime.5.1.2.3.msi
>added folders to support file search paths - same errors.

In another post (which I cant seem to find now) some code was posted as help to this problem:
(defun c:TestIt (/ odcl_arxpath) 
  (vl-load-com)
  (princ (strcat "\n  Demand Load Setting :" 
                  (itoa (getvar "demandload")) 
                  "\n" 
          ) 
  ) 
  (setq 
    odcl_arxpath (vl-registry-read (strcat "HKEY_LOCAL_MACHINE\\" 
                                            (vlax-product-key)
                                            "\\Applications\\OpenDCL" 
                                    ) 
                                    "Loader" 
                  ) 
  ) 
  (princ 
    (strcat "\n  ArxPath : " (VL-PRINC-TO-STRING odcl_arxpath) "\n") 
  ) 
  (princ) 
)

This is the output:

Demand Load Setting :3



   ArxPath : C:\Program Files (x86)\Common Files\OpenDCL\OpenDCL.x64.17.arx

Any help would be very much appreciated. I was indirectly directed to OpenDCL from users at theswamp.org. From what I have read I am pretty excited to dive in. I am a bit slow to get into .net though I want to. For now though, I really want this to work. Thank you.

Welcome to the team Oak3s.
Hmmm, you shouldn't be getting that error with these results of TestIt...
You did have AutoCAD installed before installing OpenDCL, right?
You're not moving the ARX's to anther folder or on the network, right?

I have made some headway.

I manually loaded OpenDCL.x64.17.arx. I havent tested things completely but I was able to drag and drop the _MasterDemo.lsp.

For anyone with similar error:

Command: arx



Enter an option [?/Load/Unload/Commands/Options]: load



OpenDCL Runtime [5.1.2.3] loaded

When I picked load I was able to browse to C:\Program Files (x86)\Common Files\OpenDCL\OpenDCL.x64.17.arx

I hope I posted this soon enough. Also hope this helps anyone with a similar problem.

author=BazzaCAD link=topic=1189.msg6354#msg6354 date=1267055842 wrote:
You did have AutoCAD installed before installing OpenDCL, right?
You're not moving the ARX's to anther folder or on the network, right?

You are correct. AutoCAD was installed already (both 2008 and 2010).
The ARX's were not moved.

Thanks Berry for the welcome.

Welcome to the forum Oak3s.

What happens when you type 'OPENDCL' in a new drawing ?

When I first start up AutoCAD I get the 'Unknown command' message.
If I load the ARX manually and then close the drawing, then type 'opendcl' I dont get a message at all.

Start AutoCAD, then enter the following to get the value of the LoadCtrls demand-load registry key:
(vl-load-com)
(vl-registry-read (strcat "HKEY_LOCAL_MACHINE\\" (vlax-product-key) "\\Applications\\OpenDCL" ) "LoadCtrls")

If these values are all set corrctcly, and the runtime .arx file is accessible, then AutoCAD should demand load the file when you enter the OPENDCL command.

author=Oak3s link=topic=1189.msg6360#msg6360 date=1267116050 wrote:
When I first start up AutoCAD I get the 'Unknown command' message.
If I load the ARX manually and then close the drawing, then type 'opendcl' I dont get a message at all.

If you don't get a message at all, that's good. It means it's already loaded. But it should demand load, without you having to load it manually.
Now that you've got it working manually, does the demand loading work or do you always have to load it manually?
I noticed in your fist post you said you installed both the studio & the run-time. You shouldn't have to install both. Just install the Studio (it includes the run-time). Maybe you installed different versions of the Studio & the run-time...

I installed the runtime because of the original error message.

When I run Owens code:

Command: (vl-registry-read (strcat "HKEY_LOCAL_MACHINE\\" (vlax-product-key) 

"\\Applications\\OpenDCL" ) "LoadCtrls")

12

Then Opendcl returns:

Command: opendcl

Unknown command "OPENDCL".  Press F1 for help.

I have to load it when I start AutoCAD. I do not have to load it with every new drawing.

Given what you have posted, it appears that something is causing AutoCAD's demand load feature to fail. Are you running any other add-ons or Windows utilities (like anti-virus software) that could be interfering? Is this plain AutoCAD, or a vertical variant?

There are no add-ons to plain AutoCAD other than custom cui/lisp's. If anti-virus software is interfering I am not getting any report of it doing so. The AV software (as I understand it) is through a server. I dont even know what it is. :) Just started a few weeks back.

Strange. Does AutoCAD's IMAGE command work correctly?

:) If by work correctly you mean bringing up the xrefs. If I put in -image then I get the image option at commandline. If I attach everything seems to work as expected. Though I have never really put this into much practice. Seems to work though.

The IMAGE command relies on the same demand loading feature that OPENDCL uses, so if it works for the IMAGE command, it should work for the OPENDCL command. I'd sure like to know why it doesn't.

Hello,
sorry for bringing up an old thread but I'm having the same problem right now. I've been using 2008 & OpenDCL5.1.2.1 recently I've updated to 2011 and removed 2008. opendcl didn't work at my first attempt and I removed it and installed 5.1.2.3 version.

It still doesn't load at the startup. If I manually load .arx everything works but how do I make it load automatically? Thanks

I'm not sure why it's not demand loading correctly, but I wonder if you somehow have multiple versions installed.  I recommend to upgrade to OpenDCL 6 to see if that fixes the problem.  OpenDCL 6 is more stable than 5.1 by now, so you should probably upgrade anyway.