11-14-2005 12:58 PM
11-16-2005
01:25 PM
- last edited on
07-08-2025
02:39 PM
by
Content Cleaner
Brian,
You may find this page useful.
Briefly, setup.exe first determines if the target has the Windows Installer program present. It is present as part of Windows 2000 & XP, but may not be present if the target machine is ME, 98 or NT. The instmsi.exe and instmsiw.exe install the Windows installer program, if needed, onto 98/ME and NT machines respectively. Then your package can begin to be installed. So if you are only installing onto 2000/XP you can drop instmsi.exe and instmsiw.exe from the kit.
With good knowledge of and control over your target machines, you may also be able to create a smaller kit that assumes that the CVI run-time engine is installed, but watch out for other components (e.g DataSocket, ActiveX container support, etc.) that might be needed. The link above should give you good some clues for that.
My practice has been to live with either the full kit if it might be installed anywhere, and reduce it by 3MB by dropping instmsi and instmsiw, when I know that all imagineable target machines are 2000/XP. Beyond that the low cost of bandwidth and storage has not warranted further tweaking for me.
Hope this helps.
11-16-2005
01:44 PM
- last edited on
07-08-2025
02:39 PM
by
Content Cleaner