Hi,
As I have read in previous messages, in certain situations, you can use the duplicatefile table to allow the MSI self-repair to create user profile files without having to go back to the sources (by copying the default profile to the programs files folder, and duplicating this to the user profile). I have tried this, but the dialog still comes up prompting for the location of the original source MSI, it does not seem to recognise that the files are present and need to be copied from programfiles. Could you please expand on exactly how to accomplish this?
Thanks
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
DuplicateFile Table
Started by
sean2004
, Aug 09 2005 10:33
2 replies to this topic
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 09 August 2005 - 14:11
Where did you read this? What you could do is use the DuplicateFile table to put the file into each user's profile during initial install, thus avoiding the repair alltogether.
Another (IMHO better) option would be to put thoise files in the program files folder, and have your application copy them to the user's profile folder during startup if they don't exist there. In other words you would be placing the defaults in the program folder.
Another (IMHO better) option would be to put thoise files in the program files folder, and have your application copy them to the user's profile folder during startup if they don't exist there. In other words you would be placing the defaults in the program folder.
Stefan Krüger
InstallSite.org twitter facebook
mandy
-
- Members
- 121 posts
Posted 09 August 2005 - 15:24
Hi Sean.
You should be able to accomplish what you are trying to do as follows (for a per-machine install):
1) Copy any "user-profile" based files under the "INSTALLDIR" (a machine location) instead of directly to the user profile.
2) Create duplicate file entries to copy the files to the correct profile location.
3) Ensure that all "user" components containing the duplicate files have unique "HKCU" keypaths.
4) If the files are unversionned, ensure that they have "MsiFileHash" table entries.
5) Ensure all entry points to the feature in question are "advertised".
Good luck! :)
You should be able to accomplish what you are trying to do as follows (for a per-machine install):
1) Copy any "user-profile" based files under the "INSTALLDIR" (a machine location) instead of directly to the user profile.
2) Create duplicate file entries to copy the files to the correct profile location.
3) Ensure that all "user" components containing the duplicate files have unique "HKCU" keypaths.
4) If the files are unversionned, ensure that they have "MsiFileHash" table entries.
5) Ensure all entry points to the feature in question are "advertised".
Good luck! :)