Hi Everyone,

I'm new to this repackaging stuff so please go easy [:)]

I have had some success in creating packages but am currently having problems repackaging Macromedia Dreamweaver 8. I am using the repacking wizard from Admin Studio 6 Pro Edition mapped from a network drive.

The package creates the MSI (with some ICE33 warnings) and I can install it. But when I run it I get an error message

Unable to Locate Component
The application failed to start because MSVCR71.dll was not found. Re-installing the application may fix this problem.

When I do a search for this file it is found in the following places

C:\Packages\PROGRAMFILESFOLDER\Macromedia\Dreamweaver 8
C:\Packages\PROGRAMFILESFOLDER\Macromedia\Extension Manager

I'm using Win XP SP2.

I hope someone can help

Thanks in advance

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Try by copying this file to your windows system32 folder. If it works, change the target of the file in your MSI.
Answered 11/16/2005 by: quitaxe
Yellow Belt

Please log in to comment
Hi Shaun:

I think u need to add this dll to ur package as this is a merge module. There is an option to add merge modules in wise but i dont know how u have to go about it in Admin Studio 6 Pro Edition.
Answered 11/16/2005 by: akhlaque
Orange Senior Belt

Please log in to comment
Thanks to both of you.

I have discovered the 3 files that are not copied to C:\Program Files\Macromedia\Dreamweaver 8

They are:


They exist in the C:\Packages\PROGRAMFILESFOLDER\Macromedia\Dreamweaver 8 when the Package is created. Why are they not being copied to the correct palce when the MSI is run. If I copy them over manually Dreamweaver runs perfectly.

Thanks again

Answered 11/16/2005 by: ShaunT
Senior Yellow Belt

Please log in to comment
Not sure if this will help you with the Install Shield piece, I used this to package with WISE but everything worked fine. I just took the lines I needed and called them from a .exe wrapper.


Lots of good info in there on how to get this working, hope this helps.

Answered 11/16/2005 by: Foleymon
Orange Senior Belt

Please log in to comment
Hi ShaunT,
The three files u have mentioned are common files and these will be used by other application as well. So if u add the dll manually, this will replace the files which are already existing in the target machine at the time of installation and may affect other application using these files. For solving out this problem, we have the idea of merge module. It is simple. Create a new MSM, u can look into installshield help file, how to create a mergemodule, give the corresponding directory loacations and complie the msm to create the merge module. Add this merge module by adding it from the Re- distributables option in Install shield. When u complie after that, u'll have the dll added to ur msi.
Try out this and revert if u need more help on this

Answered 11/30/2005 by: Freewords
Senior Yellow Belt

Please log in to comment
U can also try to isolate those files in wise. Then it will place the dlls in the program files dirs and work from there
Answered 11/30/2005 by: Gastro
Senior Yellow Belt

Please log in to comment