06-24-2009 01:24 PM
Hi all,
We build a large program with hundreds of vis using Labview 8.2. We create an installer to install this program at our cusomter's computers. It appears that after installing our program, Orcad (previously installed on customer's computer) doesn't work and a number of Windows dll files are erased.
Does anyone know why this happens, and how we can prevent it? We certainly don't use anything from Orcad in our program.
Thanks,
Danielle
06-25-2009 01:51 AM
Hi,
I was misinformed: Installing our program doesn't erase any dlls, but it changes the system environment variables: it removes the system path variable consistently (%systemroot%system32), and in the case of Orcad it removes additional parameters so that Orcad does not find its dlls.
Why does Labview do this? Is there any way to prevent this?
Thanks,
Danielle
06-25-2009 02:10 AM
06-25-2009 06:08 AM
Hi,
We develop and install our program on Windows XP.
The problem doesn't appear when Labview is installed with Orcad; only when installing a Labview executable program after installing Orcad.
For example, I build a project myfun in Labview to myfun.exe, and build an installer for it. After using the installer, the environment variables are changed and Orcad can't find its dlls.
Thanks,
Danielle
06-25-2009 07:40 AM
08-18-2009 05:01 AM
Hi,
Does anyone have any ideas?
Thanks,
Danielle