In some rare cases the local computer's environment may interfere with building Condor: most of the time this is due to an incompatibility in SDK versions. By default, newer versions of *Visual Studio* install the, at the time, up-to-date SDKs. This is usually found in the *%ProgramFiles%\Microsoft SDKs* folder. If there is a problem when running the build scripts, this is likely the culprit. It also contains the same configuring scripts that the *Platform SDKs* do; however, they do not support Windows 2000. A sure sign that this is incorrectly configured is easy to diagnose: the scripts have the name, but take different command-line options, so you will see an error after running =set_env.bat=. You can remedy this by renaming *%ProgramFiles%\Microsoft SDKs* to something else while developing or compiling the Condor software. This will not be a problem when Condor drops support for *Windows 2000*. -Put shortly, if you do not see, the following two lines in the build output: +Put shortly, if you do not see the following two lines in the build output: Setting environment for using Microsoft Visual Studio 2008 x86 tools. Targeting Windows 2000 and IE 5.0 RETAIL
