>Ed:
>
>Isn't there some utility somewhere that could be run to properly install and register msm - seperate from Installshield? This would solve my Innosetup script problem.
>
Any of the Windows Installer technology installers - Visual Studio Installer, Wise, etc. The problem is that the MSM not only contains one or more compressed files in it, it also contains information about versioning, dependency, deployment ordering, registration and more - you need to invoke the installer technology to make it work.
Basically, you're screwed by using Innosetup; you'd have to create a runtime install with VSI or InstallShield or the like, and then run the generated MSI on each target platform to find the combination of files, version dependencies, locations, order of registration, whether or not the install will require delayed copy for some or all components. Unless Inno tells you they have a way to work with the Windows Installer technology, you're SOL, since installation of components is a sensitive process - it's not like copying a few files for DOS to make it work right, whatever you might like to believe or are being told by people who in all likelihood haven't a clue about the process of installation of COM and system compoents, especially with OSes that will try to protect themselves and other apps by charging in like a bull in a china shop.
If Me, Win2K and XP are important to you, the use of MSMs is a well-supported and documented way to install things right, especially where the OS is protective of existing potentially version-sensitive component pieces. Looks likey're important and Inno doesn't support the Windows Installer technology, it's time to find a new installer.
>Mike
>
>
>>>Thanks, I think...
>>>
>>>I guess I'll use Installshield for now
>>
>>You have alternatives - Visual Studio Installer 1.1 is freely available for download from Microsoft at the sire listed, and you can uses the MSMs provided with IS LE with VSI (or any other Windows Installer based product). www,installsite.com has a number of useful MSMs you can download - it has MSMs for a number of ActiveX controls and third party product runtimes, like Crystal Reports 8 and Sheridan Widgets, and some remarkably good replacements for MS-provided MSMs - like a VFP6 SP5 MSM you can use with IS LE or VSI 1.1 to install the last version of the VFP6 runtime properly, side by side. It also has tutorial information on using some useful tools like the ORCA editor, comparisons or several of the major Windows Installer based products, and active, ongoing thread message bases related to installer issues.
>>
>>>
>>>Mike
>>>
>>>
>>>>>I'm using Innosetup to create a Installer routine. It seems to install, yet when I run the program it is missing the VFP runtime. I've tracked down an error in my install script that should solve the problem, but my question is what are the msm's and where should they be installed to? Right now I'm telling the installer to place them in
>>>>>DestDir: "{cf}\Microsoft Shared\Merge Modules"; CopyMode: normal
>>>>>where {cf} stands for Common Files. should then go into the c:\windows\system instead?
>>>>
>>>>You don't copy MSMs to install them - you need to invoke the Windows Installer to place them properly. Inno is not a Windows Installer based product.
>>>>
>>>>I'd suggest running out to
www.installsite.org and doing a little reading on the Windows Installer technology. Products that do not leverage the Windows Installer technology and are not in the managed code arena are in for a rude awakening. But don't believe me, I just clean up the debris after other people's installs crash and burn...
