parallel Studio 2016 XE installations in windows 10

[dajum]

Hi,

We are having some issues with installing this on a windows 10 machine, and have tried it several ways and most of them seem to fail when trying to run the fortran compiler.

questions

1.  Should the installer be able to run if only the windows 8.1 SDK is installed and no version of Visual Studio is installed?

2.  if the message in the attached file appears - what process needs to be followed to correct the installation?

3. We didn't find any shortcuts or listing for the compiler and the command prompt development windows being installed like on previous versions of parallel studio.  SHould they be there? and can you post pictures of what they should look like?

Thanks,

Dave

[TimP]

You would need VS2012 pro,or 2013 or 2015 community to install some of the full Parallel Studio components.  Fortran ought to install by selecting Visual Studio Shell, if you follow the instruction to install that separately first (this changed from previous Parallel Studio versions).  All of them install for me on Win10 with VS2012 and 2013, but Advisor doesn't work either inside or outside VS on Win10.

There was a hint on another forum that Intel planned to complete some testing and more complete support of Win10 over the next 6 months.

The part of the message about visual studio express doesn't look right.  Rather than installing Express, you should install VS2013 or 2015 (Community, if you qualify) (the latter being very time consuming).

[dajum]

Parallel Studio XE 2016 is supposed to come with Visual Studio Shell 2013 according to the notes, but it doesn't seem to get installed.  We only want the Fortran compiler to work for most installations.  I found this as a source for what 2016 has:

https://software.intel.com/sites/default/files/managed/0b/32/PSXE2016_Release_Notes_en_US_Lin_Win.pdf

But the system requirements section is pretty sparse.  Notes on how to install are also pretty spare.  Most of our users who install this have very little idea what any particular part of it does, or what the requirements are.  They don't need VS standalone so an integrated component is good for them.  But the message I included with my original post seems pretty specific that VS is NOT required iv the SDK is installed.  And that is hard to figure out from the system requirements listed.

[TimP]

You posted the instructions on how to install VS Shell, now try them out.  It's not included in the Intel installer you downloaded. Right in the reference you gave, it says VS2013 Shell support "is provided" but doesn't say it comes automatically (as it used to do).

[Kevin_D_Intel]

Visual Studio 2013 Shell is included in the Parallel Studio 2016 download packages. The PSXE 2016 installation checks for the presence of the required Windows 8.1 SDK and warns when that is missing, or other supported Visual Studio version alternatives are also missing as was shown in the image in the original post.

The noted Windows 8.1 SDK only needs to be installed to proceed with the PSXE 2016 installation. The VS 2013 Shell installation is completed as part of the Parallel Studio 2016 installation when the SDK is present and no other Visual Studio is detected.

If you are meeting that minimum SDK requirement and not seeing VS 2013 Shell being installed then I'd like to send you a private reply to obtain some installation logs from your system to help the installation engineers analyze what might be going wrong.

[Kevin_D_Intel]

To close on this issue. The underlying issue related to using an evaluation license and the installer failing to clearly indicate the VS 2013 Shell would not be installed given that license. Instead, for this scenario, the installer issued information about installing the Windows 8.1 SDK needed for the VS 2013 Shell and then silently did not install the shell. New install checks and messaging will be added in PSXE 2016 Update 1 to avoid this situation and clearly indicate the shell will not install with the evaluation license.

Thank you Dave for providing the logs that helped us understand this issue.