OpenDCL Forums

OpenDCL => Runtime/AutoLISP => Topic started by: Fred Tomke on April 24, 2008, 11:30:50 PM

Title: 64 Bit loading
Post by: Fred Tomke on April 24, 2008, 11:30:50 PM
Hello,

if I cannot use the opendcl command (because of political reasons), I would do it by hand using arxload. But how to decide whether 64 Bit runtime must be loaded or not. Does anybody have any solution for it?

Regards, Fred
Title: Re: 64 Bit loading
Post by: owenwengerd on April 25, 2008, 06:47:10 AM
Take a look at ManualLoading.lsp in the Samples folder.
Title: Re: 64 Bit loading
Post by: Fred Tomke on April 26, 2008, 09:16:43 AM
Thanks, I will do.

Meanwhile I tried to load using demand load and I got an error:

Befehl: opendcl
Laden nach Bedarf wegen eines fehlenden Moduls fehlgeschlagen:
Name: OpenDCL
Beschreibung: OpenDCL
Modulpfad: C:\Program Files (x86)\Common Files\OpenDCL.x64.17.arx

In the registry the loader item of runtime install is not correct:

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

Regards, Fred

Title: Re: 64 Bit loading
Post by: owenwengerd on April 26, 2008, 11:45:03 AM
Fred, can you be more specific about how and what you installed?  I did find and fix a bug whereby the "Language" value is not read correctly on x64, but this results in a "Language module not found" error and does not affect demand loading.
Title: Re: 64 Bit loading
Post by: Fred Tomke on April 26, 2008, 12:28:37 PM
Sorry Owen,

OS: Vista Business 64 Bit
CAD: AutoCAD 2008 Deu 64 Bit
ODCL: Only Runtime Alpha 12 DEU

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

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

I think the subfolder OpenDCL in C:\Program Files (x86)\Common Files was missed.

Error message:
Befehl: opendcl
Laden nach Bedarf wegen eines fehlenden Moduls fehlgeschlagen:
Name: OpenDCL
Beschreibung: OpenDCL
Modulpfad: C:\Program Files (x86)\Common Files\OpenDCL.x64.17.arx

Hope that is more enough to debug.

Fred
Title: Re: 64 Bit loading
Post by: owenwengerd on April 26, 2008, 01:21:00 PM
Got it.  This is now fixed.