Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Determining if the Intel Fortran Redistributables are already installed

Tim_R_
Beginner
‎09-07-2017 01:48 AM
970 Views

Hello,

we are distributing software built with the Intel Fortran 2017 Compiler, Update 4.

As we use dynamic runtimes, we have to install the redistributables on the user's PC, which are found here: https://software.intel.com/en-us/articles/redistributables-for-intel-parallel-studio-xe-2017-composer-edition-for-windows

  1. For a silent install, I found that the switches "/quiet /qn" as specified in the provided link do not really work - we are now using "/quiet /passive /norestart". Are those "correct"?
  2. Is there any possibility to determine whether the redistributables are already installed beforehand? Like some registry value, existence of a specific DLL, ...? Or should I always just start the installer?

Thank you,

Tim

0 Kudos

Link Copied

1 Reply
Tim_R_
Beginner
‎09-08-2017 12:22 AM
970 Views

When automatically installing the Fortran Redistributables on a user's PC, I get an error code 1603: the specified account already exists.

I attached the log, which I produced with the /log log.txt switch.

The Redistributables are already installed on the PC - maybe this is the problem?

Thanks,

Tim

Preview file
25 KB
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.