Currently testing installation via -r :- Seems promising.. I should've thought of that ages ago Lol; I was first ; Ha ha! Sorry didn't see that at time of posting! Unless someone has lots of time on their hands, I doubt very much someone is going to create step-by-step instructions, with or without screenshots, especially since its already documented elsewhere, like here.
Microsoft Orca will probably be your best friend, unless you can get your hands on an old version of InstallTailor. Again, its documented online like here and here among other places. Once more, other apps are available and some may be trials. This is an interesting question. I've yet to run into an application that has multiple MSI's that are required for the install.
I don't have anything constructive to contribute here: You're on your own on this one. Get in the trenches, do some grunt work; work that elbow grease! I deployed the new package by GPO to one of my test computers. At first the package seems to install oke. But after some testing, i noticed that every time the application is started by a different user a msi repair starts. The package validation showed some ICE03 invalid format string , ICE38 component install in user profile and ICE64 directory is in user profile but is not listed in the removeFile table errors.
I checked this forum and found a post stating that this problem may be caused by a msi inside the installshield setup. I monitored the installation from the Installshield setup with procmon and noticed the following: -the installation starts by copying files from the setup file to the installdir and to the "common file" dir -when all files are in place, another setup is started which installs some files and starts a msi file to install some drivers -after that, a commandbox is open to execute "netsh exec" to set some firewall setting I have little experience with repackaging applications, and no experience with repackaging Installshield setup files.
I tried to extract the files from the setup, but was unsuccessful. So, any ideas how to handle this will be appreciated. TIA Asked 12 years ago views. Software Deployment Package Development. The installation of. Even that did not work.
I opened the converted. How to get these custom dialogs while converting. Custom dialogs are lost in repackaging. No aspect of any user interface can be preserved--instead, the repackaged output will use a default set of dialogs in its default editor template. The easiest way to handle this in editor is to use the Project Assistant under the 'Installation Interview' section.
Also, in repackaging, you'll want to be very careful that an installshield setup is not already in MSI format--check the list of running processes to see if Msiexec. Thanks Cary fro your reply. The msiexec. I first migrated the setup. After Migrating all the installscript logic and custom dialogs were available in I have an installation package that installs a mapping program I use for work. As I now have to upgrade to Windows 10, unfortunately the program won't install as some components are no longer valid and it crashes out part way through installation.
So far I have unpackaged the data1. I have also decompiled the setup. Should I be looking a purchasing a license for Flexera Install Studio and learning some packaging skills!? Or am I going about this the wrong way completely and could I just pass through a variable to the setup.
To add insult to injury I would like to get this to the stage where it can be installed silently within SCCM! If you have access to a full version of InstallShield, it can automatically convert that old installer of yours into the newer MSI format. Virtual Machine : I would run such a legacy application in a virtual machine. Both for compatibility reasons, but also for security reasons. Such old applications might have security issues is my reasoning - even if the compatibility teams work to prevent that.
Compatibility Mode : I have never tried to install such an installer in compatibility mode I have, but only for repackaging capture on a virtual, not for real install.
Right click the setup. Now run the installer with the suggested compatibility settings. You can also right click , go " Properties " and " Compatibility " to see a dialog of compatibility settings.
0コメント