Condor Installer Notes

From Ben's Writing

CRT Merge Modules

Instead of using the CRT redistributable installer that comes with Visual Studio 2005 it is possible to use MSI merge modules when constructing a new installer. Visual Studio 2005 also provides these; they can be found in the following directory:

C:\Program Files\Common Files\Merge Modules

How yo use them is use them is highly dependant on the installer software you are using. If you are using WIX, then you can use the following syntax:

<Merge Id="CRT" Language="0" DiskId="1"
       src="C:\Program Files\Common Files\Merge Modules\Microsoft_VC80_CRT_x86.msm" />
<Merge Id="CRT" Language="0" DiskId="1"
       src="C:\Program Files\Common Files\Merge Modules\policy_8_0_Microsoft_VC80_CRT_x86.msm" />

Or, if you are using MakeMSI, then the following syntax may be of insterest:

#(
<$MergeModule "C:\Program Files\Common Files\Merge Modules\Microsoft_VC80_CRT_x86.msm" 
              language="0" 
              IgnoreErrors=^InstallExecuteSequence:AllocateRegistrySpace^>
#)
#(
<$MergeModule "C:\Program Files\Common Files\Merge Modules\policy_8_0_Microsoft_VC80_CRT_x86.msm"
              language="0" 
              IgnoreErrors=^InstallExecuteSequence:AllocateRegistrySpace \
              InstallExecuteSequence:SxsInstallCA InstallExecuteSequence:SxsUninstallCA^>
#)

We opt use merge modules because running the CRT redistributable executable fails on account that it detects another installer running — namely, ours. We ignore the errors listed above because they are only from the validation table, so they are not essential to the proper functioning of the merge module.

Windows 2000

If you receive the message:

The procedure entry point getnameinfo could not be located in the dynamic link libary WS2_32.dll.

You will need to update Windows 2000. This DLL is part of the Winsock suite and is required for Condor to function properly. It turns out that if Condor was built on Vista, then it is not possible to run the resulting binary on Windows 2000. This is because the Platform SDKs that are available for Vista only allow one to target for as far back as XP and Windows Server 2003.