InstallAware

Hi,
Here is the scenario.
We have dlls in two different directories say Path1 and Path 2. Some of the dll's in Path2 are dependent on dll's in Path1. We set the paths of Path1 and Path2 in the %Path% environment variable using in the beginning of the install using "Set Environment" command. After "Appy Install" we are trying to register a dll, DLL2 in Path2 which has dependency dll, Dll1 in Path1, using "Register Library". The first time we run the installer, the registration of Dll2 failes because it cannot find Dll1. The second time we run it it passes. We could easily reproduce this issue by removing the paths Path1 and Path2 from the %Path% environment variable.
The issues seems to be when the InstallAware is running and even if we set the path, it doesn't take effect while the installer is running the first time. When we run the installer the second time then it sees the Path1 and Path2 and the registration works. Is there a way to make the installer look at the path the first time when we are trying to register the dll?

Dear User,

I suppose that you must RESTART the system in order to have the PATH environment variable resolved correctly by the target system.

You can force a system restart from your setup package using "Restart & Resume" command or alternatively, instead of the PATH environment variable to register the DLL, you should specify the dll path directly with the command.

Regards.

Hello,
Thank you for your reply. Regarding RESTART,it is not needed because if I reinstall it again, it works. The reason could be that when the new installation process comes up, the path is already set. But the first time, the path is set during install and for some reason, the process is not able to see it.
Regarding the explicit path,I do provide explicit path to the main dll that is being registered. But the issue is the dll2 that the main dll depends on is in a different path and it is not able to resolve all the dependencies causing registration to fail.
My main issue is how can I set the PATH variable so that the installer can use the path entries to resolve all the dependencies.
Thanks

Dear User,

Unfortunately, I still believe that a system reboot is always recommended after environment variables modification.

Some applications and system process, gets snapshot of environment at start up only.
This can cause that environment variables changes are not propagated to a running app or to a system process.

Regards