如何分发 VB6 引导文件？
我正在将 VB6 安装程序移植到 NSIS。查看 LST 文件，有一个用于引导文件的部分：
[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,..........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,......
[email protected],$(WinSysPathSysFile),$(TLBRegister),...........
[email protected],$(WinSysPathSysFile),,,...........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),.........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,...........
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),.........
另一个用于 setup1 文件
[Setup1 Files]
[email protected],$(AppPath).......
[email protected],$(AppPath),.......
在另一篇文章中，我收到有关分发 wshom.ocx 文件（引导文件）的警告，内容如下：
“wshom.ocx 不应该以这种方式分发。在 Windows 的低级版本这可能会成功，但会破坏 WSH 以及系统上的其他脚本。不要像这样重新发布这个库 这。 ”
所以，我想知道分发引导文件是否有任何考虑因素？我是否应该分发它们？
谢谢
I am porting my VB6 installer to NSIS. Looking at the LST file, there is a section for bootstrapping files:
[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,..........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,......
[email protected],$(WinSysPathSysFile),$(TLBRegister),...........
[email protected],$(WinSysPathSysFile),,,...........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),.........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,........
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,...........
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),.........
and another for setup1 files
[Setup1 Files]
[email protected],$(AppPath).......
[email protected],$(AppPath),.......
In another post, I was warned about distributing the wshom.ocx file (bootstrapping file), saying:
"That wshom.ocx is not meant to be distributed in this way. On
downlevel versions of Windows this might succeed, only to break WSH
and other scripting on the system. Do not redist this library like
this. "
So, I was wondering if there are any considerations for distributing bootstrapping files? should I even distribute them?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
此警告与您正在安装的其他一些文件更为相关。 Windows 仍然可以使用 borked 脚本解释器运行，但当您不小心使用 oleaut32.dll 或 asyncfilt.dll 时，它就无法生存。这就是为什么这些文件不会被糟糕的安装程序意外覆盖，Windows 文件系统保护功能会立即恢复正确的文件。
您实际在需要安装这些文件的计算机上运行安装程序的可能性为零。 Windows 95 已经消失了。如果这样的机器确实存在，那么您安装错误版本的可能性非常高。这是让它摆脱长期痛苦的一种方法。
只要您的安装程序采取了最低限度的对策，通过简单的版本检查来避免用旧副本替换新的 DLL，那么就不会出错。别担心。请考虑一下，是时候停止依赖这些古老的工具了。
This warning is much more relevant to some of the other files you are installing. Windows can still run with a borked script interpreter but it can't survive when you accidentally oleaut32.dll or asyncfilt.dll. Which for one is why these files are protected from accidental overwriting by crummy installers, the Windows file system protection feature puts the correct one back immediately.
The odds that you'll actually run your installer on a machine that requires these files to be installed are zero. Windows 95 is gone. The odds that you'll install the wrong version of them if such a borked machine actually exists are very high. Which is one way to put it out of its prolonged misery.
As long as your installer has minimum counter measures in place to avoid replacing new DLLs with old copies with a simple version check then this isn't going to go wrong. Don't worry about it. Do consider that it is time that you stop relying on such ancient tools.