Project: Basic MSI I created a minor update through the patch design window and there were only four changes: a new registry entry, two new program files, and a file to be removed. When I build the patch, I get 0 errors and 0 warnings. When I run the patch, I get the error "Error 1328:Error applying patch file...." If I click ignore, the registry entry is added, the file I wanted to remove is gone, and one of the two files I wanted to update is updated. The other (the actual program executable) is unchanged. I can't figure out why this one file isn't updated, especially when I get 0 errors or warnings when I build the patch. Can anyone help? It seems like every time I try to build a patch, something goes wrong, and it's different every time. I can't believe how temperamental these patches are, it's ridiculous, and very frustrating. ... View more

Can someone please offer some guidance on Merge Modules? My C:\Program Files\Common Files folder has newer merge modules I need to include in my project. I'd rather not override the older ones, because I have multiple projects and they don't all need the newer ones. I copied the newer msm files to the C:\Program Files\InstallShield\2010\Modules\i386 folder and appended the file names with _new. I assumed they would show up in the Redistributables view, but I don't see them. Is what I'm trying to do even possible? My projects are basic MSI. Thanks for your help. Clark ... View more

I made several changes to a basic MSI project, created a patch, and when I try to install it over the previous installation, I get "error 2705 invalid table directory could not be linked as tree" I suspect this may have to do with Merge Modules. I removed a Merge Module and added a new one between updates. I noticed in the FeatureComponents table that Merge Modules are actually stored in components, even though they aren't shown in the component view. I know you can't remove components when building a patch, but do the same rules apply to Merge Modules? Thanks for your help. ... View more

I have a basic MSI project with three releases: a CD, a web release, and an uncompressed web release (which I use as a reference for patching). For the CD release, I compressed all the files so they fit onto the CD which they do (~350 MB). Everything works great until I try installing from the CD onto a computer that has the program already installed. The installer tells me it will perform an upgrade of the previous version, which I would expect, and then suddenly I'm prompted to insert Disk 1. If I copy the files from the CD to my hard drive and rerun, I am not prompted to insert a CD and the upgrade works fine. Does anyone know why I'm getting prompted to insert Disk 1 when I clearly have plenty of space on the CD? Thank you! Clark ... View more

To create a hybrid setup that will result in 32-bit and 64-bit packages, should I set the "64-Bit Component" property to "Yes" for all the 64-bit components, or leave it at "No"? The knowledge base article below doesn't clarify this. http://kb.acresso.com/selfservice/viewContent.do?externalID=Q107786 ... View more

I have a custom dialog in my InstallScript project and I added code to handle silent installs. I can create a response file fine, but when I try to run in silent mode using the response file, the install stops early. The log file makes it to the line "Lang=0009" and then stops. If the next line should mimic the response file, this means the line referring to the Dialog Order ([{f713B2Af-...}-DlgOrder]) would be next, but it's not getting written. Any ideas? Thanks! Clark ... View more

Can anyone offer some insight on the best way to version from beta to release? The issue is we use three version numbers when we release: 1.0.0. With each update, we increment the third element, 1.0.1. We just switched to a Basic MSI install project, and this all works fine. In beta mode, though, we have problems. This is because we use a fourth element. 1.0.0.0. Ideally, we would increment the fourth element in beta and when we release, we drop the fourth element and start incrementing the third. Since the fourth element is ignored in MSI patching, it means we can't test our patches until we release. We're considering this instead: beta1: 1.0.000 beta2: 1.0.001 release1: 1.0.0 release2: 1.0.1 Does anyone know if 1.0.0 is considered a later version than 1.0.001? Any help would be greatly appreciated. ... View more