Hi all,

I am currently packaging an application called IBM Rational Method Composer
after the packaging, it appears that some files will not be install in the first round, end up a repair will trigger when user launch shortcut, only then the files are installed and works.
Any idea what is causing this and any solution to rectify this? please help~
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
try making the files permanent.
Answered 04/03/2008 by: Ram
Senior Purple Belt

Please log in to comment
0
what do you mean by making it permanent?
FYI, I am using Wise Package Studio 7
Answered 04/03/2008 by: dinozilla
Orange Senior Belt

Please log in to comment
0
try making the files permanent. I *think* I know what RAM means (i.e. marking the files so that they are kept after an uninstall) but no idea why he's suggesting it here...

If a repair is being triggered, it sounds like the package is already an MSI, so my first question is, why are you packaging it? Do you mean that you're applying a transform? If not and you have re-packaged it, I sugest you abandon it and revert back to the original MSI. If the install is started with a setup executable (e.g. SETUP.EXE) then check in your %TEMP% folder for an MSI (almost always named with a 6-digit random name). It would be best to clear the %TEMP% folder before you start, but then, you'll be using a clean machine or VM anyway, right?
Answered 04/04/2008 by: VBScab
Red Belt

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