将Installshield 5.0安装程序重新打包为MSI并删除依赖项 [英] Repackaging Installshield 5.0 installer to MSI and removing dependencies
问题描述
我有一个安装包，用于安装我用于工作的映射程序.由于我现在必须升级到Windows 10，很遗憾，该程序无法安装，因为某些组件不再有效，并且在安装过程中部分崩溃了.
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.
前一段时间，安装程序包是使用Installshield 5.0制作的.
The installer package has been made with Installshield 5.0 some time ago.
安装的依赖项是 -dcom 95/98 -Visual C ++ -Microsoft数据访问组件
The dependencies installed are - dcom 95/98 - Visual C++ - Microsoft Data Access Components
我想删除视觉c ++和MDAC这两个依赖项，因为它们已经存在于我的Windows 10安装中.
I would like to remove the two dependencies visual c++ and MDAC as they are already present in my Windows 10 installation.
到目前为止，我已经将data1.cab与所有文件解包了.我还反编译了setup.ins脚本，因此它现在是带有所有安装命令的.rul文件.
So far I have unpackaged the data1.cab with all the files. I have also decompiled the setup.ins script so it is now a .rul file with all the install commands.
我是否可以直接删除安装命令并重新打包?
Is there a straight forward way for me to remove the install commands and repackage?
我应该寻找Flexera Install Studio的许可证并学习一些包装技巧吗??
Should I be looking a purchasing a license for Flexera Install Studio and learning some packaging skills!?
还是我会完全以错误的方式解决这个问题，我是否可以将变量传递给指定不安装依赖项的setup.exe文件?
Or am I going about this the wrong way completely and could I just pass through a variable to the setup.exe file that specifies not to install the dependencies?
要增加侮辱性伤害，我想让它进入可以在SCCM内静默安装的阶段！
To add insult to injury I would like to get this to the stage where it can be installed silently within SCCM!
无论如何，任何建议都会很棒-谢谢.
Anyway, any advice would be great - thanks.
推荐答案
虚拟机 :我会在虚拟机中运行这样的旧应用程序.既出于兼容性原因，又出于安全原因.我的理由是，此类旧应用程序可能存在安全性问题-即使兼容性团队正在努力防止这种情况.
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.
兼容模式 :我从未尝试过以兼容模式安装这样的安装程序(我有，但仅用于在虚拟机上重新打包捕获文件，而不是用于实际安装) .右键单击 setup.exe ，然后选择" Troubleshoot Compatibility "(或等效名称-没有英语操作系统).现在，使用建议的兼容性设置运行安装程序.您也可以右键单击，转到"属性"和"兼容性"以查看兼容性设置对话框.
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.exe and select "Troubleshoot Compatibility" (or equivalent - don't have an English OS). 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.
重新打包 :正如其他人提到的那样，您可以捕获安装并将其转换为MSI，然后可以通过SCCM以静默方式轻松分发该安装.对于简单的设置，此过程可能是微不足道的，但对于复杂的设置，则无需野餐.您必须具有相当多的Windows知识才能清理所得的捕获内容，因此它不是松散的大炮".建议您联系可以为您做打包的部署顾问. 应用程序重新打包工具 .
提取并打包文件 :对于某些设置，可以从旧的setup.exe中提取所有文件，并根据经验和检查自己打包.再次，没有野餐，但最终的安装程序可能非常简洁.这完全取决于设置中有多少自定义逻辑，而不仅仅是文件和文件夹副本以及注册表写入.再一次，我将工作发给经验丰富的顾问，以节省时间和金钱.
Extract and Package Files: For some setups it is possible to extract all files from an old setup.exe and package them yourself based on experience and inspection. Again, no picnic, but the resulting installer could be very neat. It all depends on how much custom logic is in the setup as opposed to just file and folder copy and registry writes. Again a job I would send to an experienced consultant to save time and money.
- Extract MSI from EXE
- How to run an installation in /silent mode with adjusted settings
这篇关于将Installshield 5.0安装程序重新打包为MSI并删除依赖项的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
