I am working on a large application, 2gb 80,000plus files. It comprises some vendor supplied msi's and some setup-capture msi's of my own creation using Wise Package Studio 4.5

One of my msi's insists on self repairing the first time an advertised application is run, this is fair enough because it does contain some CU registry entries. I have created the CurrentUser feature and made the Complete feature a child of it. The CurrentUser feature contains the CurrentUser component with all (that I can find) required entries. BUT It does a complete self-repair referencing back to the source and takes 15minutes. NOT Ideal! After the first run it is fine for that user,

To further complicate matters the application (Mentor Graphics) uses XVision as a Unix Emulator and has a great many environment variables and additions to the Path. So many that we regularly overrun the 256character limit on the path. To get round this the customer has created startup scripts which set the required variables for each portion of app that is started (i.e the shortcut calls the script which sets the variables then starts that bit of the app). The list of script wrapped shortcuts is currently at 15 and growing, therefore the customer wants to exclude the shortcuts from the msi's have them copied in initially by our kix script that runs the install - no problem there. That way if they need to add/change the shortcuts they make them available via the log-in script so that they are copied in to the Shortcuts folder (permissions granted to allow this- in our locked down environment.

I can't find why the full self-repair is happening. If I run one of the rogue portions as the user who did the install, there is no self-repair.

The exe's that the scripts/shortcuts call are advertised via the classes.

Does anybody have any ideas, PLEASE?

BTW Using Win2k desktops in a non AD domain at prsent.

Thanks in advance

Gary
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
First step is to use the event viewer to find out which component is broken.

Do you have any user-profile based files? Maybe something under "Application Data"?

ICE validate your MSI - make sure you don't have machine and user resources in the same component. Also make sure that your user components have "HKCU" keypaths (not files).

Regarding the "Path" environment variable - have you tried using "AppPaths" to set the path on a "per-process" basis?
Answered 05/17/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
created the CurrentUser feature and made the Complete feature a child of it. The CurrentUser feature contains the CurrentUser component with all (that I can find) required

Got any empty components in your captured packages? That can cause a self repair every time.
Answered 05/21/2005 by: GB1
Orange Belt

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