Broken KeyPath - Self Repair
Posted 29 July 2003 - 19:24
Here is the problem ... It seems on some systems that it is attempting to apply the total cost of installation to the C:\ during the repair. Does anyone know what action this is? Maybe I could just bypass this costing during the repair install.
Some users have minimal space on their C:\ (our install requires 80 MB during a successful install for system files, etc.) so they install our product and the majority of it's files to an alternate drive.
For example, we have a user with 200 MB free on his C:\ drive. After installing the update and starting the application (to trigger the self repair), the self repair is indicating he need 600+MB.
Does anyone understand what I'm trying to say or am I just rambling. I hope someone can help me out.
Thanks in advance!!
Posted 29 July 2003 - 21:13
How can I create a log during the self repair? The installation has actually completed and it only repairs itself when the user attempts to start our application.
Posted 30 July 2003 - 10:21
Use the registry entry method to globally enable logging for all MSI setups, including repairs. See http://www.msifaq.com/a/1022.htm
Posted 30 July 2003 - 14:06
Here's what I was thinking. Find out which action is actually calculating the cost. Insert it again later in the sequence and condition it to calculate if the install type is that of self repair. On the original cost calculation, condition this to run only if NOT a self repair installation. This is just a thought because I don't actually know how the self repair/sequencing works.
I might be in BIG trouble here.
Posted 30 July 2003 - 18:27
Sometimes MSI doesn't preserve the value of INSTALLDIR, so it falls back to the default value upon repair.
Posted 31 July 2003 - 15:16
I was wondering if I can skip whatever costing action calculates to the error during this type of self repair install. In other words, can I condition whatever action is doing this to not run if the install type is self repair?
Posted 31 July 2003 - 15:40
Posted 31 July 2003 - 18:39
I simply installed a component to INSTALLDIR and my problem I solved.
Thank you SOOOOOOO much for the info!