Intel Software Network articles Feed http://software.intel.com/en-us/articles/intel-visual-fortran-compiler-for-windows-kb/type/installation/ en-us How do I uninstall Microsoft Visual Studio 2008 Shell?
Microsoft Visual Studio 2008* Shell – ENU
Microsoft Visual Studio 2010 Files for Intel Visual Fortran (if present)
Microsoft Visual Studio 2008 Remote Debugger - ENU 

This is in addition to uninstalling the Intel(R) Visual Fortran Compiler which may be entitled a title similar to: "Intel Composer XE 2011 Update 1 for Windows"
]]> http://software.intel.com/en-us/articles/how-do-i-uninstall-microsoft-visual-studio-2008-shell/ Wed, 16 Nov 2011 00:00:00 -0800 http://software.intel.com/en-us/articles/how-do-i-uninstall-microsoft-visual-studio-2008-shell/#comments http://software.intel.com/en-us/articles/how-do-i-uninstall-microsoft-visual-studio-2008-shell/ Intel® Visual Fortran Compiler for Windows* Knowledge Base Resolving link errors after installing Microsoft Visual Basic 2010 Express on a system where Intel(R) Visual Fortran Composer XE is installed
Problem : I have been using Visual Fortran Composer XE for several weeks without problems. Recently, I installed Microsoft Visual Basic 2010 Express (free download), and now I get the LNK1104 error for uuid.lib. If I uninstall Visual Basic 2010 Express I do not get the link error.


Environment : Windows 7, Intel(R)64, Visual Studio 2008


Root Cause : Visual Basic 2010 Express will install a new Windows SDK 7.0 probably at c:\Program Files(x86)\Microsoft SDKs\Windows\v7.0A. This Windows SDK is incomplete, not containing the lib folder. It also updated registration key of HKEY_LOCAL_MACHINE->Microsoft->Microsoft SDKs->Windows->"CurrentInstallFolder" to reference to this new Windows SDK folder. The Visual Studio development environment will use this registration key to set "WindowsSdkDir" which is used in Visual Fortran library list.


Resolution : There are two possible solutions:
1.Download and install the complete Microsoft Windows SDK manually.

2. Add your original SDK path to the Fortran project library path list:
E.g., my original SDK path before I install Visual Studio express can be got by opening a Fortran Composer XE command prompt, and run:
> echo %WindowsSDKDir
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\PlatformSDK

In Visual Studio, select Tools > Options > Intel Visual Fortran > Compilers.
- For IA32, add "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\PlatformSDK\Lib" to library list.
- For Intel 64, add "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\PlatformSDK\Lib\AMD64" to the library list.
]]> http://software.intel.com/en-us/articles/lnk1104-cannot-open-file-uuidlib/ Fri, 04 Mar 2011 09:00:00 -0800 http://software.intel.com/en-us/articles/lnk1104-cannot-open-file-uuidlib/#comments http://software.intel.com/en-us/articles/lnk1104-cannot-open-file-uuidlib/ Intel Software Network communities Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel Software Network communities Intel Compilers for Windows Silent Installation Guides The Intel(R) Composer XE 2011 for Windows* and Intel Parallel Composer 2011 installation support both Setup Wizard mode installation and silent installation.

1. Simply run the downloaded package, the installation will proceed in the Setup Wizard mode.
2. To proceed in silent installation mode, use following: 

  1. Run the download package and it will ask for a directory for extracting files like "c:\temp\IntelC_setup\". After extracting, cancel the installation.
  2. Open a command window, run following command:
    >> c:\temp\IntelC_setup\setup /?
  3. The above command displays the command line flags for silent installation and describes below:

    4. Usage: Setup.exe [<command>] [arguments...]

    If no command is specified, the installation program will proceed in the Setup Wizard mode.
    If any command is specified, the installation program will proceed in non-interactive (silent) mode.

    Commands
    --------------------------------------------------------
    install - install the product
    remove - remove the product
    repair - repair existing installation
    modify - modify existing installation
    toc - table of contents

    Mandatory arguments for silent installation
    --------------------------------------------------------
    --output=<file> [command: all]
    Specify a file to which the output will be redirected. This option cannot be omitted.

    --eula={accept|reject}    [command: install]
    Specify if you accept or reject the End User License Agreement (EULA). You should explicitly accept EULA to proceed with the installation.

    Optional arguments for silent installation
    --------------------------------------------------------
    --installdir=<installdir> [command: install]
    Specify the installation directory.

    --license=<license> [command: install]
    Activate product via license file(s). You can specify either file or folder. If folder is specified, installer will

    seek for *.lic files. Many locations may be pointed by specifying this options many times. Do not use this option with the option '--s/n'.

    --sn=<s/n> [command: install]
    Activate product via serial number. The internet connection is required in this case. Do not use this option with the option '--license'.

    --update={no|always} [command: install]
    Define if the Installer should force removal of the currently installed version of the product prior to installing the version in this package. The options are: 'no' ?do not remove the currently installed version; and if any version is found, end the installation. 'always' ?remove the currently installed version (if any) and proceed with the installation. The default value is 'no'

    --force-remove [command: remove]
    Force Installer to remove any currently installed version of the product. If this option is not specified, installer will remove only version of the product installed with this package.

    --log=<log file> [command: all]
    Specify a location for a LOG file. Log file is used for debug purposes. Support Engineer can ask you to send this file.

    Comments on activation:
    You can activate the product by either specifying license file (--license) or by specifying serial number (--sn). If don't specify any of this options the Installer simply checks if the product is already activated.

    Arguments for Setup Wizard mode
    --------------------------------------------------------

    In the Setup Wizard mode the Installer asks you all the necessary questions via dialogs.
    The following options allow specifying answers from the command line to facilitate the installation.

    --sn=<s/n>
    Specify serial number.

    --installdir=<installdir>
    Specify the install location.

  4. Example command for silent installation:
    >> setup install --output=c:\temp\installout.txt --eula=accept --license=c:\temp\intelc_setup\mylicense.lic
    >> setup install --output=c:\temp\installout.txt --eula=accept --sn=xxxxxxxxx 
]]> http://software.intel.com/en-us/articles/intel-compilers-for-windows-silent-installation-guides/ Sun, 27 Feb 2011 21:00:00 -0800 http://software.intel.com/en-us/articles/intel-compilers-for-windows-silent-installation-guides/#comments http://software.intel.com/en-us/articles/intel-compilers-for-windows-silent-installation-guides/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Overinstalls of Intel(R) Visual Fortran 2011 on non-English Operating Systems can cause errors openning projects
Reference Number : DPD200162396


Version : Intel(R) Visual Fortran Composer XE 2011 First Release and Update 1


Product : Intel(R) Visual Fortran Composer XE 2011



Operating System : Windows


Problem Description : When installing Intel(R) Visual Fortran Composer XE 2011 over an older compiler (e.g. 11.1) on a non-English OS some needed directories are removed.




Resolution Status : Install the Update 2 compiler which has this problem resovled.




[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.]
]]> http://software.intel.com/en-us/articles/overinstalls-of-intelr-visual-fortran-2011-on-non-english-operating-systems-can-cause-errors-openning-projects/ Fri, 04 Feb 2011 00:00:00 -0800 http://software.intel.com/en-us/articles/overinstalls-of-intelr-visual-fortran-2011-on-non-english-operating-systems-can-cause-errors-openning-projects/#comments http://software.intel.com/en-us/articles/overinstalls-of-intelr-visual-fortran-2011-on-non-english-operating-systems-can-cause-errors-openning-projects/ Intel® Visual Fortran Compiler for Windows* Knowledge Base Fail to install the Intel(R) C++ or Visual Fortran Composer XE 2011 on system with Visual Studio 2005
Reference Number : DPD200161613, DPD200162865


Version : 2011


Product : Intel C++ or Visual Fortran Composer XE for Windows, Version 2011, Build: Initial Release (2011.0.104), or any other products contains Intel Parallel Debugger Extension


Operating System : Windows XP*, Windows 7*, Windows Server 2003*, Windows Server 2008*


Problem Description :

This issue happens in some environment only. But the symptoms and work-arounds are below.

When you try to install new Intel C++ or Visual Fortran Composer XE for Windows, and select to integrate them into Visual Studio 2005 which is already installed on your system, you will see the error message:

"Microsoft Visual Studio 2005 software is currently running. Installation cannot continue while MS VS 2005 software is running. Suggestion: Exit MS VS .NET 2005 software and run the installation again."

You have to press OK to continue, will see another error message:

"Error while installing the package 'C:\Program Files\Intel\Download\w_fcompxe_ie32_2011.0.104\Installs\1033\w_cproidb_vs_p_12.0.104\w_cproidb_vs_p_12.0.104.msi' Fatal error during installation.".

Then the installer will rollback and remove all componets installed on your system.

We have identified that the root cause of this problem is caused by installation failure of “Intel Parallel Debugger Extension” component (which will be installed by default with "Full Installation" type).


Resolution Status :

Compiler engineering team is working to fix this problem in future release.

The work around is to select “Custom Install” and deselect the “Intel Parallel Debugger” component while the installer ask you to select components to install. Then the installation will finish successfully without any problem.

Update: The update 1 of Intel Composer XE for Windows (package 2011.1.127) should have fixed this issue.   Please note that the final installation steps may take some time, please wait till the installation "Finish" dialog appears that shows the completion of the installation. 


[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.]
]]> http://software.intel.com/en-us/articles/fail-to-install-composer-xe-2011-on-system-with-visual-studio-2005/ Thu, 11 Nov 2010 08:00:00 -0800 http://software.intel.com/en-us/articles/fail-to-install-composer-xe-2011-on-system-with-visual-studio-2005/#comments http://software.intel.com/en-us/articles/fail-to-install-composer-xe-2011-on-system-with-visual-studio-2005/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel Fortran Composer XE 2011 Release Notes This page provides the current Installation Guide and Release Notes for the Intel® Fortran Composer XE 2011 products. All files are in PDF format - Adobe Reader* (or compatible) required.

For version 11.1, please see Intel Fortran Compiler 11.1 Release Notes

To get product updates, log in to the Intel® Software Development Products Registration Center.

For questions or technical support, visit Intel® Software Developer Support


Update 8 - December 2011
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 7 - October 2011
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 6 - September 2011
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 5 - July 2011
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 4 - May 2011
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 3 - March 2011
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 2 - January 2011
Intel ® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Update 1 - December 2010
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

Initial Product Release - November 2010
Intel® Fortran Composer XE 2011 for Linux*

Intel® Fortran Composer XE 2011 for Mac OS X*

Intel® Visual Fortran Composer XE 2011 for Windows*

]]> http://software.intel.com/en-us/articles/intel-fortran-composer-xe-2011-release-notes/ Thu, 28 Oct 2010 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-fortran-composer-xe-2011-release-notes/#comments http://software.intel.com/en-us/articles/intel-fortran-composer-xe-2011-release-notes/ Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Checklist for Installation and Troubleshooting Intel® FLEXlm* License Manager

1. Download the latest Intel FLEXlm* License Manager user guide. Click here to download the user guide.

Steps to complete FOR THE LICENSE HOST SERVER SYSTEM(S)

2. Download the Intel® FLEXlm* license server that best matches your license host server OS. Click here to download license servers.

3. Verify your license host server machine’s host name and host id. If you are using three redundant license host server systems, verify the host name and host id for all three machines. Click here for more information. 

4. Verify your floating licenses are registered with the correct host name and host id specified. If you are using three redundant license host server systems, verify all three host names and host ids are specified for each floating license.
You can find this information by logging  into the Intel Registration Center and checking your floating license information.

5. If any of your floating licenses have incorrect or out-of-date host name or host id information, follow the instructions in this user guide to correct the information in the floating license(s), and obtain updated license file(s). Click here for more information.

6. If you wish to combine your floating license files into one file, follow the instructions in section 4.3 of the Intel(R) FLEXlm* License Manager user guide, or follow the instructions here.

7. Verify that all the individual floating license files or the combined license file resides on your license host server system. Ensure there are no Single User, evaluation, or Beta licenses residing in the flexlm license directory on your license host server system.

On Linux*: /opt/intel/flexlm/
On Mac OS* X: /opt/intel/flexlm/
On Windows*: C:\Program Files\Common Files\Intel\FLEXlm

8. If you have specified three redundant license host server systems in your floating licenses, at least two of the three redundant license host servers must be up and running at all times. Click here for more information.

9. Install your Intel® FLEXlm* license server binary on your license host server system. If you have specified three redundant license host server systems in your floating licenses, complete all three license host server installations. Follow the instructions in Chapter 3 of the Intel FLEXlm* License Manager user guide.

10. Start your license host server process by following the instructions in Chapter 3 of the Intel FLEXlm* License Manager user guide. If you are using a Vista or Windows Server 2008 system, please see the information at this link.

11. Ensure your license server is running by following the instructions in the user guide for the << lmstat >> command. Click here for more information.


Steps to complete ON THE CLIENT SYSTEMS

12. On each client system, install the Intel software product(s) your users will be running from that client system. You will likely need a copy of the floating .lic license file on the client system for each product you will be installing; please put the copy of the Intel product floating license file(s) in the default Intel license file directory, and make sure you are using the same license file on the client system as you are using on the license host server system(s).

There is a different default Intel license file directory on Windows*, Linux* and Mac OS* X.

Windows*:   C:\Program Files\Common Files\Intel\Licenses

Linux*:   /opt/intel/licenses/

Mac OS* X:  /Users/Shared/Library/Application Support/Intel/Licenses/


13. Set the INTEL_LICENSE_FILE environment variable on each client system. Click here for more information.

14. Try launching the Intel product, such as the Intel® C++ Compiler product.

15. If problems occur with floating license seat check-out, or with any of these steps, please follow the steps in Chapter 5 of the user guide to capture a debug log for your license host server. 

Then submit a new issue to Intel® Premier Support and attach the debug log you generated.
If you do not have access to Premier Support, please post a new question on the user forum.

15. To help the Support team assist you efficiently with your problem, please provide the following information:

     a. OS and architecture for your license host server system(s)

     b. the name of the specific Intel FLEXlm license manager server file you downloaded and installed

     c. the serial number for the floating license you are using
[NOTE: DO NOT POST SERIAL NUMBERS IN USER FORUM COMMUNICATIONS UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     d. the environment variable setting for INTEL_LICENSE_FILE

     e. a copy of each floating license file you are using
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     f. the combined license file (only if customer is using a combined license file)
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     g. host server name and host server id for the license host server(s)

      h. verification that Intel License manager is running (capture of the results of running the appropriate lmstat command)
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]

     i. license server debug log and client-side debug log
[NOTE: DO NOT ATTACH FILES TO A USER FORUM POSTING UNTIL OUR SUPPORT TEAM HAS CHANGED YOUR POSTING TO PRIVATE STATUS.]



]]> http://software.intel.com/en-us/articles/checklist-for-installation-and-troubleshooting-intel-flexlm-license-manager/ Mon, 16 Aug 2010 00:00:00 -0700 http://software.intel.com/en-us/articles/checklist-for-installation-and-troubleshooting-intel-flexlm-license-manager/#comments http://software.intel.com/en-us/articles/checklist-for-installation-and-troubleshooting-intel-flexlm-license-manager/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® License Manager for FLEXlm* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel® FLEXlm* License Borrowing Capability Overview

This feature allows users to ‘borrow” a license seat from the license host server for a limited time, disconnect from the network and use the borrowed license even with no connection to the license server. This is very useful in case you want to use the software offline.

Required Information

To use the license borrow functionality for Intel floating product licenses, customers need to ensure they have the following items:

1) A build of the Intel® License Manager for FLEXlm* (for the desired OS) that supports the Borrow capability:

a) Users need to make sure that they are using a build of Intel FLEXlm* License Manager which supports borrowing
and early return of borrowed licenses.

b) We recommend the customer download and install one of the free license manager servers available at the
following website link:
http://software.intel.com/en-us/articles/performance-tools-for-software-developers-intel-flexlm-license-servers/

2) A license file which has the keyword BORROW in it: 

a) Licenses for Intel® Software Development Products with version 2011 have the BORROW feature with a BOROW period of 7 days enabled by default.  

b) To obtain a borrow-enabled license for a multi-seat floating product license with a version older than 2011, please   submit an issue to Intel® Premier Support at https://premier.intel.com/ under product 'Download, Licensing and Registartion'.
     

Steps for starting the FLEXlm* License Manager (Server) for using the Borrow feature

(1) Start the license server using the new borrow-enabled license file(s).

(2) Check the log for the Intel® FLEXlm* License Server and make sure that it does not complain about BORROW keyword in the license file.

     • By default, the log file location on Windows* is: %ProgramFiles%\Common Files\Intel\FLEXlm
     • By default, the log file location on Linux* and Mac OS* X is the same where FLEXlm server has been installed

     A typical log file when FLEXlm Server has started successfully looks like the following:

     14:00:31 (lmgrd) US Patents 5,390,297 and 5,671,412.
     14:00:31 (lmgrd) World Wide Web: http://www.macrovision.com
     14:00:31 (lmgrd) License file(s): server.lic
     14:00:31 (lmgrd) lmgrd tcp-port 28518
     14:00:31 (lmgrd) Starting vendor daemons ...
     14:00:31 (lmgrd) Started INTEL (internet tcp_port 35860 pid 9309)
     14:00:31 (INTEL) FLEXlm version 9.23
     14:00:31 (INTEL) Server started on LicenseServer for:
     14:00:31 (INTEL) I3F97C15E (consisting of:   ArBBL
     14:00:31 (INTEL) CCompL    DbgL    FCompL
     14:00:31 (INTEL) MKernL    PerfAnl    PerfPrimL
     14:00:31 (INTEL) StaticAnlL    ThreadAnlGui    ThreadBB)


Client System Setup for the Borrow feature (Application Setup)

NOTE: The term “Client” refers to the application that uses Intel FLEXlm floating license seat check-out and check-in.

1) Download the lmutil for your operating system and architecture from http://www.globes.com/support/fnp_utilities_download.htm.

2) If you are not able to download the lmutil from the website above, work with your Intel Support team contact (or submit an issue to Premier Support at https://premier.intel.com/) for access to lmutil, and have the information about your Operating System, OS Version and Architecture (IA-32, Intel® 64 and/or IA-64[Intel® Itanium®]).

3) Verify that no Intel product components’ license seats (i.e., Compiler Professional Edition, Vtune, etc.) can be borrowed by running the following command. If you see any information that indicates one or more features/components were borrowed, then borrowing has already been enabled for those licensed features/components. Here is an example of output when no borrowing is enabled.

lmutil lmborrow -status

Example:
lmutil lmborrow -status
lmutil - Copyright (c) 1989-2009 by Macrovision Corporation. All rights reserved.


4) Configure the borrow duration and FLEXlm feature to be borrowed:

lmutil lmborrow INTEL dd-mmm-yyyy:[time] <featurename> -c <serverlicense file>

Example:
lmutil lmborrow INTEL 06-Oct-2011 CCompL -c server.lic

where,
server.lic is the license file which was used to start the server. It should be noted that license borrowing will fail if the license file on the client side is different than the one which was used to start the server.

The command above borrows a “featurename” called CCompL (Intel® C++ Compiler for Linux*) from the vendor INTEL until 6th Oct 2011 using the license file server.lic

NOTE:  The time specified on command line of lmborrow is the end date/time the user planed to borrow, which must be <= 168 hours, which is the maximum borrow period. If the user wants to borrow the license seat for only 1 or 2 days, the corresponding date/time for that period should be set.
Users cannot borrow a license seat for more than the 168 hour barrier that is set in the license file and in the license server logic. If an extended borrow time is required, please submit an issue to Intel® Premier Support at https://premier.intel.com/ under product 'Download, Licensing and Registartion' providing a jsutification of why you need to extend the borrow time beyond 7 days.

After running this command, the customer should see the following:

lmutil - Copyright (c) 1989-2004 by Macrovision Corporation. All rights reserved.
Setting LM_BORROW=3-oct-2011:INTEL:06-oct-2011:CCompL


5) If the above steps are successful, you are now ready to borrow a seat by running the client application (e.g. – Composer XE, Vtune Amplifier XE, Inspector XE, etc). The FLEXlm feature will be borrowed when you run the client/application and a successful check-out happens. As soon as the first license is checked out, the server log file will confirm the borrowed feature with the following message in the log file:

14:35:14 (INTEL) OUT: "I3F97C15E" User1@Host1
14:35:14 (INTEL) OUT: "CCompL" User1@Host1

Note that there are no corresponding IN entries in the server log. This is different behavior than a normal check-out where corresponding to every two OUT entries in the server log file, you will also see two IN entries after the OUT entries after the application exits.


6) Verify that the FLEXlm product feature was really borrowed by running the following command on the client system:

lmutil lmborrow –status

Example for borrowing a seat for the Intel C++ Compiler for Linux*:

lmutil lmborrow –status
lmutil - Copyright (c) 1989-2004 by Macrovision Corporation. All rights reserved.

Vendor Feature Expiration
______ ________ __________

INTEL CCompL 6-Oct-11 23:59

NOTE: Before the Borrow period expires, the product will always get the license from the local storage for the Borrowed license seat when it tries to check-out license. The Client system on which the product is used does not need to be attached to FLEXlm* license host server.


7) Disconnect the client system from the server network. Now with the borrowed license, you can use the software application with the borrowed license.

NOTE: After the Borrow period expires, the product license seat will no longer to be able to check-out the license from local storage. Instead, the client system must be “attached” to the FLEXlm* license host server to check-out a product license seat.


8) Run the following command to return a borrowed license:

lmutil lmborrow -return -c server.lic featurename

Example:
lmutil lmborrow -return -c server.lic CCompL
lmutil - Copyright (c) 1989-2009 by Macrovision Corporation. All rights reserved.

On the FLEXlm server side, you will see the following message in the log file for the borrowed feature which was returned. This message is different compared to a normal check-in.

14:40:17 (INTEL) REMOVING User1@Host1:/dev/pts/0 from CCompL by administrator request.

14:40:17 (INTEL) IN: "CCompL" User1@Host1 (USER_REMOVED)
14:40:17 (INTEL) IN: "I3F97C15E" User1@Host1 (USER_REMOVED)


9) Run the following command to verify that the license was returned successfully back to the server:

lmutil lmborrow -status

Example:
./lmutil lmborrow -status
lmutil - Copyright (c) 1989-2009 by Macrovision Corporation. All rights reserved.

Note: If you try to return a license which has not been borrowed, you will see a message like this:

./lmutil lmborrow -return -c server.lic CCompL
lmutil - Copyright (c) 1989-2009 by Macrovision Corporation. All rights reserved.
Error: CCompL not currently borrowed.


]]> http://software.intel.com/en-us/articles/intel-flexlm-license-borrowing-capability/ Fri, 06 Aug 2010 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-flexlm-license-borrowing-capability/#comments http://software.intel.com/en-us/articles/intel-flexlm-license-borrowing-capability/ Intel® TBB Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Integrated Performance Primitives Knowledge Base Intel® License Manager for FLEXlm* Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Threading Building Blocks Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel® VTune™ Performance Analyzer for Linux* Knowledge Base Intel® VTune™ Performance Analyzer for Windows* Knowledge Base Intel® License Manager for FLEXlm* Servers

Intel® License Manager for FLEXlm* servers are available from Intel® Registration Center Download Center.

Remember that the OS of the server system where the Intel License Manager for FLEXlm is installed does not have to match the OS for the license(s) it supports. So the Intel license manager for FLEXlm can be installed on either Windows, Linux, or Mac machines regardless of the OS for each of your floating and nodelocked Intel software product licenses.

For customers with a current "counted" product license, Intel® License Manager for FLEXlm* servers are available from the Intel® Registration Center Download Center. After logging into the Intel® Registration Center, select "Product Download". Select "FLEXlm servers" from the Product list, then search through the list of files to download the Intel® License Manager for FLEXlm* driver for your particular operating system environment.

You can also use this direct link: https://registrationcenter.intel.com/RegCenter/Download.aspx?productid=633
]]> http://software.intel.com/en-us/articles/performance-tools-for-software-developers-intel-flexlm-license-servers/ Mon, 19 Jul 2010 22:00:00 -0700 http://software.intel.com/en-us/articles/performance-tools-for-software-developers-intel-flexlm-license-servers/#comments http://software.intel.com/en-us/articles/performance-tools-for-software-developers-intel-flexlm-license-servers/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® License Manager for FLEXlm* Knowledge Base Intel® Thread Checker for Linux* Knowledge Base Intel® Thread Checker for Windows* Knowledge Base Intel® Thread Profiler for Windows* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel® VTune™ Performance Analyzer for Linux* Knowledge Base Intel® VTune™ Performance Analyzer for Windows* Knowledge Base Redistributable libraries for Intel C++ and Visual Fortran Composer XE for Windows Overview

This article contains links to the redistributable library packages and merge modules for the Intel C++ Composer XE for Windows* and Intel Visual Fortran Composer XE for Windows.

The redistributable library packages (.msi) are for the end users who use applications that are built with Intel Compilers. Please note that there is one redistributable package for every compiler update. Make sure you download and install the one recommended by the application vendor.

The redistributable merge module (.msm) is intended to be used by the application installation engineers to merge the redistributable into the application's installation.

OS and prerequisite library requirements for redistributable packages for Intel® C++ Composer XE and Intel® Visual Fortran Composer XE for Windows

The supported OS are: Windows XP*, Vista*, Windows 7*, Windows Server 2003*, Windows Server 2008*, Windows HPC Server 2008*.

In addition to a supported OS and Intel redistributable libraries, the target system must have either Microsoft Visual Studio with Visual C++ libraries installed OR the Microsoft Visual C++ redistibutable library kit installed.  In addition, the target system must have the same version of Microsoft Visual C++ libraries installed at the same version ( 2005, 2008, 2010 etc ) as the version of VC++ used on the development platform when the Intel compiled application was built.  Visit the Microsoft website or search the web for "Microsoft Visual C++ Redistributable Package" and find the appropriate version to match your development system.

The Microsoft Visual C++ redistibutable libraries OR Visual Studio with the C++ tools (libraries) may be installed before or after the Intel compiler redistributable libraries.


Installation instructions

The installation program of the redistributable package will guide you through the installation. You will need to accept the EULA and the installation will install all the libraries to the fixed directory.

The installation directory is: [Common Files]\Intel\Shared Libraries\redist\[ia32|intel64]\compiler

The installation will add the above directory to your environment variable "path" as well.

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 like:
>> w_ccompxe_redist_ia32_2011.0.104.msi /S /V/qn

 

Testing your Installation:

After installation of the Intel redistibutable libraries AND the prerequisite Microsoft Visual C++ redistributables or Visual Studio with C++ tools and libraries, try to run your Intel-compiled binary.  If there are any issues, please try to determine the missing DLLs or libraries using a tool such as Dependency Walker.  If you are still having issues, please consult the Intel User Forums:

C++:  http://software.intel.com/en-us/forums/intel-c-compiler/

Fortran:  http://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/


Links to the redistributable packages

Note:

 

  • The redistributable library package: this is intended for end users. It contains two .msi installation files: one .msi is for IA-32 applications; one .msi is for Intel® 64 architecture applications.
  • The redistributable merge module: this is intended for developers who create the application installation program. It contains two .msm installation merge files:  one .msm is for the installation program of an IA-32 application. another .msm is for the installation program of an Intel 64 architecture application.
  • The redistributable packages contain the redistributable files from Intel C++ Compiler and Intel Visual Fortran Compiler only. The Intel® Performance Primitives (Intel® IPP), Intel® Math Kernel Library (Intel® MKL) or Intel® Threading Building Blocks (Intel® TBB) redistributable files are not included.

Intel C++ Composer XE for Windows Intel Visual Fortran Composer XE for Windows
RTM

• Redistributable library package
• Redistributable merge module

 RTM

• Redistributable library package
• Redistributable merge module
Update 1

• Redistributable library package
• Redistributable merge module

 Update 1

• Redistributable library package
• Redistributable merge module
Update 2

• Redistributable library package
• Redistributable merge module

 Update 2

• Redistributable library package
• Redistributable merge module
Update 3

• Redistributable library package
• Redistributable merge module

 Update 3

• Redistributable library package
• Redistributable merge module
Update 4

• Redistributable library package
• Redistributable merge module

 Update 4

• Redistributable library package
• Redistributable merge module
Update 5

• Redistributable library package
• Redistributable merge module

 Update 5

• Redistributable library package
• Redistributable merge module
Update 6

• Redistributable library package
• Redistributable merge module: please use the *.msm installed under
[install-dir]\redist\ia32\compiler
[install-dir]\redist\intel64\compiler
directory.

 Update 6

• Redistributable library package
• Redistributable merge module: please use the *.msm installed under
[install-dir]\redist\ia32\compiler
[install-dir]\redist\intel64\compiler
directory.
Update 7

• Redistributable library package
• Redistributable merge module: please use the *.msm installed under
[install-dir]\redist\ia32\compiler
[install-dir]\redist\intel64\compiler
directory.

 Update 7

• Redistributable library package
• Redistributable merge module: please use the *.msm installed under
[install-dir]\redist\ia32\compiler
[install-dir]\redist\intel64\compiler
directory.
Update 8

• Redistributable library package
• Redistributable merge module: please use the *.msm installed under
[install-dir]\redist\ia32\compiler
[install-dir]\redist\intel64\compiler
directory.

 Update 8

• Redistributable library package
• Redistributable merge module: please use the *.msm installed under
[install-dir]\redist\ia32\compiler
[install-dir]\redist\intel64\compiler
directory.



References

 

]]> http://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-visual-fortran-composer-xe-for-windows/ Tue, 06 Jul 2010 23:00:00 -0700 http://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-visual-fortran-composer-xe-for-windows/#comments http://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-visual-fortran-composer-xe-for-windows/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base