S
Sam Cannell
Hi all,
I've been trying with little success to repackage Adobe Pagemaker 7 as an
MSI using SetupCapture in Wise Package Studio.
After installing the package that WPS generates, it will work for the user
the package was installed by, but when trying to run it as a different user
it installs the registry values under HKCU and then requests the original
MSI to reinstall files as well. From what I've been able to glean from the
event log and by watching filemon, the following is happening.
* User tries to start Pagemaker from the shortcut
* Msiexec sees that the keypath for the CurrentUser component is missing,
and reinstalls the missing registry keys.
* Msiexec continues on to reinstall the rest of Feature3 (Pm70.exe)
* Application starts
If I move the CurrentUser component into its own feature, it puts no
registry information at all into HKCU, as the shortcut is an advertised
shortcut for Feature3.
From searching on Google, I've found that msiexec only performs repairs at
the feature level, and will not reinstall individual components. I'm
assuming this is what I'm experiencing. Surely what I'm seeing above isn't
the intended behaviour?
If any of you could shed any light on this, it would be most appreciated.
Regards,
Sam
I've been trying with little success to repackage Adobe Pagemaker 7 as an
MSI using SetupCapture in Wise Package Studio.
After installing the package that WPS generates, it will work for the user
the package was installed by, but when trying to run it as a different user
it installs the registry values under HKCU and then requests the original
MSI to reinstall files as well. From what I've been able to glean from the
event log and by watching filemon, the following is happening.
* User tries to start Pagemaker from the shortcut
* Msiexec sees that the keypath for the CurrentUser component is missing,
and reinstalls the missing registry keys.
* Msiexec continues on to reinstall the rest of Feature3 (Pm70.exe)
* Application starts
If I move the CurrentUser component into its own feature, it puts no
registry information at all into HKCU, as the shortcut is an advertised
shortcut for Feature3.
From searching on Google, I've found that msiexec only performs repairs at
the feature level, and will not reinstall individual components. I'm
assuming this is what I'm experiencing. Surely what I'm seeing above isn't
the intended behaviour?
If any of you could shed any light on this, it would be most appreciated.
Regards,
Sam