OpenDCL Runtime MSM

Not sure if this is the right place to post this... I used the OpenDCL Runtime MSM file to add it to my installation program. When I run the new INSTALL file, it adds the TXT, ARX & DLL files to the proper "Commons" folder. But when you launch AutoCAD it does not do the demand load (OpenDCL is an unknown command). Is there something I should look for in my INSTALL to make sure the ARX are added to the demand load of AutoCAD?

This might be a stupid question, since I know nothing about these installers, but is your demandload sys. var. set to 2 or 3?

DEMANDLOAD is set to 3. I'm guessing that my Installer is not registering the DLL... Just not sure.

Daniel,
What is the value in the registry at ;
HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R17.1\ACAD-6001:409\Applications\OpenDCL

your version may differ
.. something like this ??

[attachment deleted by admin]

There is no entry for OpenDCL under the ACAD Application... in any version. I'm assuming I need to add the registry items for OpenDCL to each version of AutoCAD in my installer. I don't have 2004 or 2005 loaded. Is there a list for these registry locations? I can make some assumptions, but I would prefer to do it right.

Also what is in the "Command" key under OpenDCL? I guess I could install the OpenDCL Runtime MSI to get these... but I was trying to work with a clean install. May be useful to list this in the documentation. At this point, I'm just babbling  ;)

Here's a piccy of mine for AC2008



[attachment deleted by admin]

author=dkh007 link=topic=11.msg34#msg34 date=1184121114 wrote:
There is no entry for OpenDCL under the ACAD Application...

The MSM should create the demand load registry keys. Both the Runtime MSI and the Studio MSI include the same MSM file, so I'm not sure why it's not working for you. Are you running the MSI with no administrative privileges, or installing for "Just Me"? If this is the case, the demand load keys should be created under the HKCU key instead of HKLM, but it should still work for that user.

What process and settings are you using to incorporate the MSM into your installation? I'm guessing that either your installer does something that causes the custom actions to be ignored, or else there is something causing the RxInstall.dll to malfunction.

The OpenDCL Runtime MSI installs the Demand load keys just fine. It has worked for both XP and Vista. I install it with Administrator privillages.

I'm using Tarma ExpertInstall {2}. It has a section for working with and importing Merge Modules. When I do the import it does not include the registry keys. I'm assuming this is a limitation of Tarma. At this point, I think the best bet is to install the Runtime MSI, export the registry keys and then import those into the Tarma Installer. Of course, I have normally stayed away from the ACAD registry, not sure if the (R16.0\ACAD-xxx:xxx, R17.1\ACAD-xxxx:xxx, etc) xxxx:xxx are the same on all machines/installs, just different for each version... Any insight is greatly appreciated, even though I know this probably isn't the place for the AutoCAD registry 101 course.

author=dkh007 link=topic=11.msg37#msg37 date=1184124949 wrote:
... At this point, I think the best bet is to install the Runtime MSI, export the registry keys and then import those into the Tarma Installer...

That won't work for general installations. Your installer has to enumerate the registry to find the installed AutoCAD (or AutoCADs). RxInstall.dll does this (and does the reverse on uninstall). It looks to me like your best bet is to include the entire Runtime MSI and execute it (see ).

It looks to me like your best bet is to include the entire Runtime MSI and execute it

Thanks Owen! That was going to be my original approach, but I thought I would give the MSM a try. Including the entire MSI worked just fine.