folder is resolved incorrectly


I'm running into a weird problem here. I've sequenced an app that places a folder directly on the C: rootdrive called Bimwin. Usually, such a thing is no problem at all. Take Oracle for example. Oracle has always worked just fine this way. Sequencer creates a folder called Oracle alongside the CSIDL_* folders and resolves it correctly to C:\oracle.

However, for Bimwin this is not the case. When running the sequence on a client it can't find the folder C:\Bimwin. And the weird thing is, the very same sequence contains Oracle as well, and Oracle is resolved just fine, as it always does.


Some more specific details:

- The Bimwin folder has a subfolder called Bimasimp, set to Merge with local. If I set it to override (to follow the example of oracle, like C:\oracle\ora92 for example), it shows a variable path for the subfolder: %Bimwin%\Bimasimp (instead of something like C:\oracle\ora92). When I try to change it, weird stuff happens, like it's being displayed as a file instead of folder, or most of the files disappear.

- The CSIDL_* folders all have variables as well, just as the oracle folder directly under the root. They however get correctly resolved...?

Has anyone encoutered this before, or knows a way to fix the path of the folder? Any clue where to look for the problem?

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ