IBM DB2 Client which I'm packaging with WPS at the moment (I *love* IBM software...grrrr) insists on putting a file DB2CLI.INI into the 'root' of the user profile (i.e. C:\Docuemnts & Settings\[username]). One of the reasons I love IBM s/w is that this one COMPLETELY ignores the DB2CLIINIPATH environment variable (documented on IBM web site) which I'd set to bypass the issue.

Both the component and the INI entry have their directories set to 'ProfilesFolder' but on installation, the file ends up in the Windows folder, not user profile. We know the user profile is set OK 'internally' because the Start Menu entry and other files which are in a tree below the profile folder go to the correct locations. I've also tried treating the INI as a file but the result is the same: it gets copied to the Windows folder.

It seems WPS has a problem with files in the root of the profile. Question is, how do I work aroud it "cleanly"? I have a CA which moves it but I can't realistically use it because other packages coming on-stream need to add aliases to the file and it's unrealistic to have to add CAs to each of them, just to bypass WPS's failings.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

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

Answers

0
As you were...

I've sprinkled a few 'Set Directory' CA around which has worked. Yet another bug report into Altiris...
Answered 11/14/2007 by: VBScab
Red Belt

Please log in to comment
0
Great that you found a solution Ian,

However this isn't a WPS think but how Windows Installer resolves system folders.
Using a Set Directory is the only solution for this one as you already found out.

Cheers!
Answered 11/14/2007 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity