SET ICPP_COMPILER11=D:\Programme\IntelCompiler\Intel\Compiler\11.0\061\cpp
SET PATH=%ICPP_COMPILER11%\Bin\ia32;%PATH%
This is the entry for the base path of the tool chain and an additional path to be setup.
SET INTEL_LICENSE_FILE=C:\Program Files (x86)\Common Files\Intel\Licenses
This you need to set using the envvars plugin
SET LIB=%ICPP_COMPILER11%\Lib\ia32;%LIB%
SET INCLUDE=%ICPP_COMPILER11%\Include;%INCLUDE%
This you need to put into the toolchain compiler and linker options.
1. All changes from the MS batch file to the path variables are set to the second position. If I remove the MS batch file, I get a message from the Watcom Linker. So the Intel Compiler uses the MS Linker?
Watcom linker? So this compiler is in the path, too? This probably leads to conflicts. Besides: Intel may use several VS tools but most important the libs
and include files of the platformm SDK. That's why the vcvars32.bat is called IIRC.
2. The path to the bin files is correct within CodeBlocks. If I set a wrong path, CodeClocks will show an err msg.
Hopefully the others are, too (see above).
3. Lib path and include paths from Codeblocks were pointing to the same location as within the batch file.
OK...
I think I must take a closer look to the vsvars32.bat file from the Visual Studio.
Yes, because these path's are needed in the compiler and linker settings at least, too (not to forget resource compiler).
You may want to use the verbose switch of the Intel compiler... IIRC there was such. That way (and also if you enabled to log the full command line in the compiler settings) you might get a more descriptive error message.
BTW: Oce you've finished I would love to see an update to the WiKi article (if required). ;-)