However, if you have suggestions, feel free to submit them via
http://register.microsoft.com/mswish/suggestion.asp.
- Carolyn Napier
Microsoft Windows Installer 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.mspx>
"doc" <david.d...@gmail.com> wrote in message
news:1111593158.4...@z14g2000cwz.googlegroups.com...
I'll relay your request for a MsiZap "fake" mode though for future
consideration.
- Carolyn Napier
--
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.mspx>
"doc" <david.d...@gmail.com> wrote in message
news:1112035393....@o13g2000cwo.googlegroups.com...
I suspect you have a problem you are trying to solve, perhaps asking about the problem might help.
My 2 cents worth,
Dennis
Dennis Bareis [MVP] (den...@KillSpam.dennisbareis.id.au)
http://dennisbareis.id.au/index.htm
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://dennisbareis.id.au/makemsi.htm
Whenever my install starts doing things that are totally unexplainable
in QA I have them first run MsiZap with our product code and then try
to see if they can still recreate the problem. In the past (other jobs)
this hasn't been a problem. But since we've seen a few bugs where we've
had to EndTask on some msiexec processes it's not surprising that we're
seeing some bits of our install hanging out in the registry.