Jump to content


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.
Photo

Understanding MSDN


3 replies to this topic

agord

agord
  • Members
  • 10 posts

Posted 12 March 2002 - 22:18

Platform SDK contains following statements in Windows Installer->Windows Installer Examples->A Small Update Patching Example->Planning a Small Update Patch topic:

"To create the small update first obtain a fully uncompressed image of the MNP2000 product that includes the error in Concert.txt. The image must include MNP2000.msi and all the source files described in Planning the Installation. In the following discussion this is called the Target image. The Target image must be fully uncompressed because the patch creation process is unable to generate binary patches for files compressed in cabinets. Put the .msi file and all the source files of the Target image into a folder named Target."

Since my installation is .MSI package with files placed in .CABs in it and Bit 1 of Word Count Summary Property set i don't understand:
- what is "fully uncompressed image"?;
- how to "obtain" it?
- how to "Put the .msi file and all the source files of the Target image into a folder named Target"?


Thanks for your reply!

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 13 March 2002 - 08:34

You can either create an uncompressed release (the steps depend on the tool you are using), or you run an administrative install of the compressed setup. This should uncompress the files from the CABs and store them in a folder you select.

agord

agord
  • Members
  • 10 posts

Posted 23 March 2002 - 21:52

When during creation of administrative installation under ordinal user account MI interrupts with error "You do not have sufficient privileges to complete this installation for all users of the machine.  Log on as administrator and then retry this installation."

How to make administrative installation under non-administrator account? Should the package be authored in some way or MI policy set?

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 24 March 2002 - 06:22

You can set the AlwaysInstallPrivileged policy (see Windows Installer help for details).
When authoring your package you should in general check for the Privileged property instead of the AdminUser property when checking user rights.