Jump to content

Old program doesn't work anymore in acad


andyr74

Recommended Posts

On acad we use some own created lisp routines. We also use an "*.exe" program, probably created in lips and compiled in exe and made by an old collegue. We don't have the source code for this. This program is maybe 20 to 25 years old. This program is used for the input and drawing of some things we use. We never had problems with this program.

 

Up until now we used 32 bit Windows versions.

We now just switched to new computerhardware with 64bit windows 8.1.

 

The lisp routines stil work but the biggest problem is the exe-file. When trying to run in acad it says the program is not compatible with the current windows version.

So, I think it is a 16 bit program we try to run on a 64 bit OS.

 

Is there anything we can do about this.

Link to comment
Share on other sites

On acad we use some own created lisp routines. We also use an "*.exe" program, probably created in lips and compiled in exe and made by an old collegue. We don't have the source code for this. This program is maybe 20 to 25 years old. This program is used for the input and drawing of some things we use. We never had problems with this program.

 

Up until now we used 32 bit Windows versions.

We now just switched to new computerhardware with 64bit windows 8.1.

 

The lisp routines stil work but the biggest problem is the exe-file. When trying to run in acad it says the program is not compatible with the current windows version.

So, I think it is a 16 bit program we try to run on a 64 bit OS.

 

Is there anything we can do about this.

 

Your .EXE is a compiled, external, stand-alone application, and not an internal routine such as LISP, nor an AutoCAD plug-in (.DLL)... External code that accesses AutoCAD uses COM API (as a generalization), which is environment dependent (i.e., 32-bit vs 64-bit), and requires a recompile for 64-bit environment.

 

If this code was produced by a former employee, then presumably it was not obfuscated, so you can simply decompile with IlSpy, etc. and paste the source code into your own, new Visual Studio project and compile for the correct environment, or simply port the code to .NET API if you can still get a hold of the 2009 SDK (the version you list as using, unless you've upgrade that too, with Win8.1?).

 

Cheers

Link to comment
Share on other sites

Your .EXE is a compiled, external, stand-alone application, and not an internal routine such as LISP, nor an AutoCAD plug-in (.DLL)... External code that accesses AutoCAD uses COM API (as a generalization), which is environment dependent (i.e., 32-bit vs 64-bit), and requires a recompile for 64-bit environment.

 

If this code was produced by a former employee, then presumably it was not obfuscated, so you can simply decompile with IlSpy, etc. and paste the source code into your own, new Visual Studio project and compile for the correct environment, or simply port the code to .NET API if you can still get a hold of the 2009 SDK (the version you list as using, unless you've upgrade that too, with Win8.1?).

 

Cheers

 

The program reads values from a text file and makes a script file (together with some input) for everything that has to be drawn. Running this script file will draw everything needed.

 

I will try to decompile it.

Can I recompile it with the visual basic editor within acad or do I need a special program?

Link to comment
Share on other sites

I tried to load the "exe" file in IlSpy but I get the message: "This file does not contain a managed assembly."

 

The "exe" file was originally created many years ago (around autocad 10 or 12 I think). I don't know how it was created.

Is there a way to know how it was created and the to decopile it with a correct program?

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...