Is msizap.exe redistributable?
![Rich [Microsoft Windows Installer MVP]'s profile photo](https://lh3.googleusercontent.com/a/default-user=s40-c)
Rich [Microsoft Windows Installer MVP]
=?Utf-8?B?Um9i?= <anon...@discussions.microsoft.com> spake the secret code
<EA8B9D85-E456-4211...@microsoft.com> thusly:
>Does anyone know what the restrictions are (if any) on including
>msizap.exe with an installation?
Check the redistributables license from the Platform SDK to see if you
can include it. I don't think its on the list of things you can
redistribute.
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>
Christopher
Except...you can redistribute msicu.exe and msicuu.exe to clients that have a licensed copy of MS Office installed on the machine to which you are redistributing them.
We've concluded that we have to write our own. If anyone already has, please advise. Thanks!
Dennis Bareis
On Thu, 12 Feb 2004 08:21:09 -0800, "Christopher"
<temp9.removeme.@real-d.com.invalid> wrote:
>We've concluded that we have to write our own. If anyone already has, please advise. Thanks!
I'm not sure what sort of advice you'd like as you haven't mentioned
any problem...
Bye,
Dennis
----------------------------
Dennis Bareis (dba...@KillSpam.labyrinth.net.au)
http://www.labyrinth.net.au/~dbareis/index.htm
Free MSI automation/creation tool:
http://www.labyrinth.net.au/~dbareis/makemsi.htm
----------------------------
Chris Gouge [MSFT]
intended for development machines which often encounter partially-completed or
buggy setups. It is sometimes used as a last-ditch troubleshooting step, but
this is a very dangerous step to take on a customer machine and is discouraged.
MsiZap is NOT an uninstall, upgrade, or general-purpose cleanup tool.
If your setup exhibits behavior that you think requires MsiZap on customer
machines as a normal course of action, please use this newsgroup or other forums
to further explore the behavior. It is almost always possible to come up with a
robust solution that does not use MsiZap.
It is not possible to write your own MsiZap - MsiZap performs direct
manipulation of undocumented data stores and structures which should not be read
or changed directly by app setups.
-Chris Gouge
Microsoft Software Distribution Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.asp>
"Christopher" <temp9.removeme.@real-d.com.invalid> wrote in message
news:25D08AB6-64D7-4ED6...@microsoft.com...
Rich [Microsoft Windows Installer MVP]
"Chris Gouge [MSFT]" <cgo...@online.microsoft.com> spake the secret code
<uCaP$fa8DH...@TK2MSFTNGP09.phx.gbl> thusly:
>You should never need to redistribute MsiZap.
Agreed. If you need to redistribute MsiZap, its because you have a
problem with your install that you need to fix.
Zweitze de Vries
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q240116
--
Zweitze de Vries
Cyco Software
Rijswijk, The Netherlands
"Chris Gouge [MSFT]" <cgo...@online.microsoft.com> wrote in message
news:uCaP$fa8DH...@TK2MSFTNGP09.phx.gbl...
Dennis Bareis
On Sun, 15 Feb 2004 14:51:05 -0800, Rob
<anon...@discussions.microsoft.com> wrote:
>The original question arose from our need to remove an installation without going through the uninstall process. We don't want to go through the uninstall process because it uses custom actions that have undesirable side effects (eg files get deleted).
>
>Whats the recommended way of fixing something like this?
If it were me, I'd write a script that works out the cached MSI and
updates it to prevent whatever you don't want occuring and then run a
normal uninstall.