If you wish to install the redistributable package "silently", so that no output is presented to the user, run the executable with the following options added to the command line:
>> composer_update3_redist_XXXX.exe /S /V/qn

Links to the redistributable packages

References

FAQ Intel® Parallel Composer Redistributable Package

Old Solution: The user can solve this problem by setting TBB paths manually in Visual Studio* - "Tools\Options\Projects and Solutions\VC++ Directories\Include files", and "Tools\Options\Projects and Solutions\VC++ Directories\Library files". For example, the user inserts new item "C:\Program Files\Intel\Parallel\Studio\Composer\tbb\include", and "C:\Program Files\Intel\Parallel Studio\Composer\tbb\ia32\vc9\lib" (for Microsoft* Visual Studio* 2008) respectively. The problem has gone.

This change will effect in all VC++ projects, we changed VS environments.

New Solution: The user also can use Parallel Composer's new feature - "Project\Intel Parallel Composer\Select Build Components" to check on "Use TBB" and click "Apply" button. After doing this, the user can verify Paths enabled in project's "Property Pages", See new items in "C/C++\General\Additional Include Directories", and "Linker\Additional Library Directories".

Note that this change effects on your project only. The benefit is that the user doesn't need to find exact TBB installed directories, Parallel Composer does it for you!   

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Q: Could you comment on Linux* usage of these tools?
A:  Intel® Parallel Studio is mainly targeted to the Windows* C/C++ developers. Intel also offers other software solutions to support Linux, please find more information on other operating systems support at Intel Software Development Product website (including Intel® Integrated Performance Primitives product)

Q: What are the licensing terms for using Intel® Integrated Performance Primitive (Intel® IPP) in commercial products? What about demo / prototype products?
A: Please refer to Intel Software Products end user license agreement document at http://software.intel.com/en-us/articles/intel-software-development-products-license-agreement/.

Also, licensing policy questions are documented in Intel IPP knowledge Base at, http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-faq/

Free code samples/demo are located at http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-samples-license-agreement/

Q: Novice question: With all the efficiency (over handwritten C/C code) that the Intel IPP brings in does it close-in to the performance of image processing and allied ASICs or is it that ASICs are in a totally different level of solution space?
A: When you call Intel IPP , you do not need to deal with ASIC level as the Intel IPP libraries are internally implemented in ASIC, it is transparent for users.

Q: Can you control when Intel IPP will use threading?
A: Yes, you can control threading in Intel IPP by calling ippSetNumThreads() function. Check more on Intel IPP threading FAQs at: http://software.intel.com/en-us/articles/intel-integrated-performance-primitives-intel-ipp-threading-openmp-faq/

Q: In the H.264 example showing performance improvement from 1 thread to 8 threads, is this data on single core? OR multiple threads mean multiple cores in the underlying hardware?
A: Multiple threads on multi core machine.

Q: Can you tell Intel® Parallel Inspector to ignore the system DLLs? They probably don't contain threading errors, wouldn't you expect?
A: Yes, but most are already ignored by default.  Suppressions can be used to suppress any errors reported in any DLL, source file, or function.  See the Defining Private Suppression Rules topic in the Parallel Inspector help for more information.

Q: Can you comment on the compatibility of OpenMP* with Windows Threads?
A: The short answer is that you can create your own threads and that won't interfere with the threads created by the OpenMP runtime. It's OK to mix.

Q: I have tried running Intel® Parallel Amplifier on an interactive Embedded system and it quickly fails to start. What I would like to do is profile execution for a period of time and then get an analysis. Any tips for how to work with this type of application?
A: You can read this article at: http://software.intel.com/en-us/articles/how-to-analyze-a-portion-of-your-application/ for more reference.  Or share your thoughts or questions on embedded system at Intel Parallel Studio Forum at http://software.intel.com/en-us/forums/intel-parallel-studio/.

Q: Can I use Intel® Fortran Compiler with Intel Parallel Studio?
A:  Intel® Parallel Studio is designed and targeted and tested for C++ software. The analysis is based on the binary not the source, how well it works with Fortran may vary. Please be aware that in addition to Intel Parallel Studio product, Intel offers a HPC line of products that offer full support for Fortran.  This includes the Intel® Fortran compiler of course, but also Intel® VTune^TM Performance Analyzer and Intel® Thread Checker.  The Intel® Math Kernel Library also includes full Fortran interfaces to BLAS, LAPACK, FFT and other common numerical algorithms.  Most Fortran developers use the HPC line of Intel products. You may find other Intel software tools for Fortran at Intel® Compiler Professional Edition

Q: Can Intel Parallel Studio help us detect cache thrashing? Which is one of the bottlenecks of multi-core programming?
A: No. Intel VTune Performance Analyzer can monitor processor specific events and detect cache misses.  You may find Intel VTune Performance Analyzer better suited to this type of analysis.

Q: What about cross-compiling and Mac OSX*/Linux* support?
A: Intel Compilers are also available for Linux and Mac OS X. Intel Linux and Mac compilers are source and binary compatible with gcc and share the backend optimizer support including OpenMP. You will not be able to cross-compile between OSs. Please see intel.com/software/products for additional information.

Q: Can I use Intel Parallel Studio to compile with Microsoft* Foundation Classes (MFC) based applications?
A: Yes. Intel Parallel Composer is compatible with Microsoft Visual Studio native. So as long as the MFC does not contain code with attributes or common language runtime (CLR), you can use Parallel Studio.

Q: Does the Intel Parallel Studio encompass all the usage of Intel VTune Performance Analyzer? Can Intel Parallel Studio replace Intel VTune Performance Analyzer usage?
A: Check this article for more details

Q: Sure your product target is Intel Platform how about other brand CPUs. When we use your product it will also work in other CPUs without problem and same performance?
A: Intel® Parallel Studio runs on platforms with "an IA-32 or Intel® 64 architecture processor supporting the Intel® Streaming SIMD Extensions 2 (Intel® SSE2) instructions (Intel® Pentium 4 processor or later, or compatible non-Intel processor

Q: How long does it take to finish the amplifier and inspector analysis on a large application (32 MB)? I have been running one for hours, and it is still going.
A: These should be separated.  Intel Parallel Inspector will be long and depending on the analysis time you select it could be 50X slower.  Intel Parallel Amplifier should not be as intrusive.  If you are seeing orders of magnitude slower response times with Intel Parallel Amplifier please let us know about it.  

Q: What happens if you have an application with languages other than C++? Can you still analyze it with Parallel Studio? What if a deadlock happens in your VB code, for example?
A: Parallel Studio is focused on C/C at this time (it works with C code), so the thread checking part called Parallel Inspector will not help for VB code.

Q: Some operating systems like AIX* allow application developers to have threads to be rescheduled on the same processor -- does this tool presently (or a later version may) capture processor cache hits/misses?
A: Processor architectural information is captured by our HPC product line - Intel VTune Performance Analyzer can capture information about processor events such as cache misses and is the recommended product for looking at processor events.

Q: Will there be command line version of these tools?
A: Intel Parallel Composer does provide command line support.

A: The "Serialize Parallel Region" option of the Intel(R) Parallel Debugger extensions temporarily sets the OpenMP* omp_set_num_threads() environment variable to 1, thus forcing single threaded execution even on a multi-core system. This temporary change applies to the next parallel block or parallel region in your code relative to the current EIP or program counter location.

Thus, yes - the "Serialize Parallel Region" option can be applied to a specific parallal region of your choice. You can do so by setting a breakpoint just before you enter the parallel region you would like to have executed as a single serial thread and then selecting the serialization option from the Intel(R) Parallel Debugger Extension menu inside Microsoft* Visual Studio. 

A: Most of the Parallel Debugger Extension features like Thread Data Sharing Event Detection, Function Reentrancy Detection amd Serialize Parallel Region, rely on instrumentation of debug information and on the OpenMP* library. As such these features are currently only available for OpenMP* based threading. The one feature that is independent of the threading model used are the enhanced and highly configurable SSE register windows.

A: The debug symbol information instrumentation done by the Intel(R) C++ Compiler when the /debug:parallel option is set along with /Zi is different from the code instrumentations used by the Intel(R) Parallel Inspector for it's instrumentation assisted operating mode.
The Intel(R) Parallel Debugger Extensions do not rely on executable code instrumentation, but rather on instrumentation of the symbol information used for debugging. As such the Parallel Debugger Extensions cannot statically anaylze the execution flow, but rely on a detectable event that may be of interest happening at real time during a debug session. At the same time, because only the debug information is instrumented there should only be very minimal performance impact on the execuatble if run outside the Microsoft* Visual Studio Debugger.

A: Yes, all enhanced parallelism features of the Intel(R) Parallel Debugger Extensions rely on OpenMP* based threading, except for the SSE register windows.

A: Yes, the Parallel Debugger Extensions rely on debug info instrumentation added with the Intel(R) Compiler option /debug:parallel in conjunction with /Qopenmp. Therefore the full capabilities of the Intel(R) Parallel Debugger Extensions are only available when used with the Intel(R) Compiler.

A: In principle yes, BUT this would require rebuilding and relinking the Intel(R) IPP with symbol information and /debug:parallel. Since you are most likely taking the primitives from prebuilt libraries that you link into your project, this not really a supported usage model, although it may work in some cases depending on how the call to the Intel(R) IPP function of your choice is embedded in the rest of your application.
The short answer thus is really no, with some exceptions.

A: The OpenMP* library can be linked in statically or dynamically into your application build for the use of the Intel(R) Parallel Debugger Extension. The OpenMP* library used by the Intel(R) C++ Compiler is really a standard OpenMP* library. However, there is the dependency on the debug information instrumentation using /debug:parallel. This instrumentation has only been tested and is only expected to work with the OpenMP* libraries provided with the Intel(R) Compiler.

A: The SSE Register Window allows you to group the display of the register contents and display said contents in the exact way that you are using it in your parallelized loops, your structured arrays or other parallel structures. By doing this the highly configurable SSE Register Window provides you with the link between your data as it is used in your application and the way this very same data is actually stored and processed in the SSE registers.

This can be quite valuable for understanding more complex heavily parallel multimedia or graphics code for instants.

This feature does not rely on any instrumentation or any specific threading implementation. It is independent of OpenMP*.