Microsoft Installer Bug? (Error 1327. Invalid Path…)
I’m still not sure if this is another Microsoft bug, or if it’s the fault of the developer who setup the installer. But first…
I’ve built installers before but overall am not very knowledgeable on the topic. I’m probably not using the correct terminology and I may have made other mistakes, but the core question here is sound. Back to to the question at hand…
This forum post claims it is Microsoft’s fault or the developer’s fault. (I think)
There is official documentation from InstallShield regarding the problem.
My understanding of the problem is that the MSI (Microsoft Installer) engine (by default) verifies all the Personal paths in the registry, even if they’re not needed. For example, “My Music” and “My Pictures” are personal directories who’s existence would be verified but obviously aren’t needed. This turns into a real problem when you’re like me and have these non-essential directories re-located on an external or network drive. Basically, I can’t install or uninstall without my external drive plugged in.
What I don’t understand (based on those links and the several others I found using Google) is if the MSI engine will try and verify those paths regardless, or if it only does so by default and that it’s possible to only verify the necessary paths when configured properly?
Does anybody know if this is a bug, or if it’s the installer builder’s fault?
This entry was posted on Friday, January 25th, 2008 at 7:26 pm and is filed under Development. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
